It is a fact that Android development arena is saturated with -deprecated- widgets which incorporate custom implementation of existing functions. I personally think over-complicating simple widgets leads to premature deprecation, and increases incompatibility issues; not to mention lack of proper documentation. Therefore, I decided to code the concept on top of RecyclerView. It may seem like an over kill, but I figured that if I used RecyclerView, people would be able to use it on top of their existing adapters without having to change anything, plus I don’t have to worry about compatibility with older Android versions. I’m also fan of one-class libraries, since they can be easily downloaded and integrated into projects, specially in the case of simple widgets.

Fast-forward couple of days later, I was able to recreate Oleg’s concept by using RecyclerView.OnItemTouchListener implementation. Overall, I think it turned out nicely. Simple, light, sustainable, and one-classer.

You can check out the library here

Using ImageJ, the app (or plugin, if you will) first allows the user to highlight the black and grey compartments. This is because the mice used had white fur and there’s no reliable contrast between them and the white compartment. After highlighting the black and grey compartments, the user is asked to select an optimal threshold value that highlights the mouse from everything else. This threshold value will be applied to all frames. The app then starts analyzing the video. The app uses ffmpeg to extract all frames in the video, then process them one by one. First thing it does is cropping the frames to the area the user had highlighted in the beginning, then apply the threshold value. The app will check if the image is completely black (which means there is no mouse in the frame). If true, the app will skip this frame and move to the next one to save time and reduce false-positives. Else, which means there is a mouse, particle analyzer will analyze the 'mouse'. Of course there will be false-positives, so in order to eliminate the chance of error, the particle analyzer is initiated with area threshold. If the object is truly a mouse, the particle analyzer will find the centroid, then check if it’s in black, or grey compartment. The process is repeated for all frames, which are about 13,000 for a 15 minutes video at 15fps.

You can get the code by clicking here. Once you downloaded the file, extract the included four files, run ImageJ, go to plugins > compile and run > UI.class then follow the instructions. Don’t forget to download and extract ffmpeg to the same folder

I’ve checked it with manual counting, and the app is pretty accurate when configured correctly. After each analysis, there will be a folder called "debugging" which shows the results of the first 500 frames, you could check the accuracy from there.

WTFPL

First you need to change the channel from red to all, then slide maximum to 0. Once you’ve done that, gradually increase minimum until you get something like the picture shown above. The mouse should appear featureless with contrasting background which doesn’t contain significant artifacts. The tail shouldn’t be visible. Note: it is imperative that you don’t press "Apply"; otherwise, the application will not be able to capture threshold values.

The picture above shows a bad example of thresholding because the tail is visible, and minute artifacts can be seen at the lower edge. It’s for the best if you provided clean images.

This module requires Android 5-based ROM and above (until 9). It was tested and developed on Android 6.

You can get the module from Xposed repository here.

Preferences are ignored and default values are used in certain apps (such as settings app) when SELinux is set to enforcing. The problem lies within Xposed preference class 🤷

This mod causes rubber-band effect when playing multiplayer

Whenever the frame rate drops below 60, you will experience "slow-mo" mode

Either Wyatt or Eddie has to check the guy after hitting him, while being chased by an unknown man. You have to stay in the car and leave Eddie behind as this will give Wyatt a reason to join Tavia.

Next, you have to refuse Eddie’s suggestion of playing rock-paper-scissors to decide who checks the body. This will make Eddie go and check the body himself. Or you can accept and play rock-paper-scissors, but you have to win. Losing will cause Eddie to leave Wyatt behind and that is not the option you are looking for.

When Vince is in the bus, you will have to chop-off either of Justin or Danny’s ankle in order to take the chain off. Shoot Danny’s ankle. Running away with Justin (shooting Danny’s ankle) will teach Vince that shelters are important, while running away with Danny (Shooting Justin’s ankle) will teach him not to trust anyone as this will affect his trust towards Tavia, resulting not going with her.

At the end of Russell’s chapter, you have two options where you get to decide either joining or leaving Nate. Leaving him will make Russell more likely to join Tavia, but this is largely affected by the way Tavia convinces him.

Killing or freeing the stranger will not affect Shel’s decision but killing Stephanie will. When you talk to Becca, take the keys and drive the RV away. As Becca mentions, Roman will hunt them down. This will give Shel a reason to join Tavia.

Bonnie is the last one because she will be the first one to join Tavia; no matter what your choices were. You can lie to Leland about Dee’s death or tell him the truth. You can also leave him to die. None of the choices will affect her decision.

In Tavia’s chapter, you will have to recruit as much members from the camp as possible. To do so, follow these choices:

Russell becomes nervous when Tavia comes. Regardless of your previous choice regarding Nate’s fate, he won’t join Tavia unless she says "You might find people you know" as this will give him hope to find his family.

This section contains various general cheats which you might want to check out, such as unlimited ammo, health, credits, etc…​

Note: After the V1.05 update, the codes must be placed in sfxgamemodedefault instead of sfxgamemodebase. If that doesn’t work, place the codes in both sfxgamemodedefault and sfxgamemodebase

As you might have noticed already, each command is mapped to a key which you can modify to your liking. The setup above gives you the following options and their key triggers:

Note: screenshots are saved to .\Documents\BioWare\Mass Effect 3\biogame\Screenshots

In Mass Effect 3 story, you don’t get to use heavy weapons as often as you did in Mass Effect 2. Luckily, they did not remove them completely from the game, therefore, the following method is used to replace one of your equipped weapons with a weapon of your choice.

To activate any of the listed weapons, add the following line under bindings section (as mentioned above):

As you can tell, this command lets you obtain the weapon Cain by pressing F12. You can change these two to your liking.

Below you will find a list of the weapons you can get (replace the word Cain in the command above)

(The tutorial ends here for Mass Effect 3, as Miranda’s outfit doesn’t work properly on ME3)

First of all, you’ll need to edit your Coalesced.ini in order to have Miranda’s outfit for your female Shepard, to do so:

To [SFXGame.SFXPawn_Player]

To [SFXGameModeDefault]

Finally, add the following to [SFXGameModeBase] & [SFXGameModeDefault]

Your Coalesced.ini is not yet ready to be used in the game yet, you’ll need to run a fixer "Ruby-based".

Now that you have the outfit, we’ll move on to the next step.

Now that you have the outfit and the skin tone, it’s time to remove the neck clipping that occurs when you apply Miranda’s outfit on FemShep.

You will have to use TexMod every time you want to play Mass Effect 2 because the effect of the TexMod is not permanent.