It's no secret that the operating system Android widespread in the mobile world.

Such a widespread use of the brainchild from Google also provokes an increase in the number of hacker attacks on this platform. In order to combat this unpleasant moment, the IT giant is trying to introduce new functions aimed at increased safety owners of devices with the Android system, but some of these functions can become a source of additional inconvenience. How to eliminate one of these inconveniences will be discussed below.

Restricting access to the memory card

In the subject Memory on Android. All sections of the memory of Android devices we have already touched on the issue of mobile operating system memory. Many smartphone users based on Android versions 4.4 and older faced a situation where third-party programs do not have access to the root of the memory card... Moreover, this problem also arises for those who purchased new apparatus already with Android KitKat and higher on board, and for those who have updated to the new system after the purchase.

Why can't Android programs have access to the root of the sd card?
The fact is that open access to the root of the drive is a big security hole in the entire operating system... Trying to protect users from intruders, Google went to such a step as limiting access to the memory card.

In simple terms, in many firmware based on Android 4.4 and higher, third-party programs can no longer write data to the root of the memory card. The ability to write to directories located on a flash card is preserved. The situation is aggravated by the fact that this limitation affected all applications, without exception, including file managers.

This state of affairs does not suit everyone, so below we will consider a way to return access to the root of the memory card to third-party programs.

It's finished! On the tablet, namely, on the Asus MeMO Pad 7, which I am replacing my honest workaholic, an update to Android 5.0.1 arrived. Now I have a device with Lollipop, or, as they say on the Internet, with Lolipopa.

The update arrived somewhat unexpectedly. To be honest, I was expecting a new firmware for my phone (Asus ZenFone 5) in April - at least they promised it. Nobody said anything about the tablet and here - on you, get it and sign it.

This, in fact, discouraged me (in a good, of course, sense), also because I bought the tablet in December, and it had version 4.3. That is, this is the second significant update of the operating system (in fact, there were more updates, but the Android version number has not changed). The previous manufacturer of my devices - Samsung - could not boast of such a rate of fire, although it also updated the operating system twice: from Android 3.2 to Android 4.1.2 (via 4.0.1). Only now it took much longer to wait for these new versions.

Well, long live surprises! Having received a notification about the release of a new firmware version, I immediately downloaded it, which is more than 700 meters, and launched the update. Since I downloaded not through my home network, but through a mobile one, it took a little more time for everything about everything: about an hour passed from the start of the download to the completion of the update. The update itself lasted about twenty minutes, but, potentially, it can take more time - because after installing the operating system, the update process follows installed programs... My counter counted to 205. But now, the process is over and it's time to see what has changed.

The first thing that caught my eye was the more sophisticated graphics when unlocking the device. The second is a hand in the notification area. For a couple of days I put up with her, hoping that by chance I would see something connected with her somewhere. Didn't see. Then I began to search purposefully and found an explanation on it on w3bsit3-dns.com. It turns out that notifications were divided into important and not so important, and it is possible to specify which notifications you want to receive. If you set the option Always alert , then the hand disappears if the option Important alerts only then the hand appears. To be honest, I removed my hand several times, but, for some reason, it stably returns. Why? I don’t know yet.

Here, in fact, is the procedure for "removing" this hand:

The above method is not complicated at all. But you can achieve the result even faster and easier: press one of the two volume control buttons - a window will appear on the screen, allowing you to change the volume levels for various system components, as well as, attention, control Alert modes ... True, for some reason, these same Alert modes are displayed in such a fast version not always. I haven’t found any patterns yet, but, to be honest, it didn’t hurt and I was looking.

A few words about installed programs. Although before starting the update process, I got a warning that some programs will be removed, since they are not included in the new firmware, nevertheless, most of the programs have survived.

The only thing I'm a little sorry about is a program with an atypical name "Two Applications". Although, I must admit, I did not even immediately understand what I was talking about: I was thinking which two applications would be removed, it was really impossible to specify the names.

