• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Device Crashes when OTG cable is plugged in

R

Riley Davies

Lurker
I have a rooted galaxy s5 with cyanogenmod 14.1 installed. Before installing cyanogenmod, all of my 3 OTG cables worked perfectly. Now, whenever I plug the cable in, it freezes the phone for about 5 seconds and then it crashes to the boot up screen (shows "galaxy s5" with the custom os lock and "powered by android"). The weird thing is that it even crashes if there is nothing plugged into the other end of the OTG cable. I experimented a little, and found that it doesn't crash if I have a normal charging cable plugged into my phone, and the otg cable on the other end (phone>charging cable>otg cable). It only crashes if the otg cable is plugged directly into the phone and doesn't matter if it has anything on the other end or not. Leaving the otg cable into the phone only results in a boot loop until it is removed. I have no idea why this is happening. Is there any solution? Can I do anything about this? Or do I have to find another custom rom or simply abandon otg cables...
If anyone needs any specs then tell me.
 
Riley Davies said:
I have a rooted galaxy s5 with cyanogenmod 14.1 installed. Before installing cyanogenmod, all of my 3 OTG cables worked perfectly. Now, whenever I plug the cable in, it freezes the phone for about 5 seconds and then it crashes to the boot up screen (shows "galaxy s5" with the custom os lock and "powered by android"). The weird thing is that it even crashes if there is nothing plugged into the other end of the OTG cable. I experimented a little, and found that it doesn't crash if I have a normal charging cable plugged into my phone, and the otg cable on the other end (phone>charging cable>otg cable). It only crashes if the otg cable is plugged directly into the phone and doesn't matter if it has anything on the other end or not. Leaving the otg cable into the phone only results in a boot loop until it is removed. I have no idea why this is happening. Is there any solution? Can I do anything about this? Or do I have to find another custom rom or simply abandon otg cables...
If anyone needs any specs then tell me.
Click to expand...

Sounds like it's a bug with the particular build of CM you're running. As CM is no longer developed and Cyanogen Inc. is dead, don't expect a fix any time soon. However LineageOS basically continues where CM left off...so I suggest try their Galaxy S5 custom ROM instead.
https://lineageos.org/
 
You must log in or register to reply here.
Back
Top Bottom