App Factory Kid App Problem - Foreground Service and Permissions
47 kali dilihat
Langsung ke pesan pertama yang belum dibaca
whitedavidp
12 Mei 2023, 14.32.2612/05/23
kepadaTasker
I am trying very hard to migrate from an an Android 9 LG V40 to an Android 11 Moto XT2213-2.
I have written and employ several kid apps, and in trying to migrate the 1st one, I can see in logcat the following repeated:
Foreground service started from background can not have location/camera/microphone access: service [my kid app's package name]/net.dinglish.android.taskerm.MonitorService.
I have looked at the app's manifest and do not see any of these in the permissions listed for the app. The app certainly does NOT use them.
What to do? I see in the release notes for
v5.7.2.beta - 2019/05/03:
Added android.permission.FOREGROUND_SERVICE permission to factory apps if target API >= 28
But this kid app was made with at least version 6.1.
Damn, I hate how google consistently cripples Android and makes it less useful with each release! If they want Android to be iOS, they ought to just use iOS!
Soudane GMTA
12 Mei 2023, 20.14.3512/05/23
kepadaTasker
On Friday, May 12, 2023 at 2:32:26 PM UTC-4 whitedavidp wrote:
I'm with you 100 percent!
<rant>
And if you really want to see how increasingly user-hostile Google is being, just check out how much more onerous the process of rooting a device has become starting with Android-11. Google is making it easier and easier for apps to find out if a device has been "modded" (in other words, unlocked bootloader, rooted, etc.), and now more and more app developers are jumping onto the bandwagon to cripple their apps when such device modding is discovered.
This has resulted in tools like Magisk and related utilities having to become increasingly complex, convoluted, and error-prone in their efforts to try to hide the presence of modding from Google's detection software. Now, rooting and mod-hiding for these later Android versions involves going down into a crazy, headache-producing, boot-loop-prone rabbit hole, and the complexity and headaches are continuing to get worse.
As Google continues to "improve" (ha ha!) their modding-detection tools, it's becoming more and more of a liability to root devices, because more and more apps are beginning to utilize these detection tools and then cripple themselves when root is detected. This is not only true for "banking" apps, but also games and other kinds of apps. I heard that even the McDonald's app is now starting to do this.
And as for "banking" apps ... the same banks that are trying to "protect" people by crippling their apps' functionality on rooted Android devices don't make the slightest effort to prevent full access from desktop machines, and each and every desktop machine in the world (at least those running Windows, linux, and MacOS) is rooted in the same way that Android can be rooted. And rooted Android devices make a very small percentage of mobile app users and a very small percentage of banking customers, while there are millions upon millions of desktop computers, many of which are continue to be hacked on an ongoing basis via phishing and other attacks, after which keystroke monitors can be installed to capture people's login credentials to banks. Banks do nothing to prevent this, and there is much more fraud (both in terms of the number of incidents and the total amount of money involved) occurring via desktops than via rooted Android devices.
Furthermore, most banks gladly issue their clients totally unprotected access devices: namely, debit cards. It's just as easy for someone to steal my wallet which contains my debit card than it can be for someone to steal my Android device. And stolen debit cards can be easily hacked. Banks don't care in the least about trying to "protect" us by crippling the use of their debit cards.
It's really sad that we're going more and more to a "cashless society".
</rant>
[ ... ]
Damn, I hate how google consistently cripples Android and makes it less useful with each release! If they want Android to be iOS, they ought to just use iOS!
I'm with you 100 percent!
<rant>
And if you really want to see how increasingly user-hostile Google is being, just check out how much more onerous the process of rooting a device has become starting with Android-11. Google is making it easier and easier for apps to find out if a device has been "modded" (in other words, unlocked bootloader, rooted, etc.), and now more and more app developers are jumping onto the bandwagon to cripple their apps when such device modding is discovered.
This has resulted in tools like Magisk and related utilities having to become increasingly complex, convoluted, and error-prone in their efforts to try to hide the presence of modding from Google's detection software. Now, rooting and mod-hiding for these later Android versions involves going down into a crazy, headache-producing, boot-loop-prone rabbit hole, and the complexity and headaches are continuing to get worse.
As Google continues to "improve" (ha ha!) their modding-detection tools, it's becoming more and more of a liability to root devices, because more and more apps are beginning to utilize these detection tools and then cripple themselves when root is detected. This is not only true for "banking" apps, but also games and other kinds of apps. I heard that even the McDonald's app is now starting to do this.
And as for "banking" apps ... the same banks that are trying to "protect" people by crippling their apps' functionality on rooted Android devices don't make the slightest effort to prevent full access from desktop machines, and each and every desktop machine in the world (at least those running Windows, linux, and MacOS) is rooted in the same way that Android can be rooted. And rooted Android devices make a very small percentage of mobile app users and a very small percentage of banking customers, while there are millions upon millions of desktop computers, many of which are continue to be hacked on an ongoing basis via phishing and other attacks, after which keystroke monitors can be installed to capture people's login credentials to banks. Banks do nothing to prevent this, and there is much more fraud (both in terms of the number of incidents and the total amount of money involved) occurring via desktops than via rooted Android devices.
Furthermore, most banks gladly issue their clients totally unprotected access devices: namely, debit cards. It's just as easy for someone to steal my wallet which contains my debit card than it can be for someone to steal my Android device. And stolen debit cards can be easily hacked. Banks don't care in the least about trying to "protect" us by crippling the use of their debit cards.
It's really sad that we're going more and more to a "cashless society".
</rant>
whitedavidp
13 Mei 2023, 12.59.0613/05/23
kepadaTasker
Turns out this is just a warning in the logcat. No idea why it is there since my app doesn't reference those.
But it turns out the reason why my app no longer works on Android 11 is that since Android 10 apps can no longer access /proc/net/arp (anything in /proc/net). Crap!
Balas ke semua
Balas ke penulis
Teruskan
0 pesan baru