[Q] Assigning permissions for floating notifications - Android Q&A, Help & Troubleshooting

How or where can I assign permissions for apps that use floating notifications?
I use a couple of these apps, and after updating to a new firmware (official) in my Ascend P6 they say they don't have permission for "showing the area of placement" or something like that (I'm not quite sure how to translate this properly - the message in Spanish is: "Esta aplicación no tiene permisos para mostrar el área de colocación") and niether of them show the floating notifications.
I tried checking the permission manager of the phone (which I had to dig out from the shurtcuts because it dissapeared from the settings menu) but there are no permissions for that.
I'm running Android 4.4.2 with B512 firmware.
Thanks in advance

I found a solution to this issue:
The problem, apart from the fact the phone was not allowing apps to show these types of messages on screen, was that the option to manage this permissions was hidden in B512.
The solution involves modifying a specific line in the build.prop file that hides or shows a particular option inside the built in phone manager app.
The line is ro.config.DelStartupManager=true and needs to be changed to ro.config.StartupManager=true. This enables a menu inside the phone manager that leads to the "placement area" permission settings (again, not sure if this is the actual string in English) from which you can assign these permissions to any app.
Hope it helps.

Related

Repeated Invalid SMS Notification - Resolved

Hi X10 mates, I was facing a typical SMS notification problem when i used "Handcent SMS" or "GO SMS". I was repeatedly receiving an invalid SMS notification of an old message which i deleted long back. Though it goes off when i clear the notifications, the notification comes back whenever i get a new message or open the "Handcent SMS" or "GO SMS" software. It was annoying me until i sat for 4 hours to crack it. I did all the crap (spend few hundreds too ) to crack it. If you are ready to do all the crap, here it goes,,,
PREREQUISITES
1.Get access to your ROOT folder
- I used "SuperOneClick1.7(Free)" - It works with the latest firmware 2.1.A.0.435 - Pinch Zoom
2.Get a file explorer for your mobile
- I installed "Root Explorer(2.5 pounds)/(Free)"
3.Get a ".db" editor
- I installed "SQLLite Editor(1.8 pounds)"
SOLUTION
4.Open the Root Explorer and grant "SuperUser" Access when it pops up (This is the case with SuperOneclick)
5.Go to /data/data/com.android.providers.telephony/databases
6.Open the "mmssms.db" (This is where all the mms and sms are stored) and select to SQLLite Editor in the pop up
7.Open the "sms" table and view for a row which has empty value in "thread_id" column.
8. Just press the row and delete the record ! And we are done !!
Though this may not be the easiest way, but i did at last!
Interesting. Can this help on MMS unsendable & unreceivable?

Fake GPS location problems.