Yes, the program that appeared in version 4.4.2 and allowed to share the screen between two simultaneously running applications has sunk into oblivion. To tell the truth, its functionality was rather weak, since it was possible to run a very limited range of applications at the same time. If my memory serves me, I only used it once or twice, just to see what it is. Maybe someone will miss the opportunities provided by this program, but somehow I was not particularly upset. Although, of course, I do not really like it when they take away what they gave before.

A couple more remarks about the programs. After I got over to a new tablet, for a while I installed programs on it that I used on my previous device. Some of them have happened, but we are not talking about them now. We are talking about those programs in the behavior of which something has changed. Of course, I have not managed to try everything yet, but here's what I found so far.

TuniIn Radio Pro, bought, by the way, did not work for me on KitKat. Everything went smoothly - until the queue came directly to listening to a radio station. That is, the program started, I selected a group of radio stations, for example, Local radio stations, selected a specific station (for example, RockFM, Radio Jazz, and in general, any station) after which the program crashed with an error. Sometimes there was even a sound, but the program still crashed. Time passed, TuneIn Radio updates were released, but nothing changed. However, after the upgrade to the five, the problems magically disappeared, now everything works without any complaints.

Another positive change is the office suite SoftMaker Office HD, also a fair purchase. The programs included in it worked fine on the Samsung tablet. When I installed these programs on a new tablet, they didn't start at all. After a while, an update was released for this office and the situation improved somewhat: programs began to run, however, in the process of work, in the menu area (the top line of the program window), some strange graphic artifacts accumulated. When switching to the desktop (or to another application) and back, artifacts disappeared, but not for long. After android updates all programs included in the package run like clockwork.

Well, a small negative point. I use, very actively, a program called Video Recorder. For her, too, I gave money. The program worked fine on the new tablet, no complaints, plus functions that were not available on the previous tablet, for example, video stabilization, worked. After updating the OS, the program began to crash at the start of recording. At first, I thought that there were some problems with writing to a memory card - I have set up a write to the program directory on an external MicroSD card. But, after I was able to create a subdirectory in the recording directory in the program itself, it became clear that the use of an external card had nothing to do with it. Then I decided to disable one program function at a time, and the first thing I touched my finger was a checkbox with a stabilization checkbox. After turning off the option, the program began to write video, but its quality dropped. No, the resolution and stream rate - everything remained the same, but the picture on the recording floated in waves. The program has a setting that tries to smooth out this effect, and, in principle, turning it on helps a little, but for some reason, when you re-enter the program, the very mark that the option is turned on remains, but the picture floats, as if the option is turned off ... If you poke into an already enabled option, everything is immediately normalized. Most likely, this is a bug in the program, I am going to report it to the developer and, perhaps, the author will fix this glitch. But the fact that video stabilization does not work is a little annoying. First of all, because the standard camera program has a stabilization option in the settings and, when it is turned on, the recording is carried out without errors.

From special cases related to programs, I will move on to more general properties of the system. Well, firstly, the amount of free memory has increased. As I already wrote, all my software remained in place. At the same time, I must say that I strain the tablet quite a lot. Not in terms of the fact that I constantly play games, but in terms of the fact that I have a lot of services hanging, some of which I may not use, but I keep just in case. First of all, we are talking about all kinds of mailers - Outlook, Yandex Mail, GMail, more precisely, now Inbox. Further, a variety of cloud storages - Yandex Disk, OneDrive, Google Drive, Dropbox, Box, Asus WebStorage. A couple of social networks - Odnoklassniki and Google+. All sorts of messengers - Viber, ICQ, Skype, Hangouts. All these programs, one way or another, consume the device's memory, even when you are not using them. But I, in principle, realize what I'm going for.

