yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm... could you screenshot the path it shows right after you select the file? It may have to do with some of the recent file IO changes I made.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Builds 8.0.0.r1359.g340805a and newer will no longer touch system apps in any way.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Bah, the server migration didn't go as well as I planned. The builds are completing, but aren't uploaded to https://snapshots.noobdev.io. I'll fix it after work tomorrow.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Wiping's not unusual - I'm aware of that ;)

Currently using patcher 1212 and it doesn't show the TW AEL kernel in the presets list. Tried others, same problem.

Edit: just tried v1360, all the same...
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
[MENTION=4277844]chenxiaolong[/MENTION]

On LG G2 could you do the same for the bootloader aboot.img?

Reason is LG stock LP ROM needs Kitkat bootloader at minimum and AOSP Roms need JB Bootloader (I know it's a mess^^).

Partition name of aboot is mmcblk0p5
[Galaxy S 4 i9505 Original Android Development] Technical:
Thanks. I have tried this and the results were not (even close) satisfactory.

I have tried to share the apps in primary one by one with the other ROMs. But I can't do that. Not a single app appears to be shared.

Only the apps installed in the other ROMs appear as shareable, not the primary ones.

What I want is to share all apps and data in primary with the other ROMs.

Doing the short way, choosing to share globally, allowed me to share the apps (not the data).

Trying to share one by one did not allow me to share anything: neither the apps nor the data.
[Galaxy S 4 i9505 Original Android Development] gaww:
To do app data sharing, they had to actually be first installed on both ROMs. The result of that was initially little if any savings in space. In latest versions, I believe one of them is removed after data sharing is working so free space is created for that app.

Unfortunately, this has to be done individually with all shared apps (and they can't be on the SD). I will probably just stay with global app sharing only next time I upgrade my multiROM.
[Galaxy S 4 i9505 Original Android Development] Technical:
I've updated the patcher in both ROMs and could share apps one by one. Sorry, seems my first report was made by an old patcher.

But, what a mess! I've lot almost any shared app (more or less 100 apps disappeared from primary ROM).

I'm not sure now I'll reinstall them (TitaniumBackup disappeared also) or I will just restore a nandroid :silly:

By the way:

1. Why the patcher itself (the app) is shareable? When I've shared it, I've lost the updated RAM disk in the primary ROM, i.e., reinstalling the app I need to update the RAM disk. Nevertheless, the apps did not come back.

2. Why when I share an app from primary, the data kept is from the other ROMs? Can't we set which data will prevail when I share apps?
[Galaxy S 4 i9505 Original Android Development] v00d007:
So, then you're probably a candidate to wait for a final...?
[Galaxy S 4 i9505 Original Android Development] Technical:
Sure! I did not give up ;)

Restored app with TB and now, after booting, Google Account disappear and I lost TB... Emotion :)

The app is FC...
[Galaxy S 4 i9505 Original Android Development] sronweb:
The possibility to select the rom data to be shared would be interesting. currently I'm sharing i.e. facebook between primary and multi slot 1, but after reboot of the ms1 facebook crashes and I have to restore it from Titanium back up. Same for Firefox.

Is it important if I start to share the multi slot 1 apps first instead of the primary?
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=3145598]rlorange[/MENTION]

Any update? Still can't restore the system folder of a backup. Restore (of a valid backup) results always in 'System 0 MB'. Using v1.1c on EchoeRom v49 (TWz LP 5.01) and trying to restore cm12.1 to multi slot-1.
[Galaxy S 4 i9505 Original Android Development] Technical:
Yeah. This happens with me. But, worse, it happens with more than 50 apps :(
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Are we still having to reinstall all Apps on CM 12.1 when patched for Dual? Just downloaded the latest update but stopped short of installing it when I remembered what happened last time I did :)
[Galaxy S 4 i9505 Original Android Development] todivefor:
Yes, you'll have to modify the updater-script to remove the format data. I did it for latest AtaresOne 12.1 optimized build.
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Is it a case of deleting that whole line in the script?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Yes.
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Hmmm flash failed for me. Guess I did something wrong :(
[Galaxy S 4 i9505 Original Android Development] todivefor:
Are you flashing AntaresOne Optimized 12.1 to dual?
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Yep. Well trying to :)
[Galaxy S 4 i9505 Original Android Development] todivefor:
I'll PM you a link.
[Galaxy S 4 i9505 Original Android Development] rlorange:
OK guys I've found a way to share apps with libs.