Hi, so sometimes i use the app called Fake GPS location that spoofs your real location.
But then one day i couldn't get my default location back that is calculated trough cellular tower and is shown trough other apps (Weather, Foursquare etc.)
I tried deleting data/cache to Fake GPS location and Google Maps even tried deleting Dalvik cache to no avail.
So does anyone have any solution to this thing please?
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5lY2xpcHNpbS5ncHNzdGF0dXMyIl0.
Try resetting your aGPS data and download the assistance data.
AlexWekell said:
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5lY2xpcHNpbS5ncHNzdGF0dXMyIl0.
Try resetting your aGPS data and download the assistance data.
Click to expand...
Click to collapse
Already have this app and tried reseting and then redownloading A-GPS data then reset my phone but still shows that fake location.
Do you think this is the problem with A-GPS data ?
Where the heck is even location data like for spoofing location stored in Android ?
I have no problem with the location sets, but i've another problem..
I use samsung galaxy mega 6.3 lte...my device keep turn on gps itself even i've already disable it on location svc setting on my device when i turn on wifi or mobile data..any chance to disable it or prevent it from auto run/run by itself?
I am with the same problem...
Followed this tutorial (http://windowspcguide.com/play-poke...-ios-iphone-ipad/comment-page-3/#comment-7144) and now I can't go back...
Someone could help me please?
Same problem here. Now fixed on Android.
Go to Settings > About the phone, then tap SEVEN times on "Compilation Number". Now you are in "Developer Mode". Go to Settings > Dev Options. Look for GPS "locations" and deselect "test/fake locations". That's it.
In Spanish:
Deshabilitar ubicaciones de prueba. Para Androides solamente, vaya a "Acerca del telefono" y luego pulse sobre el numero de compilacion 7 veces. Esto permitira entrar en las opciones de desarrollador. A partir de ahi vaya a Ajustes > Opciones del desarrollador, y abajo, donde pone "ubicaciones de prueba" desactivar ubicaciones de prueba. Eso es todo!
Friends this will work... First go to google maps then go to "you are place" option and in top right u have settings symbol.u will have " delete all locations history" select that and u will get u r original gps... Thank you...
Can anyone tell me which phns support fake GPS?
I never had an issue like that with this app bit.ly/gpsfaker It is the easiest app i've found out there to fake gps locations or routes.

Monitor system file changes (root) ?

Checked posts / searched for an existing answer... didn't see anything (please move this post if it is in the wrong section)
So I have a app, when I open it asks me what Google ID to uses (preferred ID) but after selecting a Google ID I can not change to a different ID
- If I clear the App Cache the selected ID persists
- If I clear the App Data the selected ID clears and the app returns to the select ID option
- I keyword searched for the App name on my device (Nexus 5x)with Root Explorer (12 different file locations, with subfolders and a bunch of empty folders)
Clearing App Data is a working interim solution, the downside is that every time I clear the App Data the app "downloads assets" (40mb+ ~40 times per day - 1.6Gb!)
What I am hoping to find is a app / script / terminal / log solution that will tell me what file is being modified when I select the Google ID, so I can delete that file re-open the app and change Google Logon
(I contacted the app developer, they said they may be able to fix the problem on the next patch eta 12-24 months)
So I have tried these apps:
https://play.google.com/store/apps/details?id=file.observer
https://play.google.com/store/apps/details?id=scd.lcex
https://play.google.com/store/apps/details?id=eu.thedarken.sdm
But I didn't see system changes (root level) or I didn't know what to look for in LogCat
Any help or suggestions are appreciate!
- I do not have a computer with me (ADB) will be about 7 days before I can try that
- I have been experimenting with deleting files / folders and testing to see if I get lucky (probably not the best method)
- I am not a developer
My current process (as of today) - I clear the app data, then restore the app data with TB (just restoring doesn't clear the sign in status)
As long as my TB backup is "always" in the signed out state, then the "app assets" restore with no issues (and I don't have to keep downloading them)
I am looking for a way to get these (2) operations into a single script / file / shortcut, but it is working for now
I did try the terminal with cp -a (copy the assets - app had a error on library permissions when the files were restored) chmod, chown, and find (try and locate the file) but had minimal success

[SOLVED] Soft boot-loop/brick on Eken GC10X Tablet

Greetings!
First, this message will be rather long, for which I apologize. I am providing headings that allow whomever is interested to skip to whatever is relevant to them.
About the device:
It is one of two Eken GC10X tablets, purchased from Micro Center a while back dirt cheap. The second one is 6000 miles away in Europe. . . .
It is currently running Android 4.2.2
Its firmware revision is v2.0patch1
Its kernel version is 3.4.39+, dated Friday, October 18th, 2013, at 18:11:40 CST
Its build number is wing_k70-eng 4.2.2 JDQ39 20131028 test-keys
It comes pre-rooted by default. All that needs to be done is to install a terminal program and pay attention to certain paths.
About me:
I have been messing with computers, programming, and operating systems since the time of "wood burning computers"
I know my hosts file from my fstab, I have run various flavors of both Linux and Windows in both client and server configurations, and I know that both man pages and a good search engine Are Your Friends. (which is how I came to be here!)
Issue:
Since this Eken tablet comes with a bare minimum of internal memory, I was researching ways to mitigate this. I found an article that mentioned a workaround:
Copy everything in root to a large external SD card
Transpose the settings for the internal and external memory in the /etc/vold.fstab file
Save and Reboot
The result of this is a tablet that - regardless of the presence or absence of any external SD card - always boots as if it had never been booted before, (returns to "first-boot / out-of-box" setup). Any installed apps are gone and the "internal" memory - which is about 1-2 gigs - shows absolutely full. In addition to all that, I cannot do anything with the ADB port since it requires setting the "USB Debugging" flag, which gets reset on reboot. (i.e. The ADB interface is not available.
Examining the vold.fstab shows that the original setup of that file has been returned after I did a nuke-and-reboot.
I can reboot and re-install a terminal program and advanced file manager. (X-plore is my favorite)
I see three possible solutions:
Find the reason why it's booting like this and fix it.
Find a compatible firmware release for this tablet and re-flash it - if possible - from an external SD card.[/INDENT]
Do some kind of "nandroid" backup from the other Eken GC10X tablet I have and copy it to this one. Unfortunately it's 6000 miles away and I won't be able to get to it until sometime after January 2019. In addition, I cannot access the device via the ADB port.
Research I have done:
gsmhosting's allwinner forums
This site claims to have a (ahem!), "modified" version of the firmware, which I have downloaded.
The androidmtk site
This site has the "PhoenixCard" software which alleges that it can be used to create external SD card images of firmware files that can:
Install firmware from the SD card to the device.
Allow you to run the firmware from the SD card to verify it. It should be noted that MalwareBytes flags the updater.exe file because it attempts to download from a known Trojan site. Renaming the extension, (exe.bad), solves that problem.
I have not tried re-flashing any firmware version, though I have tried running the firmware from SD, which doesn't work.
Can someone help me with suggestions on how to return this tablet to normal?
Thanks in advance for any help you can provide!
Solution:
I guess it's "umpteenth time's the charm!" :highfive:
Having done considerable research, (with everything pointing to an issue with the busybox file being in the wrong place), I decided to revisit this, did a little more digging and ultimately found a solution.
Since nothing irritates me more than someone posting "I fixed it!" without telling everyone else HOW they fixed it, here are the steps I used to solve this problem.
Please be careful. You will be mucking around with your tablet's/phone's root file system in ways that can be fatal if you're not paying attention. It's not that difficult but you DO have to PAY ATTENTION to what you're doing.
TO-DO:
Instead of copying the busybox file, it should really be a symlink to /sbin/busybox.
If anyone figures out a way to create a symlink in Android that actually works, I'd like to know.
Here it is:
Pre-requisites:
The device MUST be rooted for this to work. I cannot help you with advice on how to root individual devices. This Eken tablet comes rooted by default.
Download off-line from Android Archives, (using a different system), an early version of X-plore, which is an excellent file manager.
Load X-plore onto a thumb-drive or a micro-SD card, (I used a micro-SD), and then install the SD card / thumb drive into the tablet you're trying to fix.
Steps to solve the problem:
First, go to Settings => Security and enable "unknown sources"
Open your device's file manager
Find the copy of X-plore you downloaded, and tap it to begin the off-line installation process.
Once it installs, open it and go to the "configuration" menu. This is within the three-dot menu drop-down in the upper right-hand corner.
Select:
* (near the top) Show hidden files => select the check-box. (optional)
* Root Access => Superuser + mount writable (this allows you to change permissions to permit writing the root filesystem)
* (scroll down) Dark mode => select the check-box. (this is a personal preference; IMHO it makes it easier to read.)
* Exit configuration by using the "back" button or back arrow in the upper left corner.
* You should now see two columns representing two views of the device's file-system.
On the left side, open the "Root" filesystem, also labeled with a "/"
Scroll down and find the "/sbin" folder and open it by tapping on it.
* You may, or may not, see several folders and files. You are looking for the file "busybox"
* If you don't see it there, you may have to "find" it using the magnifying glass icon in the center row of icons.
* Open the "find" dialog and replace the "*.*" with "busybox" and then select "OK".
* (assuming you found it), tap at the right-hand edge of the row with the file-name to "select" it - a big check-mark will appear there.
Go to the right-hand side list now. Find and open:
* Root (/) like you did before.
* system
* bin
* At the top of that column, you should see a folder icon, followed by "/system/bin"
Look to see if there is a file named "busybox" there. (In my case, it was missing - which is the problem)
(assuming it's missing)
Collapse the "bin" folder by tapping on it - it might take a couple of taps.
Touch-and-hold the "bin" folder until a long list appears. Scroll down to the bottom of that list and select "permissions"
Within the permissions dialog, there are three columns: Read, Write, and Execute.
* There should be three selected boxes under "Read".
* There should be ONE selected box, the top one, under "Write"
* There should be three selected boxes under "Execute"
* Directly below the last box under "Read", the box labeled "Recursive" should NOT be selected.
* To the far right of "Recursive" should be a note that reads "Mode: 755"
Under the heading "Write", select the other two boxes so that all three are selected. The word "Mode" should now be followed by "777" Close the permissions dialog by selecting "OK".
Verify the following:
* The arrow at the top of the center column is pointing to the right. If it is not pointing to the right, tap it until it points toward the right-hand column.
* The file "busybox" on the left-hand pane has a check-mark next to it and no other files are selected.
* The "bin" folder on the right-hand side has been collapsed and is selected by being a darker black with NO check-mark.
* The top of that column shows the folder icon and "/system/bin" as the selected path.
Copy the "busybox" file into the /system/bin folder by doing the following:
* Tap the "copy" icon in the center column - it will look like two pieces of paper stacked together.
* Verify that the dialog that opens:
* Just below the top right it says "busybox" (the file you're copying)
* Under that, "Copy to"
* Under that, a folder icon and then "/system/bin".
* Under that, the selection "Move mode (delete source files) is NOT selected!
* Tap "OK" to copy the file to /system/bin. Once the copy is done, the dialog will close.
Tap "bin" on the right hand side to open it if it does not open by itself.
Verify that "busybox" appears in both the left and right hand panes.
Press and hold the "busybox" file until the list dialog re-appears.
* Select "permissions".
* Verify that all three "Read" permissions are set, only the top "Write" permission is set, and all three "Execute" permissions are set. (You may have to clear the bottom two "Write" check-boxes.)
* Verify the "Mode" is set to "755"
* Close the permissions dialog by tapping "OK"
Collapse the "bin" folder by tapping on it.
Long-press the "bin" folder, select "permissions", and set the permissions of the bin folder to "755" the way you did for the busybox file above.
Return to the "Configuration" menu by following the steps at the beginning and select "Superuser" or "Normal User" instead of "Superuser + mount writable" to prevent accidental changes in the future.
At this point, you should be able to close and re-open X-plore and verify that "busybox" actually exists within /system/bin. If it does, you can reboot and your should be good to go.
If it's not there, re-trace the steps I listed above, paying particular attention to the "Superuser" setting in "configuration" and the various file permissions.
If you're still having trouble, post a reply below and I will try to provide what help I can.
Thanks for your patience and I hope this helps others who were puzzling with this as long as I was.

What are MIUIOP?

If anyone knows descriptions to miuiop please share, I'm curious what they do.
What App Ops does is allow a user to revoke an individual permission for an app. When the app then starts and tries to make an Android system call to access something that the user has now forbidden then Android will return an error and won’t grant access to that data or functionality.
As you can see there are several numbers starting with 100xx. These are the app IDs (UID = user IDs) the system is dealing with. Every app has a corresponding UID which is needed for file permission rights. Example: If only a certain app (UID 10666) has the permission to open a certain folder, the folder will be restricted to u0_a666 (=user 0, that's you, + app UID 10666)
Usually the first UID slots 10001, 10002, ... are system apps since they get started first upon an initial boot of your device. I assume that MIUIOP belongs to the MIUI optimization, but not sure about that. But you can figure it out with the help of the UIDs:
Apk Analyzer - Apps on Google Play
Detailed reports of the applications on your device. 📱
play.google.com
Selecting an app shows you its UID. Unfortunately it doesn't show you the UID in the app's list directly.
So the uid number could be different across different miui versions… unlike standard appops which are the same regardless of device?
Posting a list of the apps just because:
10008 com.miui.core.internal.editor.services
10017 - com.miui.systemui.overlay.devices.android
10020 - com.android.theme.font.notoserifsource (Noto Serif / Source Sans Pro)
10026 - com.android.internal.systemui.onehanded.gestural (One Handed Mode)
10033 - com.android.overlay.gmstelephony
10036 - com.android.systemui.gesture.line.overlay
10037 - com.miui.systemui.carriers.overlay
The app UIDs are assigned ongoing by your system on first boot (for system apps) or after installation (for user apps). Example: The first app you install on your device gets the UID 10201 then the second one gets 10202 and so on. It doesn't depend on your MIUI version or sth like this.

Categories

Resources