yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] vikassaini01:
Great Kernel, ;)

Can you please Add USB Host mode driver for Samsung Galaxy S (i9000) ?

Read this :

http://xdaforums.com/showthread.php?t=1450298

That will be a great feature for SGS

Edit :

Just found that you have already included it in next Beta version 2.6.0b, :)

quite fast.. I will get a cable and test it out.
[Galaxy S I9000 Android Development] Brignoud:
Hi Stratosk,

Upgrading CWM (the application manager) seems to be rejected.

The application itself after installing correctly dooesn't recognized a correct kernel: it state that Chainfire is not present and so some feauterad resulting disabled.

In fact it seems that backup function, disappear from version 2 to 3.

Thks
[Galaxy S I9000 Android Development] jna9000:
Looking at the Youtube Video how to cable a USB stick to the phone, I would strongly suggest not to waste energy to implement the driver.

If you could plung in a USB stick and everything would work well, than it would be great. But you need a special cable (OTG), a powered(!) USB hub and some things more - it is way faster to plug the phone in a pc and you're ready.

As a proof of concept it's nice, but not for daily use...
[Galaxy S I9000 Android Development] andip71:
I would still appreciate to go for the driver because of my specific holiday scenario:

By taking an external HD with me (a powered one) and this extension, I can put my pictures and videos onto the HD and free up my SD card again for new pics and videos. Although i have a 32 GB SD Card, taking videos eats the storage up quite quickly.

Same with videos I put on my mobile to watch at the beach. I can load new videos from the harddisk if required.

So I think it makes anyway sense for many of us :)

Thanks

Andi
[Galaxy S I9000 Android Development] stratosk:
I have already implemented. :) I just want to know if it works.

It's a feature. Using a feature or not it's a matter of taste.

I never use tethering (maybe in the future). Should I remove tethering from the kernel?
[Galaxy S I9000 Android Development] Dinesen68:
Hi, is the semaphore 2.60beta compatible with 2.3.4 JVQ??? thanks...
[Galaxy S I9000 Android Development] yobbei:
any chance to see captivate version soon?
[Galaxy S I9000 Android Development] sgw99:
CWM version

Hello, I follow the semaphore kernel for a while now.

Big thanks to stratosk in special and everyone else contributing to this very useful kernel.

My question is:

Using 2.5.0 I assumed I should have CWM-5 as well, according to the release notes. When I open the app CWM I read "CWM Manager v2.0" ... is that correct? If no, how to change that?

Thanks, greetings, Stefan
[Galaxy S I9000 Android Development] sefira:
That is correct. It is the version of the app itself only.
[Galaxy S I9000 Android Development] sgw99:
Ah, ok. Do I see the version 5 of CWM somewhere else?

Thanks.
[Galaxy S I9000 Android Development] sefira:
Only when you enter recovery mode you will see CWM 5 at the bottom of the screen...
[Galaxy S I9000 Android Development] Brignoud:
The recovery mode, today 5.0, it's not the CWM manager application.

As state some post earlier asking to Stratost for a problem, you can have version 2 or version 3 of the manager application but 5 of the Clocwork.

Please Stratosk, answer my question: how to have, version 3 of the manager totally compliant with your kernel?
[Galaxy S I9000 Android Development] sgw99:
Thanks, just wanted to make sure that things don't drift apart somehow in the background.
[Galaxy S I9000 Android Development] elhennig:
I'd like to know, if it is possible to use Chainfire's DSLRController with this OTG driver? Anyone testes this so far?
[Galaxy S I9000 Android Development] ramanadodda:
AFAIK, all Semaphore kernels can be applied to any GB 2.3.X ROMs.
[Galaxy S I9000 Android Development] stratosk:
Anyone tried the new OTG driver successfully?

Please for your feedback.
[Galaxy S I9000 Android Development] bitblaster:
I'm waiting for the OTG cable. Do you think it should work using an external hd with its own power supply or i need also an usb hub?

