yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Done that, unfortunately vibrations all the time.

Maybe something wrong at my end idk.

Going to wait for the next release maybe it will be sorted out
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Did you use 7.0.0.r151 to patch kernel and ROM?
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Yes indeed I did. Removed all previous and snapshot versions and installed only this, didn't work as well. Vibrations..
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Did you wipe system before flashing?
[Galaxy S 4 i9505 Original Android Development] MohamedN:
System for primary?

I wiped everything for secondary via the recovery tool but didn't touch anything that could mess up primary or mutislot.

If it's necessary please do let me know :)
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
No you did it right, no need to me with your primary. Just wipe the slot you are putting it in.

It should work, so long as the kernel is also patched with 7.0.0.r151

Mine is working perfect, so good I've swapped to it for my daily driver :good:
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Glad it's working for you, used to have ge as daily driver as well so I will keep trying until I get it right
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

I just perceive me that the synchronisation of contacts wasn't done correctly in the roms other that primary.

Let me explain

When I do so with the primary, everything works fine for this primary.

When I do with roms other than primary, it works for synchronization with other roms, except that if I want to send a message by typing the name in the message application , I can't find the name. If I do it by typing the number, it doesn't show me the name of the contact. If I want to delete the contact, it makes me a FC of contacts application.

However, if I create the contact, in other roms, and I'm doing all these manipulations in the primary, everything works.

If I create the contact in the primary, and I go to other roms, I have the name that will appear in the contacts, but I have the same problem that if I create contact in other roms. All these problems.

I do it with the latest snapshot, I have the same Gmail address for all roms, it seems to me, however, before it worked properly.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
After missing so many promised ETA's, here's a very alpha build (Windows only) of 9.0.0 :)

Changes compared to previous release:

Completely ported to C++ and Qt5 (originally written in Python with PyQt5)

Fully translatable

Everything is implemented as a plugin, so the patcher's functionality can be easily extended

Patcher information files are now in XML format to make it easier for adding support for new files without updating the patcher

TouchWiz ROMs still take a long time to patch, but with the libarchive library, it can shave off 2 minutes or more from the patching time

Known bugs:

Does not work on Windows XP. Is it possible to target XP anymore with Visual Studio 2013? (My 2012 license from school expired already)

The GUI layout needs some fixing

Custom patcher comboboxes are not refreshed when the device is changed

The patcher will happily accept non-ZIP files and then crash when you try to patch it

