yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I dirty reflashed jfltespr official CM nightly after patching with DualBootPatcherAndroid-8.0.0.r1275.ge240bf3-snapshot.apk to slot-1 to try and get stock kernel. Everything worked as expected, but reboot never got past the android boot animation. Did logs.zip and logs are posted. I flashed alucard kernel and it booted fine.

I want to run stock kernel. I patched my nightly with same patcher. I patched hulk kernel zip (because it has fewer mods). Both to slot-1. I copied boot.img from nightly patched to hulk patched and rezipped. When I flashed, I got an error. Recovery log attached. Where am I going wrong in trying to get a stock kernel zip?
[Galaxy S 4 i9505 Original Android Development] gaww:
Multi 1. Able95LL3.1 Hybidmax kernel TWLPv3.5

Patched Primary CardHD33.2 (tmo based4.4.4 for WiFi calling) kernel AEL v6.3 modded.

Shared apps:

Amazon

Aquamail

Battery monitor widget

Currency

Drop box

Earth

Earth HD free

ES file explorer

Flight aware

Greenify

Maps

Mega v1

OfficeSuite

QuickPic

SmartBench

Speed test

Like other posters, when sharing implemented, data often wiped (greenify,battery monitor, etc.).
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
I flashed Alliance V2 and was able to boot back into it. I enabled per app sgaring and shared some apks and some data. When i start up alliance i had the same theme i had on my primary. Also all apks were shared. Then i switched back to primary and it reverted my data lol.
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
I would like to know if is possible to install a rom to a external sd card or is to hard to do?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the log, very useful! The issue is right here:

05-18 09:04:57.840 E/libmbp (14778): Device tree image exceeds boot image size

The dt_size field in the kernel is bigger than the kernel's file size. Could you send me the boot.img from /sdcard/MultiBoot/ so I can take a look at why that might happen? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Merged! Thank you! ;)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1277.g4862b4d :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Is the Alucard kernel not working too? That zip already has complete boot.img, but unpacks and repacks it during install. This should already be supported because a boot.img exists.

The KT zip had everything split out (separate file for device tree, kernel, ramdisk, etc.).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, I might have to flash the build myself to see why that might happen. I'm not seeing anything suspicious in the logs.

What you did was exactly right. However, it looks like the recovery couldn't read the modified zip. Maybe try using another program to edit the zip?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I pushed some changes late last night (or early morning lol) that fix some more bugs that might cause apps or their data to disappear.
[Galaxy S 4 i9505 Original Android Development] gaww:
Update - already sent them. I stopped app sharing to see what would happen. All the apps and original date are back on the Multi 1, but free space hardly changed (maybe 1mb), so sharing did not save any space, whereas the old method with similar TW ROMs saved well over 1gb.

Would app sharing only maybe get past this? Also, is it possible by only doing ramdisk update on one ROM and flashing freesly patched kernel on the other that some necessary file structures were not created?

To other users of new app/data sharing - did any of you take a before and after look at the free space in the internal SD ?
[Galaxy S 4 i9505 Original Android Development] ESTIMULO:
Sure, here you have it.

I hope it help you to find the problem

Thanks
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you! I did some searching around and it looks like that kernel is Fulgor kernel: http://xdaforums.com/galaxy-note-3/orig-development/kernel-fulgor-kernel-v1-0-t3087348.

Unfortunately, that kernel is 12MB and the Note 3's boot partition is only 11MB. It's a lucky coincidence that it boots at all. When you hit the update ramdisk button, it can only read that incomplete 11MB on the partition, which is why it fails every time.

If there's another custom kernel you could use, I'd recommend trying that.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I was finally able to reproduce this and I may have found something that would cause this to happen. This is a relatively large fix that might take me a few hours to implement. I'll keep you posted :)

There shouldn't be any difference regarding freshly patched vs. ramdisk update because all the file structures are created on boot. If you look at the top of /sdcard/MultiBoot/appsync.log and it shows the correct ROM, then the appsync service is running properly and the issues are probably bugs in my implementation.

eg.

