Allow only broadcasts you want for each app.
With this app you could prevent apps to receive broadcasts, e.g. "SD-card inserted" oder "W-Lan connected".
All with Android-18 shipped broadcast actions are integrated. Others will be collected from time to time and marked with an exclamation sign in the app.
Technical limiation: Actions wich are only sent and not received by any app could not be found.
Changed settings are applied after a reboot. For BOOT_COMPLETED please use the app BootManager.
To restrict system apps you have to donate. The key of "BootManager" is recognized by this app too!
Important:
This app needs the Xposed Framework. The framework requires root access for installation. Don't forget to enable the module in Xposed. You can grab it here: Xposed Installer
Donation:
No self-promotion in the app.
System apps could also be selected
Sorting by action, not only by app name
You support this app and further development!
Website: http://tinyurl.com/pkos9om
Play Store: http://tinyurl.com/p3dqxj2
Xposed Repository: http://tinyurl.com/q9u2l8o
Changelog: http://tinyurl.com/njov9yd
My personal intension to create this app:
There was no app which could do this
Translation:
You could find here a interface to translate the english strings: http://tinyurl.com/okycacj
A free account of www.oneskyapp.com is required to edit. Additional, please attach your email address or send it via PM
Kudos to you! This is great for development purposes!
However, you must warn the user that disabling Broadcast for some app just because he[user] thinks that might be a good idea is bad and user should think twice, as disabled Broadcast can result in a vary of results - from no effect to system crash.
For example, your favorite launcher is listening for the broadcast for call state. You're thinking - Ah-ha, it's spying on me! And you disable the broadcast. And then you are surprised, why does Phone app icon stopped displaying missed calls.
great thanks for that :good:
Dr.Alexander_Breen said:
However, you must warn the user that disabling Broadcast for some app just because he[user] thinks that might be a good idea is bad and user should think twice, as disabled Broadcast can result in a vary of results - from no effect to system crash.
For example, your favorite launcher is listening for the broadcast for call state. You're thinking - Ah-ha, it's spying on me! And you disable the broadcast. And then you are surprised, why does Phone app icon stopped displaying missed calls.
Click to expand...
Click to collapse
I'm not sure about wich i should warn, potentially are all dangerous to disable.
eg the brodcasts to update a widget are useless for you if you don't use a widget of the app. But you should not disable it if you are using the widget...
And some actions i do not even know, because the ReceiverStop collects them if you are using your apps...
Btw, the release of today shows a logfile with newly added actions.
defim said:
I'm not sure about wich i should warn, potentially are all dangerous to disable.
eg the brodcasts to update a widget are useless for you if you don't use a widget of the app. But you should not disable it if you are using the widget...
And some actions i do not even know, because the ReceiverStop collects them if you are using your apps...
Btw, the release of today shows a logfile with newly added actions.
Click to expand...
Click to collapse
No, you must not warn out every broadcast. Virtially, there is infinite set of them, as I can create my own broadcast as easy as 1-2-3. Just show the warning at the start that it's better not to meddle with the system app's broadcasts and that even user-installed apps can cause side effects without some broadcasts.
Dr.Alexander_Breen said:
No, you must not warn out every broadcast. Virtially, there is infinite set of them, as I can create my own broadcast as easy as 1-2-3. Just show the warning at the start that it's better not to meddle with the system app's broadcasts and that even user-installed apps can cause side effects without some broadcasts.
Click to expand...
Click to collapse
Warn about all? Good point
I'm wondering where's the best place. At startup is the changelog shown (if updated) and a message about xposed, if not installed/active. So it could be nothing is been read...
defim said:
To restrict system apps you have to donate.
Click to expand...
Click to collapse
How to donate? I click the bottom part within the module - no reaction whatsoever...
Edit: ok, that was through the website. I donated and received the key file! :good:
But... why "Maps" is not is the list of apps...?
Thanks...
Looki75 said:
How to donate? I click the bottom part within the module - no reaction whatsoever...
Edit: ok, that was through the website. I donated and received the key file! :good:
But... why "Maps" is not is the list of apps...?
Thanks...
Click to expand...
Click to collapse
Hi, i've planned to put donator apps for each app to the market, but had not time yet.
If a app is not shown, no receivers are detected for it unitl now. You could do:
1) show all apps by enable in settings. Then you have only the option to "diable all, even unknown"
2) or open (in this case) Maps and wait. If it gets a broadcast ReceiverStop adds it to internal list and 1) is not needed
Adding new receiver actions are always logged, independet if logging of allowed/denied is enabled
Dr.Alexander_Breen said:
No, you must not warn out every broadcast. Virtially, there is infinite set of them, as I can create my own broadcast as easy as 1-2-3. Just show the warning at the start that it's better not to meddle with the system app's broadcasts and that even user-installed apps can cause side effects without some broadcasts.
Click to expand...
Click to collapse
I've added a warning dialog in the latest version
defim said:
Hi, i've planned to put donator apps for each app to the market, but had not time yet.
Click to expand...
Click to collapse
How will then work the donation I made? Is there a possibility for me to appear like I bought the donation app?
This way, in case I wipe the phone, I can download from play store the donation app and don't need to bother you with e-mails "hey give me again the license file..."...
And will the donation app work as well for both "bootmanager" and "stopreceiver"?
defim said:
If a app is not shown, no receivers are detected for it unitl now. You could do:
1) show all apps by enable in settings. Then you have only the option to "diable all, even unknown"
2) or open (in this case) Maps and wait. If it gets a broadcast ReceiverStop adds it to internal list and 1) is not needed
Adding new receiver actions are always logged, independet if logging of allowed/denied is enabled
Click to expand...
Click to collapse
Strange... I did "show all apps" and Maps is here. This is OK.
But the yellow "!" appears side to it... doesn't it mean that receivers were used?
But at the same time, when I click on Maps, there is only the "stop all" line... that sounds not consistent...???
Maybe a sign of a bug?
Anyway, very good job! THANKS!!!
@Looki75:
I'm not sure yet of the donation apps. But i think it should be again 1 app for the 2.
On the 1st view are packages shown, system apps have a "!" -> could be more dangerous to change sth
On the 2nd view with the receivers of each app, evere action which is a custom action (= not listed in broadcast_actions.txt of Android platform-18 sdk) has a "!". These non-default actions have to be collected by the app.
So it's consistent Maybe not the same icon for both would be better...
Are you sure Maps receives broadcasts? I tried to get Manifest.xml by the apk, but apktool failed -.-
defim said:
@Looki75:
I'm not sure yet of the donation apps. But i think it should be again 1 app for the 2.
On the 1st view are packages shown, system apps have a "!" -> could be more dangerous to change sth
On the 2nd view with the receivers of each app, evere action which is a custom action (= not listed in broadcast_actions.txt of Android platform-18 sdk) has a "!". These non-default actions have to be collected by the app.
So it's consistent Maybe not the same icon for both would be better...
Are you sure Maps receives broadcasts? I tried to get Manifest.xml by the apk, but apktool failed -.-
Click to expand...
Click to collapse
Ok... I think I understand... your module is about BROADCASTS... I'm not a dev and not familiar with these... but is it the same than Autostarts (https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts)?
My dream is to have the exact same functions than Autostarts in an Xposed module.
You might wonder why... well as strange as it sounds, I have Xposed framework but I am un-rooted. So I can use modules, but I can't use Autostarts for example...
I thought your module would be this "similar", but there are more stuff shown in Autostarts than is your module...
You talk about "broadcasts" and Autostarts or similar (root toolbox for example) talk about "receivers for certain events"... is there a difference?
Is it a big deal to expand the scope of your module to equal Autostarts functions?
Thanks for your help!
@Looki75:
After talking a look at the screenshots of Autostarts, it seems that these are all broadcast receivers, so the apps should do the same (with other methods: root/xposed). My app has no nice-names for the action names. So i wonder how Autostarts shows receiver names which a apps creates by its own? Which actions did you miss exactly in my app? Maybe they are not related to broadcats.
I think extending ReceiverStop is not so a good idea, because it's only for intercept receiving broadcasts of app. But maybe a seperate app. I used LBE some time and I didn't like that it has much things i did not need.
defim said:
@Looki75:
After talking a look at the screenshots of Autostarts, it seems that these are all broadcast receivers, so the apps should do the same (with other methods: root/xposed). My app has no nice-names for the action names. So i wonder how Autostarts shows receiver names which a apps creates by its own? Which actions did you miss exactly in my app? Maybe they are not related to broadcats.
I think extending ReceiverStop is not so a good idea, because it's only for intercept receiving broadcasts of app. But maybe a seperate app. I used LBE some time and I didn't like that it has much things i did not need.
Click to expand...
Click to collapse
When you look at these:
http://forum.xda-developers.com/showpost.php?p=35634745&postcount=11040
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
it seems that MAPS has much more than that...
However, I just installed Autosarts on my phone and it shows nothing, just like in your module...
So I guess we're ok.
Thanks!
Looki75 said:
When you look at these:
http://forum.xda-developers.com/showpost.php?p=35634745&postcount=11040
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
it seems that MAPS has much more than that...
However, I just installed Autosarts on my phone and it shows nothing, just like in your module...
So I guess we're ok.
Thanks!
Click to expand...
Click to collapse
I don't know what this other app does. Maybe it shows sometimes simply all recevers for every app.
But I know that ReceiverStop shows per app the specific actions.
There is now a donation app available in Play Store for this app. (1 donation for both, ReceiverStop+BootManager)
I'm looking for a way to disable SMS and missed calls notifications from appearing on the stock (clock) lock screen widget on my rooted Note 3 (running 4.3). Could this tool acheive this and if so, how?
The following entries were logged when not answering a call and a call notification is shown on the lock screen:
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.sec.android.SimpleWidget - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: netgenius.bizcal - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.umang.dashnotifier - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.roymam.android.notificationswidget - android.intent.action.USER_PRESENT
[ReceiverStop] 2013-11-22 15:07:20 handle not: com.sec.android.app.controlpanel - android.intent.action.PACKAGE_RESTARTED
Would I simply be able to disable android.intent.action.USER_PRESENT in the SimpleWidget app to disable the SMS being displayed in the lock screen?
What is the risk of trying this out?
Happy to donate if this will do the above.
Thanks,
Eddie
@sireddie:
I think android.intent.action.USER_PRESENT is not the right action.
From http://developer.android.com/reference/android/content/Intent.html:
Broadcast Action: Sent when the user is present after device wakes up (e.g when the keyguard is gone).
Click to expand...
Click to collapse
Just open ReceiverStop and look which actions are listed for the app. I'm using "SMS Unread Count" widget, which has only android.appwidget.action.APP_WIDGET_UPDATE, so this could be the right. (I've blocked APP_WIDGET_UPDATE for all apps i'm using, but without widget)
Risk? I think it's low. It could be that something does not anymore what you expected To be save, do a android backup - i've never needed one
I've just added strings for translation to the first post. If you attach here a translation, please send me you email address via PM.
Notice to @kalashenicof @jzak1083 @vipa
Dear friend!
The receiver "android.provider.Telephony.SMS_RECEIVED" is blocked
But receiver "android.provider.telephony.SMS_RECEIVED" is constantly being allowed
("Telephony" vs. "telephony")
Please fix it! Viber application is listening to both of them!
katada1 said:
Dear friend!
The receiver "android.provider.Telephony.SMS_RECEIVED" is blocked
But receiver "android.provider.telephony.SMS_RECEIVED" is constantly being allowed
("Telephony" vs. "telephony")
Please fix it! Viber application is listening to both of them!
Click to expand...
Click to collapse
Yes, Viber could receive both. ReceiverStop collects all receiver actions it could get on your device. If you open the GUI it build a list of apps and their receiver. If one receiver is missing, it was never been seen on your device. So it should not be a problem. Btw, if you select "deny all", this will also handle never seen before receiver.
Does you know which app should send this misspelled "android.provider.telephony.SMS_RECEIVED"?
Related
Whenever I scan an NFC tag I created with NFC Tag Launcher it brings up a prompt that says "Open in browser" with options for OK and Cancel. However, it does not do that for tags I create in Lightflow for turning sleep on or off. Is there any way to disable this prompt?
Can't offer any help but I'm having the same problem with NFC Task Launcher.
I too get this. Not sure why. I'm on a rooted Verizon S3.
Download an app for NFC from the market first, then overwrite the default command that was stored on it. Most likely the command was to redirect you the site of the brand or seller of the tag.
nunyabiziz said:
Download an app for NFC from the market first, then overwrite the default command that was stored on it. Most likely the command was to redirect you the site of the brand or seller of the tag.
Click to expand...
Click to collapse
These are blank tags that I wrote to myself. I click OK every time and it never opens anything in the browser.
Have you verified that it was blank or have you erased the tag yet? I had the same issue with blanks that were not completely blanks.
nunyabiziz said:
Have you verified that it was blank or have you erased the tag yet? I had the same issue with blanks that were not completely blanks.
Click to expand...
Click to collapse
How can I tell if it's blank? According to NFC Tagwriter by NXP it's blank, and according to NFC TagInfo, the first two pages are read-only factory locked..
What do you have using NFC taginfo under "NDEF"?
nunyabiziz said:
What do you have using NFC taginfo under "NDEF"?
Click to expand...
Click to collapse
The blank tags have no message. One that I've written with NFC Tag Launcher has a message of the following:
Code:
WELL-KNOWN: urn:nfc:wkt:U(URI)
Identifier: 0x03("http://")
"tags.to/ntl"
MIME: ntl
enU:2:M:0,Q:-1;O:7;E:h:1__3:M:2;S:2;E:h:0
One written by lightflow has the following:
Code:
MIME: application/vnd.lightflow
SleepToggle
I would imagine the first part is what's causing it, but I don't know what there is to do about it.
EDIT: looks like that URL goes to the play store page for NFC Tag Launcher. Not sure why it's not actually opening in the browser though.
I personally use "NFC task launcher" and "erase tag" option.
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
Sounds like you got it figured out.
nunyabiziz said:
I personally use "NFC task launcher" and "erase tag" option.
Click to expand...
Click to collapse
The issue is that I'm pretty sure it's NFC Tag Launcher that's writing the URL to it when it writes the task to the tag. I don't know what I'd do to write the tasks out to the tag otherwise.
I use NFC Task Launcher's erase function as well. As soon as the tag is written to again, this issue occurs.
jh120 said:
I use NFC Task Launcher's erase function as well. As soon as the tag is written to again, this issue occurs.
Click to expand...
Click to collapse
And did you write a task to the tag after? The NFC tag will always be detect, even blanks. It will just try to launch a unknown command.
nunyabiziz said:
And did you write a task to the tag after? The NFC tag will always be detect, even blanks. It will just try to launch a unknown command.
Click to expand...
Click to collapse
The issue is that the act of writing the task with NFC Task Launcher writes the URI to the tag. So erasing then rewriting the task accomplishes nothing.
I dont know all tags are the same size so maybe my tags are different. Im using web evolved tags and by default until erased and written to the tags will launch my browser and redirect to their site.
nunyabiziz said:
I dont know all tags are the same size so maybe my tags are different. Im using web evolved tags and by default until erased and written to the tags will launch my browser and redirect to their site.
Click to expand...
Click to collapse
Yeah, this isn't caused by anything with the tags themselves, it's just that NFC Tag Launcher adds the URI to the tag when you write out a task no matter what.
I can confirm that this happens regardless of tag type. I erased an old NFC-capable train ticket and wrote a wi-fi toggle to it. It works, but the browser dialog box still pops up.
Yeah, it's NFCTL writing that URL to the tag.
That URL is used as the intent filter and serves a few purposes. 1.) it saves space over a longer custom mime type or application specific record (which stores the package name). 2.) it directs anyone who doesn't have to the app to the play store to get it so that the tag actually does something - an application specific record does the same thing but has to store the *entire* package name (28 bytes in this case).
The way this has worked on *every* other device (and the way it should work in Android) is that the entire NDEF message hits the intent filter for that URL and the message is then delivered to the app. The app then grabs all records from the message (there are two) and parses the second record and executes those actions.
Given what the OP has sent me for some reason the Verizon S3 isn't doing this. (The international and ATT version work as expected).
Given that it's showing the chooser it's missing the specific intent filter and showing a dialog for what to do with this URL:
Code:
D/NfcService( 909): TAG: Tech [android.nfc.tech.MifareUltralight,
android.nfc.tech.NfcA, android.nfc.tech.Ndef]
D/NfcService( 909): Attempting to dispatch tag with override
D/NfcService( 909): No activities for NDEF handling of Intent {
act=android.nfc.action.NDEF_DISCOVERED dat=http://tags.to/ntl (has
extras) }
However it's still delivering the payload to NFCTL as the actions get executed (which it shouldn't do if you're getting the browser chooser dialog). It shouldn't work this way, literally. If you get the chooser it should deliver the entire payload to the chosen app (it's not).
So, what can we do here? I can add an option to use an application specific record in place of the URL. This should ensure it doesn't happen but at the cost of space - you'll lose 15+ bytes of space on the tag as a result though as it will write a separate NDEF record to the tag containing the full package name.
Is there anyone with a Verizon device this *isn't* happening for?
I could in theory get this into a release tomorrow as I'd want to have this squashed pre release.
I've been playing around quite abit with this and I have "sort of" gotten around this by use the Tasker URL Launcher.
With TUL installed along with tasker, I can use another NFC writer utility to create the url of tasker://taskname
Now if I touch the new tag without NFCTL installed I will be prompted with the "New Collected Tag" screen....unfortunately its still not an autorun but I can tap the "new tag" and the sequence fires correctly.
Obviously as previously stated the problem is the interception by the phone of the URL string used by NFCTL. Personally I have rooted and ripped out most all the Verizon bloat so I'm unsure what is left to cause this interception.
Let me know and I'll test whatever.
konman2k4 said:
I've been playing around quite abit with this and I have "sort of" gotten around this by use the Tasker URL Launcher.
With TUL installed along with tasker, I can use another NFC writer utility to create the url of tasker://taskname
Now if I touch the new tag without NFCTL installed I will be prompted with the "New Collected Tag" screen....unfortunately its still not an autorun but I can tap the "new tag" and the sequence fires correctly.
Obviously as previously stated the problem is the interception by the phone of the URL string used by NFCTL. Personally I have rooted and ripped out most all the Verizon bloat so I'm unsure what is left to cause this interception.
Let me know and I'll test whatever.
Click to expand...
Click to collapse
I may add a quick option tomorrow morning and throw a test APK up here. If the Verizon release is anything like the International and US pre-orders I suspect we'll see a lot of downloads and this is a *really* annoying thing to happen. So far Samsung takes the crown from HTC's head as the OEM making the weirdest changes.
Background
Starting with the GS4, Samsung removed the ability to see SysScope status. As you S3 users may know, this is the "Root Detection" software that runs on devices. It has 3 status's, Scanning, Normal, and modified. The results of this status gets sent off to the RIL layer as the form of an AT command (AT+SYSSCOPE) in order to be remotely queried by whoever.
What does Sysscope Query?
Files-
/proc/stat - not sure why, but it does
/proc/cmdline - checks for authorized kernels
/proc/task - not sure why
busybox - in any classpath
su - in any classpath
/proc/mounts - Checks if /system is in RW mode
Props-
ro.csc.sales_code - Read my rant in S3 dev section, DO NOT CHANGE THIS VALUE TO LOLs
ril.sales_code - See above
ro.secure - adb props
ro.debuggable - adb props
Does this App let me change status?
NO. This app does not modify any stock functionality it just gives you the ability to see what status you are passing. You will see what your Carrier/whoever else knows about the SysScope status of your device.
Using App:
Test 1:
First push apk to SYSTEM/APP. This is important and I do not believe it will work in /data/app.
Open the app. Go to menu -> Preferences. Turn on "Start on SysScope Event". This will automagically open the app whenever an event is received.
Reboot the device. Wait about 30 seconds. The app should open and show a response.
If the app did not start at all after boot, you likely have a -1 and failed SysScope with a modified.
*Once it is queried you can turn off the SysScope preference*
Test 2:
Click the read button and allow root access.
What the status's mean: (GS4 specific, app works on GS3 just do not know status's)
-1 means scanning. If the state stays at a -1 for more than 120 seconds, it means the device is modified (Sysscope was removed)
0 is also a failure. It means sysscope was removed
1 is a Status of NORMAL. This is what stock roms will return
2 is a status of MODIFIED.
If the app did not start at all after boot, you likely have a -1 and failed SysScope with a modified.
Thanks
Eschelon/Ziggy471/NxtGenCowboy/Virus for testing/being awesome!
See if you can find the hidden Ziggy easter egg
Mines
Thank you for all your hard work and meticulous attention to privacy! It is much appreciated, especially in these times.
Just to clarify, is the purpose of this to help anyone who is working on a workaround to "fool" the SysScope app into thinking that the device is unrooted/unmodified (ie to remove the custom padlock splash screen at boot)?
CPA Poke said:
Just to clarify, is the purpose of this to help anyone who is working on a workaround to "fool" the SysScope app into thinking that the device is unrooted/unmodified (ie to remove the custom padlock splash screen at boot)?
Click to expand...
Click to collapse
Yep, we like giving users visibility to see mods done like this so they do not have to take dev's words for it. Always a fan of giving everyone a way to test for themselves. The S3 had a menu item right in settings, this brings back that removed functionality.
TrevE said:
Yep, we like giving users visibility to see mods done like this so they do not have to take dev's words for it. Always a fan of giving everyone a way to test for themselves. The S3 had a menu item right in settings, this brings back that removed functionality.
Click to expand...
Click to collapse
Awesome, I was hoping that's what it was for
@TrevE Sorry to revive old thread, but did you reverse this thing? What is the code used for the AT, and where can I find it? What other binaries are involved in this. I'm on 4.2.2...
Hi TrevE can I get the AT code as well please? Maybe you could pm it to me? Thanks.
Can sysscope be the reason why backup manager plus will not work anymore? This could help
Is sysScope used for tracking the phone, mirroring it, or anything else like that
Xposed app firewall.
This app is an firewall for the installed apps. Only apps with permission "android.permission.INTERNET" are
shown. IPv4 and IPv6 are supported together with TCP and UDP. You could configure outgoing and incomming
connections independent from each other.
The rules could be applied for each network: W-Lan, local network, mobile, roaming, unknown.
Logging is configurable for incomming/outgoing and allowed/denied connections.
Colors:
Blue: Template is used.
Yellow: Custom settings.
Green: The app is trusted.
Red: The app is blocked.
Features:
No iptables required, the kernel doesn't need to support it.
The firewall is active when Android starts, no startup data leak.
The rules are always active, no re-apply on connection change is needed.
Limitiation:
Host names in the log file are PTR entries.
Works only for Android (Java), not the native (Linux) part
Donation:
No self-promotion in the app.
You could trust or block an app (Menu/ActionBar)
You could use a template for not configured apps
Additional (experimental) networks: Bluetooth, WiMAX, Ethernet
Tasker support, per App
You support this app and further development!
Permissions:
ACCESS_SUPERUSER: apply iptables rules
This app does not connect itself to any websites or hosts!
Important:
This app needs the Xposed Framework. The framework requires root access for installation. Don't forget to enable the module in Xposed. You can grab it here: Xposed Installer
Website: http://tinyurl.com/l5bpv23
Play Store: http://tinyurl.com/ome2pvc
Xposed Repository: http://tinyurl.com/ksc6plz
Changelog: http://tinyurl.com/n8gsqja
Why this app? No firewall for Xposed exists yet
Translation:
You could find here a interface to translate the english strings: http://tinyurl.com/okycacj
A free account of www.oneskyapp.com is required to edit. Additional, please attach your email address or send it via PM
Insane.. I was looking for something like this about 12 hours ago.. its almost like you read my mind and made it just for me!.
I like your style. Nice and simple and keeping it in line with your others.
Sent from my GT-I9300 using Tapatalk
Downloading now.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shivadow said:
Insane.. I was looking for something like this about 12 hours ago.. its almost like you read my mind and made it just for me!.
I like your style. Nice and simple and keeping it in line with your others.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Maybe you head me thinking loud 6 weeks after starting this app: "i will release today, if there are still error, i'll fix them later"
Am I correct in assuming this is not open source?
I got a question about incoming/outgoing connections, maybe somone else want to know:
Incoming connections are used by less than 1% of all apps. This is used if the app is a "server", like BubbleUPnP. So most time incoming conections could be blocked, i think for mobile network 100%.
An outgoing connection is like a phone call: You call someone (outgoing connection), and can talk (send "data") and hear (receive "data")
Wifi Internet and Network:
If you want to control eg your local tv-receiver, xbmc device or avm router (with FreetzMobil), only connections to the local network are required. This prevents app to send data to the internet.
The "local network" are all "private" IPv4 and IPv6, they will not be forwarded by internet routers. Additionally, if you use "public" IPs they are local if it is in the same subnet as a ip of your device. Uncommon for IPv4 usage, but public IPv6 are the common usage (public IPv6 for every device)
an0n981 said:
Am I correct in assuming this is not open source?
Click to expand...
Click to collapse
As usual i send source only to people i know
I took this mod for a quick test drive, a little feedback:
-Is it not possible to restrict kernel?
-Could it be that apps that use native libraries to connect to the internet cannot be restricted? Firefox and Mega (both use native libraries) were able to connect even when completely restricted.
Also a little cosmetic issue com.android.process.gapps showed completely green at all times. However restrictions were applied properly
an0n981 said:
I took this mod for a quick test drive, a little feedback:
-Is it not possible to restrict kernel?
-Could it be that apps that use native libraries to connect to the internet cannot be restricted? Firefox and Mega (both use native libraries) were able to connect even when completely restricted.
Also a little cosmetic issue com.android.process.gapps showed completely green at all times. However restrictions were applied properly
Click to expand...
Click to collapse
Yes, see OP: "Limitiation: ... no native binaries." This is because the design of Xposed
Isn't it "com.google.process.gapps"? Onyl this one app has the wrong colors? Has it a green dot for "trusted app"? What did you configured for it?
Yes I meant com.google....
I set it from template to custom, blocked everything, however in the app overview it still showed as all green. When it was restricted GCM was blocked and the log showed blocked connections to mtalk.google.com:5228. Then I unrestricted outgoing mobile and wifi and GCM was available and the log correctly showed allowed connections but the colors in the app overview didn't change
Version 1.0.1 uploaded
- fix "incoming" thx @w0rinal
- also an error related to coloring, @an0n981 can you check if it fixes your problem? Toggling options could be required
defim said:
- also an error related to coloring, @an0n981 can you check if it fixes your problem? Toggling options could be required
Click to expand...
Click to collapse
Sorry the bug is still present
Also 1 more questions. Do you see any problem running this along side AFWall?
The bug affects any app that starts end ends with <>. <android.media> and <org.mozilla.firefox.sharedid> also always revert back to displaying completely green once the app is reloaded
an0n981 said:
Also 1 more questions. Do you see any problem running this along side AFWall?
Click to expand...
Click to collapse
No, should work without problems. The one created iptables rules other hooks the connection methods - if one fails, the other does it
an0n981 said:
The bug affects any app that starts end ends with <>. <android.media> and <org.mozilla.firefox.sharedid> also always revert back to displaying completely green once the app is reloaded
Click to expand...
Click to collapse
The "<>" entries are not real apps (.apks) with a package name, they are uids. At app start i load all installed apps with internet-permission and hide apps which are no more installed / have not any longer the permissions -> the uid items are not in the list of installed apps (obviously)
Will be fixed in next release
EDIT: Uploaded
This is awesome ?
A few questions:
- is there a way to edit template? I couldn't find it anywhere in settings- am I missing something?
- Can you add multiple selection? For example, someone has lots of apps and wants to block roaming to them etc. etc. without having to change it manually for each app.
- filtering or sorting apps? perhaps something simple like the way afwall , or a more thorough filter like XPrivacy has?
Sent from my Nexus 5 using Tapatalk
defim said:
The "<>" entries are not real apps (.apks) with a package name, they are uids. At app start i load all installed apps with internet-permission and hide apps which are no more installed / have not any longer the permissions -> the uid items are not in the list of installed apps (obviously)
Will be fixed in next release
EDIT: Uploaded
Click to expand...
Click to collapse
Confirmed fixed
jaibar said:
This is awesome ?
A few questions:
- is there a way to edit template? I couldn't find it anywhere in settings- am I missing something?
- Can you add multiple selection? For example, someone has lots of apps and wants to block roaming to them etc. etc. without having to change it manually for each app.
- filtering or sorting apps? perhaps something simple like the way afwall , or a more thorough filter like XPrivacy has?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The template is used for all "blue" apps, which where are not configured by user. Modifying template is part of the donator options (see OP).
Btw, next planned feature: detection of VPN connections
defim said:
The template is used for all "blue" apps, which where are not configured by user. Modifying template is part of the donator options (see OP).
Btw, next planned feature: detection of VPN connections
Click to expand...
Click to collapse
Nice feature !
I dry tested this app (i.e. not checked in the Xposed module on my device) and already saw that the VPN was missing. Now I use AFWall+ which is good and has more profiles. I block all Google apps with it with a 'limited internet' profile and every time I download something from Play, I load another profile which allows 'Google Play services' and 'Google Play store' internet connection and after download/update I revert to 'Limited internet'.
On my Mac I have 'Little Snitch' firewall which has the ability to let it prompt for certain apps which I don't want to be connected permanently (such as the Mac App Store), but only when I do e.g. an OSX update. In that case I let it prompt and say 'only this time'.
A similar approach on LightingWall should be very welcome. E.g. a notification that the Play store wants to connect with internet and when one wants to download / update an app, say 'only this time' and not permanently.
mermaidkiller said:
Nice feature !
I dry tested this app (i.e. not checked in the Xposed module on my device) and already saw that the VPN was missing. Now I use AFWall+ which is good and has more profiles. I block all Google apps with it with a 'limited internet' profile and every time I download something from Play, I load another profile which allows 'Google Play services' and 'Google Play store' internet connection and after download/update I revert to 'Limited internet'.
On my Mac I have 'Little Snitch' firewall which has the ability to let it prompt for certain apps which I don't want to be connected permanently (such as the Mac App Store), but only when I do e.g. an OSX update. In that case I let it prompt and say 'only this time'.
A similar approach on LightingWall should be very welcome. E.g. a notification that the Play store wants to connect with internet and when one wants to download / update an app, say 'only this time' and not permanently.
Click to expand...
Click to collapse
Xprivacy implements a similar thing, allowing the user to be informed when one of the restrictions are asking for access of that permission, including internet permissions(no distiction between lan or vpn), i would also welcome an on demand prompt feature for this app, its one faeture i wished afwall had, but believe it cant because of the nature of iptables i believe,
Saying that im also kinda worried that this might conflict, two apps essentially fighting for control to "pause" the system, hope im wrong, maybe if the two devs of the two respective apps co-orporated in implementation,it might be resolved, if there is an issue, i dont know........... but im getting ahead of myself here, defim has not even stated that he'll implement this, still, no harm in discussing possibilities, slim or not
@banderos101 @mermaidkillerIf you want to be informed if an app is allowed or denied to access some hosts, you could get it with Tasker. Just with a simple message box or more enhanced things Tasker can do. It should not be a problem using this app wiht Xprivacy, AFwal etc. If you block a connection with one app, it could be that the others can't see/log it. This depends on the order of the apps, An iptables firewall should be the last the connection is passing.
A per host filter is not planned, if you want to stop connection to some (tracking, malwar, adware) hosts a hosts file filter could be used, like my UnbelovedHosts
defim said:
As usual i send source only to people i know
Click to expand...
Click to collapse
Too big a risk to take for security software like this. Post your work up on Github under a reasonable license.
I'm not seeing a big advantage over the GPL AFWall+ anyway.
Hi there.
i have used google up and down. But didn't find one example how to do this. I even don't know if this is possible.
I want to disable a receiver for a particular app. I have root. For example i have this:
android.intent.action.CONFIGURATION_CHANGED:
BroadcastFilter{edb90ff u0 ReceiverList{178f01e 568 system/1000/u0 local:f47ec59}}
BroadcastFilter{5ff4d53 u-1 ReceiverList{1275942 568 system/1000/u-1 local:c9f738d}}
BroadcastFilter{9e64aaa u0 ReceiverList{bb72995 10860 com.google.android.gms.persistent/10010/u0 remote:193d54c}}
BroadcastFilter{61ba762 u0 ReceiverList{9d9a62d 11015 com.google.android.gms/10010/u0 remote:7668544}}
can i block one of this receivers? if yes, how??
pm disable com.google.android.gms.persistent/android.intent.action.CONFIGURATION_CHANGED doesn't work. also with ./ not. Other combinations won't work either.
can i block somehow a underlying permission? i don't think so.
is system also a package? i cant find it. I only find it in the processlist with ps.
any ideas??
I know this is a very old thread. But it is Very interesting indeed. I found some apps in the play store that do exactly that but there not very beatufiul and also not open source. I'm planning on building one myself and trying right now to debug the process on how to disable receivers from the apps with no progress so far...
LuigiTheHunter said:
I know this is a very old thread. But it is Very interesting indeed. I found some apps in the play store that do exactly that but there not very beatufiul and also not open source. I'm planning on building one myself and trying right now to debug the process on how to disable receivers from the apps with no progress so far...
Click to expand...
Click to collapse
I also know this is old... I had an app that could disable receivers and services inside an app without root. I've been trying to find it for weeks...
I used it to disable basically everything inside OneUi except the app switcher. If I fully disable OneUi I save lots of battery but then app switch doesn't work
THIS TUTORIAL IS GEARED TOWARDS THOSE THAT HAVE THE VERSION OF THE PHONE WITH CHINESE FIRMWARE,MAY BE USED AS A GENERAL GUIDE FOR OTHER VERSIONS.
The subject of app/bloatware removal/disabling has been mentioned in a few threads throughout the Oppo Find X forum,so,I thought I'd start a thread to centralize the topic.
As w/any mods go,this is one that's fairly harmless,worse case scenario,a factory reset will get you back on track,but,ultimately everyone is responsible for their own phone & what happens to it.
With that out of the way..............
1) Any app that can be easily uninstalled by the "uninstall" button is 100% safe,no harm whatsoever. If you want,d/l an apk extractor tool app to make a copy & store wherever,should you change your mind.
2) Now,most are interested in getting rid of as many of the OPPO system apps as possible w/o crippling wanted functionality. This will be an evolving list,& gradually adding to it,with input from anyone interested,I'll update the list right here.
3) OK,the How-To is right here https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
4) Any input regarding adding to the list is encouraged.
If you have something to add to the list that you're tried out yourself,please include any effects on functionality that may have resulted,especially if it affected other apps & their functionality,good,bad,or otherwise.
5) Once again,tried & tested input is highly encouraged & welcome. I'm open to suggestions on trying out app removal that ventures into uncharted territory,however,depending on what it is & how/when I'm using my phone,it might be a few days before I'm free for Guinea Pig duty..... :laugh:
6) Touching on point #5,if,for whatever reason,one is in no position to go into uncharted waters w/this,that's fine,I just recommend waiting a few days after the apps that you're interested in removing 1st,check the list & dates below. No one wants a borked phone that needs reset at an inoppportune time to get things restored to useability.
I myself won't be able to test every day,I get it,so,if you can't test things for yourself & share here,that is perfectly OK,JUST HANG IN THERE UNTIL THE SAFE LIST IS STABLE FOR A FEW DAYS BEFORE PROCEEDING.
The list will grow & evolve/be edited on a continuous basis until we all get it figured out. :good:
KUDOS to @justinswidebody for stepping up as a community leader & testing the apps that have risks/etc... that may warrant a reset/starting over,your efforts are to be commended by all who reap the rewards of your contributions,I can't thank you enough. :good:
A couple points worth repeating,from the link & instructions :
******** A factory reset will restore all uninstalled apps.
******** OTA's shouldn't be affected or affect the status of apps,whether they're installed or uninstalled (unless,of course,you've deleted something pertaining to updates,which won't be listed below)
FYI: The dates reflect the time of posting/removal,for ease of troubleshooting,in the event something noteworthy gets broken,it gives a good reference where to begin looking for the problem/solution.
*****************************************************************************************************************************************************
OPPO LAUNCHER com.oppo.launcher (7/18/18) : Must install A 3rd Party Launcher (Nova/etc....) prior to removal.
Also,for those that plan on using swipe gestures for navigation,for some,it gets broken somewhat,read the following post on the subject:
https://forum.xda-developers.com/showpost.php?p=77119245&postcount=40
The fix for the swipe navigation,if needed can be found here,courtesy of @justinswidebody ......... KUDOS :good: :
https://forum.xda-developers.com/find-X/how-to/guide-remove-lockscreen-rid-developer-t3819122
Those using virtual navigation buttons are unaffected.
******************************************************************************************************************************************************
MESSAGES com.android.mms (7/18/18) : Ensure that you have an Oppo account before removal,to prevent Oppo ID pop-ups & possibly other issues.
Recommend to have another SMS/MMS app installed before removal,may not be necessary.
DO NOT REMOVE INFORMATION SERVICES (com.android.mms.service)
******************************************************************************************************************************************************
com.android.browser (7/18/18) : Recommend to have another browser installed before removal,may not be necessary
com.android.printspooler (7/18/18)
com.coloros.cloud (7/18/18)
com.coloros.gamespace (7/18/18)
com.coloros.soundrecorder (7/18/18)
com.coloros.speechassist (7/18/18)
com.nearme.atlas (7/18/18)
com.nearme.instant.platform (7/18/18)
com.oppo.logkitservice (7/18/18)
com.oppo.logkit (7/18/18)
com.oppo.ovoicemanager (7/18/18)
com.oppo.oppopowermonitor (7/18/18)
com.oppo.quicksearchbox (7/18/18)
com.oppo.securepay (7/18/18)
com.oppo.webview (7/18/18)
com.android.calendar (7/19/18)
com.coloros.appmanager (7/19/18)
com.coloros.childrenspace (7/19/18) KidSpace
com.coloros.healthcheck (7/19/18)
com.coloros.weather.service (7/19/18)
com.coloros.widget.smallweather (7/19/18) Clock Widget
com.mobiletools.systemhelper (7/19/18)
com.oppo.fingerprints.fingerprintsensortest (7/19/18) Fingerprint Sensor Test
com.coloros.oppomultiapp (7/20/18) Clone Apps (Removing Clone Phone breaks this,by removing the base package & suspect vice versa,removing one breaks the other)
com.coloros.backuprestore (7/20/18) Clone Phone
com.coloros.assistantscreen (7/20/18) Smart Assistant
*****************************************************************************************************************************************************
The following,while they can be removed,are known to break significant functionality,or,cause other undesired results,remove at your own risk:
com.coloros.securitypermission (Privacy Permissions) (7/19/18) Breaks app permission management when removed.
com.coloros.pictorial (Lockscreen Magazine) (7/19/18) Removal will result in no longer being able to access Lockscreen settings,I recommend keeping this one
com.OppoFreeFallingMonitor.apk (8/8/18) Provides protection for camera slider in the event of a fall. Best described here: https://www.gizchina.com/2018/06/20...s-anti-fall-feature-guarantees-5-years-usage/
*****Reserved*****
Added the following to the OP/List:
Oppo WebView com.oppo.webview (7/18/18)
Game Space com.coloros.gamespace (7/18/18)
Oppo/ColorOS Cloud com.coloros.cloud (7/18/18)
Good list. There is one issue if using 3rd party file manager to install anything it asks to login. Need to find out if we can do a workaround by deleting some package.
varun.gid said:
Good list. There is one issue if using 3rd party file manager to install anything it asks to login. Need to find out if we can do a workaround by deleting some package.
Click to expand...
Click to collapse
Guessing it has something to do with Phone Manager & Security apps,but,I'm not quite comfortable removing either ATM,until I can take a look around @ other Oppo Devices running a recent version of Color OS & get a better idea of the effects of removing either.
In the meantime,just another alternative:
You can side-load apps/.apks via Bluetooth sharing from another device without issue.
Thanks a lot for the Guide! I really wanna get rid of the launcher....
Therefore, beginner question:
If I run the adb devices command (inside the platform-tools folder) it shows no device in the list.
I enabled USB Debugging on the phone.
Is it necessary to manually install the driver for the phone to make adb work?
I found a driver here (mobileheadlines.net/) but I am not sure if this website is trustworthy.
Thanks for your help.
BTW: I think your link to the make adb run is not working properly. At least i get an 403 error message. Is this the how to you wanted to refer to?
tschifeif said:
Thanks a lot for the Guide! I really wanna get rid of the launcher....
Therefore, beginner question:
If I run the adb devices command (inside the platform-tools folder) it shows no device in the list.
I enabled USB Debugging on the phone.
Is it necessary to manually install the driver for the phone to make adb work?
I found a driver here (mobileheadlines.net/) but I am not sure if this website is trustworthy.
Thanks for your help.
BTW: I think your link to the make adb run is not working properly. At least i get an 403 error message. Is this the how to you wanted to refer to?
Click to expand...
Click to collapse
THX for the heads-up on the link,it's fixed now. :good:
The drivers should install themselves,but,before you do that,you have to enable Developer Options & once there,you'll need to toggle-on USB Debugging.
This tutorial for Dev Options/USB De-Bugging is for other OPPO devices,but,is applicable here:
https://www.syncios.com/android/how-to-debug-oppo-f1.html
Once you do the above,plug-in to your PC & the drivers will automatically install.
Then pull down on the notification bar,tap on the USB Debugging notification,select Transfer files.
Also,the 1st time you connect/use USB Debugging,you'll see a pop-up window asking for permission,allow it. If you don't see it,disconnect from the PC,re-connect,select File Transfer & keep the phone unlocked,until you see the permission pop-up. I recommend selecting "Always" so,you don't have to bother w/it again.
Check this video out,it covers most of the steps:
https://www.youtube.com/results?sea...er+options+&+USB+Debugging+on+the+OPPO+FIND+X
Removed (OPPO) Search com.oppo.quicksearchbox ........added to OP/List.
KOLIOSIS said:
Removed (OPPO) Search com.oppo.quicksearchbox ........added to OP/List.
Click to expand...
Click to collapse
Just removed com.oppo.launcher which was the primary concern! Nova Launcher works as far as I can tell without the need to set it as the default browser. Many thanks KOLIOSIS, I'm sure you have an idea of how much I hated the default launcher...
rmurase said:
Just removed com.oppo.launcher which was the primary concern! Nova Launcher works as far as I can tell without the need to set it as the default browser. Many thanks KOLIOSIS, I'm sure you have an idea of how much I hated the default launcher...
Click to expand...
Click to collapse
this system i very closed..
nova do not stay on ..
Any adverse effects removing power monitor? Notifications or battery life?
How do you get rid of the oppo security message asking to sign in to oppo ID when sending sms through a 3rd party sms app?
varun.gid said:
Any adverse effects removing power monitor? Notifications or battery life?
Click to expand...
Click to collapse
I haven't noticed any undesirable effects.
Sent from my OPPO PAFM00 using XDA Labs
just to add correction if you dont mind..the package is com.oppo.oppopowermonitor
I've just removed
com.coloros.healthcheck
com.coloros.appmanager
com.mobiletools.systemhelper
Don't see anything bad happening from what I can tell.
Also removed
com.coloros.securitypermission
However this removed the ability to change any permissions.
One of these that I removed allowed me to use mobile data for Showbox. I wasn't able to watch any Showbox stuff on mobile data before removing these
justinswidebody said:
I've just removed
com.coloros.healthcheck
com.coloros.appmanager
com.mobiletools.systemhelper
Don't see anything bad happening from what I can tell.
Also removed
com.coloros.securitypermission
However this removed the ability to change any permissions.
One of these that I removed allowed me to use mobile data for Showbox. I wasn't able to watch any Showbox stuff on mobile data before removing these
Click to expand...
Click to collapse
I'll add the 1st three you listed to the OP/List & start another list in the same OP for those such as the one here that breaks some functionality.
varun.gid said:
just to add correction if you dont mind..the package is com.oppo.oppopowermonitor
Click to expand...
Click to collapse
Thank you,I've since edited the OP/List to reflect the correct package/app/.apk name,much appreciated. :good:
Anyone using 3rd party SMS? If so are you getting prompted to login to OPPO ID whenever you send an SMS?
yakuzlin said:
Anyone using 3rd party SMS? If so are you getting prompted to login to OPPO ID whenever you send an SMS?
Click to expand...
Click to collapse
Yes,I am,using Textra & removed the stock messaging app,still getting the pop-up,but,messaging does work.
I suspect the banner is tied to the Privacy Permissions app (com.coloros.securitypermission) Don't remove this,breaks permission management.
@justinswidebody
If you haven't performed a factory reset,can you test a 3rd party SMS/MMS app & see if the OPPO ID Prompt still pops-up?
THX again. :good:
EDIT: @yakuzlin
The Privacy Permissions app (com.coloros.securitypermission) is not tied to the banner pop-up,see the following post.......
I installed Textra, but I still have the default messaging app so I can't set it as default. But when I send a text it sent fine , when I receive a text it puts up a hint pop up message that the default messaging app is used for security reasons.