Related
So I can't get my desktop OR laptop running XP Pro 32 to even recognize the phone. As in no audio plays and nothing appears in the system tray. Tried with/without debugging mode, installed the samsung drivers etc. The phone doesn't even show up in device manager at all- not even as something unrecognizable. Its as if the port is dead. The phone does 'ding' though and charge ok so it is receiving power... though nothing at all appears in the android notification tab when connected. Any ideas or anyone know of any apps on the pc or android side to take a closer look at whats happening on the bus?
The only way that I can get it to work is to put it in media mode. It shows up as a media device in Win7. If I put it on, "ask every time" or whatever it doesn't work and in mass storage mode it shows up as two unreadable drives, they are grayed out in Explorer... Basically...don't use the "ask every time" for USB function.
This function seems like such a simple thing, not sure why Samsung has so many issues with it considering they have been making media devices for a long time.
Anyway... do you have access to a newer OS to at least rule that out as a cause. Not saying it shouldn't work with XP 32 but just something to check out.
I was having similar issues at first. I take it adb doesn't work either? Well my fix was to delete my whole Android SDK folder, then I redownloaded it (though I just kept the "tools" folder this time). Then I downloaded "USBDeview" (google it) to delete every USB driver that had to do with android (basically just left the printers, HID, and my Sansa drivers), restarted, then I downloaded the samsung drivers from the thread on here, plugged my phone in and manually pointed the driver search to the drivers.
ADB and Mass Storage has been working fine since. All I can tell you is to keep checking cause there's something you're missing, I also thought to myself "what the heck else can I do?" since I had done each one of those steps previously, but maybe I just had to do them all together. Good luck.
another possible solution is to change cables if you're not using the samsung provided cable - some cables are charger only (no data) - some of the motorola cables are charger only and we've already had one poster that had that issue
I couldn't get it to work at first either. I more or less did this.
I plugged in my phone. I did not enable mass storage mode on my phone. Walked away and let my PC think for a while. I came back and I noticed I had two new drives. I then enabled mass storage mode and could connect.
Two of my machines I had to do this. I'm not sure why it wasn't instant, but it just took a bit of patience and walking away from the machine to let it think for a while before I guess it installed the drivers and made its peace with the fact it wasn't the G1 any more.
Say into voice dialer "Open SD card" -> check "Enable USB mass storage". That works if port on PC is OK.
If it's a driver issue, open device manager and uninstall the usb ports. Unplug everything from usb and when you reboot the computer it will automatically reinstall the usb ports.
Sent from my Vibrant
I ran into the same issue. It was a problem with the USB cable I was using. As soon as I tried a different cable it worked fine.
larryccf said:
another possible solution is to change cables if you're not using the samsung provided cable - some cables are charger only (no data) - some of the motorola cables are charger only and we've already had one poster that had that issue
Click to expand...
Click to collapse
I second this, I forgot my sammy cable at work on Friday and on way home stopped at T-Mo and picked up a charger w/cable and realized right away this was just a charging cable as soon as I connected it to my PC. I'm returning the cable back to T-Mo tonight. At least I was able to charge my phone over the weekend.
UPDATE: You guys are right, it is the goddamn cables! I bought an extra wall charger + cable at the t-mobile store and was using that at home. I had left the original in-box cable at work. Tried the cable at work today and now the drives pop up. Still don't appear writeable but I can look into that when I have time, probably the typical driver issue. As far as I can tell those separate cables are power only! $15 for a two wires + dc adapter. Thanks Samsung. Grr.
i suspect the mfgrs have gone to charge only cables to help keep folks from tethering - just a suspicion
if the "drives" are popping up, have you "mounted" the phone (pull down notification bar, clik on USB connected and it should give you a window asking to mount the cards or drive)
FYI....The Rocketfish cables you get from Best Buy do not work. They are only capable of charging.
@larryccf...I don't think certain manufacturers are implementing this on purpose so we can't tether. I think their just being cheap.
Where I got my cables on the cheap! and my problem.
I got my cable at monoprice.com. Check it out that is a 10 foot usb cable for $1.69 and it works for me. They have different lengths and even some colors. Now my Mass Storage issue . . .
My Mass Storage via USB works fine unless I enable "USB Debugging" which one of my apps needs to work. Once debugging is enabled I loss the ability to see my sd card and internal storage on my XP netbook. any ideas????
Same Problem
I have the exact issue, tried many things have'nt found a fix yet. Any help would be greatly appreciated!!!
Thanks,
crx
larryccf said:
if the "drives" are popping up, have you "mounted" the phone (pull down notification bar, clik on USB connected and it should give you a window asking to mount the cards or drive)
Click to expand...
Click to collapse
this worked for me Thanks
Yes phone is mounted, and can be seen w/o usb debugging enabled. However with usb/debugging on it does not read the phone being connected. Meaning that I cannot connect to ADB which is my main concern.
thanks for response tho,
crx
crxforya said:
Yes phone is mounted, and can be seen w/o usb debugging enabled. However with usb/debugging on it does not read the phone being connected. Meaning that I cannot connect to ADB which is my main concern.
thanks for response tho,
crx
Click to expand...
Click to collapse
This is my issue exactly, and I haven't found a fix either. Called T-Mobile and they thought turning off debugging was the only fix I needed.
Most of them, sorry to say are half retarded. They think a data reset is the cure-all
crxforya said:
Most of them, sorry to say are half retarded. They think a data reset is the cure-all
Click to expand...
Click to collapse
Ain't that the truth!
If you are running windows (x86 or x64), it would be wise to install the samsung drivers. I was having this exact problem, but as soon as I installed the drivers from samsung, viola!
I had the latest drivers from google, and they did not work for me.
Here is a link to the thread containing the links to the drivers, thanks to TGA_Gunnman:
http://forum.xda-developers.com/showthread.php?t=728929
I'm having an issue getting Android Auto to launch in my Subaru Crosstrek 2018 model. It works when I use my Nexus 6p but not with the Essential phone. I've tried different cables and reinstalling Android Auto but no luck. Anybody else having issues with Android Auto in their car with the Essential phone?
I had major problems getting Android Auto to work with my Essential phone.
At first, I kept getting the red screen of death (something about "do this when the car is stopped and the brake is on"...of course the car was stopped and the brake was on...). The next day (after a phone update), I tried again and could get past that screen. But then it wouldn't connect.
Turns out you have to scroll down the notifications and change the connect mode from USB charge to MTP manually. Once you do that, it quickly connects. Why the phone can't automatically do that for you...I don't know. But I've done this repeatedly now and each time it connects once you change to MTP mode.
(I also have USB debugging on--don't know if that's important as well).
quadcrap1 said:
I had major problems getting Android Auto to work with my Essential phone.
At first, I kept getting the red screen of death (something about "do this when the car is stopped and the brake is on"...of course the car was stopped and the brake was on...). The next day (after a phone update), I tried again and could get past that screen. But then it wouldn't connect.
Turns out you have to scroll down the notifications and change the connect mode from USB charge to MTP manually. Once you do that, it quickly connects. Why the phone can't automatically do that for you...I don't know. But I've done this repeatedly now and each time it connects once you change to MTP mode.
(I also have USB debugging on--don't know if that's important as well).
Click to expand...
Click to collapse
Android Auto doesn't kick-in on my '20 Subaru Outback (works on my wife's '19 Nissan Rogue).
Can you specify how to get to this setting. I'm unable to find it...
Thanks
levpri said:
Can you specify how to get to this setting. I'm unable to find it...
Click to expand...
Click to collapse
For the current connection, expand the "usb charging" notification, and it will give you a prompt to the available options - just select what you need. To change the default USB connection behaviour, go to Settings - System - Developer options - Default USB configuration, and select an appropriate connection mode.
kt-Froggy said:
For the current connection, expand the "usb charging" notification, and it will give you a prompt to the available options - just select what you need. To change the default USB connection behaviour, go to Settings - System - Developer options - Default USB configuration, and select an appropriate connection mode.
Click to expand...
Click to collapse
Funny there is no USB charging notification on the top, but in Default USB configuration should it be on File Transfer? Thanks!
I've never had a problem with android auto on mine, though I think I probably did change the default connection mode to file transfer a long time ago (before I had a vehicle with android auto).
You can also try a USB hub. These resolved the problem:
AmazonBasics 4 Port USB to USB 3.0 Hub with 5V/2.5A power adapter
ASIN B00DQFGH80
TP-Link | 4 - Port USB 3.0 Hub | Slim & Foldable Cord Design | Compact Travel Size with Charging Ports | Universal Compatibility - USB Flash Drive, Notebook, MacBook, PC, Chromebook and More (UH400)
ASIN B012B6YQY6
Sorry, I can't post direct links
Hi,
I am having a hard time trying to get a couple of USB devices to work properly on my headunit. One is a USB CarPlay dongle, and the other is an OTA tv tuner. Both USB devices get recognized by the headunit, however in the case of the first, it never gets passed a connection state where the dongle starts talking to the application. In case of the second, the OTA never finds TV stations after doing a complete scan.
USB devices like keyboards, mice, USB flash drives, even a webcam work fine. I contacted the manufacturer and they said they only support USB synchronous which may be the reason these devices can't work properly.
The unit is an Eonon GA7157 with the Allwinner R16 1.6GHz Cortex A7 Quad-Core CPU.
Questions:
Is it possible this is a valid claim?
My unit is rooted, can USB asynchronous be enabled via software?
I was also thinking this could be an OTG wiring issue, what do you think? I say so because the only way I could get the CarPlay dongle to work on my Samsung Tablet A, was with an OTG cable. A straight connector presented the same symptoms.
I am not too experienced with Android, so please be gentle
He was feeding you a load of horse manure.
Either that, or he meant something entirely different by "USB synchronous".
Precisely what do you mean by "get recognized by the headunit"?
What exactly *are* these two devices you are trying to use?
What *drivers* do they use?
Have you confirmed that the kernel is enumerating the devices?
Have you confirmed that the kernel is binding the proper drivers to them?
Have you confirmed that Android knows how to deal with the interfaces that the drivers are providing for these devices?
Have you confirmed that the interface permissions are such that a user application will be able to access it?
An OTG cable does two things;
1) It reverses the gender of the connector,
2) It sends a signal to the phone/tablet/whatever that it should switch its USB port from slave mode to host mode.
Nothing else.
Thanks for the tips. By recognize I mean that Android prompts me to confirm opening the accompanying apps when I plug in these devices to the USB port. E.g. I plug in the CarPlay dongle, Android prompts: do you want use Zbox (App) every time you use this device (Cancel or OK); I press OK and then the App stays in trying to connect mode forever.
The manufacturer has locked down USB debugging. Do you know of any apps (rooted or not) that will give me the information you pointed out?
thanks
It is unlikely that USB debugging is "locked down". More likely, its just because your USB device port is stuck perpetually in "host" mode on the wrong side of a USB hub, and therefore you can't connect to it. Try connecting to adb over IP instead.
I've never heard of any USB device on Android causing any kind of popup. That is very strange. Is it possible that the popup is being created by the program, i.e. "zbox"? Its possible that the system is sending a broadcast upon device enumeration, but the device access permissions are either wrong, or the kernel doesn't have the proper driver available.
luciusfox said:
It is unlikely that USB debugging is "locked down". More likely, its just because your USB device port is stuck perpetually in "host" mode on the wrong side of a USB hub, and therefore you can't connect to it. Try connecting to adb over IP instead.
I've never heard of any USB device on Android causing any kind of popup. That is very strange. Is it possible that the popup is being created by the program, i.e. "zbox"? Its possible that the system is sending a broadcast upon device enumeration, but the device access permissions are either wrong, or the kernel doesn't have the proper driver available.
Click to expand...
Click to collapse
Thanks again. I am including some pictures that may help explain the problem a little better. As far as the passcode, from what I can tell this unit has 3. One for the Advanced Car Settings, Developer Settings, and USB Debugging. The first 2 I found on another forum and are 123456 and the other 7890. The USB Debugging is an alphanumeric string which I haven't found anywhere, and the manufacturer refuses to release it. When I toggle the USB debugging on, I get prompted to input the passcode. I have tried a few codes but no go, the USB debugging switch goes back to the off position.
The other pictures show the USB port capabilities of the headunit. The unit has 3 USB ports: one is taken by the WiFi module, the other by a dashcam, and the remaining one is open and where I plugged in the CarPlay dongle. There is also another picture of the USB CarPlay dongle device plugged in and listed as Mass Storage Gadget. The dongle does have internal storage of a few MBs.
Finally, I include a picture of the application Zbox. This is the latest version and it starts automatically when I plug in the USB CarPlay dongle.
Well, I made some progress with the password for the USB debugging switch. To summarize:
Car Settings: 123456
Developer Options: 7890
USB Debugging: [email protected]
Now I just need to figure out how to make the USB port work properly. Any ideas? I have USB debugging access and the device is rooted.
Well according to your second-last picture, the device is being detected as UMS (Usb Mass Storage). I.e., like a usb flash disk.
VIDID of 0x0525:0xA4A5 looks to be an e-ink tablet called "Pocketbook Pro 903".
The problem may be that your "carplay dongle" is masquerading as something it isn't.
Well, the VIDID could be the problem; however, this same CarPlay dongle works fine on 2 other Android devices; moreover, a USB OTA tuner behaves the same way, meaning it does not work on the headunit but does on remix and a tablet.
Well guys, this unit is going back to the seller. After playing with it and not getting anywhere with customization and customer service, it’s out the door.
I am getting an xtron octacore px5 unit. It looks like these head units have better developer support.
Do you have the English version of 3.0 you can post?
bass_rock said:
Do you have the English version of 3.0 you can post?
Click to expand...
Click to collapse
You mean the Zbox firmware and software? if so, pm me, and I'll forward it to you.
isisyodin said:
You mean the Zbox firmware and software? if so, pm me, and I'll forward it to you.
Click to expand...
Click to collapse
Yea, and actually I was able to use the version on their site. It was al in English when I installed it and I’m now on version 3.0.2
bass_rock said:
Yea, and actually I was able to use the version on their site. It was al in English when I installed it and I’m now on version 3.0.2
Click to expand...
Click to collapse
Whats new on 3.0.2 compared to 3.0.0? Do you know what was updated?
isisyodin said:
Whats new on 3.0.2 compared to 3.0.0? Do you know what was updated?
Click to expand...
Click to collapse
According to Google Translate:
1. Optimize U disk upgrade USB recognition rate is higher
2. Optimize the phone connection, mobile phone recognition rate is better
3.carlife in the help page to add download guide
I was able to get it from here: https://translate.google.com/transl...=en&ie=UTF-8&u=http://zjinnova.com&edit-text=
bass_rock said:
According to Google Translate:
1. Optimize U disk upgrade USB recognition rate is higher
2. Optimize the phone connection, mobile phone recognition rate is better
3.carlife in the help page to add download guide
I was able to get it from here: https://translate.google.com/transl...=en&ie=UTF-8&u=http://zjinnova.com&edit-text=
Click to expand...
Click to collapse
My new Xtrons recognizes the Zbox dongle very quickly. I think it is now as quick as some of the dedicated Alpine and Pioneer units.
As far as software, crisper icons and bypassing the connection window would be nice option. It should only display when a problem occurs. One thing that is flimsy is the USB connector but no software upgrade will fix it. I am considering opening it up and soldering a better connector. Also, heat dissipation is an issue. It needs a heatsink. I may just add one when I crack it open.
I am looking forward to the next iteration with wireless CarPlay. Someday.
isisyodin said:
My new Xtrons recognizes the Zbox dongle very quickly. I think it is now as quick as some of the dedicated Alpine and Pioneer units.
As far as software, crisper icons and bypassing the connection window would be nice option. It should only display when a problem occurs. One thing that is flimsy is the USB connector but no software upgrade will fix it. I am considering opening it up and soldering a better connector. Also, heat dissipation is an issue. It needs a heatsink. I may just add one when I crack it open.
I am looking forward to the next iteration with wireless CarPlay. Someday.
Click to expand...
Click to collapse
Yea the update definitely enhanced it a lot. I used to have a pioneer and it feels close to the same now.
bass_rock said:
Yea the update definitely enhanced it a lot. I used to have a pioneer and it feels close to the same now.
Click to expand...
Click to collapse
Prior to 3.0.2, what firmware/software where you running?
Anyone manage to get Dex PC mode working? I tried this morning, and while the phone says it's ready, the app doesn't connect.
I suspect that there needs to be a driver update to make the new devices work, but wanted to see if anyone has gotten it working.
Do you mean the standard Dex Mode or the Link to Windows?
buddy66 said:
Do you mean the standard Dex Mode or the Link to Windows?
Click to expand...
Click to collapse
DeX on PC is when you connect the phone to a Windows computer and get a window with DeX running inside.
_Dennis_ said:
DeX on PC is when you connect the phone to a Windows computer and get a window with DeX running inside.
Click to expand...
Click to collapse
Have you downloaded and installed the app from https://www.samsungdex.com?
EDIT: I have tested it and it does not work. Drivers are installed, phone is set to usb storage and shows the Dex notification but the PC software wont flinch.
EDIT2: I have uninstalled the Samsung USB driver, connected the phone, dex software prompted to install the driver, PC reboot and works like charm. I have tested both classic USB and USB-C. Both work and sometimes I have to switch to USB just charging, wait a second and switch to file transfer and Dex boots up.
I saw a review for the NexDock and it looked like a great way to use the Dex feature on the S20 Ultra.
buddy66 said:
Have you downloaded and installed the app from https://www.samsungdex.com?
EDIT: I have tested it and it does not work. Drivers are installed, phone is set to usb storage and shows the Dex notification but the PC software wont flinch.
EDIT2: I have uninstalled the Samsung USB driver, connected the phone, dex software prompted to install the driver, PC reboot and works like charm. I have tested both classic USB and USB-C. Both work and sometimes I have to switch to USB just charging, wait a second and switch to file transfer and Dex boots up.
Click to expand...
Click to collapse
I don't even have the phone yet......I'm not the OP.
buddy66 said:
Have you downloaded and installed the app from https://www.samsungdex.com?
EDIT: I have tested it and it does not work. Drivers are installed, phone is set to usb storage and shows the Dex notification but the PC software wont flinch.
EDIT2: I have uninstalled the Samsung USB driver, connected the phone, dex software prompted to install the driver, PC reboot and works like charm. I have tested both classic USB and USB-C. Both work and sometimes I have to switch to USB just charging, wait a second and switch to file transfer and Dex boots up.
Click to expand...
Click to collapse
Thanks, I will give that a shot. It looks like a potentially useful feature that I am really looking forward to trying.
EDIT: Managed to get it working, turns out I had a cable with an intermittent short in it. I went direct C-to-C and it popped right up. Works really well, now just need to see if is useful enough to bother with.
PottMatter said:
I saw a review for the NexDock and it looked like a great way to use the Dex feature on the S20 Ultra.
Click to expand...
Click to collapse
It looks interesting, but I am more interested in setting up a segregated environment to use on my existing PC, which is supported out of the box via Dex for PC. Sometimes the mobile app version of something is better than what you can get for the PC.
_Dennis_ said:
I don't even have the phone yet......I'm not the OP.
Click to expand...
Click to collapse
Pardon me sir
I am using my S9+ with DexPad hooked up to my TV through receiver and with a Logitech keyboard that has a touchpad. I don't need a computer for daily internet and media consumption anymore. Tomorrow I will test it with the S20U but the experience is gonna be the same.
Scroll down on your notifications, then change USB from charging to File Transfer and it should prompt you on your phone to start Dex (assuming you have the software installed on the pc already). Works on my S9+ that way. I haven't figured out how to force this usb mode on connect yet.
buddy66 said:
Pardon me sir
I am using my S9+ with DexPad hooked up to my TV through receiver and with a Logitech keyboard that has a touchpad. I don't need a computer for daily internet and media consumption anymore. Tomorrow I will test it with the S20U but the experience is gonna be the same.
Click to expand...
Click to collapse
Lol, no problem just didn't want to make it seem like I had the device at the time (just got it today lol).
Yes its been working great. After installing the dex software make sure you reboot the laptop. I had similer problem and rebooting my pc solved it.
I can't get dex to work on my phone. I have a USBC hub that works fine connected to a monitor with my Tab S4 but when I plug in my phone with the same setup I get nothing on the screen. I see in the notifications that Dex is running and the mouse that's plugged into the dock moves around on the phone but no picture on the monitor
Hello.
I've got my mother's Samsung A20. And i need to recover data, but the screen doesn't work.
When power button is pressed, display flashes the lock screen (wallpaper, current time and so on). And then it turns black (backlight stays on for 30 seconds, and then turns off). Pressing the button doesn't guarantee flashing the display, sometimes it goes black immediately. Touch screen gives no input as far as i know (can't hear anything when trying to type pin). Problem still occurs during and after reboots.
I managed to connect a mouse and keyboard with USB OTG, and i was able to unlock. But the phone has no MHL support, so i can't get any image through USB. I'd try pressing the power button repeatedly to get some image and inch my way through the interface, but the lockscreen interferes.
The USB port is set to Charging Only mode, so i can't copy files to my computer. USB Debugging is disabled, bootloader is locked.
Does anybody have a clue, how to get image? Some way to get data? Maybe some keyboard shortcuts, so i can disable lockscreen and make my way easier? And maybe disable 20 alarms in the morning?
damiandbcz said:
I'd try pressing the power button repeatedly to get some image and inch my way through the interface, but the lockscreen interferes.
Click to expand...
Click to collapse
I like to be helpful so I'll try to give you some suggestions but I hope others pitch in who know far more than I do.
I never use the USB cable anymore to operate my phone from my PC (but my screen isn't broken so your situation will be much harder).
I connect to my phone from Windows over Wi-Fi without USB all the time, and I can unlock my screen from the PC, and I can mount my entire Android device as a drive letter on Windows over Wi-Fi, etc., so "maybe" (just maybe though), you can consider using either a WebDav server on Android to access your files and/or adb to bring up and manipulate activities on Android....
damiandbcz said:
The USB port is set to Charging Only mode, so i can't copy files to my computer. USB Debugging is disabled, bootloader is locked.
Click to expand...
Click to collapse
However, I don't know if adb will work for you if you can't turn on USB debugging in the first place... but as of Android 12, adb now works completely over Wi-Fi (see screenshots below) without needing the USB cable to establish the initial connection like it used to be prior to Android 12.
damiandbcz said:
Does anybody have a clue, how to get image? Some way to get data? Maybe some keyboard shortcuts, so i can disable lockscreen and make my way easier? And maybe disable 20 alarms in the morning?
Click to expand...
Click to collapse
If the screen problem is "just" hardware and not software, and if you can turn on Wireless Debugging, you might be able to display your phone over scrcpy or vysor (both of which use adb over Wi-Fi) as shown in the screenshots below on my phone - which never needs the USB cable connection.
Hope this helps, but you seem to need folks who know more than I do as adb/vysor/scrcpy all work for me because I can set up USB Debugging & Wireless Debugging as shown below.
Note that you might have an FTP server or a WebDav Server on your Android phone, and if you do, you might be able to at least transfer important files since they each can mount your entire Android phone as a drive letter on Windows over Wi-Fi (without needing the USB cable).
GalaxyA325G said:
I like to be helpful so I'll try to give you some suggestions but I hope others pitch in who know far more than I do.
I never use the USB cable anymore to operate my phone from my PC (but my screen isn't broken so your situation will be much harder).
I connect to my phone from Windows over Wi-Fi without USB all the time, and I can unlock my screen from the PC, and I can mount my entire Android device as a drive letter on Windows over Wi-Fi, etc., so "maybe" (just maybe though), you can consider using either a WebDav server on Android to access your files and/or adb to bring up and manipulate activities on Android....
However, I don't know if adb will work for you if you can't turn on USB debugging in the first place... but as of Android 12, adb now works completely over Wi-Fi (see screenshots below) without needing the USB cable to establish the initial connection like it used to be prior to Android 12.
If the screen problem is "just" hardware and not software, and if you can turn on Wireless Debugging, you might be able to display your phone over scrcpy or vysor (both of which use adb over Wi-Fi) as shown in the screenshots below on my phone - which never needs the USB cable connection.
Hope this helps, but you seem to need folks who know more than I do as adb/vysor/scrcpy all work for me because I can set up USB Debugging & Wireless Debugging as shown below.
Note that you might have an FTP server or a WebDav Server on your Android phone, and if you do, you might be able to at least transfer important files since they each can mount your entire Android phone as a drive letter on Windows over Wi-Fi (without needing the USB cable).
Click to expand...
Click to collapse
A20 can have only Android 9, 10 or 11, but thanks for ideas anyway.
I didn't even know adb can work over WiFi, I'll look into it. Hopefully this version can do it too.
Now trying blindly to turn on the screen reader…
damiandbcz said:
A20 can have only Android 9, 10 or 11, but thanks for ideas anyway.
I didn't even know adb can work over WiFi, I'll look into it. Hopefully this version can do it too.
Click to expand...
Click to collapse
Ooops. My bad. I apologize. You'll need the USB cable in Android 11 for a moment to establish the connection first. Then you can switch over to Wi-Fi after that (or you can stay on USB).
damiandbcz said:
Now trying blindly to turn on the screen reader…
Click to expand...
Click to collapse
I feel for you. I really do. It hurts me when people can't access their phone remotely to get their data back. I am searching all over the XDA site for a solution for you, where I just moments ago opened this thread to help (I'm still searching for you though).
What is the best XDA solution to control Android on the PC & recover data over Wi-Fi when the user suddenly has an unresponsive broken screen?