[I] === APPSYNC VERSION 8.99.7 ===
[I] Calling restorecon on /data/media/obb
[D] Running command: [ restorecon, -R, -F, /data/media/obb ]
[D] Looking for named ROMs in /data/multiboot
[D] [Config] ROM ID: primary
[D] [Config] ROM Name: TouchWiz 5.0
[D] [Config] Global app sharing: false
[D] [Config] Global app sharing (paid): false
[D] [Config] Individual app sharing: true
[Galaxy S 4 i9505 Original Android Development] gaww:
That would be great - would like to return to a few gb available space in the SD.

Question - does moving apps to SD impact this? I had to move quite a few of the larger ones just to have at least the minimum needed to run of 500 mb.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Moving apps to the SD does impact apk sharing (not data though). It will see that the app isn't in /data/app and should just skip over it. There isn't too much I can do about that. Those apps are stored in encrypted containers which are mounted much later in the boot process.

EDIT: I have absolutely no idea if this works or not, but there's a chance two TouchWiz ROMs could use the same apps on the SD if you copy /data/misc/systemkeys/AppsOnSD.sks from one ROM to the other. I believe that's where the encryption key is stored.
[Galaxy S 4 i9505 Original Android Development] ESTIMULO:
It Works perfect now with stock kernel. Sharing data for what's app, telegram, bbm , etc. between TW, CM12 and Miui

Thanks thanks thanks
[Galaxy S 4 i9505 Original Android Development] gaww:
In using the app to SD process it appears the whole thing is not moved and was hoping that would allow it to be shared.

Next time I will only experiment with a few large apps and moniter the impact on free space. Will also give your suggestion above a try.

In duplicating the situation did anything else come out?
[Galaxy S 4 i9505 Original Android Development] Technical:
Just to report.

A lot of issues while trying to share app and data from primary to other ROMs.

Rebooting in primary, a lot of apps were gone, other crash without possibility to enter the start page: messages, pushbullet, avast mobile security and some others make impossible to use the ROM.

I've restoring a nandroid.

Edit: mess! Everything FC. All the app were instable after a nandroid restore. Trying to factory restore and then restore a nandroid.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Maybe my configuration is more simple then others but apps and data sharing is working!! Chen, you did the magic!!!

I have two roms and I'm sharing now Facebook, Whatsapp, Firefox and others....
[Galaxy S 4 i9505 Original Android Development] haoyangw:
[MENTION=4277844]chenxiaolong[/MENTION]

Honestly I haven't tried it before, it is my primary kernel so I just flash the zip as is when I wanna get back to primary without patching. Couldn't try out app sharing because it bootloops at bootanimation for me when ramdisk gets patched.
[Galaxy S 4 i9505 Original Android Development] gaww:
Mine worked also - but did you verify that you saved significant space - which is what this originally was all about ?
[Galaxy S 4 i9505 Original Android Development] rlorange:
Hmm I'm not getting individual app sharing to work.

---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------

5.01 tw primary cmremix 5.1.1 on dual
[Galaxy S 4 i9505 Original Android Development] carandcar:
I'm running the same set up on my note 4 as well and no success yet. I flashed the tmo stock kernel to see if that made a difference but it didn't.
[Galaxy S 4 i9505 Original Android Development] Technical:
Man, I nightmare... :crying:

After sharing app+data of most apps, a nandroid restore couldn't solve the issues as the data is linked in every boot.

Tried wiping system, caches, data. Tried factory reset twice. Used Boot utilities 4.0 to wipe both secondary and primary...

Tested 3 nandroids...

Installation from scratch did the same: app FCs, no homescreen, etc.

The "only" solution was wiping all + sdcard.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Well, this is correct. I can confirm that the app and data are shared, in example on primary I have a Trip advisor version from Samsung which now appears also on Multi-slot 1 rom or if I create a file with WPS office the same file is also visible on the recent file opening the other rom, etc.

But you are right, the space is not reduced and if the patcher create a simlink between the apps apparently some data is still present on both roms. As I understood it should be deleted.