Users of Asus devices know that there is an application in the Android curtain that allows you to clear the memory, at least temporarily. It is called in the top five Cleaning, and in KitKat it was called more bizarrely - Gain. When you open the curtain, the icon of this application shows the amount of free memory at the moment. So, when the Android 4.4.2 version was installed on the tablet, this figure fluctuated in the range of 200-300 MB and the icon, most often, was yellow. Now the amount of free memory changes from 400 to 600 MB and the icon is green almost all the time. Probably, this change is due to the change of the virtual machine used in Lollipop, but perhaps something has changed in the firmware itself, for example, Asus removed something. In general, you need to figure it out.

The change of the virtual machine was supposed to affect two more parameters - speed and power consumption. What can I say about performance. Nothing, I guess. I don't play igruhi, I don't really like parrots (Antutu, etc.). The tablet itself is quite powerful, so I didn't notice any brakes either on KitKat or now in Lollipop. Everything is smooth and flawless. When I'm driving, I have a DVR, Arrow, Maps (either Yandex or Google) working, I also listen to music using Kodi, and after all this, it still reacts to switching to the desktop, launching some other programs, in general - a beast.

And about power consumption ... Basically, the latest update on KitKat deprived me of the opportunity to complain about the inefficiency of the device. If after the initial installation of KitKat the tablet lost 20-30 percent of its energy reserves overnight, then after updating to the 31st version of the firmware, the losses became quite acceptable - from two to five percent per night. Upgrading to Lollipop didn't make anything worse in that sense, and thanks a lot for that. As for consumption under load, here again I can cite the experience of operating in a car: all the same initial ones - DVR, Arrow, Yandex Navigator, Kodi, screen brightness somewhere around 75-80 percent - a bright, sunny day, plus all wireless interfaces are on , so, during the trip - about two hours - the battery was discharged to 57 percent. In my opinion, quite worthy. By the way, under KitKat it was about the same.

Well, and the last - in turn, listing, but not in order of importance - which I would like to note. It's about working with an external memory card. I, as I got out of the situation due to KitKat restrictions on writing to an external memory card. Apparently, the wave of negativity was so strong that Google had to listen and change something. Or maybe they just changed something, not listening to anyone. But let's leave this important issue aside (listened / did not listen), let's move on to the changes themselves.

Google allowed third-party programs to write to the memory card. In principle, he did not prohibit it before, just the permissions were set in such a way that, under normal conditions, only the native file manager had write access to the entire external card. Well, maybe some manufacturers also allowed access to their other programs, but I only came across a file manager. Now any program can write, but for this several conditions must be met.

First, the program must take advantage of the new features of the Storage Access Framework, namely, use the OPEN_DOCUMENT_TREE intent and several new or updated SDK functions.

Second, the user must decide for himself which branch (or branches) of the file system he will give access to this or that application. That is, you can give access to the entire card if, in response to a request for access, you specify its root, or you can give access only to a specific folder and its children. In general, you will have to take responsibility on yourself, and if something happens, you will also have to blame only yourself.

The third is luck. On my tablet everything worked as it should, with a friend on Htc one M8 - did not work, although online is there a video , how exactly on this model of the smartphone everything plows wonderfully. There is an assumption, however, that it did not work due to the fact that the card in his phone was formatted somehow wrong, maybe without specifying the volume name, or maybe in the wrong file system.

In fact, this is both joyful and sad news at the same time. Joyful - because now you do not need to get root access to the device and you can go beyond the application directory. Sad - because until the developers deign to use the new API and release new versions of their programs, nothing will work. From my experience: the file manager ES Explorer has already acquired support for the new API, and I managed to give it write rights to the entire external SD card, and the file manager Total Commander did not get it and still cannot write to the MicroSD card - nowhere, except your own directory. Like this.

In fact, there are quite a few nuances in this whole story with recording to an external memory card. For example, you gave access to some programs, but forgot to some. Where to look? I understand that, currently - nowhere. That is, in principle, you can see it, but not on the tablet itself, but on a computer, if you connect a tablet to it and use the adb program. Here's the command you need:

