Develop Bugs

[Q] What is telephony.db? What are consequences of deleting?

So on CM6.1 I cannot SEND mms. I can get them but when I attempt to send it does nothing...and every time after that I open the thread it is sitting there for me to send again but it never works.
There are two 'fixes' it seems. One involves deleting a file called telephony.db. (/data/data/com.android.providers.telephony/databases/telephony.db)
What is this file and what else breaks when you delete it? (Is this a file that is 'recreated' when phone boots or does it actually impact something in the system?
I cannot find anything about the file other than it's mention in the steps to delete it to make MMS on CM6 work.

sablesurfer said:
So on CM6.1 I cannot SEND mms. I can get them but when I attempt to send it does nothing...and every time after that I open the thread it is sitting there for me to send again but it never works.
There are two 'fixes' it seems. One involves deleting a file called telephony.db. (/data/data/com.android.providers.telephony/databases/telephony.db)
What is this file and what else breaks when you delete it? (Is this a file that is 'recreated' when phone boots or does it actually impact something in the system?
I cannot find anything about the file other than it's mention in the steps to delete it to make MMS on CM6 work.
Click to expand...
Click to collapse
Find out yourself: nandroid your current rom, delete the file and try it out. If something else breaks then restore, if not, well at least you now have a recent backup of your current setup.

It's the database that stores all your sms/mms messages. So when you delete it, it deletes all your messages (so back them up if you want them).
The file will get corrupted on occasion, and that causes problems with your text messaging, so deleting the corrupted file normally fixes it.

fenixjn said:
Find out yourself: nandroid your current rom, delete the file and try it out. If something else breaks then restore, if not, well at least you now have a recent backup of your current setup.
Click to expand...
Click to collapse
Fenixjn...please take this in the spirit of constructive feedback, but how did your response actually add to the knowledge collected in this thread? If I had wanted to...or was even willing to...don't you think I would have done that?
The issue with your approach, and I have been around the IT world for almost 20yrs is that I have no information on how to even start a regression test of 'delete..and try it out'. If I went to a boss with that plan for a software change they would hit the roof.
I am here to find out what the file is...thereby understanding what the potential impacts are so that I can plan for them. Your approach could have impacts many many days/weeks down the road and then what? Nandroid back to something that has weeks old information about my apps, calls, messages, calendars...??

souleman said:
It's the database that stores all your sms/mms messages. So when you delete it, it deletes all your messages (so back them up if you want them).
The file will get corrupted on occasion, and that causes problems with your text messaging, so deleting the corrupted file normally fixes it.
Click to expand...
Click to collapse
Interesting...so is this NOT something that would get wiped by Davlik/Cache/ect? Because I started from a clean slate going from rooted stock to CM...and did them all twice even.

Ok, sorry for multiple threads but trying to keep info straight for now...
I used adb to delete the telephony.db file. This allowed handcent to work but no the stock mms. BTW...telephony.db does NOT store your texting history. That is stored in mmssms.db. I know this because when I renamed mmssms.db my chat history was gone but not when I deleted telephony.db.
Now the follow up is that when you delete telephony.db it is remade when you reboot the phone. It was there right after when I adb'd back in. Same with mmssms.db.
So...back to square one on the CM6.1 mms. It is not working for sending. Am I really the only one that has this issue? Where can I report it as a bug? The 6.1 thread is over 1800 posts long and no one seems to look.

Tying up the threads I had...MMS is now working. Honestly I cannot say why, but maybe someone else will need this info.
The telephony.db and the mmssms.db do not appear to be the cause of the issue. Also you can rename them in adb....and when you reboot they are recreated. I went in and deleted the news and returned the .olds to the right name and all my texts came back.
Not sure if that will ever help anyone, but there you go.

sablesurfer said:
Fenixjn...please take this in the spirit of constructive feedback, but how did your response actually add to the knowledge collected in this thread? If I had wanted to...or was even willing to...don't you think I would have done that?
The issue with your approach, and I have been around the IT world for almost 20yrs is that I have no information on how to even start a regression test of 'delete..and try it out'. If I went to a boss with that plan for a software change they would hit the roof.
I am here to find out what the file is...thereby understanding what the potential impacts are so that I can plan for them. Your approach could have impacts many many days/weeks down the road and then what? Nandroid back to something that has weeks old information about my apps, calls, messages, calendars...??
Click to expand...
Click to collapse
The great thing about your phone is that you can do a backup and restore in less than 5 minutes. Honestly, you don't have to flash your seniored ID badge around here. Just do a backup, delete, restore.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

awesomecomb said:
The great thing about your phone is that you can do a backup and restore in less than 5 minutes. Honestly, you don't have to flash your seniored ID badge around here. Just do a backup, delete, restore.
Click to expand...
Click to collapse
I think the OP has a valid point. And just because you CAN simply backup and restore, doesn't mean that the right approach to troubleshooting is to start deleting files and retreating to backup when you discover you've hosed yourself.
These are complex devices, and willy-nilly deleting of files that are not (normally) user-accessible or -editable is a prescription for your own telecom disaster. (A reason that they are not user-editable, perhaps). Asking if anyone can provide insight on the workings of configuration files is a smart technique. Be targeted in your approach, and instead of taking 5 minutes to do X, Y, Z, it takes 2 minutes and gives you better results.
The process is equally as important as the outcome.

I'm kind of curious as to what is in this telephony.db...has anyone tried to cat it? I would, but I'm at work :/

good to know.

Biting in this thread after quite sometime. My CC ( Cheap Chinese ) Jiayu S3 phone cracked. with Debugging prolly disabled I was doomed.
Went through through that Nivranic Journey to restore logs contacts and SMS's and restored contacts.db telephony.db and another <dot>db ( cant rem ) to my HDD. So WHATS inside telephony.db
ALL the metadata regarding your ISP - frequency , geo region etc etc.
Here is a peek of telephony.db
I think part of the data is provided by the ROM itself as as data already known cos a lot of these Telephone providers are totally unknown to me ( not sure if roaming got them there - not likely ) and part of the data added is "learnt"
I think this file is pretty much dispensible as all these facets of info can be "learnt" by the new phone or ROM

Low Storage.

Have searched and searched but cannot find something directly pertaining to System Rom memory full.
What would cause Rom being full and what can be done to make it not so? It's a stock rooted system and all apps that can be have been moved to SD card and everything not needed uninstalled. Handcent, Dolphin, and everything else could think of is set to save cache to SD card as well.
Here's a pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

My recommendation would be do a Nandroid and save your apps with BT.. and do a hard reset and see if that fix the problem.... I never had this problem before.....
Edit: Now I want to know too... cuz my is acting weird now too...
260MB (24.7 MB free) can anybody tells us why this happen....????

1107963 said:
Edit: Now I want to know too... cuz my is acting weird now too...
260MB (24.7 MB free) can anybody tells us why this happen....????
Click to expand...
Click to collapse
Was traveling yesterday so wasn't able to do any research but no matter what I do it will not get above 7.66MB free. Now after reloading the time doesn't auto update when crossing a time zone... gotta find that too.

Ben,
That's the way it is due to amazing silly usage of resources by HTC in the Incredible. du ./system = 260M and that's it. If you're using the stock system, then it just happens to add up to about ~7M free. Unless you're going to reapportion all the initial partitions, then you can't do anything about it.
All the ROMs are the same unless they've made radical changes, but all the ROMs will have different amounts of free out of the 260M.
If you want to 'fix' it, then you've got all you need if rooted and have TB. Just use ADB or a terminal emulator to do something along these lines (being careful and taking notes so you can retrace the steps if needed):
1) su ; mount system r/w (you can tell which partition it is using 'df' or 'mount' command from a shell and it is of type yaffs2
2) cd /system/app ; ls -l *[Hh][Tt][Cc]* ; ls -l *[Ss][Ee][Nn][Ss][Ee]* and check out which are kind of sizable. All you care about is stuff that is under ./system/... because things like handcent and other userspace apps are really in /data/app, and have nothing to do with this problem.
3) When you locate a few (you can do 2&3 in reverse if it makes more sense) big ones, then use TB to 'freeze' as many *SENSE* and *HTC* as you think you don't use (be careful or you'll have to restore a backup). If it's running OK with the things frozen, then you can return to the file system (./system/app) and delete the ones you've frozen. You can tell from TB which filenames go with which apps you've frozen.
4) Delete them or move them if it makes you feel safer to /sdcard/{create a dir here}.
5) df ; and look at free space in /system. It should be getting larger. When you've got ~20-30 free, you've got plenty for most things, and can remount /system a r/o (read-only).
--------------
Why? For example: If you wanted to install, for some reason, one of Lou's kernels, where he for some reason, uses separate modules for everything (It is nice in desktop linux, but sucks in the droids), then they'll go into /system/lib/modules/* and eat up a ton of space (Like 25M), and basically fail on your current system.
If you use one of Ziggy's kernels, he tends to compile all modules but Wifi into the kernel itself, coming up with a similarly sized kernel as Lou but with the functionality built-in. I use all the functionality so I like that, but if you're using the stock kernel and don't care, then forget that.
HTC did some nutty stuff with this thing, like /emmc having 6+ GB but none of it is of much use to most users, then /data/data which is where all the userspace programs keep their data and libs, is tiny, giving way to the 'out of space' message when installing programs. Google Earth, for example uses 30M in libs itself.
The only reason I used the syntax *[sS][Ee]* etc, was because I fixed this up long enough ago so that I forgot if Sense and HTC apps were case sensitive (I mean used upper case and lower or some combo of those), so this is just covering bases.
If you don't use much social networking stuff (99% of HTC & Sense apps), then you don't need a lot of /system/app files and will do OK. If you use all of that, then I suppose you're stuck unless you can locate other things you never use. (there has to be stuff you don't use). If it gets deleted from /system/... then it releases space to you in what you're calling the system ROM.
Use caution -- Changing anything from /system is asking for trouble, so make sure it's not a showstopper.
Good luck - Hashi

Thanks hachamacha for all the info. After looking at the /system and /system/app folder, I can see several files that I care nothing about. I'm going to do some research and try and find some dependencies on some of the files cause seeing files like stocks, twitter, newsreader, friend stream, radio, and amazonmp3 could clear up a lot of room. Just don't want to freeze/move any of them then discover they are a requirement for some other function.
Guessing I only need to clear up a MB or two as the only time I see the warning is when installing a program or have several running at once. It doesn't lock up and require a batt pull, just freaks me right the hell out.

dependencies
BenHolliday said:
Thanks hachamacha for all the info. After looking at the /system and /system/app folder, I can see several files that I care nothing about. I'm going to do some research and try and find some dependencies on some of the files cause seeing files like stocks, twitter, newsreader, friend stream, radio, and amazonmp3 could clear up a lot of room. Just don't want to freeze/move any of them then discover they are a requirement for some other function.
Guessing I only need to clear up a MB or two as the only time I see the warning is when installing a program or have several running at once. It doesn't lock up and require a batt pull, just freaks me right the hell out.
Click to expand...
Click to collapse
You may want to checkout Autorun Manager (free app from market) to see what apps startup automatically, and more importantly, have interdependencies with other apps/programs.
Specifically, it tells you what apps have receivers, and gives you the ability to disable programs from autostarting. It's another way of disabling an app or program temporarily instead of randomly disabling/freezing apps in TB.
Might help. Might not.
Much love

chris7os said:
Specifically, it tells you what apps have receivers, and gives you the ability to disable programs from autostarting. It's another way of disabling an app or program temporarily instead of randomly disabling/freezing apps in TB.
Might help. Might not.
Much love
Click to expand...
Click to collapse
Kewls and thanks. That it will tell what depends on the programs is what I'm looking for. No time to list all of them, but I froze about 20+ apps with TB. Didn't have any troubles all day yesterday but maybe can *.bak them and move to computer until needed.

Platform.xml caused broken bluetooth and write permissions

So, this all started, because I was annoyed that Dolphin Browser, wouldn't let me save directly to the external_SD\download folder. I googled, and found out it was a thing since 4.4, that writing to the SD card was kinda wonky. Anyway, I did the "fix" where you add those lines in the platform.xml file, and bluetooth no longer works (something I use every day, so it's important to me). I deleted the file and restored my backup, which at the very most, stopped the bluetooth toast error from constantly appearing. Now, I can no longer take screenshots, or use the camera app. I also noticed that sdcard0 no longer shows as an active directory. Everything appears to have been moved to emulated\0. I have used Root Explorer to try and change folder r/w permissions, to no avail. I'm wondering if having Apps2sd move everything to the sd card, the day prior, aided in this debacle. I have tried using the apps on the play store to fix the sd issue, which just tell me that it's already fixed, even though it isn't.
Is there a known fix to this, other than wiping and starting completely over? When I attempt doing a factory reset, do I need to have the rooted image on the root of the internal memory, and by that I mean, do I need to re-access sdcard0, or will it work on the emulated/0 mount? Will this cause a boot loop?
I am on 11A, and rooted.
I have read all the threads I could on this, but I didn't really see a solution.

ishb3w said:
So, this all started, because I was annoyed that Dolphin Browser, wouldn't let me save directly to the external_SD\download folder. I googled, and found out it was a thing since 4.4, that writing to the SD card was kinda wonky. Anyway, I did the "fix" where you add those lines in the platform.xml file, and bluetooth no longer works (something I use every day, so it's important to me). I deleted the file and restored my backup, which at the very most, stopped the bluetooth toast error from constantly appearing. Now, I can no longer take screenshots, or use the camera app. I also noticed that sdcard0 no longer shows as an active directory. Everything appears to have been moved to emulated\0. I have used Root Explorer to try and change folder r/w permissions, to no avail. I'm wondering if having Apps2sd move everything to the sd card, the day prior, aided in this debacle. I have tried using the apps on the play store to fix the sd issue, which just tell me that it's already fixed, even though it isn't.
Is there a known fix to this, other than wiping and starting completely over? When I attempt doing a factory reset, do I need to have the rooted image on the root of the internal memory, and by that I mean, do I need to re-access sdcard0, or will it work on the emulated/0 mount? Will this cause a boot loop?
I am on 11A, and rooted.
I have read all the threads I could on this, but I didn't really see a solution.
Click to expand...
Click to collapse
i know the feeling but it is best to KDZ 11A on your phone and then reroot it to be safe. there is a way to get the SD card fix without messing with the XML file, i have 1 app but i cant post it on here but i do some looking around tomorrow and i let you know the best one you can use to write to SD card, i got y G4 unrooted to do a video, so once i get it rooted and do some looking around. i let you know
my youtube channel can show you how to use a KDZ file
https://www.youtube.com/watch?v=KDnfyWhSEEo
dont use the same file that i used, just use your 11A KDZ if you want to stay on 11A. if you want to use 13B please use the LGUP tool dont take the OTA cause you may be pushed to 25A

ishb3w said:
So, this all started, because I was annoyed that Dolphin Browser, wouldn't let me save directly to the external_SD\download folder. I googled, and found out it was a thing since 4.4, that writing to the SD card was kinda wonky. Anyway, I did the "fix" where you add those lines in the platform.xml file, and bluetooth no longer works (something I use every day, so it's important to me). I deleted the file and restored my backup, which at the very most, stopped the bluetooth toast error from constantly appearing. Now, I can no longer take screenshots, or use the camera app. I also noticed that sdcard0 no longer shows as an active directory. Everything appears to have been moved to emulated\0. I have used Root Explorer to try and change folder r/w permissions, to no avail. I'm wondering if having Apps2sd move everything to the sd card, the day prior, aided in this debacle. I have tried using the apps on the play store to fix the sd issue, which just tell me that it's already fixed, even though it isn't.
Is there a known fix to this, other than wiping and starting completely over? When I attempt doing a factory reset, do I need to have the rooted image on the root of the internal memory, and by that I mean, do I need to re-access sdcard0, or will it work on the emulated/0 mount? Will this cause a boot loop?
I am on 11A, and rooted.
I have read all the threads I could on this, but I didn't really see a solution.
Click to expand...
Click to collapse
ok sorry that this is late but i found an app, enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I tried that app, and mentioned it in my OP. It doesn't do anything, it tells me my phone has already been fixed (even though it wasn't).

ishb3w said:
I tried that app, and mentioned it in my OP. It doesn't do anything, it tells me my phone has already been fixed (even though it wasn't).
Click to expand...
Click to collapse
hmm, when i used it and used my other app, it said it fixed the sd card issue, i can keep looking for you, sorry i haven't replied for awhile. been playing with the lg V10 and LG G3

No MicroSD card Encrypton... only Samsung has it?

I have both phones, Z Play and Galaxy A7 2017, Z Play is the one I like more because of audio, response (not lag at all compared with the A7), etc, only the camera in A7 is better than Z Play but something is impeding me to use as a daily driver: external SDCARD Encryption, how can it be possible?... I have EX. SDCARD Enc enable option in my A7 and there is no performance impact, why Lenovo didn't do that too?... is it dependent to a chip or something like that? unbelievable to be honest.

Try to format it on device and see if you get asked if you want it to be formatted for media or for apps. Choose the latter one

Encryption is good way to lose your data if something happens to your device or perform factory reset.
Maybe Android solved that issue? Login to Google acc will gain access to encrypted sd card in another device?
Sent from my XT1635-02 using Tapatalk

Thanks for your reply, in the screenshot of my A7 I have the option to encrypt or decrypt my SD with a simple click maintaining your data (the microSD is not formated), never lost information and of course, before you change the phone you should decrypt the data otherwise you will loose it.
This function is excellent because if someone stole your phone, your pictures or whatever you have in your phone will be protected, I really like the moto phone, but with this functionality is impossible, last year I got my phone stolen from the metro, so this stuff happens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

citytrader said:
Thanks for your reply, in the screenshot of my A7 I have the option to encrypt or decrypt my SD with a simple click maintaining your data (the microSD is not formated), never lost information and of course, before you change the phone you should decrypt the data otherwise you will loose it.
This function is excellent because if someone stole your phone, your pictures or whatever you have in your phone will be protected, I really like the moto phone, but with this functionality is impossible, last year I got my phone stolen from the metro, so this stuff happens.
Click to expand...
Click to collapse
Well this is a Samsung only feature. Android can encrypt SD cards since 6.0, but that's only if you format it for storing apps. You most likely won't be able as your normal SD card. If you want to take it to another device you'll have to format it. I'm theory it's possible to take the key from your old phone and implement it into your new one so you could just keep on using it, but that's just theory and would be quite difficult.

Artim_96 said:
Well this is a Samsung only feature. Android can encrypt SD cards since 6.0, but that's only if you format it for storing apps. You most likely won't be able as your normal SD card. If you want to take it to another device you'll have to format it. I'm theory it's possible to take the key from your old phone and implement it into your new one so you could just keep on using it, but that's just theory and would be quite difficult.
Click to expand...
Click to collapse
Something I don't understand is if Samsung did it why Lenovo for example didn't yet... I really like this Z Play but the encryption is a big limitation for me.

citytrader said:
...of course, before you change the phone you should decrypt the data otherwise you will loose it.
Click to expand...
Click to collapse
If you remember to do that and/or still have the old phone

Zeljko1234 said:
If you remember to do that and/or still have the old phone
Click to expand...
Click to collapse
That is ok, but what happen if you phone is stolen!?... are you happy if anyone can check your pictures for example?

citytrader said:
That is ok, but what happen if you phone is stolen!?... are you happy if anyone can check your pictures for example?
Click to expand...
Click to collapse
Depends what kind of pictures Anyway, I agree with you just giving another point of view

citytrader said:
Something I don't understand is if Samsung did it why Lenovo for example didn't yet... I really like this Z Play but the encryption is a big limitation for me.
Click to expand...
Click to collapse
Because they chose to use stock Android with little to no modifications. Samsung on the other hand cripples down Android to something unuseable. Using their encryption methods will kill off all possibilities of nothing modifying since TWRP can't handle them. I don't know if they finally switched to the standard methods but at least it was so on my Note 4.
So the only two options you have is to stick to that Samsung garbage or just get an app that can create encrypted folders. That way not the whole SD card will be encrypted but everything you want to

Artim_96 said:
Because they chose to use stock Android with little to no modifications.
Click to expand...
Click to collapse
That is why I like a lot Moto, for example I have enabled the pattern lock at boot, it means that even to access TWRP you need to pattern unlock, at this point I can put all the important files in the internal memory. Is this safe in this way?... it will be not encrypted but there wont be a possibility to access the file system, am I correct?
I tried EDS and the file write speed is about 2MB/s, without encryption, the internal memory speed is 50MB/s and the external is 20MB/s...

citytrader said:
That is why I like a lot Moto, for example I have enabled the pattern lock at boot, it means that even to access TWRP you need to pattern unlock, at this point I can put all the important files in the internal memory. Is this safe in this way?... it will be not encrypted but there wont be a possibility to access the file system, am I correct?
Click to expand...
Click to collapse
They are encrypted. The whole /data partition is encrypted. The internal storage (that part you can access even without root) lives under /data/media/0. Other mountpoints like /sdcard in TWRP is just how it's made accessible, try are only links. That's why you can't just format or change file system of /data in TWRP. If you "wipe" it it'll tell you it deletes everything but /data/media. So if you have bootup security enabled it's impossible as far as I know to get to those files. Sure, someone would be able to flash custom ROMs through fastboot but I doubt it's possible to make one that can give you access without password. And the key is stored inside a SoC in a digital part that can't just be written and can't be read from outside.

Booting into fastboot and flashing different recovery will probably get rid of your pattern protection.

Zeljko1234 said:
Booting into fastboot and flashing different recovery will probably get rid of your pattern protection.
Click to expand...
Click to collapse
I don't believe it could be very easy to do, take a look at the screenshot I did when booting the phone, there is a block that needs to be decrypted and I think that block is encrypted independently of the recovery you have... that is only my speculation...

Zeljko1234 said:
Booting into fastboot and flashing different recovery will probably get rid of your pattern protection.
Click to expand...
Click to collapse
No. The only pattern protection that can be circumvented is the one on the lockscreen. Circumventing the one for bootup protection is impossible for all I know.

Artim_96 said:
No. The only pattern protection that can be circumvented is the one on the lockscreen. Circumventing the one for bootup protection is impossible for all I know.
Click to expand...
Click to collapse
Ok, good to know. Thx.

Why would you want to encrypt SD card? If it gets corrupted for any reason and the only way to view info is from a PC (since Android won't mount it) then your data is toast...
Sent from my [device_name] using XDA-Developers Legacy app

techware7 said:
Why would you want to encrypt SD card? If it gets corrupted for any reason and the only way to view info is from a PC (since Android won't mount it) then your data is toast...
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you lose your phone or someone steal it, how do you protect the info? Is it supposed that the info in the card is backuped, so if there is corruption on SD (never happened in my A7) shouldn't be a problem.

a) I use my phones such that if anything on the phone is put up on a billboard, I won't care. Course some days I flash 5 different ROMs... :|
b) you might try Lenovo's forums and see if you get any ideas there...
https://forums.lenovo.com/t5/Moto-Z-Phones-Mod-Capable/ct-p/Moto_Z_Mod_Capable
c) maybe a googleplaystore app that would do what you need?

Uninstalled System Apps reappear all the time

So i wanted to uninstall some bloatware and telemetry apps with mixplorer. But shortly after i delete them, they just reappear in the folders.
Never had this on oxygenos 9. What happened here on oxygenos 10? Is there some service that just restores deleted system apps or something?

MarcTremonti said:
So i wanted to uninstall some bloatware and telemetry apps with mixplorer. But shortly after i delete them, they just reappear in the folders.
Never had this on oxygenos 9. What happened here on oxygenos 10? Is there some service that just restores deleted system apps or something?
Click to expand...
Click to collapse
You can't mount /system as rw in Android 10 while booted. Any changes that you do (or try to do) will get reverted after a reboot. It is possible to do that via TWRP though.

shadowstep said:
You can't mount /system as rw in Android 10 while booted. Any changes that you do (or try to do) will get reverted after a reboot. It is possible to do that via TWRP though.
Click to expand...
Click to collapse
Ahh, didnt know that. In TWRP it indeed worked. Thx mate! :good::highfive:

@shadowstep @MarcTremonti I'm experiencing this SAME issue and it's driving me crazy but I don't quite understand the solution that was given here and apparently worked; would one of you kindly explain this further so I can solve this problem for myself? I'd really appreciate it .

FamilyGuy0395 said:
@shadowstep @MarcTremonti I'm experiencing this SAME issue and it's driving me crazy but I don't quite understand the solution that was given here and apparently worked; would one of you kindly explain this further so I can solve this problem for myself? I'd really appreciate it .
Click to expand...
Click to collapse
Whatever changes you're making in the /system partition, make them through TWRP's built-in file manager (instead of attempting to make them via a root file manager while booted into android -- which won't work anymore):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@shadowstep I'm a bit confused. I'm trying to uninstall apps using Titanium Backup. How do I uninstall an app using TWRP? I can do that via the file manager? If so, how?

FamilyGuy0395 said:
@shadowstep I'm a bit confused. I'm trying to uninstall apps using Titanium Backup. How do I uninstall an app using TWRP? I can do that via the file manager? If so, how?
Click to expand...
Click to collapse
You have to delete the folder containing the app via TWRP's file manager, for example, /system/app/<AppName> or /system/priv-app/<AppName>.

@shadowstep I just did this for the YouTube app and the app still exists and functions normally. Any idea what I did wrong? Also, does the TWRP file manager actually lack a search function to make sure all YouTube files are indeed gone?

FamilyGuy0395 said:
@shadowstep I just did this for the YouTube app and the app still exists and functions normally. Any idea what I did wrong? Also, does the TWRP file manager actually lack a search function to make sure all YouTube files are indeed gone?
Click to expand...
Click to collapse
You probably removed it from the system partition, but have an update from Play Store installed (which will be a normal app, uninstallable normally like any other installed app after booting). Also, TWRP is only a recovery environment, not a full fledged, feature rich UI. It's meant to be minimalistic and small in size.

@shadowstep I know I deleted the entire folder in data/app but, doing a search in my file explorer (Solid Explorer), I still see some leftover stuff from YouTube in my root folder (specifically, in system/product/app, config/sdcardfs, and a ton of other folders actually). Are you aware of any recovery file browser I can flash and use that has a search function? I ask this because I have a feeling I'm going to run into this crap again with other apps, and would prefer to not have to write down all these folders and manually delete them all individually as that'll take forever.
Also, since you've been enormously helpful, I'd love to get your input on another Android question that's been burning in my mind lately and I cannot for the life of me find any solution online or in the many forums I've been to:
I'm trying to download some files from one of my apps to my android phone hooked up to an external hard drive. However, the app will not let me download to the hard drive, and instead auto installs to the Downloads folder in my internal storage. When an app doesn't let you choose a download location, is there anyway around this where I can force the app to download files where I want it to?
I'm sorry to burden you with all my junk but you've truly been the only helpful person I've been able to find to answer these questions I've been having.

FamilyGuy0395 said:
@shadowstep I know I deleted the entire folder in data/app but, doing a search in my file explorer (Solid Explorer), I still see some leftover stuff from YouTube in my root folder (specifically, in system/product/app, config/sdcardfs, and a ton of other folders actually). Are you aware of any recovery file browser I can flash and use that has a search function? I ask this because I have a feeling I'm going to run into this crap again with other apps, and would prefer to not have to write down all these folders and manually delete them all individually as that'll take forever.
Also, since you've been enormously helpful, I'd love to get your input on another Android question that's been burning in my mind lately and I cannot for the life of me find any solution online or in the many forums I've been to:
I'm trying to download some files from one of my apps to my android phone hooked up to an external hard drive. However, the app will not let me download to the hard drive, and instead auto installs to the Downloads folder in my internal storage. When an app doesn't let you choose a download location, is there anyway around this where I can force the app to download files where I want it to?
I'm sorry to burden you with all my junk but you've truly been the only helpful person I've been able to find to answer these questions I've been having.
Click to expand...
Click to collapse
If you're on OOS 10, the system instance of YouTube is actually in the product folder (/system/product/app/YouTube). That's the folder you have to delete via TWRP's file manager to remove YouTube from the system partition.
If you still see YouTube installed after removing that, then it's most likely a user instance of the app (system instance = pre-installed by the manufacturer; can only be removed via root, user instance = normal installation by the user/Play Store; can be removed via normal uninstall while booted).
You don't have to remove any other file(s). The APK is the main thing.
Regarding your second question, I'm afraid that's something I don't know. I've never had to do that so never dug into it. Google is your best friend at this moment. Good luck!

@shadowstep I've now deleted both folders in TWRP and the app is still here . I also can't delete it normally like a non-system app. I'm about to lose my mind .

FamilyGuy0395 said:
@shadowstep I've now deleted both folders in TWRP and the app is still here . I also can't delete it normally like a non-system app. I'm about to lose my mind .
Click to expand...
Click to collapse
Hmm. In that case, try the Magisk method using Terminal Debloater: https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163

shadowstep said:
Hmm. In that case, try the Magisk method using Terminal Debloater: https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163
Click to expand...
Click to collapse
THANK YOU SO MUCH! That module did the trick! For some reason, there are still some apps that are being pesky and not getting detected/deleted, but that module helped get rid of almost all of these annoying apps. Thanks again!

FamilyGuy0395 said:
THANK YOU SO MUCH! That module did the trick! For some reason, there are still some apps that are being pesky and not getting detected/deleted, but that module helped get rid of almost all of these annoying apps. Thanks again!
Click to expand...
Click to collapse
Glad I could help.