Jul 15, 2023 13:47
Would be off-topic here (development focused), but of course by altering the code one could do that. Maybe someone wrote a corresponding XPosed module for this – but there's no hit in the XPosed repo yet.
Jul 15, 2023 13:47
I did – but reading it again, I've misread it the first time. You want to have the screen overlay ignored it seems – not much luck with that, I'm afraid, for reasons already pointed out. Sorry.
Jul 15, 2023 13:47
Have you seen Determine which app is drawing on top of other apps? That should help you finding the culprit.
 

 Android Enthusiasts

Welcome to the main chat room for android.stackexchange.com! H...
Apr 6, 2023 17:43
@AndrewT. And since my repo is, too, find it there: SD Maid SE (v2 = Second Edition).
May 1, 2022 18:47
"I'm Ma Baker. Put your hands up and give me all your money." Freeze! #D Oh, your exclamation mark is on the other end of the word…
Apr 12, 2022 23:02
2freeze || !2freeze →← ¿
Mar 30, 2022 19:49
Funny: I have a notice hanging on top of this page that I was mentioned in this very room where I am "not in". Looks like whatever posts those announcements has a little schizo – or I have…
Mar 27, 2022 19:22
We usually reply if there are questions – but rarely have time for "just small-talk", Jim.
 
Feb 15, 2023 22:32
Gladly done – and best luck then!
Feb 15, 2023 22:32
The border line between websites and web apps is pretty thin sometimes…
Feb 15, 2023 22:31
Feb 15, 2023 22:13
@barlop so do cars ;) Yes, it can be adapted. But in its current form it would be rejected here. So better point the user to What is required for a question to contain "enough information"? Then they can place the "proper & acceptable" question.
Feb 15, 2023 08:20
@barlop No, that's asking for a how-to, not for software. Though one might imply a software might be wanted, it lacks details demanded by our guidelines.
Jul 22, 2022 18:53
@JourneymanGeek Thanks! Comment left, maybe you want to integrate it.
Jul 22, 2022 18:48
@JourneymanGeek Not sure. A general rule would be good – something we can agree upon. I sometimes think that, if an answer is 5+ years old, it's still not bad even if the link is dead: if it holds sufficient details, one gets at least a clue what to look for.
Jul 22, 2022 07:26
As it comes up again and again: may I raise awareness to this 2 years old meta-question which still is unanswered? Answers with broken links to software that is no longer available
 
Jul 30, 2022 17:28
Argh, the page got lost in the link: It's on page 68 of that thread, first post on that page. Sorry for that.
Jul 30, 2022 17:28
That issue is not new, see this XDA post from a year ago.
 
Jul 30, 2022 17:21
Luckily, I'm not affected (I never used MMS). So your provider could not help? A different device, maybe, at least to test with? A newer version of CM?
Jul 30, 2022 17:21
Any progress made? What was the solution? Please don't just abandon your question once the issue is solved, be fair and "complete" it by adding and accepting a solution once it is found :)
Jul 30, 2022 17:21
Stop googling Australia, stop guessing around -- start asking your provider in the US :)
Jul 30, 2022 17:21
I cannot tell for sure, but in all cases I know of they either direct you to a webpage providing the settings, tell you the settings directly (or via mail), or tell you about some "service SMS" they want to send you. In the latter case let them know that those "service SMS" with settings do not always work on Android, so they should send/tell you the settings in addition to that so you could enter them manually. Should they insist on having the device sent in, say you cannot do without (no backup device, daily need, ...). I doubt they insist.
Jul 30, 2022 17:21
Strange thing is also that you seem to have only one APN. Whereever I looked, it were at least 2 APNs: 1 for internet, 1 for MMS. Then, seeing in your comment MMSC: null, and in your APN mmsc="http://mmsc.vmobl.com:8088/mms?" clearly makes me wonder. Have you considered consulting the service of your carrier/provider, so they tell you their expected APN settings?
Jul 30, 2022 17:21
Good choice, and good chances you will get an answer there. Keep my fingers crossed :)
Jul 30, 2022 17:21
The last line of the log reads: RecipientId 79 has empty number! (so either there was no recipient entered, or it got lost). Also note, further on top, WAP PUSH is complaining: no receiver app found for 4:application/vnd.wap.mms-message. Both are only marked "W" (warning) where one might have expected "E" (error) -- but to me that looks very much like your system has trouble dealing with MMS. I'd suggest filing a ticket with CyanogenMod, or at least ask in their forum.
 