Use link 2 sd install your app on primary and share then install on your secondary then use the link only lib files option.

As a bonus if your libs dissappear causing fcs just reinstall the app via link 2 sd

Doing this I have hangouts sync sms across roms... finally!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I've ran into this several times too, where almost all of the apps disappear. The problem is whenever a tiny issue occurs, Android s**ts over itself and breaks everything. And there's no way to know that and error occurred until it's too late. A lot of stuff used to work with the old syncdaemon, but that wasn't because I wrote good code (it was really crappy); it was because Android back then had very relaxed SELinux policies. Nowadays, different ROMs use different contexts and permissions on /data/app and a slight mismatch causes apps to disappear. It's quite frustrating...
[Galaxy S 4 i9505 Original Android Development] peppe130:
[MENTION=4277844]chenxiaolong[/MENTION] Chen please release a new snapshot so I can check Italian translation :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry, I just started working as a full time intern and haven't had the time to fix my server yet :) The new snapshot was built already, but the upload process broke. You can get the build from here: https://jenkins.noobdev.io/job/DualBoot_Patcher/513/
[Galaxy S 4 i9505 Original Android Development] peppe130:
Thank you :)
[Galaxy S 4 i9505 Original Android Development] peppe130:
Chen there is a problem.. Look at the screenshot

How to solve?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Argh, transifex doesn't support xliff and it's escaping the xml characters. I'll remove those tags for now; they're not that important.

EDIT: Transifex sources are updated. Once you remove the tags, I'll merge and push the changes :)
[Galaxy S 4 i9505 Original Android Development] peppe130:
Done :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done also :) The new build should be up soon.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
EDIT: I'm an idiot. Scratch all of that. I'm clearly too tired; I included blocking commands in the time.

I've been debugging mbtool lately to determine why it slows down the boot so much when app sharing is enabled. There are a *lot* of instances like this where it takes a ridiculous amount of time to receive a command from the installd socket (a command is usually less than 50 bytes). I originally thought this may have been due to files being moved around for app sharing, but that completes in about 20ms on average, with a maximum of about 120ms.

Example of slow command. In this case, Android sends the "linklib" command to installd to create the "lib" symlink in /data/data/[the app]/lib. Takes 1 millisecond to perform the operation and 118 milliseconds to run the app sharing code, but nearly 4 seconds in socket communication.

[2015/06/06 15:43:28 EDT][D] Received command: [linklib, com.sgn.pandapop.gp, /data/app/com.sgn.pandapop.gp-2/lib/arm, 0]
[2015/06/06 15:43:28 EDT][D] Hooking linklib command
[2015/06/06 15:43:28 EDT][D] Not copying user apk to shared apk for package com.sgn.pandapop.gp
[2015/06/06 15:43:28 EDT][D] User version (300) <= shared version (300)
[2015/06/06 15:43:28 EDT][D] Syncing com.sgn.pandapop.gp to all ROMs where it is shared
[2015/06/06 15:43:28 EDT][D] Sending reply: [0]
[2015/06/06 15:43:28 EDT][D] Command stats:
[2015/06/06 15:43:28 EDT][D] - Time to receive command from client: 3940ms
[2015/06/06 15:43:28 EDT][D] - Time to send result back to client: 0ms
[2015/06/06 15:43:28 EDT][D] - Time to complete installd command: 1ms
[2015/06/06 15:43:28 EDT][D] - Time to hook installd command: 118ms
[2015/06/06 15:43:28 EDT][D] - Time to complete entire proxy logic: 4059ms

EDIT: Even more ridiculous: on Android >= 5.0, the framework sends "markbootcomplete" when the boot finishes. This 22 byte message takes 8 seconds to receive. I have no idea why yet...

