Hi Guys
Why Special Forces Group 2 crashed for me?
there is a log of crash:
Code:
https://ufile.io/3bba9
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
Hello, guys. Please help me undestand the problem that appeared after the update from LineageOS 14 to 16.
I've tried different versions and variants of WebView (clean stock, chrome & bromite), but at all of them I can see nothing but a completely blank page without trying to access the network.
The Webview test displays information about the installed version, but also does not open any page.
The log indicates this error:
webview_zygote: jni_internal.cc: 616 JNI FatalError called: (com.android.webview:sandboxed_process0) Failed to open(/sys/kernel/debug/tracing/trace_marker,1): Permission denied
(trace_marker permissions is -w--w--w-)
Thank you so much for your help!
(Moto XT1092 root)
Mi 9T, MIUI 11/Android 10 (11.0.4.0 QFJEUXM), rooted Magisk), installed Adaway (ofc, must use systemless hosts)
I found that I was unable to connect to the public hotspots - it was not opening the hot-spot accept conditions/login page
By examining a logcat I found:
-ActivityTaskManager(1598): START u0 {act=com.miui.action.OPEN_WIFI_LOGIN dat=http://connect.rom.miui.com/...
...
-OpenWifiLogin(30894): IOException: java.net.ConnectException: Failed to connect to connect.rom.miui.com/::1:80
Upon whitelisting connect.rom.miui.com, phone successfully opens the login page again and I can connect to the public hot-spots
You may or may not have this login to hot-spot problem (with AdAway, DNS66, Blokada...) depending on which hosts sources you use
However, if you don't block connect.rom.miui.com (or you don't use an ad blocker), be aware that MIUI sends some data to its server every time you are connecting to a public hot-spot (?!)
Btw, http://connect.rom.miui.com is valid site (Welcome to nginx! - see a screenshot), and I found a similar report on the Net:
https://www.reddit.com/r/Xiaomi/comments/bk6viy/redmi_note_7_issues_with_public_wifi_networks/
zgfg said:
Mi 9T, MIUI 11/Android 10 (11.0.4.0 QFJEUXM), rooted Magisk), installed Adaway (ofc, must use systemless hosts)
I found that I was unable to connect to the public hotspots - it was not opening the hot-spot accept conditions/login page
By examining a logcat I found:
-ActivityTaskManager(1598): START u0 {act=com.miui.action.OPEN_WIFI_LOGIN dat=http://connect.rom.miui.com/...
...
-OpenWifiLogin(30894): IOException: java.net.ConnectException: Failed to connect to connect.rom.miui.com/::1:80
Upon whitelisting connect.rom.miui.com, phone successfully opens the login page again and I can connect to the public hot-spots
You may or may not have this login to hot-spot problem (with AdAway, DNS66, Blokada...) depending on which hosts sources you use
However, if you don't block connect.rom.miui.com (or you don't use an ad blocker), be aware that MIUI sends some data to its server every time you are connecting to a public hot-spot (?!)
Btw, http://connect.rom.miui.com is valid site (Welcome to nginx! - see a screenshot), and I found a similar report on the Net:
https://www.reddit.com/r/Xiaomi/comments/bk6viy/redmi_note_7_issues_with_public_wifi_networks/
Click to expand...
Click to collapse
its same with every vendor, like apple does it to captive.apple.com
anirudhks said:
its same with every vendor, like apple does it to captive.apple.com
Click to expand...
Click to collapse
Probably most send some data one way or another (btw, I don't use iPhones for that and several other reasons), but it is good to know for some who encounter a similar problem with ad blockers, when trying to connect to the public hotspots
Btw, some hosts sources for AdAway/DNS66 also block miui.com or update.miui.com, but update.miui.com is repository for downloading firmwares - eg, open (enable Desktop site):
https://c.mi.com/oc/miuidownload/detail?guide=2
and try to download some firmware - if you cannot, whitelist:
update.miui.com
EDIT:
Also, for Mi Account, to login and sync (backup/restore) the following two must not be blocked:
api.micloud.xiaomi.net
sgpac.account.xiaomi.com
Hey. I had the same issue. Make sure your DNS is set to automatic.
For some reason Xiaomi does not let you access DNS settings directly. You have to install quick shortcut make and access com.android.settings.Settings$NetworkDashboardActivity from the setting.
I didn't take into account your rooted phone. You may have the option right away or it may be one of the apps you installed.
tkiafar said:
Hey. I had the same issue. Make sure your DNS is set to automatic.
For some reason Xiaomi does not let you access DNS settings directly. You have to install quick shortcut make and access com.android.settings.Settings$NetworkDashboardActivity from the setting.
I didn't take into account your rooted phone. You may have the option right away or it may be one of the apps you installed.
Click to expand...
Click to collapse
As described above, access was blocked due to one of host source lists for AdAway (and solved as described above)
Im not using Private DNS, but you can set Private DNS (easier than by shortcut maker apps) through Hidden Settings for MIUI app, available from Playstore, root not required
To login and use Mi Account two more URLs must be whitelisted:
api.micloud.shaomi.net
sgpac.account.xiaomi.com
All together, I white-list four of them, i.e. these two also (as in the above posts):
update.miui.com
connect.rom.miui.com
This is needed (only) if using a particular hosts source blocking Xiaomi/MIUI analytics:
https://raw.githubusercontent.com/j...ter/Extension/GoodbyeAds-Xiaomi-Extension.txt
This maybe old thread, but if you are rooted/ just use adb from PC, you can change the default captive portal back to original/stock :
adb shell settings put global captive_portal_https_url https://google.com/generate_204
adb shell settings put global captive_portal_http_url http://google.com/generate_204
Trying to upload an apk to the Xiaomi app store and Xiaomi's GetApps Console says:
"The package name does not match, please upload the Apk file with the same name as the created package".
But they ARE the same. Been at this for a long time. Anyone uploaded to these guys before? Is there something about this I'm missing here?
Package name is com.example.myApp and apk is com.example.myApp.apk
Package name is verified using Android Studio, Google Play Store listing, etc.
What am I not getting?