Jul 30, 2022 17:18
You can use the built-in "anti-virus-switch". Go to Settings -> Backup & Reset and trigger the factory reset. That will kill all the virii you've installed on your device, including facebook, pandora, and all. It's like a "big buzz" cleaning the entire device as good as the factory could reset it. Your device will be as smooth and fast as if it were new.
 
Jul 30, 2022 16:29
Have you seen the Adebar Wiki? It's all documented. I have not used it on Cygwin, so I cannot comment on that. But as the very same command worked locally on the Android device (and just failed when reaching the 4G limit), I doubt the scripts created by Adebar will be more successful.
Jul 30, 2022 16:29
Sorry, then I'm out of ideas. I've just done the very same yesterday without issues on one of my devices, but on "partition base" (e.g /dev/block/mmcblk0p26).
Jul 30, 2022 16:29
Again: Adebar does not run that command, it creates scripts containing such commands (by checking what partitions exist on the device etc). You just need to run the above mentioned command from a shell prompt: adb exec-out "su -c 'cat /dev/block/mmcblk0'" > mmc.img. The only thing you need to install beforehand is ADB.
Jul 30, 2022 16:29
Sorry, Adebar won't help you in the copy process itself – it just creates the required scripts to do so. I don't use Windows, so I cannot tell you what can go wrong on that end. I'm using the above command without issues on Linux, and successfully extracted partitions from several devices running Android 5.
Jul 30, 2022 16:29
Take a look at my little tool Adebar, which creates scripts for that. Obviously, you'll need a file system supporting files larger than 4G. The scripts Adebar generates pipe the image file directly to your computer. But it requires either a *nix system (Linux, Mac) or, if on Windows, Cygwin. Just checked the syntax: adb exec-out "su -c 'cat /dev/block/mmcblk0'" > mmc.img would place mmc.img in the directory you're in on your PC when calling the command.
Jul 30, 2022 16:29
If you just want to run that single command, you don't need Cygwin (for Adebar you'd need it). And mmc.img would save into the directory you execute the command from (alternatively, specify a > c:\full\path\to\mmc.img).
Jul 30, 2022 16:29
Yes, that should be possible (via loop interface or the like). It helps if you know the file system. But as you took mmcblk0, is that a single partition and not the "entire storage"? Single partitions are usually something like mmcblk0p1 (note the p1, p for partition followed by the partition number).
Jul 30, 2022 16:29
\o/ So when the "dump" is done, you just need to pull the image files. If the result meets your expectations, let me know to sum it up to an answer you can "accept" then – so folks in a similar situation see this issue has a solution :)
Jul 30, 2022 16:29
Reading your question I thought you know you need root for that. Only root (#) can access devices directly, the shell user ($) can't.
Jul 30, 2022 16:29
I don't know who wrote that tutorial – but adb pull pulls files, not devices. You'd need to cat that into a file and pull that (cat /dev/block/mmcblk0 > /sdcard/mmc.img).
 
Jul 30, 2022 16:22
Thanks, @lord-ralf-adolf – good piece of knowledge! Again, learned something new :)
Jul 30, 2022 16:22
@lord-ralf-adolf for sd cards, isn't that rather something with vold in its name – e.g. vold.fstab (reference)?
 
