When you first delete a file in Asus File Manager on your Android smartphone, a dialogue box pops up to confirm that you want to temporarily delete the file to the Recycle Bin. Included on this screen is a check box labelled “Permanently delete”. Checking this box has the advantage that disk space is saved since the file is actually deleted rather than being stored in the Recycle Bin for possible future recovery (or permanent deletion when the recycle bin is cleared).
However, once this box is checked, there doesn’t seem to be an in-app process of reversing the decision. All future file deletions are permanent and the Recycle Bin is no longer used.
As far as I can tell, the only option to restore the use of the Recycle Bin is to uninstall Asus File Manager, then re-install the app, and make sure that the “Permanently delete” box remains unchecked.
[ZenFone] How do I use Recycle Bin of File Manager?
Running Update Manager resulted in an error message to the effect that a Personal Package Archive (PPA) for the Opera web browser, was missing and/or unavailable.
Posted in Mint, Web browser
I recently downloaded and installed the LineageOS 14.1 custom ROM (Nougat) developed by MSe1969 (see A Stable Custom ROM for the Moto G3). My rationale was that this is one of the few – the only one that have found – custom ROM’s that has a recent history of monthly updates with Google’s security patches.
A bizarre consequence of installing the 14.1-20190810-UNOFFICIAL-oms-osprey (LineageOS 14.1) custom ROM proved to be that the timer in the clock app was set to use the Rooster Alarm sound file – and there didn’t seem to be anything that I could to the app to change this.
One of the annoyances with certain versions of Android is its insistence on indicating that “You are running low on free space” and, in particular, refusing to update apps even when the available free space is much greater than the size of the update. Of course, this is mainly a function of the limited internal memory of my (now) ancient Moto G3 smartphone. But, even so, this senior citizen nominally has 8 GB of memory, and usually has at least 500 MB of free space (with tons more on the separate SDcard – which evidently doesn’t count!)
The grand scheme for my Moto G3 2015 (osprey) smartphone was to use a custom ROM produced by an established team of developers (see: A new custom ROM for the Moto G3) proved to have short-lived success when no updates were forthcoming. So, the search was on for yet another – stable – custom ROM.
Having performed a number of Custom ROM installations on my Moto G3 2015 (Osprey) smartphone, I think I now have the procedure nailed down. So, for my future reference, and for anyone else who may find these useful, the following are the steps involved in backing up an existing Android system and installing a custom ROM: