I went to the Play store to search for a text to speech app. To my surprise, it said I already had one: Google Text To Speech, and that it was probably already on. Sure enough, in settings, there it was. But not a word - zero - about how to use it, or point it to any arbitrary text, and have it start reading. I found this [post](https://www.google.com/amp/s/drfone.wondershare.com/amp-arc/android/text-to-speech.html) which lauded what this app can do - but using it, controlling it? No joy. Then I read in this article about Read Aloud, a Chrome extension. Apparently, Google TTS, despite the name, is NOT used to read text?! I guess it doesn't matter if there is no way to control it. So I got Read Aloud, after checking that it works on mobile and not just desktop. Supposedly, you can control it from an icon. But after clicking the button, did I see an icon? No, of course not. People, what am I missing here? I just want to use my phone to read arbitrary text. How do I make that happen? Thank.

I have a LG lm-X320 with Android 10. I want to move all my photos to the installed SD card. I have quite a few albums created. When I looked at the native File Manager, it showed both DCIM and Pictures folders on the SD card. Which one should I move to? I also want to set the phone to store any new photos on the card.

I have an issue with my LG K10 (K430, MT6753). I was experimenting with it to learn the adb function. I accidentally erased the whole boot partition using rm, and then my phone is not booting anymore. It is showing the LG boot logo, but not starting up, keeps rebooting. I tried to: 1. Repair it through LG Bridge, to flash the stock ROM through LG UP and LG Flash Tool. But the phone is not staying in Flash mode or Download mode, and can't boot into Fastboot. The only thing that apparently works is the Factory Reset mode, but it only shows the interface. It only reboots the phone and nothing else. 2. Flash the boot image through SP Flash Tool, but have no luck. The phone is detected by Windows, but only for 3 seconds, then it disconnects. No matter what I do, when I connect the phone to my PC, it quickly disconnects, even with Driver Enforcement deactivated. I tried LG drivers and some other drivers for Mediatek, but still have no luck. Is there any other way to recover the boot partition's data or to unbrick my phone?

I've been looking to root my LG G2 phone (AT&T LGE LG-D800), but all methods require installing binaries from little-known (by me) sites with no Web of Trust rating. I feel hesitant to do that. Here are some rooting links I found for my phone: * https://forum.xda-developers.com/showthread.php?t=2448887 * https://theunlockr.com/2013/10/25/root-lg-g2-versions-video/ * https://web.archive.org/web/20161224210036/https://wiki.cyanogenmod.org/w/Install_CM_for_d800 requires ioroot: https://forum.xda-developers.com/showpost.php?p=48709232&postcount=869 The latter one refers to Kingo Root (its Web of Trust says XDA does not recommend it until it goes open source due to some suspicious activities, such as sending IMEI to the server) Which of these is safer than the others? Also, there was a manual way to root via ADB, or if there was source code, or if there was a reputable, trustworthy site to download from, I'd be feeling much more secure. I am a Java developer, new to Android development, but it's something I want to learn, so programmatic solutions are welcome.

I'm about to flash my kernel for the purposes of overclocking, and I want to start by backing up my LG G7 ThinQ partition by partition in QFIL so I can restore them later with LGUP's partition DL option. This is the safest recovery option for me, since post-root I can no longer access fastboot and it takes me 8 seconds to enter EDL mode. TWRP does not work on my model. If my firmware was corrupted to the point that the phone crashes in seconds then I might find I can't access EDL mode anymore, but I can easily reach the firmware update screen as long as my bootloader is intact, and from there I can connect to LGUP. There is just one problem with my plan: LGUP demands IMG partition files but the files generated with QFIL are BIN, and I suspect simply renaming the extension might result in a full brick. What to do? I might need to ask the creator of Magisk if nobody here can help, he would have to know how.

I have an LG G Pad 7.0 tablet with Lineage 14.1 OS installed, and I wanted to update the ROM. However, I found that I can't update it through the built-in updater. I am unable to find other versions to install on the device. I want to upgrade to LineageOS 21, but I have no means of doing so. Can anyone help me?

I have the above device with a broken display, for which I know the PIN code for. I can power the device up, but obviously cannot unlock it because of the broken screen. The screen is mangled, but you can sometimes tell what's going on. I had USB debugging enabled on this device, but ADB doesn't seem to be detecting the device, even though it appears as "LG AndroidNet USB Modem" when I plug it in my Windows PC (I installed LG support tools & the drivers). Trying to connect to the device via LG Bridge results in the following message: I've tried third-party tools like Dr.Fone, but they don't seem to connect to the device at all. I tried connecting with the LGB and listing with ADB in factory reset mode, that also didn't help. What options do I have left? I want to recover data from this device.

I have an old cell phone called LG Sunset™ LTE (L33L) that I want to completely degoogle. It is an old phone that I bought in 2013(?) that I want to install a Custom OS on. I know GrapheneOS will not install on these types or phones nor can LineageOS. I want to degoogle it so that I will not Android 5.0 on my phone. I know that the phone only has 8 GB at maximum. I moved on to another phone that I can use an Android phone. I want to use this one as an MP3 player and video player as opposed to an official phone. Can anyone help me with this? How can I completely degoogle my phone? Or install a Custom OS on it?

I got a LG Watch R for a programming project. First, I had a Gear Live that was now replaced. When I follow the guides step by step, I never get the "authorize this computer" like I did with Gear Live. My machine runs on Windows 7. My steps were: 1. Setup LG Watch R with my Note 3 2. Dev Mode enabled, enabled ADB Debugging 3. Plugged the Charging Station in my PC (got detected as "Android Composite ADB Interface" with Samsung as Company 4. Normally the popup should appear on my Smartphone asking me to authorize the machine 5. In the CMD, adb devices does return unauthorized In the device manager, the Watch R is recognized as "Android Composite ADB Interface" from Samsung. I have tried [an answer to "ADB doesn't recognize Samsung Gear Live or LG G watch" on Stack Overflow](https://stackoverflow.com/a/24716409/2821954) , but it doesn't change much as it is already recognized as ADB Composite. I'd be grateful for any tips.

I have LG L Fino (D290N) and I am not able to start Android OS at all. I have tried to enter recovery mode, but unfortunately I am getting an error. Also, I've tried to enter download mode but the same error shows up.

ERROR : boot certification verify
 ------------------------------------------

  Secure booting Error!
  Cause : boot certification verify

 ------------------------------------------

How can I enter download mode in order to flash the device?

Up until the last couple of days my keyboard had a certain layout with long-press options for the letters and also a row of buttons for emojis, gifs and other fun option at the top. Now, it's just the keyboard and it seems like that part is less functional with the long press options. How can I get it back to the original keyboard version? Is the row of emoji and gif buttons part of the keyboard or is that some other feature I'm not thinking of? Additional information: I like to listen to YouTube videos when I work out, but this occasionally results in icons being dragged around or menus getting opened by my pockets. This could be a pocket-dialing scenario or something where I was glomped by my dog while trying to do something and fat fingered some commands by accident.

I have an Android phone with CyanogenMod installed(with TWRP Custom recovery). Specifically, it's an LG G2 (d803), and I was wondering if I could dual boot Cyanogenmod and Windows Phone 8.1 or 10. It would be awesome if I could because I could really use Microsoft's ecosystem but there are lots of android apps I'm not willing to give up.

I'm new to android development so apologies if this is a stupid question. I'm having trouble seeing my android devices in Eclipse. I've switched on USB debugging, configured them to connect as a camera not mass storage, but when I run ./adb devices, there's no device showing, even though I have a Samsung Galaxy and a LG Nexus connected via USB. On both phones I get a notification saying "USB debugging connected" and "connected as a camera" so the phone obviously thinks it's connected. The problem appears to be intermittent. Sometimes the Galaxy shows up: Macbook:~/workspace/android-sdks/platform-tools ./adb devices List of devices attached 3334AB246B5300EC device Then I unplug and reconnect it, and it disappears. I've tried 3 cables and 2 devices now. Should I just give up and use an emulator instead?

I have an older [LG G Pad F 8.0 (UK495)](https://www.lg.com/us/tablets/lg-UK495-g-pad-f-8.0) . The tablet originally came with Android 5.1 but at some point received an official upgrade to 6.0. My ultimate goal is to hopefully root the device & install a custom recovery & ROM. But I am running into two problems in trying to access the bootloader & default recovery. Enable OEM unlock & USB debugging are both enabled in developer options. ADB recognizes the device connected to my Windows system:

> adb devices
List of devices attached
LGUK49520651306 device

I didn't find any instructions in the official documentation from LG. But according to many tutorials found online it should be possible start the bootloader using a combination of the power & volume keys. The only combination I have found to do anything is holding power + vol down to start the device. Release once the LG logo appears & immediately press power + vol down again. But this only brings up a minimalist menu for resetting the device to factory defaults: ADB is also unable to bring up the bootloader. Executing adb reboot bootloader restarts the device but in regular user mode. So I am unable to use fastboot to unlock the bootloader & flash partitions. I can get into what appears to be recovery mode with adb reboot recovery. A black screen with the Android logo laying on its back: But the usual "no command" text is missing & no button combinations (power + vol up/down) bring up the recovery menu options. I read on XDA that some manufacturers/distributors make the [bootloader & recovery partitions more obscure or just completely remove access](https://forum.xda-developers.com/t/android-phone-with-no-bootloader.1504664/) . Some users have been able to use a [KingRoot exploit](https://forum.xda-developers.com/t/3398918/page-4#post-68473678) to root this device without unlocking the bootloader. But the exploit only works for devices with Android 5.1 or older. So it's not an option for me. I need to access the bootloader to unlock it as far as I can tell. Is anyone familiar with this device or have any suggestions that may help me to unlock the bootloader & access recovery mode? This is the first device on which I wasn't even able to bring up the bootloader. The following is a selection of tutorials & threads from the many that I looked through for help: - [Help Can't access bootloader](https://forum.xda-developers.com/t/2738234/) - [Cannot boot into bootloader/fastboot](https://forum.xda-developers.com/t/3738850/) - [How to put LG UK495 G Pad F 8.0 in recovery mode?](https://www.hardreset.info/devices/lg/lg-uk495-g-pad-f-80/recovery-mode/) - [How to unlock Bootloader in LG UK495 G Pad F 8.0?](https://www.hardreset.info/devices/lg/lg-uk495-g-pad-f-80/faq/faq/lg-bootloader-unlock/) - [Download and Install TWRP Recovery on LGE LG G Pad F 8.0 2nd Gen LG-UK495 t8lte](https://tweakdroid.com/twrp/lge-lg-g-pad-f-8-0-2nd-gen-lg-uk495-t8lte/) _(this one says "2nd gen" so not sure if it even applies to my device)_ - [How To ROOT Android 6.0 Marshmallow Android 10](https://www.youtube.com/watch?v=rTeuF4uJ6lU) **-- Update --** I found some stock firmware images available for my device: - [UK49520c_00_0718](http://lg-roms.com/lg-firmware/lg-g-pad-f-80-lguk495/uk49520c-0718/6200) - [UK49522a_00_0329](https://lgrom.com/firmware/LGUK495/UCS/UK49522A_00/8722) I was able to flash them to the device in upload mode using [LG Flash Tool](https://androidmtk.com/download-lg-flash-tool) . The ROMs were successfully applied, but did not fix or change access to bootloader or recovery mode.

I found a LG K120 (LG Spree in US,LG K4 in Europe), after wiping it, in the setup process it asks me for the previous google acount (FRP). After searching a lot of this model, none of the bypass google account solutions are valid. I am trying now reinstalling the whole operating system via fastboot, but as the model is very new, there is no implementation (or at least, I'm not able to find it). The only solution that comes to me is to wipe the frp partion, in HTC is located in /dev/block/bootdevice/by-name/frp, but I don't know which of the listed below is related with frp. #fastboot getvar all (bootloader) max-download-size: 0x8000000 (bootloader) partition-size:flashinfo: 1000000 (bootloader) partition-type:flashinfo: raw data (bootloader) partition-size:userdata: 32000000 (bootloader) partition-type:userdata: ext4 (bootloader) partition-size:cache: c800000 (bootloader) partition-type:cache: ext4 (bootloader) partition-size:system: 9a000000 (bootloader) partition-type:system: ext4 (bootloader) partition-size:nvdata: 2100000 (bootloader) partition-type:nvdata: ext4 (bootloader) partition-size:efuse: 80000 (bootloader) partition-type:efuse: raw data (bootloader) partition-size:persist: 3000000 (bootloader) partition-type:persist: ext4 (bootloader) partition-size:factory: 1400000 (bootloader) partition-type:factory: raw data (bootloader) partition-size:rct: 100000 (bootloader) partition-type:rct: raw data (bootloader) partition-size:cust: 6400000 (bootloader) partition-type:cust: raw data (bootloader) partition-size:lgfota: a00000 (bootloader) partition-type:lgfota: raw data (bootloader) partition-size:persistent: 200000 (bootloader) partition-type:persistent: raw data (bootloader) partition-size:mpt: 1600000 (bootloader) partition-type:mpt: raw data (bootloader) partition-size:persist_lg: 800000 (bootloader) partition-type:persist_lg: raw data (bootloader) partition-size:encrypt: 80000 (bootloader) partition-type:encrypt: raw data (bootloader) partition-size:eksst: 80000 (bootloader) partition-type:eksst: raw data (bootloader) partition-size:tee2: 500000 (bootloader) partition-type:tee2: raw data (bootloader) partition-size:tee1: 500000 (bootloader) partition-type:tee1: raw data (bootloader) partition-size:keystore: 800000 (bootloader) partition-type:keystore: raw data (bootloader) partition-size:secro: 600000 (bootloader) partition-type:secro: raw data (bootloader) partition-size:oemkeystore: 200000 (bootloader) partition-type:oemkeystore: raw data (bootloader) partition-size:seccfg: 80000 (bootloader) partition-type:seccfg: raw data (bootloader) partition-size:expdb: a00000 (bootloader) partition-type:expdb: raw data (bootloader) partition-size:lo_bak_go: 800000 (bootloader) partition-type:lo_bak_go: raw data (bootloader) partition-size:logo: 800000 (bootloader) partition-type:logo: raw data (bootloader) partition-size:recovery: 1000000 (bootloader) partition-type:recovery: raw data (bootloader) partition-size:boot: 1000000 (bootloader) partition-type:boot: raw data (bootloader) partition-size:para: 80000 (bootloader) partition-type:para: raw data (bootloader) partition-size:laf: 1000000 (bootloader) partition-type:laf: raw data (bootloader) partition-size:lkbak: 80000 (bootloader) partition-type:lkbak: raw data (bootloader) partition-size:lk: 80000 (bootloader) partition-type:lk: raw data (bootloader) partition-size:protect2: a00000 (bootloader) partition-type:protect2: ext4 (bootloader) partition-size:protect1: a00000 (bootloader) partition-type:protect1: ext4 (bootloader) partition-size:nvram: 500000 (bootloader) partition-type:nvram: raw data (bootloader) partition-size:ftm: 800000 (bootloader) partition-type:ftm: raw data (bootloader) partition-size:misc2: 800000 (bootloader) partition-type:misc2: raw data (bootloader) partition-size:proinfo: 300000 (bootloader) partition-type:proinfo: raw data (bootloader) partition-size:preloader: 40000 (bootloader) partition-type:preloader: raw data (bootloader) warranty: no (bootloader) unlocked: yes (bootloader) secure: no (bootloader) kernel: lk (bootloader) product: MUSE6735M_E1LTE_L (bootloader) version: 0.5 all: Done!! finished. total time: 0.013s ¿Can anyone give me an idea? Another problem than I am facing is when trying to erase a partition y get the following. # fastboot erase cache ******** Did you mean to fastboot format this partition? erasing 'cache'... FAILED (remote: unknown command) finished. total time: 0.002s And the same answer with many other commands, it seems that LG has implemented a very reduced set of fastboot protocol commands. To overcome this, flashing the partition with zero's file can do de job, that is my guess. Thanks for your help.

How do I stop an LG phone from asking for confirmation when I turn mobile data on/off? When I turn it on, it says "data charges may apply" and requires me to tap again for confirmation. When I turn it off, it asks "turn off mobile data?" and requires me to tap again. Samsung phones don't ask, so tapping on the mobile data icon is more convenient and reliable.

Is there a way to prevent settings on an Android phone from being accidentally changed? I am using an LG K30 running Android Pie. (Yes, I know it's a dinosaur)

How do I root my LG phone? - Model LM-G820U30b - Hardware version rev.1.0 - Internal environment SELinux

I had a LG Nexus 5 running Android in developer mode with the "Show touches" option enabled. Suddenly, while holding the phone steadily in my hand, the device registered tons of touches in the top of the screen, and I decided to turn it off immediately. Now, after a reboot, the touch screen does not respond at all (not true; very rarely responds in a weird manner, that I can not reproduce). Everything else is working: volume buttons and power button. I have tried the following: - Rebooting (obviously) - Restoring to factory settings (which is why I am now stuck on the "Select language"-screen in setup) - Clearing phone cache - Clearing the sim tray (has always been empty, but I tried ejecting and taking back in) I always updated the software to the newest version available. I have not yet tried pulling the battery out and in again. Any ideas? **Update 1:** I have now tried pulling out the battery and re-inserting without any luck. I also installed Kitkat (version 4.0 from https://developers.google.com/android/nexus/images) . Still no response.

My Samsung Galaxy A51's screen broke; I got the purple screen of death . I was able to backup up the data using Samsung Switch before the screen was completely taken over by the purple ooze. However, I ended up replacing the A51 with an LG phone and now I don't know how to restore the backup I made using Samsung Switch; I can't use the Samsung Switch app, as that only works for Samsung phones. About the backup files: There are numerous folders, each containing a backup file for a category of data (e.g., contacts, messages, etc.). I really only need the contacts and the messages. The file extension for the contacts is "spbm" and the file extension for the messages is "smem". After googling these file extensions, it appears that these are proprietary file types that are exclusively used by Smart Switch. Sounds like I will not be able to restore this data without using Smart Switch. Is it possible to restore my data onto the LG Phone using the backup I made with Samsung Switch? I would just make another backup using my old phone, but the display is completely gone; I'd be flying blind.