Adb shell dumpsys activity providers

But how to get the same thing on a tablet - I did not find it.

Next question. So you gave some application access to write to a folder, and then changed your mind and want to take it away. Is there such a possibility? Fortunately, yes. But, with losses. The first, very radical way - you can uninstall the program and reinstall it. The second method is not so cardinal, but also not ideal - you need to clear the application data in the Device Settings. Naturally, along with the access rights, other program data will be deleted, so a logical question arises about the practical applicability of this method. No other methods could be found, perhaps not yet. You can use both methods if you first back up the program data, and after bringing one of the methods into action, restore them. But here the question arises about the capabilities of backups - will only data be backed up, or will data along with permissions? If with permissions, then after recovery, well, you understand ... All this strongly depends on the specific applications used, so you should be very careful. And this is another good reason to think before seeing ancient Moscow, without the approval of the relevant authorities, to issue the rights to any application to access the file system of an external card.

Further more. What happens if you change the card inserted into the slot of your tablet? The answer is this: you will have to separately give access to each card that you insert into the device. In principle, this is probably logical. That is, you gave the file manager access to the root of the card, then took it out and inserted another. The file manager will not write to the new card, you will have to give access again. But when you return the first card to the tablet, the file manager will write to it without any problems.

One more question. Here you have given access to the application in some folder, not in the root. Time passed and you needed to allow write access to the same program in another folder on the same card. Can I do this? In principle, this is a consequence of the previous case, so the answer is yes, you can. That is, the system for each application will remember the list of directories to which you have given write access.

Now the nuance associated with applications installed on the tablet for each user whose profile is created on the device. Here, too, everything is logical - for each user of the device, their own access rights for applications are stored, that is, everyone is the blacksmith of his own happiness, or, if you want, his own evil Buratino.

And of course, a lot depends on the qualifications of the developers. It may happen that you give the rights to any program to access the external card for writing, and after restarting the tablet, you will find that there is no access. Only the developer of the program is to blame for such a situation - he did not bother to save the received permission. Perhaps you should think about and look for an alternative to this program, because you never know what such a programmer did not foresee.

And, yes, this is how the process of issuing write permissions to a microSD card for ES Explorer looks like:

We need an external card

Let's try to create something right at the root of the map

We need to display the SD card

Here it is, our external memory card

Well, now, perhaps that's it.

P.S. It so happened that quite a lot of time has passed since the moment I wrote this material. It was possible to publish it many times, but I kept pulling, it is not clear why. More precisely, I know why - everything was deciding how best to present a series of screenshots describing a particular process: as a simple sequence of inserted images, or as a slide show. Ultimately, the decision was made to use (at least for now) a sequence of images. How all this happened is a topic for a separate post. In the meantime, everything remains as it is, it's a pity that a lot of time was spent. The only consolation is that it is not in vain. Moreover, a pleasant event happened. I wrote in this post that access to the external memory card will be available only when the authors of the programs start using the new API. As an example of a program in which the new API is not used, I cited Total Commander. So, while I was delaying the publication, Total Commander was updated, and now it also knows how to work with an external memory card in the style of Android Lollipop. Below is a series of screenshots describing the process of creating a new directory in the root of an external memory card using Total Commander:

Choosing an external memory card

and select the desired item in the menu

Now, perhaps that's all.

It's finished! On the tablet, namely, on the Asus MeMO Pad 7, which I am replacing my honest workaholic, an update to Android 5.0.1 arrived. Now I have a device with Lollipop, or, as they say on the Internet, with Lolipopa.

The update arrived somewhat unexpectedly. To be honest, I was expecting a new firmware for my phone (Asus ZenFone 5) in April - at least they promised it. Nobody said anything about the tablet and here - on you, get it and sign it.