Everything that was working with the old patcher should be working in the new one. If anything doesn't work properly, it's a bug. And now that I have a working build, I will try to release testing builds with any fixes daily (don't hold me to that though ;)).

Also, my university's iMacs in the computer lab have XCode installed on them now, so the final version of 9.0.0 will have an OS X build :) Ubuntu users will also get packages via a PPA and Arch Linux users will be able to install from the AUR.
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Have you seen the previous post?

¿The Patcher also works with Win64? I think but I prefer to ask...

¿Why DuakBoot Patcher 8.0.0? And not 9.0.0...
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
that's why you shouldn't announce etas
[Galaxy S 4 i9505 Original Android Development] DeuXGod:
Does it support the note 3 now? Or still in development?

Sent from my SM-N9005
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sure I'll take a look at the contacts issue and see if I can reproduce it (I use the same Google account on every ROM too).

(And it's 8.0.0 because I forgot to change the version number in the config file ;))

EDIT: It does work on Win64 (Vista, 7, 8, 8.1)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's still in development right now :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Here is the second alpha for 9.0.0 :)

Changes from Alpha1

ROMs that use the newer update-binary file (which doesn't support set_perm()) are now supported (this includes the newest CyanogenMod nightlies)

The lists in the GUI are refreshed when the device is changed now (bug fix)

Added support for the OnePlus One

Known bugs:

The autopatcher combobox on the custom patching screen has no effect (!!)

Still doesn't work on XP

The window still resizes randomly

File extensions still aren't checked
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
needs Visual C++ Redistributable Packages for Visual Studio 2013, the x86 version.
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
since theres an "update syncdaemon" and i had issues with that one (regarding vibrations), do i need to patch this additionally? like patch the original file and then patch the _dual.zip file or how does this work?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Patching is really fast.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh, I completely didn't notice I left that option in there. The "update syncdaemon" option* is rarely needed and will only work when it's run on the device itself, mainly due to complications with the locked bootloader on the AT&T and Verizon models. I'll hide this option in the next release :)

*syncdaemon is a background service I wrote that manages the copying, updating, and deleting of files for app sharing (and soon, app data sharing)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I installed the ones after the others as I usually do, rom + gapps + kernel patched with your new patcher, and Unfortunately, That does not work!

I re began with the snapshot version 8.0.0 r99 and all went correctly past.

My PC config:

Windows 8.1 x64

My phone config

:

3 roms

:

SHOstock in primary

AOSB in secondary

PAC MAN in third

Recovery: TWRP 2.8.0.1 with Black play Android L theme

Things that I've patched

:

PAC MAN rom of 09-20-2014

PA-Gapps of 09-16-2014

Alucard kernel AOSP v2 1.4e of 09-20-2014

[MENTION=4277844]chenxiaolong[/MENTION]

I hope that will help you to know why!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the info! I'll take a look at it first thing tomorrow. I'm sure it's just a simple mistake I made ;)

EDIT: Found out what was wrong. The init binary wasn't added to the ramdisk when Alucard was patched. Of course, this means the kernel starts up and finds it has nothing to load, so it just reboots.

EDIT2: It turns out the path was missing a slash character. D'oh! Next version will check for errors in the paths and will fix this issue :)
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
Hi Chen - thanks for all your hard work on this - I've been running 5 ROM's for so long now it would seem strange not to have them :D

I'm running Dandvh GE on multislot 3 and the only way I could get it to work without random vibrations was to patch with old snapshot 7.0.0r151 - I'm guessing the above syncdaemon is related to this issue??

Please could you try patching the rom for yourself and see what happens (link in my sig)

Thank you :)
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
Little question, need to update my modem, and since there's no possibility to flash it by zip, I need to do it with Odin, but how can I do this for the second rom?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
When you dual boot, everything outside of the ROM and its kernel is not touched. So when you flash a new modem, it will apply to all ROMs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Here is the third alpha for 9.0.0 :)

Changes from Alpha2

Added support for Danvdh GE ROMs that begin with "Danvdh-GE"

Fix bug where the Google Edition autopatcher (for KitKat) broke out of a loop too early causing some instances of "snd_soc_msm_2x_Fusion3_auxpcm" to not be removed from /system/etc/init.qcom.audio.sh (which ultimately causes Google Edition ROMs to not boot)

Fix bug where the old init was not removed from the ramdisk's cpio archive, so the new init would fail to be added. (Broke booting for GE 4.4, TW 4.3, TW 4.4, MIUI, and numerous AOSP 4.2 ROMs)

Fix missing slash in init paths where even if the bug above was fixed, the ROM still wouldn't boot ;)

Known bugs (same as alpha 2):

The autopatcher combobox on the custom patching screen has no effect (!!)

Still doesn't work on XP

The window still resizes randomly

File extensions still aren't checked
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Was this with 9.0.0 Alpha 2? When I patched Dandvh GE with that, I was stuck at the boot animation and it vibrated once, then three times, then once again, etc. Was that the same issue you had? If so, it should be fixed in 9.0.0 Alpha 3 ;)

EDIT: If 7.0.0.r151 is working fine, then I don't think syncdaemon is related to this issue. It hasn't been changed since 7.0.0.r115. Though, the only way I would be able to know for sure is if you happened to be grabbing a logcat when the random vibration occured.
[Galaxy S 4 i9505 Original Android Development] lpdavidgc:
What about note 3 support :)?
[Galaxy S 4 i9505 Original Android Development] MohamedN:
7.0.0.r151 didn't solve my Random vibrations issue with Danvdh-GE, instead it didn't boot stuck at bootanimation with crazy vibrations.

Going to try the new alpha today

Thanks for all the hard work :thumbup:
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
But the baseband haven't changed for the second rom, only for the primary..

Edit:

I don't know how or why but I retried it and after the third time it worked o.O
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Impossible!!!
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
First I tried whit auto reboot, didn't worked, then I tried it without and a second time with auto reboot and then it worked..
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I said "Impossible" because you can't have a baseband on a rom and another baseband on a other.
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
I had it until yesterday xD the new baseband was applied to the primary rom but not to the secondary
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Are you sure to have seen correctly? I've the same baseband for all, it's not possible otherwise.
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
Don't know if it's the new baseband or something else but I can't start my primary rom anymore, glad that my secondary rom works well..
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Try to reflash the kernel for the primary rom. See how it goes..
[Galaxy S 4 i9505 Original Android Development] gaww:
Are you confusing kernel for baseband? As has been said - ROMs do not include base bands - they are part of firmware and the current one is used by all ROMs.
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
exactly what i did.

Config file /raw-data/syncdaemon.json not found
failed to load configuration file

evey time a vibration occured, this error occured. it happend only when phone was in deep sleep

i already wrote this few pages ago
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
Doesn't helped, it builds the dalvik and shows the app names but when it says "starting apps" the phone make a reboot
[Galaxy S 4 i9505 Original Android Development] MohamedN:
You are sharing app and you recently installed or updated an app from another rom that conflicts somehow with the primary rom, uninstall any recently updated or installed app from secondary rom and then reboot into primary.. You will be fine then
[Galaxy S 4 i9505 Original Android Development] 012512:
hey man, how about the issue when the primary rom was a touchwiz (imperium 12.0 - kt kernel) and the secondary was an aosp rom (cm11 - stock kernel)?

