Back porting SystemUI

[6020peaks /\/\/\]

Hi,

I am currently running an experiment and I would like to know if back porting the SystemUI is possible at all. Let's say I want to use the Android Q SystemUI in Android P. Did anyone try this before?

If it is not possible what is the reason when it comes to the existing dependencies?

Thanks a lot for any hint!

[Glenn Kasten]

I have not tried this myself.  But I think it is likely to be difficult due to possibility of

the Q SystemUI assuming the existence of Q APIs throughout.

You could try back-porting yourself, but it might be a lot of work.

[Beyblade Challenger]

Easiest thing would be Porting your changes to Android Q. There are lot of framework changes related to apps and platform support.

Thanks

Venu

--
--
unsubscribe: android-porti...@googlegroups.com
website: http://groups.google.com/group/android-porting

---
You received this message because you are subscribed to the Google Groups "android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-porti...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-porting/dc308b5c-5141-42ad-aa13-f25b02e24aa8%40googlegroups.com.

[6020peaks /\/\/\]

I was able to get the build working (migrated the bp files to mk), but then I hit the wall you mentioned with the Q API changes. In the end this task would be like updating to Q manually, which is not the result I wanted. Unless there was something like an internal SDK backwards compatible, I guess there isn't any clean way to achieve a SystemUI back-port.