Compliance with the OCP principle regarding the controller when developing Android applications?

Question

Android

Actually, there was such a question. This principle is observed when designing business entities (i.e. models in the MVC pattern), but when designing activities, the principle of openness / closeness is not very well observed. Is this due to the fact that the controller is not an object that models some entity of the subject area?
Code example where this principle is violated :

class MainActivity extends Activity
{
         private void someMethod()
         {
                  SuperClassName objectName = new SubClassName(); // здесь нарушается принцип OCP 
                  ...
         }
}

Of course, to solve this problem, you can pass a reference to the derived class as a parameter to the "someMethod" method. Only the client code should do it. Apparently, the activity is already the client code. So?
An example of code where this principle is observed :

class MainActivity extends Activity
{
         private void someMethod(SuperClassName objectName)
         {
                  objectName.methodName();
                  ...
         }
}