[2015/06/06 15:43:37 EDT][D] Received command: [markbootcomplete, arm]
[2015/06/06 15:43:37 EDT][D] Sending reply: [-1]
[2015/06/06 15:43:37 EDT][D] Command stats:
[2015/06/06 15:43:37 EDT][D] - Time to receive command from client: 7967ms
[2015/06/06 15:43:37 EDT][D] - Time to send result back to client: 0ms
[2015/06/06 15:43:37 EDT][D] - Time to complete installd command: 1ms
[2015/06/06 15:43:37 EDT][D] - Time to hook installd command: 0ms
[2015/06/06 15:43:37 EDT][D] - Time to complete entire proxy logic: 7969ms
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Chen, as dedicated and hard working as you surely are I 'm sure you will get it all correct in your time.....calm down and for all of us ...Thank You!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thank you! :D It's just a bit frustrating to see these issues pop up after spending so much time on the app sharing code. I'm looking on the bright side though. As long as we write good and clean code and have so many supportive people, we'll eventually iron out all these bugs.
[Galaxy S 4 i9505 Original Android Development] Andycar:
[MENTION=3145598]rlorange[/MENTION], do you happen to try the Latest Dr.Ketan's BOE4 L5 ROM on N910G by any chance with dual boot?

I ran into strange issue... When I patched that ROMs kernel with the latest snapshot of Dual boot patcher, my SIM card dissapeared in the ROM... That ROM had a BOC1 modem, BTW.

Thanks!

EDIT:It was not the latest, patched with DualBootPatcherAndroid-8.0.0.r1359.g340805a-snapshot.apk

EDIT 2: Nevermind, I got it working after patching BOE4 mboot with DualBootPatcherAndroid-8.0.0.r1365.g751b8cb-snapshot.apk[emoji1] [emoji2]
[Galaxy S 4 i9505 Original Android Development] Technical:
Chen, my challenge now is discover a 2nd ROM that worth to be installed. Meanwhile, I'm waiting for the app/data sharing.

Did you see the different approach of MultiSystem? http://xdaforums.com/showpost.php?p=60583746&postcount=1

It makes a system partition copy to a 2nd partition in sdcard. All the apps e data are kept inside of the phone and can be shared.
[Galaxy S 4 i9505 Original Android Development] peppe130:
Hey Chen! I made other changes to Italian translation :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, does MultiSystem support app sharing? I don't see that feature listed in the OP you linked to and the project doesn't appear to be open-source.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Done! I'm going to see if I can set something up to automerge the translations every night (because I'm so slow at this :p)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
DualBootUtilities will be getting an update soon with improvements in a few areas, such as only showing ROMs that are installed, support for data slots, and unified ROM wiping code with the app. It should definitely fix a few issues people were having with it.

EDIT: Also automatically supports switching ROMs on non-Qualcomm devices due to unified code.
[Galaxy S 4 i9505 Original Android Development] haoyangw:
[MENTION=4277844]chenxiaolong[/MENTION]

Unfortunately when I update ramdisk for Official CM11 nightly with Alucard 1.4r kernel on my Galaxy S4 it results in a bootloop stuck at bootanimation. Hope you can fix it soon so that I may try out app sharing :)
[Galaxy S 4 i9505 Original Android Development] Technical:
No, it is not based on sharing app/data but to make a full system partition image bootable from the sdcard.