Set the kernel at primary rom. I tried installing a secondary rom and boot to secondary. On the dual app, I chose to switch in primary rom but seems it doesnt boot to primary but to secondary rom instead.
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
I removed all shared App's and retried to boot into primary rom but same issue as before.. :eek:

Edit:

Btw when i flash the zip, aroma says the memory of internal and external is -1
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll have to run it under a debugger and see if I can grab the stacktrace when it crashes. The messages you see are normal if you don't use individual app sharing, but since it appears every time the vibration occurs, it would seem that syncdaemon is indeed crashing :(

EDIT: Ohh... I know why 7.0.0.r151 worked. Back on that version, if syncdaemon crashed, it would just ignore that. With the newer versions, syncdaemon is respawned whenever it crashes.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Here is the fourth alpha for 9.0.0 :)

Changes from Alpha3

The autopatcher combobox code in the GUI has been implemented. This fixes the broken custom patching from the previous alphas.

Known bugs:

Still doesn't work on XP

The window still resizes randomly

File extensions still aren't checked

syncdaemon still crashes under certain unknown conditions

EDIT: Dang it. I reproduced the syncdaemon crash, but didn't have my phone connected to my computer at the time. Time to play the waiting game again...
[Galaxy S 4 i9505 Original Android Development] S2_fa_007:
I get an error on every operation i do by the zip

Edit:

DualBootPtacher 9.0.0Alpha4 gives me a error, MSVCP120.dll is missing

I tried the fix from the first post but didn't worked
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Look that! ;)

---------- Post added at 11:13 PM ---------- Previous post was at 11:07 PM ----------

I will confess to not having this error. But this should solve the concern. If you want other ways to solve the friend Google is there.
[Galaxy S 4 i9505 Original Android Development] alessandro_xda:
do you use omega rom as primary? did you patch it yourself (it seems not to be officially supported...)

i'm using omega v12 too but i've read that patching roms that include aroma is not that easy, is it?

bye
[Galaxy S 4 i9505 Original Android Development] kingzain900:
You can use Omega as your primary. For secondary ROMs that use Aroma, yes it's not that easy to patch.
[Galaxy S 4 i9505 Original Android Development] alessandro_xda:
do you think that it's safe to flash a patched Omega over my 'standard' omega without wiping?
[Galaxy S 4 i9505 Original Android Development] kingzain900:
Why would you need to do that? You patch it if you want the ROM to be a secondary ROM. You don't need to patch a primary ROM. Just install primary as you would normally (wiping everything). If you're installing Omega as secondary, it will not work since it cannot be patched at the moment.
[Galaxy S 4 i9505 Original Android Development] alessandro_xda:
you are right! i had misunderstood the way patch works.

now i realized what to do:

-I can keep my Omega rom as is (just install Dual Boot Switcher app and set the rom as first rom using the app)

-download and patch a second rom (CM for example)