This, in fact, discouraged me (in a good, of course, sense), also because I bought the tablet in December, and it had version 4.3. That is, this is the second significant update of the operating system (in fact, there were more updates, but the Android version number has not changed). The previous manufacturer of my devices - Samsung - could not boast of such a rate of fire, although it also updated the operating system twice: from Android 3.2 to Android 4.1.2 (via 4.0.1). Only now it took much longer to wait for these new versions.

Well, long live surprises! Having received a notification about the release of a new firmware version, I immediately downloaded it, which is more than 700 meters, and launched the update. Since I downloaded not through, but through my mobile, it took a little more time for everything about everything: about an hour passed from the start of the download to the completion of the update. The update itself lasted about twenty minutes, but, potentially, it can take longer - because after installing the operating system, the process of updating the installed programs follows. My counter counted to 205. But now, the process is over and it's time to see what has changed.

The first thing that caught my eye was the more sophisticated graphics when unlocking the device. The second is a hand in the notification area. For a couple of days I put up with her, hoping that by chance I would see something connected with her somewhere. Didn't see. Then I began to search purposefully and found an explanation on it on w3bsit3-dns.com. It turns out that notifications were divided into important and not so important, and it is possible to specify which notifications you want to receive. If you set the option Always alert , then the hand disappears if the option Important alerts only then the hand appears. To be honest, I removed my hand several times, but, for some reason, it stably returns. Why? I don’t know yet.

Here, in fact, is the procedure for "removing" this hand:

The above method is not complicated at all. But you can achieve the result even faster and easier: press one of the two volume control buttons - a window will appear on the screen, allowing you to change the volume levels for various system components, as well as, attention, control Alert modes ... True, for some reason, these same Alert modes are displayed in such a fast version not always. I haven’t found any patterns yet, but, to be honest, it didn’t hurt and I was looking.

Choosing an external memory card

and select the desired item in the menu

Now, perhaps that's all.

Many happy owners of devices with 4.4.2 "on board" have probably already faced the problem of the impossibility of writing data to a flashcard with most applications installed on the device. Made, according to the assurances of Google in order to make the Android 4.4.2 KitKat OS more secure system.

Limitations of writing to a flashcard concern primarily applications installed from third-party sources. And, most importantly, Android 4.4.2 KitKat prohibits modification of files that are not directly related to the applications that want to make this modification. Hence the impossibility of recording to an SD card.

In practice, this limitation literally means the following: use standard instant messengers, photo editors, file managers! Because if the developer of your software was unable to respond in time and add an update to your photo editor, for example, then all your edited photos will be "alive" while the photo editor is running - you will not be able to write your edited photos to the card!

More advanced users who constantly copy data from a flash drive to a computer and back may face such a problem: the computer detects your "", sees the files, but cannot do anything with them - access denied! This problem can be corrected by installing an application on your device that will give access to. But this application will work only on ROOT-based devices.

Working SDFix: KitKat Writable is simple: after installing and running the application, you click on Continue, agree to the terms and click on Continue again. If the Superuser application is already installed on your device, then you should allow SDFix access to ROOT directories in it.

SDFix KitKat Writable MicroSD in the course of its work will change the file /system/etc/permissions/platform.xml, in which it will prescribe permission for writing and modifying files by applications that have the WRITE_EXTERNAL_STORAGE permission. You can find the original of the modified SDFix: KitKat Writable MicroSD file by the name platform.xml.original-pre-sdfix. You can always restore the original file later.

For the most "handy" users with ROOT access on their device, there is an option to make corrections to the desired file without resorting to SDFix: KitKat Writable MicroSD.

To do this, start the file manager, which can edit files, find the platform.xml file at / system / etc / permissions /, and open it with the built-in editor.

After that, find the sections android.permission.WRITE_MEDIA_STORAGE and android.permission.WRITE_EXTERNAL_STORAGE and add the lines with the code in these sections:

After that, save the modified file in the editor.

After restarting the device, all unpleasant problems associated with the inability to write and modify files on the flash card will be resolved.