It creates a system partition image in the sdcard and boots from it. All the (user) app and data are automatically shared (as there is not a copy of them, it's not even necessary).
[Galaxy S 4 i9505 Original Android Development] Quote100:
Cool will this also fix the kernel crash on the g3?
[Galaxy S 4 i9505 Original Android Development] NIFTYTAT411:
Will this work on the SPH-L720 running lollipop?
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Works on Canadian Galaxy note 4 n900w8 thanks a lot.

Keep up the amazing work.

Would really appreciate if we could work together and add support for the Galaxy Tab S 8.4 t700. Is that possible??
[Galaxy S 4 i9505 Original Android Development] rlorange:
The problem with this is that each rom will require an image size to match the device partition. In the Note4 case that's 3gb even if the rom uses up just a fraction
[Galaxy S 4 i9505 Original Android Development] rlorange:
Hey chenxialong, latest r16 emotionrevolution F/G kernel won't patch!! Def the boot.img ramdisk is not able to be patched dang!
[Galaxy S 4 i9505 Original Android Development] benlm72:
Hi,

I want to try DualBoot on my Galaxy S4, already updated to the Lollipop 5.0.1 stock rom from Samsung. And add CM12.1 OPT as a second rom to test Lollipop 5.1.1 on my phone.

It seems you have done almost the same thing : what do you mean by "debloat teh TW rom" ? No need to change the stock kernel ? And is it possible to install dual roms in an ext4 partition on the sdcard ?

Many thank's for your answers !
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
You should have no problem doing this, however you should install your second rom as slot-1, slot-2 or slot-3. Installing a touchwiz ROM takes up a lot of space. Debloating simply means I removed some of the apps I did not use to create more space. I utilized the dual slot which shares space with primary rom. You can avoid this by using slot-1.
[Galaxy S 4 i9505 Original Android Development] benlm72:
Just another question : do you have to act on the primary rom to patch it or can I let it without any change ?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
After primary is installed set kernel on primary in settings, that's it.
[Galaxy S 4 i9505 Original Android Development] skezza:
Damn, trying to flash CM12.1 I get Failed to copy /data/.system.img.tmp .......

Failed to run real update-binary.

Any suggestions?
[Galaxy S 4 i9505 Original Android Development] skezza:
Right, got it to work in multislot 1. Cool.

So, can you share contacts etc? Same contacts? I'm going to have a crack at this app sharing lark anyway. See how bad that goes down :P

I'm running Stock Touchwiz Lollipop 5.0.1 and CM12.1.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Is there any chance we could add dual boot support for the Galaxy Tab S 8.4 T700??
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
might have missed something... is it possible to change the rom from within the app without flashing DualBootUtilities?

sorry, stupid. just tapping the rom... this is kind of non-obvious.
[Galaxy S 4 i9505 Original Android Development] george stamatos:
+1 !
[Galaxy S 4 i9505 Original Android Development] Technical:
The image file is on the external sdcard (regardless of its size to match the device partition). If the sdcard (2nd partition) has space, no problems. This is what I've seen testing the technology.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yay weekend! Not quite used to working full time yet :P

The new DualBootUtilities is out! It uses the same backend code as the app now, meaning data-slots are supported, only installed ROMs will be shown, and Exynos devices are supported.

I will probably be working on fixes for the problems mentioned on the last few pages over the weekend.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
What are the Multi Slots for?

Can install say a 3rd Rom in multi slot 1?

---------- Post added at 03:28 AM ---------- Previous post was at 03:23 AM ----------

Can we Tri-boot 3 Roms?

If not any work being done on allowing a third Rom install, like a secondary 2 slot of sorts?
[Galaxy S 4 i9505 Original Android Development] sireebob:
I'm not sure if the LG G3 is officially supported, but this has worked great on my Verizon variant (VS985) with everything I've thrown at it, except the latest BlissPop, v3.5.

As of v3.5, using this patcher leads to an issue verifying the baseband when trying to flash:

g3.verify_baseband() failed to read current BASEBAND version: 2

The offending line in the updater-script is:

assert(g3.verify_baseband("MPSS.DI.2.0.1.c1.13-00053-M8974AAAAANPZM-1") == "1");

It's fine if I flash the original, unpatched version directly in TWRP. The patched version has this error both in TWRP and in the flasher app. Just pointing this out, since so far this patcher has done an amazing job at working with everything so I thought we might want that trend to continue. :) Thanks for the hard work!
[Galaxy S 4 i9505 Original Android Development] Technical:
Multi slots use the cache partition (usually very big in S4) while secondary uses (partially) the system partition to store the ROM.

Yes, you can have 3 ROMs to boot, but you won't have (that much) space for apps...
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
So if I had stock Rom installed on Primary, cm12.1 on secondary I can install my third Rom like cm11 in the Multi slot 1?

If I am wrong then where would I install the third Rom just to be clear?

I am using the Galaxy Note 4 N910w8. I think I would be ok with app space.

Thanks a lot.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the detailed info!

Taking a look at the source code, it looks like it tries to access the modem partition to determine the baseband version: https://github.com/CyanogenMod/andr...blob/cm-12.1/recovery/recovery_updater.c#L125

When patched zips are flashed, the installers are run in an isolated chroot environment to prevent them from overwriting files for other ROMs. Any partitions it wants to access directly will have to be whitelisted. I've just added the modem partition to the list (https://github.com/chenxiaolong/Dua...bd8c8344e796fbb/libmbp/patcherconfig.cpp#L552). There should no longer be any flashing issues in 8.0.0.r1380.gc1f714f :)
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
What is needed to bring compatibility to a new device?

Any way I can help with bringing compatability to the Tab S8.4 model T700?
[Galaxy S 4 i9505 Original Android Development] Technical:
Yes, you can (specially if your primary is AOSP and not a TW ROM, again, due to free space issues).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, how did I miss this post? I think this is a case of an international kernel not booting on the T-Mobile variant. I just downloaded it, patched and flashed it just fine, but it doesn't boot. So I rebuilt the SIMPL kernel to enable support for /proc/last_kmsg and disabled the tima config and the kernel boots now. (Their download page mentions that they use this kernel: http://www.emo-troid.com/tw-rom-downloads.html). You can probably get it to boot by flashing any other T-Mobile TW 5.0 kernel.

EDIT: Even though I got it to boot, the modem doesn't work (unknown baseband) because it's an international ROM.

EDIT2: Man, I can't read. You said the emotionrevolution kernel, not the ROM. Hang on, I'll test that.
[Galaxy S 4 i9505 Original Android Development] rlorange:
It will Boot on any TW 5.0 rom however the modem will on l only work if you have the G variant if you are on OEM1/2.

Yeah the boot.img fails to patch completely

---------- Post added at 11:24 AM ---------- Previous post was at 11:20 AM ----------

They did shrink the img thankfully so it won't be oversized when you get out to patch lol
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Anyone know where to get cm12 builds from. Old build links on cyanogenmod website are not working. Want to test a cm12 build with native sbs
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Fixed in 8.0.0.r1382.g59c60a5 :) They compressed the ramdisk with LZMA instead of gzip.