p.s.: I sent you a pm days ago. If you could give me the build details I'll work on the "runtime patching" in the weekend. Thanks!
[Galaxy S I9000 Android Development] sirbrian:
Voodoo Color Settings

If in the Semaphore Script Manager, I select "Voodoo-Default" in the "Voodoo Color Settings" BUT in the Voodoo Control App 2.1.1 the "Color profiles" settings I selected "Original <2.3.3", does it means that I am still back default original color profile and not Voodoo?

If I want to use Voodoo color profile, what I need to do and what is the best "Screen RGB multipliers" and "Screen v1 gamma hack" settings?

Thanks for your advise.
[Galaxy S I9000 Android Development] stratosk:
I will check this. But it's not in my first priorities since I dropped this CWM manager from the kernel.
[Galaxy S I9000 Android Development] Difusal:
Thank you for including it! I haven't tested it yet as I don't own any usb otg cable. It's quite raw I think, but time will improve it hopefully. Is there any positive feedback? I will sure get a cable if this works. And for those who think this is useless, just think of going on a trip and you fill your memory with videos and photos, with usb otg you could move those files to a small pen, way easier than taking a heavy, big laptop in my opinion!

Please link it in the original post so noone misses it and for us to stay tuned regarding any updates or features :)

about tethering, I have never used it. You could make a poll to know if people want to keep it or not. Personaly, any decision for me is fine :b

have a nice day :)
[Galaxy S I9000 Android Development] gandrik:
Great feature to add USB host mode driver and I already download and install semaphore kernel 2.6.0b. I tried to find OTG driver setting like http://attachments.xda-developers.com/attachment.php?attachmentid=860655&stc=1&d=1326792101 to control OTG operation mode. but i can't found it. Could you tell me where is i can found OTG driver setting? I am using surface ROM JVU.
[Galaxy S I9000 Android Development] sztupy:
It's a separate app called UsbHostController. If it's not included in the ROM you can download it from Market: http://market.android.com/details?id=hu.sztupy.android.usbhostcontroller
[Galaxy S I9000 Android Development] stratosk:
Please download sztupy's application from market: https://market.android.com/details?id=hu.sztupy.android.usbhostcontroller

Then, follow the instructions in sztupy's thread for the setup.

Edit: Author is faster than me. :)
[Galaxy S I9000 Android Development] stratosk:
I've already have a link in OP to the beta version. No, positive feedbacks yet (and no negative yet :) ).

About netfilter: I answered (and other people also) hundreds times the question about tethering not working because the netfilter is built as modules. So there are a lot of people using it.
[Galaxy S I9000 Android Development] sztupy:
I'm very curious whether it works or not :)
[Galaxy S I9000 Android Development] stratosk:
Me too my friend. :) It was a huge patch! I also change some lines to get this work without a couple of compilation errors (I suppose because of the difference in kernel version).
[Galaxy S I9000 Android Development] andip71:
I guess many people are now hoping to be the first one owning a OTG cable :D

To come with the good or bad news... :)
[Galaxy S I9000 Android Development] stratosk:
I guess there is lack of OTG cables out there.:p

I hope that someone will come with good news. :)
[Galaxy S I9000 Android Development] Fenvarien:
I will have one in 36 hours ;-)

... using tapatalk
[Galaxy S I9000 Android Development] rmean:
is it theoretically possible that devices can get powered by the phone? anyone have the expertise to check this? I don't :)
[Galaxy S I9000 Android Development] oswade:
Ah, just realised tethering is broken (error when starting). Using 2.5.0bmsc. Sorry if this is already known (I haven't seen any mention). Does it work on non-bigmem?
[Galaxy S I9000 Android Development] moustic_moustic:
Just load the netfilter module in the semaphore options. Thanks to the member that told me that!
[Galaxy S I9000 Android Development] dherre65:
I'm sorry I honestly don't understand what the new OTG feature means/can do. Okay, OTG means On The Go. Right? But can someone please explain how it works?
[Galaxy S I9000 Android Development] oswade:
ahh, many thanks! I saw that option before but didn't realise it was a prereq.
[Galaxy S I9000 Android Development] lucbl1:
With this fix, the phone recognizes up to 10 points of multitouch instead of just 5. I know it sounds kinda childish, but it actually helps a lot in game e.g: modern combat 2

Keep up the excellent work :)
[Galaxy S I9000 Android Development] mawardi:
Yup. But it worked fine with Pimp My CPU with the same UV.
[Galaxy S I9000 Android Development] stratosk:
OK, I will examine it in the future, if I have time
[Galaxy S I9000 Android Development] stratosk:
Can you please clarify if it is possible to reproduce the issue after applying the workaround? If yes, can you provide me the exact steps and maybe logcat? (if you are in stock ROM).