But right now the data sharing is a big step forward!
[Galaxy S 4 i9505 Original Android Development] rlorange:
Hard links can be a headache since its effectively a file with the same exact identity according to Linux existing in multiple places
[Galaxy S 4 i9505 Original Android Development] rlorange:
Just remember if an keeps hardlinking to a ROM unwanted just go to data or raw/data /multiboot/_appssharing and delete the offending app that is the source of the hard link I believe
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What [MENTION=3145598]rlorange[/MENTION] mentioned is correct and if you want to completely remove all the app sharing settings, just delete config.json in /sdcard/MultiBoot/.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=3019752]gaww[/MENTION]: Is this more along the lines of what you're expecting? /data went from 0.91GB free to 1.6GB free. This is with the new code (hasn't been pushed yet).

EDIT: I should note that the apps are shared in TouchWiz 5.0 and CM 12.1.

Before:

After:

I've shared the APKs for the following apps (granted, none of them are really large apps)

AdAway

AirDroid

Analytics

Authy

Banking Card Reader

Barcode Scanner

BusyBox Free

CamScanner

CamScanner Full Version

Chrome Dev

Client Cerberus

DiskUsage

DriveDroid

Drives

ES File Explorer

F-Droid

Family Guy

Firefox

GasBuddy

Google Cantonese Input

Google Opinion Rewards

Google Pinyin Input

JuiceSSH

LIMBO

MEGA

Microsoft Account

MX Player

Newegg

Nova Launcher

Panda Pop

SDFix

Skype

Speedtest

Superbeam

Titanium Backup

Todoist

TV Guide

TWC TV

Viral lite

VLC

Wallet

WeChat
[Galaxy S 4 i9505 Original Android Development] -MaD-:
My Note 4F is really happy about this Dualboot possibility and everything was fine until I tried to flash a kernelupdate to my primary rom. After that I could not boot into it.

Due the lack of aroma I could only get to my second rom via reflashing the patched second rom + gapps. I tried to patch the kernel again, flashed it again but same result.

I think I will wipe everything- also because my 1st rom was a little bit outdated ;) and also for the second rom is a new version available.

But: I want to know what went wrong. Is there any logfile I could attach?

Thanks for the great work - till now I was only a really happy reader of this thread. Good work!

edit: my roms are emotion tw rom and aicp by the same team.
[Galaxy S 4 i9505 Original Android Development] gaww:
That would be it - similar to the earlier case where I shared between 4 Roms. Was the above global or individual?

Also would apps in SD not work - ie. would have to move them back first ?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Welcome to the thread! :) The details are logged in /sdcard/multiboot.log whenever the flashing fails. Starting from a few releases ago, AROMA is no longer used. You choose primary, secondary, etc. when you patch the file (so the repatcher app is no longer needed).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great! This was with individual app sharing. (I went into the app and ticked "share APK" for the apps I listed).

EDIT: I'll probably push the code later tonight after I spend a bit more time testing it.
[Galaxy S 4 i9505 Original Android Development] Sephy01:
Hi everyone ! I searched informations about my question in the thread but I'm still a bit confused; I'd like to have as primary rom the TW (I use Albe95's) and as secondary rom the Antares CM12.1 that uses F2FS so F2FS is supported ? If it is , flashing the secondary Rom in cache partition will effect the performance of both Roms ?

Thanks in advance :)
[Galaxy S 4 i9505 Original Android Development] haoyangw:
Yep F2FS is supported, I'm using that too you just need a kernel that supports F2FS, [MENTION=4277844]chenxiaolong[/MENTION]'s Dualboot Patcher doesn't care about what filesystem you are using. And nope, performance will not be affected because /data, /cache and /system are all internal NAND flash drives that are equally fast :)
[Galaxy S 4 i9505 Original Android Development] todivefor:
I just tried flashing over my primary and it failed on space on system. Is there someway to tell before flashing if you will have enough space?
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes.

First if you have a secondary see how much room is left in system.

Then unzip the rom and see how big it is (some unzip programs will tell you that without having to unzip).

Then allow some free space (I have had as little as 30mb) and see it it will fit.