While developing a competition application, I ran into a database storage problem. The problem was how do I identify the external memory card. In general, a web search did not give an exact answer. Therefore, by combining all the results I found, I put together my class. If anyone is interested, look under the cut.

So let's start with theory.

Terminology

Google tells us that there are the following concepts:

1. Internal ( internal) memory is part of the memory card built into the phone. By default, the application folder is protected from access by other applications (Using the Internal Storage).
2. External ( external) memory is a shared "external storage", i.e. it can be either part of the built-in memory or a deleted device. Usually this is part of the internal memory, as I saw the last time a removable device was on android 2.2, where the internal memory was about 2GB, and the connected memory became external (Using the External Storage).
3. Deleted ( removable) memory - all storages that can be removed from the device without "surgical" interventions.

Prior to KitKat 4.4, the API did not provide functionality for getting paths to external memory. Starting from this version (API 19) the public abstract File function appeared getExternalFilesDirs (String type), which returns an array of strings with paths to internal and external memory. But what about our SD Card, which is inserted into the slot? Again, we cannot get the way to it.

searching results

To answer the question posed, I turned to the all-knowing Google. But he did not give me a clear answer either. We considered many options for determining from using standard functions that lead to external memory, but they have nothing to do with removable storage devices, to processing the rules for mounting devices (Android works on the Linux kernel). In the latter cases, “hardcoded” paths to the folder with mounted devices were used (this directory is different in different versions). Do not forget that the mount rules change from version to version.

In the end, I decided to combine all the knowledge I gained and wrote my own class that can return the paths to external and removable devices for us.

Code Description

The class was created MountDevice, which contains the path to the device, the type of device and a certain hash.
There are two types of devices (I did not touch the internal memory, since it can be accessed through the system API).

Public enum MountDeviceType (EXTERNAL_SD_CARD, REMOVABLE_SD_CARD)
And the class was created StorageHelper, which searches for available memory cards.

The StorageHelper class implements two search methods - through the system environment ( Environment) and using the Linux utility mount, or rather the result of its implementation.

Method one - Environment

When working with the environment, I use the standard getExternalStorageDirectory () function to get information about external memory. To get information about the memory being removed, I use the environment variable " SECONDARY_STORAGE".

I have not found official updates for Android (for our region) on the official sites.

On the forums, I found information that Google released a firmware version for Russia in January 2015. But it is being implemented very slowly on clients' devices.

Thus, I can wait until my device receives a message that there is a software update. After that, I can update Android.

An attempt to save new information to the micro cd will fail if it is write protected. There are various reasons for the access denied message. You can remove protection from microSD in several ways - software and physical. Let's consider the most relevant ones.

Unlocking microSD

Place the memory card on a flat surface or in your palm with the label facing up. On the left side of the card case, at the top, find the small lock toggle lever - the Lock button. "Locker" serves to protect information from accidental erasure. The lever can be flat and only slightly protrude from the body, be white or silver. There is no such switch directly on the microSD. Insert the card into the adapter and locate the Lock switch on the adapter itself. Move it all the way in the opposite direction.

After moving the Lock lever to the override position of the data protection status, the reappearance of the write error notification window may be caused by moving the Lock back to the protection position. This happens due to the weakening of the switch, when the memory card is inserted into the card reader, it moves and turns on the memory lock. Fix it with a piece of rubber, cardboard, or remove completely.

To avoid automatic blocking of microSD recording, you can remove its contact with the Lock button on the adapter body. Find a small notch on the left side of the micro-flash drive, seal it with plastic or tape it with tape. Soldering must be done very carefully. The tape option is simpler, but it can cling to when the card is inserted into the adapter.

Change disk properties

If the protection of the memory card does not allow copying the information to another disk, but you need to save it, then try to remove the protection as follows. Attach the micro cd to your computer, find its name in the device list and right-click on it. In the menu, select the line "Properties", then the tab "Access". In the next window there is an "Advanced setting", open it and put a tick in the line "Open public access", confirm the settings - "Ok".

