i have app called "SuperSMS" FROM 2016
and when i upload the new version and fill the declartion form
i get this message
Hi Developers at Dustfall,
Thanks for contacting the Google Play team.
I’ve reviewed your appeal request and found that your app, SuperSMS - Text Messages (com.Dustfall.SuperSms), does not qualify for use of DEFAULT_SMS.
We are unable to verify permissions prompt in your app. If these permissions (e.g. READ_SMS, RECEIVE_MMS, RECEIVE_SMS, and SEND_SMS) are not required, please remove them from your app.
Your app does not appear to prompt the user to be a default handler prior to requesting related permissions as required by the policy. Please make necessary changes in order to comply with policy requirements and resubmit your app through a Declaration Form.
Permission requests should make sense to users. You may only request permissions that are necessary to implement critical current features or services in your application. You may not use permissions that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. For additional guidance, please review the Permissions policy and this Play Console Help Center article.
Please let me know if you have any other questions.
Best Regards,
Anya
The Google Play Team
NOW WHAT THE HELL THEY WANT ?
AND THERE IS NOBODY TO TALK WITH HIM
Related
I assume already the SuperGeeks of this forum have already realized this, but still I want to make clear of my findings.
WP7 loads number xxxxxx.Policy.xml files on First Boot and compiles them into PolicyMeta.vol database, its like loading every security policy into Memory of OS.
Everything as listed below are controlled by the virtue of userID Chambers and Access Policies.
eventlog: Macros for use with EventLog security policy.
filesys: Default file system security policy
loaderverifier: Default loader verifier security policy;
registry: Default registry security policy; templates.testcerts.loaderverifier: template security policy; toberemoved: Default loader verifier security policy
dstsvc: Daylight Saving Time Service policy definitions and rules
fsprofile: Default kernel security policy;
oalioctl: Default Device Manager Security Policy;
kernel: Default kernel security policy
The only way to hack completely into WP7 is
1. Build a ROM with ourown certificates key/pfx pair into DefaultCerts.dat as XbMod did
2. Edit all policy xml files to elevate the rights and provide all access to the everyone_group_name userID
3. Finally add the IE7 DFT xap installer.
This would make the WP7 phone completely open to all uses.
Thanks !
I appreciate your work buddy ! thanks for sharing this ! hope u gonna work too on the new wp7 ROM !
neelgangrade said:
I appreciate your work buddy ! thanks for sharing this ! hope u gonna work too on the new wp7 ROM !
Click to expand...
Click to collapse
I also thank you for your reserch!
I hope more people will say thanks to keep this usefull thread afloat!
thanks for doing the research
Wechat Share Editor is a module for Wechat that allows you to change the sharing content or even create a custom share in Wechat. This includes share link, share logo link, share title and others...
Features
Change the Sharing Content of Wechat.
Requirements
Your phone must be rooted
Xposed framework must be installed first repo.xposed.info/module/de.robv.android.xposed.installer
Wechat Required
Instructions
Install the module
Run Xposed Installer and enable the module Wechat Share Editor
Reboot the phone
Open the module in Launcher or Xposed, and set up the content you want to share.
Open Wechat to share someone else’s Moment, and check the result
Permissions
network
Limitations & supported devices
I developed this module based on Wechat 5.3 source code and tested only on my RedMi device with Wechat Version 4.51 and 5.3. I expect it to work also on Wechat 4.0-latest.
Credits
I used XLED’s SettingsHelper class, hope you don’t mind.
Supports & troubleshooting
If you want me to add support for other Wechat version, please send me the following:
Xposed log file
Your device model
Android, ROM, Wechat version
Source code
You can find source code for this module from github.com/diwulechao/WechatShareEditor
hi, can you be specify more or provide a short video clip for some intro about it? im still having some confusing about this...
Sent from my GT-I9300 using Tapatalk
i love this apps.. can you update it for latest wechat apps?? tq
Sent from my GT-I9100G
Hi!
I have created a kernel module (and insmod it at the start of the device) to control /dev/xx and only the system can access /dev/xx.
Thank to the code I have added, /dev/xx can be controlled from the Framework .
I now want to create a system service to handle this.
Which permission should be used for permissionGroup so that the service can access /dev/xx?
I have read the documentation (I am not able to post the link since I have less than 10 posts) but it doesn't help me to guess the right permission group for the system service
PS: I am working on Marshmallow
It is an xposed module capable of spoofing some of the identities of an Android device.
Customize the identites to your own choices!
Download Here : Mod edit: link removed.
Below are the supported identities :
- Android Id
- Serial Number
- IMEI
- MAC address
- Device build number
Another interesting option available is, ability to randomize the identity for different processes.
It just hijacks the identities on the fly. Hence the original valules are not modified.
Once the app is disabled, get back all the original ids.
How to use!
You need to have an android device which is rooted and has Xposed framework installed.
Open Hijack Suite and enter custome values for the identities.
Press save.
Goto Xposed installer app.
Enable 'Hijack suite'
Reboot the device.
View the customized values being replaced at places where they are tried to fetch.(Check using different apps.)
Observe the behaviour of the app under test by changing the id values.
Disclaimer
Please try the app only if you can understand the above description.
It is built for Android application security testers. (pentesting)
Do not use the app for any illegal purpose.
Use the app at your own risk.
Thanks to rovo89 for developing the wonderful XPOSED framework.
Keywords : Change Android ID, Change Serial number, Change imei, Change MAC address, Change Device fingerprint,
Mask imei, Mask identity, Spoof identity, Hijack id
No free version for XDA community, thread closed.
EDIT:
Free version added to new thread here:
http://forum.xda-developers.com/xposed/modules/hijack-suite-t3429770
I have a back-end application which is supposed to work as an Entitlement server in TS.43 flow ( https://www.gsma.com/newsroom/wp-content/uploads//TS.43-v8.0-3.pdf ). I want to test this application by triggering TS.43 flow on my android device. I have tried to do it with the help of the following documentation: https://source.android.com/docs/core/connect/ims-service-entitlement#entitlement-app
How should I trigger this application to start TS.43 flow entitlement? I know about the need to change the URL through Carrier Config, but for purposes of this discussion, I am interested in how to just trigger this flow so that the requests are made.
What I have found: I have found the source code: https://cs.android.com/android/platform/superproject/+/master:packages/apps/ImsServiceEntitlement/ However I couldn't find some Readme.md file explaining how to trigger requests from this application.
Details of test device:
Android 12, Samsung Galaxy A52