Without a secondary most tw's should fit.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
In case anyone is wondering, this would be a difficult thing to automatically detect. Let's say you flash a 200MB Gapps package. If you don't already have gapps installed, this would take up 200+ MB of space. But if you already have gapps installed, the update might only use a few MB of extra space. The patcher would have no way of knowing which case it is.
[Galaxy S 4 i9505 Original Android Development] Sephy01:
Thank you ! some more questions : when i flash the second rom do i have to do the procedure in point two of dual booting also for the second rom ( Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.) ? And one more thing : for example I share angry birds from TW ROM and I use it also on CM , if I wipe TW ROM beacause I want to change it will I lost angry birds and its data or not ?
[Galaxy S 4 i9505 Original Android Development] haoyangw:
1. Yep remember to set kernel just in case, optional but HIGHLY recommended :)

2. Yes, it will be lost, at least to my knowledge :( So do backup!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] How hard is porting this to a new device??
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] http://xdaforums.com/xposed/guide-xposed-framework-samsung-lollipop-t3113143

Xposed For Touchiz Guide
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

Wouldn't it be a good idea to rename this project i.e. to "MultiBootPatcher"? "DualBoot" isn't really appropriate (anymore), what do you think?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] I have found out with app sharing from primary enabled even with 1 app it gets rid of google apps and account and stuff in data spot
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry guys, didn't get a chance to work on anything today. Don't know if it's my allergies or if I have a cold, but I've been sneezing like crazy and my nose is running like a faucet lol
[Galaxy S 4 i9505 Original Android Development] rlorange:
Oh man allergy most likely here in Melbourne Australia we get most allergenic air in the world apparently. Argh hate it
[Galaxy S 4 i9505 Original Android Development] haoyangw:
Oh no get well soon [MENTION=4277844]chenxiaolong[/MENTION]! Do take care of your health and don't work too hard ;)

---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------