Formatting a microSD card

Sometimes, to remove protection from a memory card, it is recommended to format it if the “locker” is missing or did not help. Save important information to another drive, as it will be completely removed. You can programmatically remove the write lock on the card using Windows.

Install a microSD memory card on a personal computer through a special adapter directly or through a card reader. On modern laptops, this connector is already provided, it is usually marked with a "card" icon and looks like a narrow slot. The operating system recognizes the drive and its name appears in the list of devices on the computer.

Right-click on the CD disk icon and select the "Format ..." line in the expanded menu. Set the file system to the one that your device supports, usually NTFS. Click Get Started. All information from the disk is now deleted and the protection status is removed.

Changing the file system

When writing a file larger than 4 GB to a memory card, an error window may appear due to file system limitations. If the memory card is formatted with the FAT32 system, the file size is included in the limit for data recording. Change the file system to NTFS, as described in point 3.

MicroSD software

You can reset the write protection on a disk programmatically without deleting the information. There are various scripts and utilities for this, for example - reset.zip. When downloading software from the network, you should be careful - it may contain viruses. It is better to use trusted applications to remove protection. Low-level disk formatting with the Hard Disk Low Level Format Tool erases all data, but it will help to recover even hopeless flash drives that have not been formatted by internal Windows tools.

Removing microSD protection using a mobile device

Modern mobile devices: players, PDAs, phones, cameras have the function of formatting microSD. Try to find this option through the settings and format the USB flash drive directly on this device. Memory protection could have been programmatically installed in the machine to ensure data confidentiality. You can also remove protection in the settings. All types of electronic devices have their own characteristics, so in case of difficulty, read the instructions for the gadget or get an explanation from a specialist in the service center.

Physical damage to the microSD card

One of the options for failure when trying to write data to a memory card arises due to physical damage: the card is slightly bent, one of the contacts on the card (usually the left one) or on the adapter is dirty, and microSD closes it. If the contacts are dirty, they must be cleaned, for example, with a cotton swab dipped in an alcohol-containing liquid or acetone. A badly bent card cannot be restored. You can try to straighten a slightly curved one by putting it under the press.

Use only the native adapter with the microSD card. With a different adapter, even if you managed to format it on the phone, you will most likely not be able to write the information to the disk.

Instructions

First take map memory and insert it into the card reader, just be careful: all protection functions on both accessories must be disabled, otherwise you will constantly see the inscription "Write protection enabled, recording is not possible."

After that, insert the card reader with the card memory inside a USB port on your computer. When connected correctly, the indicator should light up. The computer will make a distinctive sound and the Found New Hardware Wizard will appear on the screen. Skip this moment by clicking "no, not now" and wait for the inscription "next". Thus, the PC is ready to work with the card memory.

Go to "My Computer" and in addition to hard drives C, D and E, which is responsible for the DVD drive, you will notice another one, for example, G or H. This will be the card memoryconnected to the computer. Click on it. You will be presented with the entire list of files. If necessary, you can leave it unchanged or delete some information to free up space.

Open another window "My Computer" and go to the section of the hard disk where the music you are interested in is located. Select the necessary folders or individual tracks with the mouse and drag them to the window where the removable disk is open, i.e. map memory... The copying process will start.

When the required amount of music has been transferred, find the Safely Remove Hardware icon on the right side of the taskbar. Click on it and select the "Stop" item, after which the message "Hardware can be removed" will appear, and remove the card reader with a USB flash drive from the computer port.

If the capabilities of your cell phone allow you to play music and video, then such a device can easily be used as a pocket media player. To do this, you need to put a lot of different melodies and videos on your mobile. Usually, an additional memory card is used to download such files, since often the device itself does not have enough space to store a large amount of information. You can write a memory card for your phone in a few simple steps.

You will need

• - cellular telephone
• - memory card
• - card reader
• - computer

Instructions

