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
Related
I've just about torn out my hair at this point, but I've tried everything I can think of!
I've made three applications just now, that I'd like to compile and upload to Marketplace.
However, it seems you are only supposed to upload Retail / Release versions of your xap file.
I can't figure out what to do!
What I've tried:
Went to Project -> Properties -> Build -> Configuration -> Release
Then I tried to Build Solution, Rebuild and also Deploy.
From what I've seen on forums, that should suffice but when I look in /Project/bin all I see is the Debug folder.
Why?
EDIT: I "fixed" it..
I can see no other explanation that it's a bug.
I had to go in the configuration manager of whatever it's called (posting from my phone) and manually set the debug "profile" to use Release configurations. I couldn't change from Debug to Release.
Weird.
Look in the Output window and see what it's doing. It should show you what the problem is or the path it's building the package in.
I "fixed" it..
I can see no other explanation that it's a bug.
I had to go in the configuration manager of whatever it's called (posting from my phone) and manually set the debug "profile" to use Release configurations. I couldn't change from Debug to Release.
Weird.
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.
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.