Best workflow when forking and renaming a GitHub project [closed]

I am trying to figure out the best workflow for working with a fork of an existing opensource project in Github. I want to take an existing project and make significant changes to it, in this case to port it to android and add specific android only functionality. I would like to satisfy the following:

1. Be able to pull changes from their public repo to the new android port as the original code is updated.
2. Be able to sumbit changes (via pull requests) to the orginal project when I fix bugs that aren't just applicable to the android port.
3. Have a seperate renamed version of the project to make it clear that it is a Android port. I looked at renaming a fork and Github gave me huge warnings about doing this.

My initial thoughts are I would fork the original project then fork and rename my fork to give me the following repos:

original-author/projectA
nicstrong/projectA
nicstrong/projectA-android

This would allow me to work on my local repo local/projectA-android push changes to nicstrong/projectA-android. Then to update from the orginal project I could rebase nicstrong/projectA to the latest from original-author/projectA then fetch/merge from nicstrong/projectA to local/projectA-android.

My questions are:

1. I am quite new to the whole Git вещь. Это похоже на хорошее подходить? Или есть лучше рабочий процесс для обработки этого сценария?
2. Как мне справиться с выталкиванием из projectA-android обратно в nicstrong / projectA, чтобы я мог настроить пул-реквест для исходного проекта?