I could not get it to boot unless I recompiled the kernel without tima support, but that might be because of my bootloader version.

EDIT: Hmm... build failing. Think I forgot to link liblzma somewhere.

EDIT2: Fixed! 8.0.0.r1383.g21221d5
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
All I need is the value of "ro.product.device" from your build.prop and the list of partitions, which you can get by running:

ls -lR /dev/block/platform/

from the Terminal Emulator app or adb.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Here are the partitions I took pictures. Hope it helps. Uploading build.prop info in a minute.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
Currently on the Galaxy Tab S 8.4 T700 I am using a Korean Stock Samsung Rom just because a stock Rom had not been released in Canada till now. I am downloading the Canadian Rom so I can be on the official one for my country. Just so it is known. I will upload pics for the build.prop for Canadian Rom also just in case once I get it installed.

Really hope all this helps with bringing compatability to a very good device.

Thanks again for your support. ?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
My device..

WHAAAT?? :eek: It was this easy?!?

Anyways, here's the details from my phone :D

ro.product.device=pepper

But typing that command in terminal gives "/dev/block/platform/: No such file or directory" error. (I also checked it with a file explorer, there is no folder named "platform" in /dev/block)

I think it's because my device is Sony.. Sony devices don't have a dedicated recovery partition (Now they are adding support for a few devices)

EDIT: I tried with adb too but it gave " 'ls' is not recognized as an internal or external command,

operable program or batch file."

EDIT 2: Used an app called DiskInfo and I am attaching screenshots from it.. Please check them

---------- Post added at 02:20 PM ---------- Previous post was at 02:18 PM ----------

Can you tell which app this is??

The terminal command doesn't work for me
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
So I checked build.prop and it looks the same but I uploaded I quick pic from the Canadian stock Rom just to be sure.

If there is anything else you need at this time let me know. I can test it on the device when you get the compatability working. No rush I am patiently waiting for your word to give it a test.

Thanks again very much appreciated.
[Galaxy S 4 i9505 Original Android Development] MrHomebrew:
I can check what it is called when I get home I am out right now. Looks like you may have found something. I can let you know a little later on when I get home.
[Galaxy S 4 i9505 Original Android Development] sronweb:
[MENTION=4277844]chenxiaolong[/MENTION], I noticed that on last Dual boot Utilities (snapshot 6) most of functions are missing, I cannot select the rom slot etc.

This is last available on the download page. Thanks
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
You are right, my last slot available to choose is multi-slot-1.