Maybe, If it is ok for you I can provide you a test kernel tonight just for the BT issue
[Galaxy S I9000 Android Development] Rebel2k:
Hi @stratosk: I'm in! :) If you find the BT issue, you will help many kernel dev! ;)
[Galaxy S I9000 Android Development] stratosk:
Ok, I want to try a couple of things in the initramfs. I don't know if it will resolve the issue...

I will post a test kernel tonight.
[Galaxy S I9000 Android Development] pikachu01:
Here's the thing, to when UV, you'll need to test it using different variety of processes to stress the setting. Some UV fails for:

- The time spent in that frequency (heating problems? or timing problem when spent too long)

- The logic being toggled in that frequency (e.g. playing video toggles floating point logic in the CPU)

When you use the UV for 400 MHz, the CPU scales quickly enough to not linger on 400MHz more than a certain period of time. However, when 400MHz is the max, it lingers on that much time causing the phone to hang.

Also, when you UV for 400MHz, sometimes when certain apps are running, some logic in the CPU toggles and then hangs because not enough voltage is provided for it.

Hence, it's due to UV.
[Galaxy S I9000 Android Development] Rebel2k:
Ok! It is nice to try to solve this issue! Any of the Semaphore kernel versions I tried until now had the BT-won't-turn-on issue for me. I hope you'll point this issue out! ;)
[Galaxy S I9000 Android Development] stratosk:
OK, attached is the first TEST version. Only flash it if you want to help me to investigate BT issue.

It disables some things in initramfs.
[Galaxy S I9000 Android Development] shashank.aviator:
can 1.3.1 be used with JVH?
[Galaxy S I9000 Android Development] stratosk:
You may try it. But maybe you will face some incompatibilities
[Galaxy S I9000 Android Development] Rebel2k:
I'm trying it right now! It is booting...
[Galaxy S I9000 Android Development] quangmach:
Hi,

Just tested no Bt issue with wifi on at startup, but I came from stock Voodoo kernel. It more accurate if result is from other people with Cf based kernel
[Galaxy S I9000 Android Development] quangmach:
Just flashed normal 1.3.1, bluetooth still working with wifi on at startup. However, It took longer to Enable Bluetooth compare to the test version. I think its related to timeout?
[Galaxy S I9000 Android Development] shashank.aviator:
Okay... just flashed 0.2.1 on my JVH... dont wanna change to JVQ till the browser problems are fixed.

btw strato... do u plan on including any update in JVH version? id really appreciate it.
[Galaxy S I9000 Android Development] Rebel2k:
Indeed, it works differently than before (with the test version)! Now, if I keep wifi enabled and reboot, I can still turn BT on, which had never been the case before on your previous versions!

I have tested a few times to be sure of it, but it seems to work better! I think you figured it out! You found the responsible! :) Hope you'll say it to every dev if it is confirmed, for everyone to fix this BT issue!

You're the man! :)

EDIT: By the way, Tweaks app isn't working anymore and CWM app reports the kernel as "unknown". But I prefer this than BT not working! :)
[Galaxy S I9000 Android Development] stratosk:
Thanks for testing. But it is not the end. :)

As I said I disabled some things in initramfs to prove that the problem is in the initramfs.

I know that CWM, and tweaks does not work.

Do you want to continue testing and narrow down the problem?

