We offer a new option for Solodroid project users who want to monetize apps with certain ad networks as an alternative if AdMob experiences problems such as being restricted or even banned. In this case we use the single ads SDK format as a backup ad or even make it the main ad. By using a single ads SDK, the advertising SDK is used only on that ad network SDK so that the size of the aab/apk file when built is minimal or smaller and can minimize problems in publishing to the Google Play Store related to SDKs from other ad networks that may not or do not comply with policies.

Below are several single ads SDK implementation options that we have released and can be used.

Wortise Ads Sdk

1. Open build.gradle (Module: app) and change the implementation to wortise-ads-sdk

implementation 'com.github.solodroid-dev:wortise-ads-sdk:1.+'

2. Open settings.gradle (Project Settings) and update the dependencyResolutionManagement

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        maven { url 'https://jitpack.io' }
        maven { url 'https://android-sdk.is.com/' }
        maven { url 'https://unity3ddist.jfrog.io/artifactory/unity-mediation-mvn-prod-local/' }
        maven { url 'https://maven.wortise.com/artifactory/public' }
        maven { url 'https://artifact.bytedance.com/repository/pangle' }
    }
}

3. Sync Now and the project is ready to be built

For other ad network sdk implementation options, simply change the sdk name in the build.gradle file (Module: app)

AdMob Ads Sdk

implementation 'com.github.solodroid-dev:admob-ads-sdk:1.+'

Unity Ads Sdk

 implementation 'com.github.solodroid-dev:unity-ads-sdk:1.+'

Today, when you want to publish or update an app, Google Play asks for: com.google.android.play:core added the following note for core (1.10.3):

If your app is targeting SDK 34+ (targetSdkVersion), then the PlayCore SDK is outdated and will likely cause crashes in your app! Please update: https://developer.android.com/guide/playcore#playcore-migration

To solve this problem in our code, it is necessary to update the dependencies in the build.gradle (Module: app) file and in the MainActivity.java file. This applies in general to all codes from solodroid.

Step 1 (Updating dependencies)

Open the build.gradle (Module: app) file, find the library implementation below and remove it.

Step 2 (Updating MainActivity.java)

Open the MainActivity.java file, find the following code below, for quick search, use Ctrl + F.
import com.google.android.play.core.tasks.Task;

Replace it with the code below, to make it faster, you can use Ctrl + R to replace the code with a new one:
import com.google.android.gms.tasks.Task;

We provide several choices of ad network libraries that you can customize yourself based on monetization needs for your application.

The library implementation can be managed easily in the Android Studio project dependencies in the build.gradle (Module: app) file

1. AdMob ads sdk (recommended) 👍

5. No ads sdk

Especially for Audience Network, Audience Network, If you choose to use Audience Network Bidding, please select Ad Network Type to be AdMob, Google Ad Manager, AppLovin Max or IronSource These Ad Networks support being a Mediation Partner although it's still a Beta version.

Regarding the addition of the lauch duration of the app in the splash screen, the application has 2 methods:

1. Force display App Open Ads
2. Skip App Open Ads on Start App

If option number 1 is used, then the application works as follows:

• Splash Screen > Load config.json > Load App Open Ads and Show > Start the Main Menu

In the load open ads process, this makes the duration of the splash screen longer because there is a process of loading ads from ad networks and waiting for a response from the ad to be displayed first before the user enters the application.

If option number 2 is used, the application works as follows:

• Splash Screen > Load config.json > Start the Main Menu

In this option, the process of opening the application after splash is faster than number 1, because no open ads are displayed when the user starts the application, but open ads will still appear when the user opens the application from the background to the foreground or when user resume the app.

App Open Ads can be disabled from json remote config.

The first step before changing the logo, it is highly recommended to delete the mipmap folder first

Then, after you delete the mipmap folder, the next steps are as follows:

• Open Android Studio → File → New → Image Asset

• You can choose 2 types of your icon type, that is Launcher Icon (Adaptive and Legacy) or (Legacy Only)

• Recommended to use Launcher Icon (Adaptive and Legacy)

• Browse and choose your image file icon (.png) format with square dimension and start customize your icon

• Make sure the resource name is "ic_launcher" → Next

• Make sure the selected Res Directory is "Main" → Finish

Important Note :

To prevent errors when changing the application logo, make sure you have deleted the mipmap folder first, if not, you need to repeate this steps to change the app logo at least 2 times, because in some cases, when you change the app logo without deleting the mipmpa folder, there may be a problem and the logo is not saved in the mipmap folder, most likely this is a bugs in Android Studio, if this problem occurs, please repeat the steps to change the app logo again and the problem will be resolved.