How to enable this app in dual apps

[niravchaudhari1011-cmd]

[EdRoxter]

I might jump in here because this has been quite some fiddling for me as well. My solution works on a Sony Xperia 10 VI with Android 15 (as far as I can tell, pretty close to AOSP) where I'm using the OS-native "Private Space" feature to run dual apps.

So my steps to make it work after initializing the Private Space:

• Download and install AppManager from F-Droid (its installer is incredibly handy for these kinds of tasks). Grant it root/su in KernelSU/SukiSU.
• In AppManager's settings, under Installer make sure that "Use the installer" is active
• In the Main/Personal Space, download the latest WaEnhancer release and, from ApkPure, a supported WhatsApp version (as well as version 2.25.6.74 if you're affected by the login issue; you'd then have to first install that old version, log in to WhatsApp the usual way by SMS code, then set up WaEnhancer and update WhatsApp to a recent, supported version). Super neato: AppManager can seamlessly handle and install XAPKs, so on ApkPure, you always opt for that download.
• Now tap on the WaEnhancer apk and select to open it with AppManager>Install
• A little modal dialog should pop up. In it, tap on the settings gear in the top right corner. Now select "All users" in the first drop-down and make sure all three bottom options are off, then tap OK and Install.
• LSPosed will probably send a notification that a module was installed and needs to be activated. Ignore that for now.
• Tap on the WA XAPK and choose to open it with AppManager as well.
• Like before, choose to install WA for all users too. You don't need to worry about the already installed version because AppManager easily downgrades apps as well.
• Now open LSPosed Manager and activate the WaEnhancer module for both spaces.
• In the Main/Personal space, tick the suggested "System Framework" and "WhatsApp" scope. In the Private Space, there's no SysFramework, so just tick WhatsApp and reboot
• Now you should have an instance of WhatsApp and WaE in both spaces. Start WaE and see what it has to say, and WA as well to see if everything works. It usually should now.
• ...but there's more: If you want to run WA exclusively in the Private Space (I do this because it's the only way to present a different address book to WA than to the rest of the system), you still need to have WaE and WA installed in the main space. This is mere guessing, but I suspect that the bridge to the system framework across dual-app borders depends on the modules/apps being present in the primary space as well.
• I don't want to have a fully functional, not-logged-in WA instance sitting in my main space, running a system service, doing stuff and things, draining battery. So it's AppManager for the rescue again:
• Start AppManager, find the WhatsApp entry, tap on it
• It should ask you which Space's installation you want to manage. Choose your primary one (marked with a "(0)")
• Then tap "Freeze" and choose "Advanced Frezee" in the pop-up.
• Voilà! It's sedated, so now you practically have only one functioning, isolated WhatsApp installation.
• Install all updates for WaE and WA with AppManager for All Users always. That even will keep the Freeze intact while properly deploying the app into the Private Space.

Hope this helps!