The only SBAS to provide ranging signals from their GEOs are the USA's WAAS, with healthy ranging UDREIs (a health bit in the SBAS 250bit message) designating it usable for ranging). That being said, I've never seen a WAAS GEO utilized in a position solution on an Android device. Believe its a limitation of both the chipsets and the Android API (ie it would have to be implemented in both). GEO ranging can make a big difference for aviation receivers using them in their position solution, especially when GPS satellites in view are diminished.
Every other SBAS has their UDREIs set to "Do Not Use" for ranging purposes. They use the GEO solely to send the modulated correction messages (250 bps) which does include the almanac (for all GEOs in the SBAS) and ephemeris (for only itself - the broadcasting GEO).
Every SBAS only sends corrections for GPS satellites. There are no corrections sent for Galileo, Glonass, Beidou, etc. This likely will change in the near future, probably lead by Europe's EGNOS as they go v3, which I believe includes multi-constellation.
PRN 134 (shown flagless above in the image) is KASS (Korean Augmentation Satellite System). They are now operational for aviation purposes. There are five SBAS operational and approved for aviation use currently: WAAS, EGNOS, MSAS (Japan), GAGAN (India), KASS.
Several SBAS are starting to send correction messages on L5 as well, for a dual-frequency SBAS solution. About a year ago they released the MOPs on the RTCA site defining how a DF SBAS user receiver should operate. WAAS should likely have a test signal OTA in the next year. Dual frequency SBAS coverage will be limited until the GPS constellation is fully modernized to all DF (L5) capable satellites. During that time, GEO ranging will be more important to availability for aviation receivers. DF SBAS coverage could be improved much sooner if an SBAS goes multi-constellation with Galileo.