3 ms·

> you can't really run your app in the background This, last I checked, was OEM specific. I agree with your point, most OEMs are indescribably awful about kill

> you can't really run your app in the background This, last I checked, was OEM specific. I agree with your point, most OEMs are indescribably awful about killing any and all background apps - this does not, however, make it Google's fault. I've disabled GApps and the GSF on my phone, but Riot/Element still works quite well with background notifications when it's excluded from battery optimizations. > I could record incoming calls easily. This is still possible, and I do it, with the stock dailer on android 8.1. I use a VOIP provider that offers call recording. As it's my primary number, all my calls are recorded with no interaction on my part. Off-topic, but transcribed voicemail is offered as well - which I think used to be carrier or even iPhone specific. There's lots of functionality in Android that's not natively supported, but that doesn't mean it can't be done :) VOIP provider in question (that I'm not affiliated with) is voip.ms, in case anyone is curious.

Andrew_nenakhov 6y ago
> This, last I checked, was OEM specific. Umm, no. It is nice how you cite your anecdotal evidence about riot, but if you would study this issue a bit you would know, that on Android 1.5 you could launch a background process and it would stay in memory indefinitely, and on recent androids it's only possible with persistent notificaton icon (to which a lot of users complain about). If you don't have the persistent notification, then oops. If you don't want to research this subject yourself, you should probably trust me, because we have an app with >1M installs that depends on being in memory. >> For example, in Android 6 I could record incoming calls easily. Not so much on Android 9, > This is still possible, and I do it, with the stock dailer on android 8.1 Let me check, was Android 8.1 released later than Android 9? Hm, I guess, not. Anyway, this link [1] would be a good place to start to learn more on this subject. Let me cite: "The official API for call recording was removed with the launch of Android 6.0 Marshmallow. Developers are hard to stop, so they found workarounds to keep this feature alive, but Google finally killed off the ability to record calls with Android 9.0 Pie." So, do you agree now with my point that Android is becoming a more and more restricted platform in every way? [1]: https://www.androidauthority.com/record-calls-android-1019109/ https://www.androidauthority.com/record-calls-android-101910...

Andrew_nenakhov 6y ago

> This, last I checked, was OEM specific. Umm, no. It is nice how you cite your anecdotal evidence about riot, but if you would study this issue a bit you would know, that on Android 1.5 you could launch a background process and it would stay in memory indefinitely, and on recent androids it's only possible with persistent notificaton icon (to which a lot of users complain about). If you don't have the persistent notification, then oops. If you don't want to research this subject yourself, you should probably trust me, because we have an app with >1M installs that depends on being in memory. >> For example, in Android 6 I could record incoming calls easily. Not so much on Android 9, > This is still possible, and I do it, with the stock dailer on android 8.1 Let me check, was Android 8.1 released later than Android 9? Hm, I guess, not. Anyway, this link [1] would be a good place to start to learn more on this subject. Let me cite: "The official API for call recording was removed with the launch of Android 6.0 Marshmallow. Developers are hard to stop, so they found workarounds to keep this feature alive, but Google finally killed off the ability to record calls with Android 9.0 Pie." So, do you agree now with my point that Android is becoming a more and more restricted platform in every way? [1]: https://www.androidauthority.com/record-calls-android-1019109/ https://www.androidauthority.com/record-calls-android-101910...