Jul 30, 2022 05:30
@Sachin Thank you! I wasn't aware of 1. -- and with 2. I have some doubts in this context: sure, the unlocking itself must not gain root access. But the custom recovery certainly will -- since without root permissions, how then would it be able to access the partitions to do a NAND backup (aka NANDroid)?
Jul 30, 2022 05:30
You are both correct: Users afraid of rooting will probably be afraid of flashing custom images as well (which might even be impossible considering locked bootloaders) -- I only implicitly thought that to be clear. So technically, Sachin's answer is valid at least for unlocked devices -- though most "standard users" won't apply it. And thanks to Sachin for pointing this out -- it's easily forgotten otherwise. Thinking out loud: Booting into that recovery, one becomes root -- or not? ;)
 
Jul 30, 2022 05:26
@RyanConrad I guess this answer might require some updates: apps can opt-out of adb_backup (setting ALLOW_BACKUP to "no" in their Manifest files). If "root users" want to work around this, there's the Backup All Apps Xposed module, but no way around it without root. Maybe you also should point out what is not covered (apart from what you've already mentioned – see porg's "!Beware!" comment above). Plus maybe integrate other hints from the comments, and then request a comment cleanup?
Jul 30, 2022 05:26
Thank you, Ryan (and +1, of course)! Did I read correctly that this does a full backup including all data? So there's no snag (except one needs the SDK installed)? Almost sounds too good to be true! And also thanks for your shameless self promotion xD
Jul 30, 2022 05:26
BTW: Adding to your solution, just today I found a post on the XDA News: Ultimate Backup Tool, No Root Required. This "Ultimate Backup Tool" is just a simple .bat file calling the ADB commands you mentioned (Pastebin) -- and thus can serve as "inspiration" to Linux/Unix/Mac friends to create a similar shell script ;)
 
Jul 28, 2022 20:45
Glad to read, Emil! And yes, test it a little more. When there are no side-effects, consider answering your own question :)
Jul 28, 2022 20:45
@Emil Link fixed (try again); if it toggles each app, they've changed it at some point (wasn't always like that); no, you can't – except when using microG as replacement on a device without any GApps installed.
Jul 28, 2022 20:45
@Emil Yes, that's the global setting – used as the default for new app installs. If you check each app entry in the Playstore app separately, you will see each has its own check-box for that. Regarding updates: System apps can obtain the permission to install apps: INSTALL_PACKAGES.
Jul 28, 2022 20:45
"how is it able to re-download, and re-install, itself?" – It is considered part of the GSF which Google considers part of the OS and "critical update". What you could check, though: Next to the "global" switch to "Auto-update apps", check how all the Google components are set up. The global setting only applies to apps installed after you adjusted it. I expect at least Playstore and GSF still being set to auto-update.
Jul 28, 2022 20:45
@Firelord if it's some Google enforced crap that GMS pulled, I'm not so sure about the "user installed app" part. GMS is a system app. Moreover, Google apps automatically get more privileges due to their signature (protection level "systemOrSignature"). // A dirty trick coming to my mind: if you know the package name of the unwanted addition, build a dummy app with the same name and install that – so GMS cannot update it due to signature mismatch. Not tried, but could work ;)
 
Jul 28, 2022 20:34
Note that Flashtool is available for Linux as well. No specific drivers needed there (I have an MTK tablet which I had to "repair" for a similar issue). // May I suggest you cleanup the comments? @esQmo_ please integrate relevant material with your answer and for the then obsoleted comments, delete your own and flag the others? It's quite a tail already :)
 
Jul 9, 2022 04:07
The link to the APK from Aptoide would be pool.apk.aptoide.com/apps/… – as @Robert coectly pointed out, going via their website you'll always get their app, regardless where you try (you can veriffy that by trying to download a few different apps, you'll see the APK you get will always be the same). As for the other two: different versions maybe? aapt d badging <APKFile> | grep -i versioncode could tell you that. (Robert: please flag comments for cleanup after posting your answer & summing up)