If yes, I will post second test version soon.

OK, Test 2. Maybe this break BT again...
[Galaxy S I9000 Android Development] Rebel2k:
Of course I want, as long as you can certify it will not destroy my data! ;)

EDIT : I download and flash in a few seconds. Do you have an IRC channel or any kind of IM we could chat a bit faster? (if you would ^^)
[Galaxy S I9000 Android Development] stratosk:
No, there will be no problem with your data... :)
[Galaxy S I9000 Android Development] stratosk:
I appreciate your help but it is not possible. Please for you patience.
[Galaxy S I9000 Android Development] jna9000:
For the plain explanaition, read Wikipedia: http://en.wikipedia.org/wiki/USB_On-The-Go

For the use with the SGS, see this post: http://xdaforums.com/showthread.php?t=1450298

You need a bunch of cables, power source, connect them all some mystic way and you might use your USB stick as external storage (yes, I'm still not convinced of the concept...)
[Galaxy S I9000 Android Development] elhennig:
No, you definitely need an OTG USB cable.

You only need a hub or a Y cable if you want to connect an USB device, that is powered through USB and needs more power, than the phone can offer. This is true for USB harddisks for example. Card readers or USB flash drivers should work without extra power supply.

There is nothing mystic about that.

Can some one confirm, that DSLR cameras can be used with the new USB-OTG function? I asked before, but so far there was no answer...
[Galaxy S I9000 Android Development] Chainfire:
I couldn't get OTG to work on this kernel (OTG cable and powered hub)

Trying CM and sztupy's kernel next. (I really don't like CM, wish this kernel worked, hehe)

/dev/bus/usb seems to be absent. Not sure if that's normal for this patch, but it's present on all other devices I've tested that have USB host support.
[Galaxy S I9000 Android Development] vd69:
Stato kalimera .Why 250sc is 7.44 mb and 2.60 beta is 6.44 mb .Is there other differences exept OTG driver?
[Galaxy S I9000 Android Development] stratosk:
Thanks a lot for checking this, chainfire.

I really wonder, how to debug this...

Edit: I just found that the /dev/bus/usb is created only when you use 'host mode' or 'OTG' mode from sztupy's application.

Could you possibly check this again using these settings in sztupy's application?
[Galaxy S I9000 Android Development] stratosk:
I used different compression method (LZMA - better compression, slower decompression) in 2.6.0beta, to keep the size of the kernel bellow 8MB.
[Galaxy S I9000 Android Development] jna9000:
If this is the case, I would be convinced :D
[Galaxy S I9000 Android Development] Chainfire:
Will reflash later and try again.... that is, if I can even get sztupy's version to work for me ...
[Galaxy S I9000 Android Development] :
OTG

Can't get OTG working... yet!

Using your 2.6.0 beta kernel with my own-made cable. Externally powered through an arduino board. Stzupy's app recognizes the cable and allows me to set USB mode to either host or OTG but dmesg show's nothing at all...

I can confirm that /dev/usb is created when Stzupy's app is running.
[Galaxy S I9000 Android Development] Chainfire:
FYI After more testing, it appears the USB hub I was using earlier is not compatible with sztupy's patch for some reason.
[Galaxy S I9000 Android Development] stratosk:
Thanks for your info and for testing.
[Galaxy S I9000 Android Development] xenon_bn:
I will try to flash JVU today + Semaphore 2.5.0 (after staying one month with JVT). Everything is fully functional with 2.5.0 (normal kernel, not sc or bm) ? Thanks!
[Galaxy S I9000 Android Development] stratosk:
Yes, everything should be functional with normal version.
[Galaxy S I9000 Android Development] gsw5700:
I was on jvt for ages, jvu is at least as good and appears to use less memory. I use 2.5.0 bm with andip's theme, all working really well

Sent using TCP/IP
[Galaxy S I9000 Android Development] xenon_bn:
Finished flashing 2.5.0 normal kernel. All good for now. I will give feedback later on
[Galaxy S I9000 Android Development] rabievdm:
Non color fix option

