Hi
I have been attempting to compile a kernel with HID gadget suppor for the galaxy S3 for close to a month now and believe i have finally found the problem.
When you run make menuconfig and select device drivers > USB support > usb gadget support and set USB Gadget Drivers to anything other than Android Gadget (the default), then in the .config file the option CONFIG_USB_G_ANDROID gets commented out. The problem is that that variable needs to be set to y for the driver to compile.
So my question to you is where should i start to diagnose this problem? can i change what options are set in .config when i select an option threw menuconfig? or is this a dependency issue that i need to fix in the drivers?
If someone can give me a push in the right direction it would be greatly appreciated.
Thanks
Adrian
Can someone explain this in layman's terms?
Gökhan Moral's port of Voodoo Sound implemented. Currently no configuration interface is available, so if you wish to play with the settings, refer to the sysfs interfaces in /sys/class/misc/scoobydoo_sound/ . If you wish to change the device name, you must do echo 0 > /sys/class/misc/scoobydoo_sound_control/enable , followed by an echo output to the same file with the target device driver name. You can use this to change the device path to /sys/class/misc/voodoo_sound/ and sub-sequentially make a certain configuration application work. Please do not ask me for support on the latter. You can disable the sound modifications completely by the same method, by of course not re-enabling it afterwards.
You would do urslelf a big favor by Google n command line. There are apps in the play store that are basically quick guide apps that have terms in them. So use the google tool bar type command line help and you will get better help.
https://www.youtube.com/watch?v=JmvCpR45LKA&feature=youtube_gdata_player
Can someone explain this in layman's terms?
Gökhan Moral's port of Voodoo Sound implemented. Currently no configuration interface is available, so if you wish to play with the settings, refer to the sysfs interfaces in /sys/class/misc/scoobydoo_sound/ . If you wish to change the device name, you must do echo 0 > /sys/class/misc/scoobydoo_sound_control/enable , followed by an echo output to the same file with the target device driver name. You can use this to change the device path to /sys/class/misc/voodoo_sound/ and sub-sequentially make a certain configuration application work. Please do not ask me for support on the latter. You can disable the sound modifications completely by the same method, by of course not re-enabling it afterwards.
I know on my Galaxy S3 I could type in some # string and it would set the USB connection type to always connect as MTP but I cannot find that for this Note 4.
When I plug it in to any PC it defaults to "Connected as Installer" and I have to manually change it to MTP to get it to work as an external USB drive.
Is there some trick or setting I am missing to change this so it will always connect as MTP unless I tell it to do otherwise?
If you have the retail version, sadly there is no way to change this setting as it is baked i believe in the default.prop or build.prop settings. For developers edition they can change it easily as such i believe as they have root.
I actually do have the Dev version so if anyone knows how to change this, please do share.
Hey!
I have LG L62VL phone, need to connect it to DFS for programming NAM...
I have root (I found ROOT method which one is working, but it works only until reboot). Tried Shortcut Master Lite apk, couldn`t find anything for activation diag or hiddenmenu. Hidden Menu is working by *#546368#*62#, but there is only:
Device Test
ELT Test
Factory Reset
Log Service
HW Version
CMAS_RMT
QFUSE_CAL
If connect usb in MTP mode, it`s showing COM Port but not working with DFS (red words...)
Is there way to connect this phone to DFS?
Since you have root, maybe doing this in a terminal might work?
Code:
su
setprop sys.usb.diag_enable 1
setprop sys.usb.config qmicm,adb
setprop sys.usb.state qmicm,adb
I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters.
Don't really know for sure if that would work. You could also write to the sysfs parameters as root located in /sys/class/android_usb/android0/. I've been able to get the Qualcomm HS 9008 mode enabled on other qualcomm devices that have been locked down using that method.
Out of curiosity, may I ask how you were able to obtain root on this phone?
zdwilson said:
Since you have root, maybe doing this in a terminal might work?
Code:
su
setprop sys.usb.diag_enable 1
setprop sys.usb.config qmicm,adb
setprop sys.usb.state qmicm,adb
I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters.
Don't really know for sure if that would work. You could also write to the sysfs parameters as root located in /sys/class/android_usb/android0/. I've been able to get the Qualcomm HS 9008 mode enabled on other qualcomm devices that have been locked down using that method.
Out of curiosity, may I ask how you were able to obtain root on this phone?
Click to expand...
Click to collapse
Hi i have a LG G7 and as u say "I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters." i cant enable the diag serial mode. Do you have any clue by looking at my init.lge.usb.*.rc on how can enable it?
I have root, but those 3 lines above does nothing.
prokiller1199 said:
Hi i have a LG G7 and as u say "I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters." i cant enable the diag serial mode. Do you have any clue by looking at my init.lge.usb.*.rc on how can enable it?
I have root, but those 3 lines above does nothing.
Click to expand...
Click to collapse
Yeah, I wasn't certain that would work, figured it'd be worth a shot. I don't have a G7 or the capacity to download the kdz and extract those files right now, I figure the contents of those files may differ slightly from the ones on the K20 I have.
If you could post the contents of your init.lge.usb.*.rc file(s) in a [ code ] tag or pastebin or something, I can take a look and see if I can gleam anything from that for you.
zdwilson said:
Yeah, I wasn't certain that would work, figured it'd be worth a shot. I don't have a G7 or the capacity to download the kdz and extract those files right now, I figure the contents of those files may differ slightly from the ones on the K20 I have.
If you could post the contents of your init.lge.usb.*.rc file(s) in a [ code ] tag or pastebin or something, I can take a look and see if I can gleam anything from that for you.
Click to expand...
Click to collapse
kindly check pm