Megajump – How to have full MPs

  1. Get the apk
  2. Run this script to
    a. Unpack APK
    b. Add debug flag
    c. Repack APK
    d. Sign APK
    e. Verify APK
  3. Install the debug APK to your phone
  4. Create on our computer a file named GSGPrefs.xml with this content:
  5. Using Android Studio, Device File Explorer, go to “/data/data/com.getsetgames.megajump/shared_prefs”
  6. Delete the existing GSGPrefs.xml if any
  7. Right-click the folder, upload your own GSGPrefs.xml file

You now have a lot of MPs


Apache2.4 – Enable SSL and HTTP to HTTPS redirection

On clean Ubuntu 18.04 installation:

Initial installation: PHP & Apache2

sudo apt-get update

sudo apt-get upgrade

sudo apt-get install php

sudo apt-get install apache2

Enable mod_ssl and mod_rewrite then restart apache

sudo a2enmod ssl

sudo a2enmod rewrite

sudo systemctl restart apache2

Create your site, enable it

sudo nano /etc/apache2/sites-available/my_site.conf

sudo a2ensite my_site

sudo systemctl reload apache2

The content of the site looks like:

  RewriteEngine On
  RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]

  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined

  SSLEngine on
  SSLCertificateFile "/etc/ssl/my_site/certificate.crt"
  SSLCertificateKeyFile "/etc/ssl/my_site/private_key.key"

  ServerAdmin info@my_site
  DocumentRoot /var/www/html



Building angular app with source map fail with “CALL_AND_RETRY_LAST Allocation failed – JavaScript heap out of memory”

I’m building an Angular app with this command:

ng build --prod --configuration=prod --source-map

The versions of Angular and other packages were:

tanguy@tanguy-Aspire-E5-575G:~/Projects/Piximate/web$ ng version

Angular CLI: 6.1.2
Node: 8.10.0
OS: linux x64
Angular: 6.1.1
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

Package Version
@angular-devkit/architect 0.7.2
@angular-devkit/build-angular 0.7.2
@angular-devkit/build-optimizer 0.7.2
@angular-devkit/build-webpack 0.7.2
@angular-devkit/core 0.7.2
@angular-devkit/schematics 0.7.2
@angular/cdk 6.4.2
@angular/cli 6.1.2
@angular/material 6.4.2
@ngtools/webpack 6.1.2
@schematics/angular 0.7.2
@schematics/update 0.7.2
rxjs 6.2.2
typescript 2.9.2
webpack 4.9.2

There is a Github thread about this issue:
But it has never been resolved. However it contains some potential solutions.

What finally worked for me is the solution proposed in this comment: Increase the max size of Node.js for the command by running this:

node --max_old_space_size=8192 node_modules/@angular/cli/bin/ng build --prod --configuration=staging --source-map

To make my life easier, I created an alias for this command in my package.json


// package.json

"scripts": {
  "ng-high-mem": "node --max_old_space_size=8192 node_modules/@angular/cli/bin/ng",
  "build:prod": "npm run ng-high-mem -- build --prod --configuration=prod --source-map",

Note the double dash “–” before passing the arguments of the build. This is needed to ensure theses arguments are not swallowed by npm run and make sure they are passed to ng-high-mem

So I can build successfully with

npm run build:staging