Hi stratosk,

Thanks for the non color fixed kernel options, my display just seems so much more

crisp without the fixes than with. And I was 'forced' to use them as everyone has

always just included them in their kernels.

Thank man! +1000

R
[Galaxy S I9000 Android Development] go4saket:
I installed Simplicity 2.2.1 ROM and then installed Semaphore 2.5.0BM. Problem is that the option to change the colors in Voodoo Control Plus doesnt exist any more. How can I get it back?
[Galaxy S I9000 Android Development] sherpa25:
what's the non color option.... is this the sc version? Using 2.5, my screen sometimes show a green layer.
[Galaxy S I9000 Android Development] ZaneZam:
Maybe you catched a "sc" (stock color) version? Flash a regular version and the settings will be there!
[Galaxy S I9000 Android Development] ZaneZam:
Try to reset gamma settings to 2.3.3 in voodoo control, this fixed green appearances for me or use one of the stock color versions ;)
[Galaxy S I9000 Android Development] sztupy:
Just got this one in PM:
[Galaxy S I9000 Android Development] Chainfire:
Well first I had a hub that simply didn't work with this. With my other hub, it all works under ICS-CM9 with sztupy's kernel, and DSLR Controller v0.85 (should be on Market in a few days).

Now, the exact same setup as on ICS-CM9 does NOT work on Semaphore 2.6.0 beta with USB host. The phone freezes and reboots as soon as I connect the hub in OTG or host modes.
[Galaxy S I9000 Android Development] GrNick:
I have a Samsung OTG cable and I flashed 2.6.0 beta in JW1. Apparently my USB hub does not work buy I will try again tomorrow with another one. Definitely though I am getting a lot of reboots (every couple of minutes) when the OTG is connected.

Edit (Some more info):

whithout the OTG cable connected, now uptime 50min without reboots. With the OTG cable, so long that I keep the "usb host controller" app in the foreground and not allowing the screen to time out, then no reboots. If the phone idles, then it goes to a reboot cycle.

regarding driver and controller app: In the info tab, the S3C OTG host enabled driver is getting found, otg cable is regognized, state changes to host and I also get the "root hub found" when the app checks for usb host mode. But nothing shows up in the usb tab. Attached the last dmesg, if anyone is interested.
[Galaxy S I9000 Android Development] stratosk:
Test version 2.6.0beta2

- removed s5pc110 USB-OTG Controller checking during initialization.

I'm sorry, I'm going like a blind on this.

If someone have some free time and want to check beta2...
[Galaxy S I9000 Android Development] sirbrian:
If in the Semaphore Script Manager, I select "Voodoo-Default" in the "Voodoo Color Settings" BUT in the Voodoo Control App 2.1.1 the "Color profiles" settings I selected "Original <2.3.3", does it means that I am still back default original color profile and not Voodoo?

If I want to use Voodoo color profile, what I need to do and what is the best "Screen RGB multipliers" and "Screen v1 gamma hack" settings?

Thanks for your advise.
[Galaxy S I9000 Android Development] Chainfire:
Probably your hub is talking USB 1.1 to the SGS. Likely the very same problem I had myself with the first USB hub I tried. With the second hub, I get the rebooting every few minutes again as soon as I add a USB 1.1 stick.

