As you can see from the comment by @TiagoCardoso, there is no consensus answer. This is remarkable given that a forum like StackExchange will self-select toward the technically inclined participant. So the the general theme of "It's handy to be technical but not necessary" indicates that having a state-of-the-art grasp of the project technology is not essential.
As per the Project Management Body of Knowledge, the PM spends 90% of his/her time communicating. See Leading technical teams as an agile non technical project manager. You will need to reach out frequently to internal and external stakeholders. The former are team members and supporting personnel and anyone appearing as a task or activity owner on your WBS. External stakeholders are customers, top management, trade associations, other divisions in your firm, or anyone you can influence your project positively or negatively. More on stakeholder management at Working with a "single point of contact" How to transition from programmer to project manager? for more suggestions on making the transition.
So there is no time for you to actually do "real work." As PM, you remove obstacles and encourage progress. That's why non-technical PMs can thrive and gain team member respect and support. The team will appreciate your ability in keeping the budget and resources flowing and keeping sight-seeing managers out of their hair. The team's lead developers should do the technical troubleshooting, with the occasional consultant brought to address the more intractable problems.