Yeah, that's ok.
But if I am completely unaware about the code, I don't know what to search in cscope, or anything about the flow of the code. How do we manage in that situation?
And if you have no task you are aiming at, find the main entry point of the code and start tracing where it goes.
But either way, I would not actually start with the code. The code glues together the data and the UX, so go figure those out first. Use the app. Browse the data schema. Figure out some connections. Once you understand that "datum A" is used in "UX widget B", the code just becomes a middle point to step through to connect them. And stepping through it once for one data field will likely teach you the patterns used in the codebase, so you can apply that learning to everything else.
And don't forget to read documentation. It isn't always kept up to date, but something is better than nothing.