(this was all tested on ICS btw, this kernel doesn't work for me for some reason)

Sure.

EDIT: Still freeze/reboot on switching to OTG/host modes.

Last thing I got out of dmesg before reboot:

<4>[ 165.407379] otg_dbg: in root_hub_feature()::00287 => root_hub_feature
<4>[ 165.407388] otg_dbg: in root_hub_feature()::00519 => case SetPortFeature
<4>[ 165.407399] otg_dbg: in root_hub_feature()::00544 => case SetPortFeature -
USB_PORT_FEAT_POWER
<4>[ 165.408479] otg_dbg: in s5pc110_otg_drv_probe()::00148 => OTG HCD Initiali
zed HCD, bus=C110 OTG Controller, us....

There could well be lines after this, of course (freeze also affects adb)
[Galaxy S I9000 Android Development] GrNick:
Flashed 2.6.0beta2 on JW1:

No OTG connected = no reboots

OTG connected + client operation mode in controller app = no reboots

OTG connected + OTG operation mode in controller app = reboot as soon as screen goes off.

Re: Chainfire's previous post:

yeap, there are more lines:

after ...case SetPortFeature and the otg hcd initialized there is...

<4>[ 698.955055] otg_dbg: in root_hub_feature()::00287 => root_hub_feature

<4>[ 698.955064] otg_dbg: in root_hub_feature()::00519 => case SetPortFeature

<4>[ 698.955075] otg_dbg: in root_hub_feature()::00529 => case SetPortFeature -

disconnected

<4>[ 698.955086] otg_dbg: in root_hub_feature()::00544 => case SetPortFeature -

USB_PORT_FEAT_POWER

<4>[ 698.955700] otg_dbg: in s5pc110_otg_drv_probe()::00148 => OTG HCD Initiali

zed HCD, bus=C110 OTG Controller, usbbus=1

<4>[ 698.956214] platform_driver_register...

<4>[ 699.053697] otg_dbg: in root_hub_feature()::00287 => root_hub_feature

<4>[ 699.053714] otg_dbg: in root_hub_feature()::00417 => case GetPortStatus

<4>[ 699.053725] otg_dbg: in root_hub_feature()::00466 => case GetPortStatus -

disconnected

<4>[ 699.053736] otg_dbg: in root_hub_feature()::00508 => port_status=0x400.

<7>[ 699.053778] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000

~ # dmesg

dmesg

C:\adb\platform-tools>

With client, host and auto mode I am OK. With OTG mode I get a reboot in 1-2minutes or as soon as I shortly press the power button and the screen goes off. Given that I precict _exactly_ when a reboot will appear, is there a way to set the dmesg to record the event?
[Galaxy S I9000 Android Development] sztupy:
Instead of running dmesg I usually do the following:

> adb connect 192.168.1.100
> adb shell
$ su
# echo o > /sys/devices/platform/s3c-usbgadget/opmode
# cat /proc/kmsg

This way you can usually see all the kernel messages up until the moment of freeze/restarting.

It seems though that a non-cm gingerbread kernel is anticipated so I think I'll try backporting it myself too.
[Galaxy S I9000 Android Development] stratosk:
Thanks everybody for helping on this. Unfortunately, I run out of 'thanks' for today.

Anyway, on more shot - 2.6.0beta3
[Galaxy S I9000 Android Development] GrNick:
Ok, here are the two logs, filenames are self-explanatory. Stratos, look at the last lines. One more thing: I just connected a _self powered_ usb disk directly to the otg cable. Not working. If I understood well, it should work (?) given that it has its own power. That usb disk is definetely usb2. Still the usb port looks disconnected (?)

Edit: Re: Stratosk post below: Yeap, still same on beta3. I further tried connecting this powered disk the correct way (powered y cable) and the wrong way (direct usb cable). Not working, both times saying:

otg_dbg: in root_hub_feature()::00465 => case GetPortStatus -disconnected

but, when correctly connected I get an error:

otg_dbg: in root_hub_feature()::00507 => port_status=0x500

whereas, when connected wrongly, I get:

otg_dbg: in root_hub_feature()::00507 => port_status=0x400

I wish I knew what the debugging codes 0x500 and 0x400 meant.

Lastly, I forgot to mention that with beta1-2-3, when connecting the powered disk correctly, the system freezes (just as chainfire described). This happens when power is 5V/300mA. When I switch to 5V/700mA, I don't get any freezes!
[Galaxy S I9000 Android Development] stratosk:
Still reboots with beta3?

Yes, I guess a self powered disk should work.

Anyway, I can't find the way today (my knowledge about usb drivers doesn't help at all). I will sleep on it. :)

Maybe I can find some cables tomorrow.

Thanks again, everybody.