It is Android. Dumb title.
In principle yes, but AOSP derivatives without e.g. Google Play are not allowed to be marketed as Android, see e.g. on Wikipedia:
While AOSP is free, the “Android” name and logo are trademarks of Google, which imposes standards to restrict the use of Android branding by “uncertified” devices outside their ecosystem.
Or in the FAQ of AOSP:
The function of the Android Compatibility Program is to define a baseline implementation of Android that is compatible with third-party apps written by developers. Devices that are Android compatible are eligible to participate in the Android ecosystem, including Google Play; devices that don’t meet the compatibility requirements exist outside of that ecosystem.
In other words, the Android Compatibility Program is how we separate Android-compatible devices from devices that merely run derivatives of the source code. We welcome all uses of the Android source code, but to participate in the Android ecosystem, a device must be identified as Android-compatible by the program.
I’m on e/OS and it works pretty great. Except phone calls usually won’t hear me unless the mic is enabled before the call rings.
Also it won’t takeT-Mobileas MMS if cell signal is zero.
First one yes, drivers could be better. The second one I’m blaming on T-Mobile.
I have not had issues with t-mobile mms, even when i have no cell signal and am on WIFI calling.
T-Mobile US
fast.t-mobile.com
proxy not set
port not set
user not set
password not set
server not set
MMSC http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS proxy not set
MMS port not set
MCC 310
MNC 260
Auth type not set
APN protocol IPv6
APN type default,supl,is,mms,xcap
APN roaming protocol IPv4
Basically the same as the T-Mobile site except they have MMS protocol as WAP 2.0 and I don’t seem to have that setting.
Edit: changed the last statement as MMS protocol is not in my APN settings