[MENTION=4277844]chenxiaolong[/MENTION] Sorry for disturbing you when you are sick, unfortunately when I update ramdisk on CM11 latest nightly with Alucard kernel 1.4r for AOSP V2 and reboot my Galaxy S4 gets stuck at bootanimation :( Do you have any idea why? Couldn't try out the new app sharing which I am so eagerly anticipating to try out lol XD
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Is there any way to share all the apps installed on the primary ROM and their data also, as far as I see the share all apps option does not share data too?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Get well soon
[Galaxy S 4 i9505 Original Android Development] royredman:
Sorry to be the guy (one of many) that asks this question, but does this dual boot option work on the Verizon Lg g3?
[Galaxy S 4 i9505 Original Android Development] jurington:
Yes it does

Sent from my VS985 4G
[Galaxy S 4 i9505 Original Android Development] monkteo:
[MENTION=4277844]chenxiaolong[/MENTION]

hi , sorry to bother you but I want to buy an Note 4 (N910F variant) I notes that you also have a Note 4 so , my version will work with dualboot ?

(I look for a list of working phone but..................)

Right now I have an S4 and it's working perfect (TW primary with MIUI in multislot1)

THX
[Galaxy S 4 i9505 Original Android Development] sronweb:
note 4 should be working on both variants. just check opening the patcher, select the option to patch a file and you will choose for Note 4 exynos or snapdragon version. This is the list of phones....[emoji1]
[Galaxy S 4 i9505 Original Android Development] Technical:
Tested Slim 5.1.1 (optimized with Alucard kernel) and fails to boot in Multi-slot1

Tested it also flashing the kernel and with/without Xposed.

Patched in PC with the latest version of the patcher.

Does it make difference from patching within the phone?

Does it make any difference on choosing the ROM/Kernel/Gapps/Su... version while patching or letting everything on "Customized" will work?

The opposite, Slim on primary and CM 12.1 in multislot1 worked.

---------- Post added at 22:34 ---------- Previous post was at 22:12 ----------

Flashing with the internal app patcher worked :p
[Galaxy S 4 i9505 Original Android Development] gaww:
If you had read some more or actually tried the latest version, you would have seen that data sharing is done - which was the major update from earlier versions.

The problem now is that this new sharing process did not result in space saving of the apps shared (unlike before), but chenxiaolong seems to be very close to resolving that. He just has to get better to finish it - lol.
[Galaxy S 4 i9505 Original Android Development] Ranomez:
Before assuming that I didn't read please at least read my comment carefully, I said I want to share ALL apps AND their DATA. I did actually read every single page since I started (trying) to use this app (when it was not yet working on Exinos devices) and I am on the latest version and I know that you can individually share apps with data but that's not really a good solution for me as I have 400+ apps installed so I would have to re-install each app in the 2nd ROM and then individually share in both ROM's and that would take me ages to do, the share all apps option does not share the data too but I did find a "solution": I restored all the data for all the user apps using Titanium Backup but still it would be great if you could share all apps and their data across ROM's, is that planned or even possible?
[Galaxy S 4 i9505 Original Android Development] Technical:
The developer always take this option into consideration. But it's not simple due to differences on how ROMs manage the app data.

Even restoring with Titanium (or Helium) there is a no zero possibility of getting UUID error when registering to Google Account.
[Galaxy S 4 i9505 Original Android Development] sronweb:
I agree. Going for massive sharing might result in applications issues, especially between touchwiz and AOSP roms, or about paid applications and gapps. Personally I will be happy improving individual sharing option.
[Galaxy S 4 i9505 Original Android Development] gaww:
Sorry -but it appeared that you had not seen that data was shared at all.

As for these comments, early on with an alpha version (9.something), I was able to share all (but basic system apps) between 4.x andf 5.x ROMs, but there were issues with some gapps and some (not all) paid apps that caused enough issues that I had revert to not sharing in order to run these ROMs in duel boot.

A compromise might be to set it up to only share non-paid user apps and data globally, and then still be able to do individual sharing on top of it for other apps selectively.

Earlier sharing versions did not require the separate installation of the apps on both versions, which really streamlined the installation of new patched ROM's - really miss that procedure (is this still done with the "Share applications" option now without data sharing?).
[Galaxy S 4 i9505 Original Android Development] Ranomez:
If you share all apps from the primary ROM you don't have to re-install each app in both ROM's, that's why I was asking if it was possible to also share their data.
[Galaxy S 4 i9505 Original Android Development] haoyangw:
[MENTION=4277844]chenxiaolong[/MENTION]

I've found a typo/bug in your Dualboot Utilities 4.0 Snapshot 4, at line 170 of aroma-config when a user selects the 'Switch to' option for Secondary ROM, partconfigid(declared at line 129 of aroma-config) which is 'secondary' is supplied to multibootutils.sh, and multibootutils.sh uses that as the name of the folder for secondary's boot.img which means it takes the path to the boot.img of the secondary ROM to be '/data/media/0/MultiBoot/secondary/boot.img', but actually the path is '/data/media/0/MultiBoot/dual/boot.img'. This results in DualbootUtilities claiming that I haven't set the kernel for Secondary as it cannot find the boot.img for secondary because the path is invalid(does not exist). Could you fix this please? I think another seperate variable should be created for the folder name for secondary(which is 'dual'). Thanks!
[Galaxy S 4 i9505 Original Android Development] Technical:
Well, they're working, i.e., CM 12.1 with Alucard kernel and Slim 5.1.1 (optimized with "internal" Alucard kernel).

I'm sharing app without problems. Well, the only problem is the space.

I need to send the data (and cache) of the secondary ROM to the 2nd partition of the sdcard with Link2SD. Otherwise, no space for everything.

Remain two questions for me:

1. Are the libraries and dex files also shared with the apks or not? Because Link2SD give me 4 options: app, cache, libraries and internal data.

2. Are the external folders (and obb folders/files) also shared? Seems so, because I can't see a duplication in the internal sdcard.
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Just tried to install Alucards CM 12 5.1.1 as Primary and it keeps failing. Using latest Patcher.
[Galaxy S 4 i9505 Original Android Development] AmyClaraRose:
If you want cm 12 5.1.1 as primary just flash it normally like any other zip in twrp
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Yeah I've now done this. Was just trying to avoid it destroying my Dual in the process :cool:

Means everytime I update it I destroy my Dual :(