Not sure if this has been talked about but I couldn't find it in here. The loss of use for outer USB port when adb is enabled is driving me crazy. (Shield 2017-16GB darcy). I know of this build.prop tweak: "persist.convertible.usb.mode=host" (should allow simultaneous use of the port. However, I believe after adding it you must factory reset being that the string has to be present upon system initialization. I'm hoping someone can confirm this working on stock ROM before I do so.
Related
Anyone know why "logcat" works when run via ADB but not when run from a local console (EG via connectbot)? I assumed they would use the same UID but in hindsight I'd guess that any android app that starts a shell would be running with the parent app's UID and ADB would provided a different UID again .
I'm trying to investigate what the N1 currently does with a powered (hacked together) USB OTG cable (say connected to a flash drive) I know the kernel doesn't currently support the host mode switch (or at lease it didn't when I was messing with my G1, don't know about 2.1 ) but I wanted to see if anything at all happened.
Anyone done any OTG experimentation of the N1?
I haven't done debugging yet, but I'm interested in your efforts. I'm looking to USB OTG support in an Android phone for MIDI sequencing purposes (record MIDI data on the phone from a USB powered MIDI device). Many people are saying that WiFi/Blutooth solutions are the way to go, but that requires the devices to be powered separately. USB OTG would solve the power problem and in the case of MIDI, solve the latency problem (not to mention that most devices are USB and don't have wifi/bluetooth support...so that would mean making an in-between widget to convert USB to wireless on the device side while powering it).
TL;DR Smashed phone, need to find a ROM with ADB enabled to use it
Long story short, I smashed my phone last Friday. The LCD screen works and the phone appears to be fully functional except for the digitiser. I had ADB disabled as I frequently plug my phone into computers at university and elsewhere and I don't want to run the risk of ADB commands being run maliciously. Since the Nexus 4 can't do USB OTG without a splitter cable (and, I believe, some configuration) I can't just plug in a mouse to control the phone. Annoyingly, this happened while moving house and I don't have internet at home until tomorrow; I was planning on using USB or WiFi tethering to get my PC online.
I found this page with a suggestion on what I might be able to do. Alternatively, my other plan is to connect an Ouya controller by bluetooth and use the touch pad on that to control the phone. Either way, the plan hinges on using ADB to control the phone to begin with to either configure an app or enable bluetooth.
I've noticed a lot of ROMs (since 4.3.1?) have ADB disabled until the user enables it. Also, whether or not ADB is enabled to begin with isn't something a developer is likely to list in their first post. Does anyone know any ROMs that have ADB enabled on first boot? Any other suggestions on what to do would also be great.
I am trying to Root my Galaxy s4 i9505 but the problems I'm facing are:
1. There seems to be a problem with my USB connection ie it does not get recognised by the PC. Appears that the USB connector is faulty. Will charge but no data
2. I have tried kingo and various other apps that offer no PC root. I can't get any of these to work
I read somewhere that I could root by using a combination of file saved on SD card and use Android Terminal Emulator to get root access. I tried one method and this doesn't work either.
Is there anything I haven't tried. Basically I'm trying to get root so I can enable the onscreen navigation keys as my menu and back button no longer work.
I made it on the same phone with this video ->
well my account is still under restriction's and i cant post links
but search on youtube for -> How to root Galaxy S4 (I9500/I9505) running Lollipop 5.0.1
and follow the first video
Hope it helps!
Are you using the original cable? If not, switch to the original cable as some USB cables, like ones from Logitech, are "charge" cables that do not have the data pins connected. Also, check your USB ports and make sure you're plugged into one of them rather than a hub.
Strephon Alkhalikoi said:
Are you using the original cable? If not, switch to the original cable as some USB cables, like ones from Logitech, are "charge" cables that do not have the data pins connected. Also, check your USB ports and make sure you're plugged into one of them rather than a hub.
Click to expand...
Click to collapse
Yeah i'm using the original cable supplied with the device. It seems like a problem with the USB connector on the phone as I've tried fresh install of OS on PC and reset the phone to factory as well. I've ordered a new USB board just in case. Problems seem to come from repair that was done on the phone after screen smashed. Repair carried out by qualified repair shop but since then no menu or back button function hence the root option so I can enable the soft keys on the device
If you had the device repaired, I would take it back to them and have them look at it instead of settling for a half-functioning device. Since they replaced the screen, they should be responsible for making sure the capacitive buttons work as well.
I managed to get into developer mode on my new NGP, there's no more "build number" as I've seen in several blog posts with the latest update you click on the Nook icon on the About page it takes you to Developer mode. I've been able to install a few apps, but here's what I'd like to do.
I'd like to plug in a USB keyboard and use it to SSH into another machine through my WiFi hotspot to do some HTML/JS/CSS text editing while I'm outdoors (at the pool, the park, etc) as my other laptops/tablets aren't visible at all outdoors with glare. This would be a nice portable solution if I could get it to work, even editing locally on the device through some editor and sending via SFTP would be just fine.
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
JohnnyFriendly said:
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
Click to expand...
Click to collapse
As a workaround I put a VNC client on it so I can access my other devices and do the typing from there, that way I can use my RPI3 as the system with a keyboard on battery power and do some Python (Django)/NodeJS/ReactJS from the NGP using it as a monitor outdoors, but if I issue the following commands via adb to rotate into landscape mode I lose input on the NGP and have to reboot:
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1
Any ideas?
I believe I looked at this once.
At least one of the problems is that the ID pin on the micro USB connector is not connected through to the processor.
B&N has never shown any interest in putting Bluetooth in a Nook.
We'll have to see if the latest "Nook Glowlight 3" will have either OTG or BT.
Hello All,
The micro USB port of my phone is a Motorola G4 Play (Harpia) has stopped working for a long time — no data transfer of any sort, no OTG, no ADB, no File-Transfer, nothing; only charging works. I thought it was the port to PCB soldering, so I re-soldered it. Didn't work. I changed the Charging PCB ("Charging Connector Flex Cable"), twice. Neither worked. Now, my LCD is broken, so it is unusable beyond being a wireless hotspot or for receiving calls. I'm in a dilemma whether I should replace it (₹1000+ for spares) or give up & move to a 2G Basic Phone.
Can anyone help me figure out why the USB data transfer is not happening in my device? I'd really love to repair it.
Thank You.
Note: It is not a driver issue as I use Linux & lsusb doesn't show the device. It is not a ROM issue either since the same happens in TWRP and across the ROMs I've flashed.