First, burn the music and videos you want to burn to your phone to your computer's hard drive. Put all your media in one folder.

If your mobile phone can operate in storage mode when connected to a computer, then insert a suitable memory card into the corresponding slot of the device. Then connect your cell to your PC using a USB cable or Bluetooth connection.

In the information window that appears on the screen mobile phone, select Mass Storage mode. Then on your PC, open the C drive and find the folder where the required media files are located.

After entering the folder, select the music files and press the right mouse button. Select "Copy" from the list that appears.

Then click the "Start" button located in the lower left corner of the computer, and in the window that appears, select the "My Computer" section. Find your new removable disk in this category.

After the necessary files are completely placed on the memory card, disconnect the device from the PC. To do this, in the lower right corner of the screen, click on the "Safely Remove Hardware and Disks" icon.

If for some reason it is impossible to connect your phone to a computer, then connect a card reader to the PC, suitable for your memory card. Then insert the card into the corresponding slot of the device and open the "My Computer" section on the PC.

Copy the prepared media files from hard disk and paste them into the appropriate folders on the drive. After this operation, safely remove the device.

Sources:

• How to choose in 2017

MP3 is by far the most widespread and popular music format. It is used everywhere: in computers, players. Music discs are burned to standardize and convert all music to MP3 format, as MP3 allows you to record much more music than classic CDA.

Instructions

MP3 recording can be done both from a medium - a music disc, and to a medium - a blank CD / DVD disc. Let's look at the first option first:
You have a music CD with several tracks, usually one album. Insert the disc into the CD-ROM and start Windows Media Player. WMP is the standard player that comes with Windows. Almost immediately, after analyzing the disc, WMP will prompt you to burn music to your hard drive.
The tracklist of the disc will appear on the right, and the tabs, among which there will be the "Recording" tab. Click on it and just below, on the very right side of the screen, you will see a small shortcut in the form of a box with a checkmark. Select it with the left mouse button and select "Additional recording options" in the context menu that appears.
In the "Options" window that opens, go to the "Rip Music from CD" tab. Under "Configuring Rip from CD", select

Modern mobile devices and cameras, in addition to small main memory, can be equipped with a memory card, the volume of which can be several times larger than the main memory. For a person who is not knowledgeable in technology, this is a novelty, which raises a lot of questions regarding the use of a memory card. Memory cards come in different sizes, but the technology is the same. So all the tips that will be listed below are suitable for any type of device.

The first difficulty arises with how to write data to a memory card. If the work is done on a laptop, then it has a special slot where the card is inserted. But this slot is made for a large card. If the card is small, then there are adapters into which it is inserted, and the work is done as with a large one. There are adapters for a computer that are connected like floppy drives. In the system, the memory card is defined as a removable disk, so the recording is performed as if it were a USB flash drive. The only difficulty can be removing the card from the device.

So the next question is about how to remove the memory card. Devices that support memory cards use spring loaded holders. The phone or camera has a slot for a memory card, usually covered with a rubber or plastic cover. To remove, you need to open it and lightly press the card until it clicks. After that, it will come out of the socket and you can pull it out with your fingers. The extraction scheme from the card reader is the same. If you want to insert the card back, you must press it into the slot until it clicks.

In addition, difficulties often arise related to how to clear the memory card. If you need to clean it up not completely, then you need to go to it and delete unnecessary files one by one. If a complete cleaning is required, then you need to format it. To do this, right-click on the device and select Format. In the window that appears, you need to select the necessary settings and click the Start button, followed by confirmation of the operation. In addition, all these actions are available directly from the device to which the memory card corresponds.

Very often they ask questions about how to unlock the memory card of the camera. If the card is in SD format, then it has a jumper on the left side, which, if the card is inaccurately inserted into the slot, switches to the locked position. This jumper must be placed in the upper position and carefully inserted into the camera. Cards of a different type can only be unlocked at the service center, then all information on it will be saved. If the information on the card is not particularly important, then you can safely format it.