-flash only the second rom (using my standard recovery) (it doesn't overwrite the first rom since it is patched)

-install the app on the second rom.

sorry for the stupid questions but i want to be sure to understand the way it works.

ps:

I think that it could be useful to create some packages with some combo of roms ready to be flashed in one shot.

what i mean is to create a single flashable OmegaV12+CM10.2.zip to be flashed as a standard rom but including both.

I think it could be very useful for people that would like to try the dualboot but don't want or don't feel safe in trying the standard procedure...

(this are just my 2 cents...)

bye
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
That would be way too much work and would lead to a TON of different "packages" as there are so many combinations of ROMs that are possible, not to mention how often roms are updated.(especially CM) If somebody finds the simple dual boot procedure outlined in the OP as difficult then they probably shouldn't dual boot lol. It's literally written step by step.
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
but then how would people install gapps? everytime I install gapps it loads it on my TW and then that causes issues. I also can't run beanstalk as a second because it isnt supported and thats the only aosp rom I enjoy. this isn't working out for me at all because I cannot get Beanstalk as second and I cannot get Foxhound as second either. I also have tried other TW roms and cannot get as a second because they aren't supported. :/
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
This dual booting isn't meant for everyone obviously if you can't compromise just a bit and use a rom that's compatible in the mean while.

You picked two tough things... First was picking an aosp rom with aroma.. And second was choosing a very large touchwiz rom that also has aroma. Why don't you choose on of those two as your primary and then choose another rom that is compatible as secondary? What rom are your trying to run as primary by the way?

Edit: Read the compatible packages and you'll see that gapps are compatible with the patcher :)
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Aosp isn't the aroma one. Tw was. Beanstalk is the one I want as my primary because it's the best one for me. Every other one that I have tried is either laggy, slow,or just isn't what I want. As for touchwiz I have tried the FoxHound because it was on the list of the ones that work. I usually have a backup of GoldenEye but its not compatible. Even though it doesn't have aroma I'm sure that it shouldn't be hard to make compatible. Also FoxHound has DPI changer and that's what I want lol. So yeah that's what is going on.

Also about the gapps I have tried the ones on the list, drag it to the patched and get nothing patched :/ lol

Also I am not hating on this awesome product :3 it just doesn't have my roms yet :) lol.
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Sorry for misunderstanding. It's just that over in the tmobile forums there is a version of beanstalk that has aroma and that's the only one I've used lol. If you want a dpi changer, just download a dpi changing app or use xposed and the app settings module.

For the gapps, try the latest AIO slim gapps from their website. I literally patched mine last and it worked perfectly! I patched mine on Linux but it should work just fine by dropping it on patch-file.bat if you're on Windows! (which I've also done)
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Yes I am sorry I didn't say I was on AT&T. But yes I am trying to patch the files manually. Because I want Beanstalk and foxhound. Also I saw that only fox 1.8 was on the list not 2.0. Is that also an issue? (It did go through the patching.)
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Before you try to manually edit the updater script, skip to the last step and see if you're able to replace the ramdisk first. I tried doing it last night for liquid smooth, made all the edits to the updater script but then I couldn't replace the ramdisk. That way if it doesn't work you'll save time from fixing the script!
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
yeah I got a name error and it didnt replace
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Found the issue with fox. It isn't installing any kernals that I had selected. Everytime I try to swap to that rom it says no kernal found.
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Then you should be able to just flash a patched kernel right after flashing the rom. Try that?
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Yeah going to try that now lol
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
Actually... I think the aroma installer might have flashed the kernel to your primary rom. Check that too. If that's the case you'll have to flash another primary kernel and reset it with the dual boot app.
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Well I chose flash no kernel and then flashed a tw kernal(I guess what wasn't approved maybe) but it booted my primary rom not second.

I am having such an issue on finding a kernal that the front says will work and then locating that said kernel to download. Point me in the direction of a kernel to use with fox 2.0 and is TW? sorry I am on phone otherwise I would search for it >.<
[Galaxy S 4 i9505 Original Android Development] marcoxx626:
It's because you can't just flash any TW kernel. If foxhound is your secondary rom, you have to flash a Touchwiz kernel that has been patched for dual boot. I see your on AT&T and I think the OP mentioned something about using loki'd kernels so check the OP for that.
[Galaxy S 4 i9505 Original Android Development] toxicpaulution:
Yeah I know about using loki(was doing that after I flashed kernels in the fox), But what I cannot figure out is which kernels he is talking about. I had downloaded ktoonz and then when I went to patch it it said unsupported zip. That is my major issue. I cannot find what exact kernels can and cannot be patched.\

Awesome, thanks for the help. booting Fox as we speak and hoping the dualboot pulls off successfully :3
[Galaxy S 4 i9505 Original Android Development] davy4475:
Would this work with carhd and dirty unicorns?
[Galaxy S 4 i9505 Original Android Development] franzyroy:
The best is to try! At least to patch them.
[Galaxy S 4 i9505 Original Android Development] monkteo:
dirty unicorns works I have it on secondary with SHOstock
[Galaxy S 4 i9505 Original Android Development] davy4475:
SHO?
[Galaxy S 4 i9505 Original Android Development] sronweb:
This rom:

http://xdaforums.com/showthread.php?t=2639202
[Galaxy S 4 i9505 Original Android Development] franzyroy:
I just put the PAC MAN rom update, everything went well.
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
I've been trying to get ge to multi boot, I have given up trying to patch and put it in dual/multi slots as there seems to be incompatibility between 7.0.0r151 and 8.0.0r90 (90 is bugged for me). All goes well until you boot into another ROM then all falls to pieces.

I think I found a workaround booting as primary then using patcher 7.0.0r151 to set kernel as primary then boot into dual/multi patched ROMs and using patched with patcher app 8.0.0r90 and sharing apps from those ROMs using patcher app8.0.0r90. I seem to be OK booting back and fourth but early days, time will tell. The random vibrations on ge occur once on boot up (nothing unusual about that) then seem to stop with this set up.

Till Chen susses out the syncdaemon bug this will do for me.

I hope this is clear enough to be helpful to others, let me know if not.

EDIT: LOL, tripping myself up with my own complicatedness! Just use patcher app 7.0.0r151 for everything and all working perfect (I think!!)
[Galaxy S 4 i9505 Original Android Development] davy4475:
It works [emoji4]
[Galaxy S 4 i9505 Original Android Development] franzyroy:
Yes, I know! ;)