THIS IS FOR SAMSUNG DEVICES THAT ARE NOT ROOTED AND HAVE THE MULTI WINDOW FEATURE.
I really wasn't able to find anything on why app crashes happen in multI window mode for some apps when using mw-pen on devices that are not rooted. So I wanted to post a blurb on how to manually stop the crashes as well as how to manually enable an app, and get things working. Again this is for devices that are not rooted. Although it will work with rooted devices as well. If you are rooted, there really is no point in doing it this way unless your bored or if you are just slightly insane. Since your not rooted you will lose all current app data that is not hosted in the respective applications cloud. As well you will need to recompile new packages when updates are released if you want new features or the program will no longer connect, etc. Updating directly from the app store will kill the multiwindow feature on the respective app. If you are user of MW-Pen app enabler skip step 9. and as MW does this already. If you just didn't want to use mw pro......or are again slightly insane.... then do step 9.
All of the steps below will be carried out on Android device.
You will need the following software:
1) File exploration program with zip support (JRUMMY Root Browser works great)
2) Apk Editor (Free version should be fine although I use pro)
We will assume you have the previously mentioned software installed. If it is not you should do so AFTER reading this post.
1) Create an independent folder in "/sdcard/APKeditor/(My project)/" , additionally I created ./backup & ./new (./ representing the working parent directory).
2)Once the folders are in place, go to Settings>Applications>All Applications>YourTargetApplication I recommend stopping your application and clearing any data or at least cache. Although the information should not transfer over it would really bite if you were the one random exception in this vers, and you were giving copies out. Do not disable the application only stop it.
3) Now you will want to backup your target app. To do this fire up "Apk Editor" select the option to pick an apk from a currently installed app select the option for common edit. Click through until you see the save button on the top right corner. THIS IS BACK UP!! SO DO NOT CHANGE ANYTHING!!
4) Once it has completed successfully I recommend flipping back to your application manager and uninstalling the target app. Then flip back over to APKeditor and install. Test the app to verify nothing became corrupted and the app functions normally with a backup only. This will help in your trouble shooting.
5) Once you have the app installed and everything is good you will want to again go to to your app manager, stop the target app and clear data or at least cache. Stop do not disable.
6) Now open your File Browser of choice that met the requirments and navigate to "./sdcard/APKEditor/" you shold see an apk named "_Base" with the icon of your target app. That is your know good backup so you will want to move the apk file to its respective backup folder created earlier
7) Once the backup is secure go back into APKeditor and again select the option apk from app. This time instead select the Full Edit option (Resource Rebuild).
8) The fun part! This part should take you no more than 15 seconds if it takes longer than that your messing up (JOKE). From the edit screen you will see 3 buttons in the bottom. Go to the last button or "tab" it is labeled "Manifest". Once selected go ahead and long press an entry under <intent-filter> any entry really should be fine but let's be safe. On the menu that pops up you will see the option "Open In New Window" select it. Take a minute at first to look things over and familiarize yourself with the patterns at first it may seem a bit overwhelming. There is a logical structure to the file it is telling things what to do and where they belong. The top will have the permissions required followed by accessing features pertains to those permissions. We don't care about that however. The main areas you should look through (just look at to get familier) are the <intent-filter> entries along with what preceded the entry and the structure and what follows and again and again until you see the pattern. What we will be doing in the next step (The 10 second step) is adding entries under the <intent-filter> sections.
9) So your 15 seconds is up and now you feel like your ready for the 10 second step. Now that your ready we need to go into a less obvious view and the reason why I had you look at the code in the first view to familiarize yourself with the pattern. So go ahead and click on the pencil icon in the upper right corner. The first edit will be slightly different than the rest. You will see ano entry that says <application> followed by icon, labels, name, theme, those kinds of things. They should be followed by <activity> then <intent-filter> and then <action>. Under the last <action> item in the grouping and before </intent-filter> is where your entry will go. (<whatever> is the starting point for instructions and </whatever> is the closing point. So if we input in <action> then that is where our command would sit, as an action). So we will go below the last action entry and input the following:
<category android:name="com.sec.android.intent.category.MULT IWINDOW_LAUNCHER" />
<category android:name="com.samsung.android.intent.category. PENWINDOW_LAUNCHER" />
Rinse, wash, and repeat, Rinse, wash, and repeat, Rinse, wash, and repeat......You get the idea... Be sure that </intent-filter> is the line after everytime you make an entry.
10) Now we need to review the document for oddities and/or anomalies to the general rule and what causes app crashes in MultI Window the majority of the time. Typically this happens when overlay singular windows are called from the app and are independent of the general <activity> <intent-filter> <action> rule. In these cases we have to put on our detective hats and poke around. Normally we already know screen the app crashes in so that will is our first clue, so we need to start to look for something to do with that window. If it is a chat window look for a chat window call, etc. In that set of instructions for your crashing window you will want to add in the calls as you have done before you may need to add the first <intent-filter> now you can test. Save the document off to the side and save the apk. And install in real-time. Test the app. You if it was done correctly your app should no longer crash.
11) save the new working apk to the "./new" directory created earlier inserting the app version number after. You can find the new file under the APKeditor folder you should see a new "_Base" File.
*As a side note if you follow these instructions, have done trial and error, and things still are not working. Then and ONLY then post below. I can not insure promptness but I will respond when able.
