fascinate shows up as cd rom

[gunnermike53]

I think the problem stems from here:

https://github.com/sirgatez/Android...ob/master/drivers/usb/gadget/f_mass_storage.c

Im just not sure if I am smart enough to fix it.

#define FEATURE_DEVICE_AS_CDROM_DEVICE_FOR_DRIVER/*-------------------------------------------------------------------------*/#ifdef FEATURE_DEVICE_AS_CDROM_DEVICE_FOR_DRIVER/* SCSI device types */#define TYPE_DISK 0x00#define TYPE_CDROM 0x05

why is this even in there. why would the phone ever need to show up as a cd rom?

we have faith in you. i certianly have more faith in you and the other indie devs than i do sansungs, that for sure.

 

[Adrynalyne]

I *believe* its in there for the verizon iso that pops up on their phones, these days. Im going to try and compare it to my HTC kernel source (it doesnt have this problem) and see if I can make heads or tails of it.

 

[Adrynalyne]

First attempt:

Failed to compile.

Second attempt:
I broke mass storage, and made Linux see my device as two storage cards + a cd rom drive, LOL.

Third attempt:
Successfully cleared out code, which in turn makes it a PERMANENT detection as a CD ROM drive.

Still trying.

 

[gunnermike53]

First attempt:

Failed to compile.

Second attempt:
I broke mass storage, and made Linux see my device as two storage cards + a cd rom drive, LOL.

Third attempt:
Successfully cleared out code, which in turn makes it a PERMANENT detection as a CD ROM drive.

Still trying.

sounds like you are making progress.

 

[Adrynalyne]

Yeah, but in the wrong direction.

 

[Adrynalyne]

I offer two test kernels. One voodoo, one not.

Let me know if it resolves the issue. Note: It does not make the verizon cd thingy that pops up go away, thats another thing entirely.

Voodoo
http://dl.dropbox.com/u/2056318/usb_test_3.zip

Nonvoodoo
http://dl.dropbox.com/u/2056318/usb_test_3_novoodoo.zip

These are not daily drivers, and may not fix the problem.

 

[fwdixon]

For anyone interested in a bit more about the phone's virtual cd-rom, sir gatez over on XDA provided me with this:

It is determined from reading nvram settings if the function should be turned on or not. By making 2 simple changes you can force it on or off. My patch below does not edit nvram it simple returns off where it should return on. NVRAM keeps the original value incase it is needed as some later point. Changing the tl_setting to 1 in get_tool_launcher_setting and returning 1 from is_tool_launcher_enabled will force the driver to load. You can change the location of the iso file in:

Eclair-2.6.29.6/drivers/usb/gadget/f_mass_storage.c
Line: 1454: static int do_inquiry_cdrom(struct fsg_dev *fsg, struct fsg_buffhd *bh)
if(is_tool_launcher_enabled())
ret = open_backing_file(fsg, fsg->curlun, "/etc/verizon_i500.iso"); //Edit this file name to your liking
#endif


Patch to disable CDROM driver in the OFF position, turning it on can disable other USB gadgets, bad kernel hacking will have your SDcard show up as an invalidly formated CDROM device if you plug it up with this on, be careful, backup your stuffs if you decide to experiment as you never know!!!:

Yes I could probably just patch one of the below functions but I like to be safe, as the NVRAM setting CAN be changed by the phone's system OS. So patching both ensures that if it does change, that it continues to return false that the driver should be disabled.

Eclair-2.6.29.6/drivers/usb/gadget/fsa9480_i2c.c

Line 2157: Function int get_tool_launcher_setting(void)
DEBUG_TL("reading tool launcher setting. TL: %d \n", tl_setting);
+tl_setting = 0; //This tells the tool launcher that the setting is off
set_tool_launcher_setting_state(tl_setting);

Line 2191: int is_tool_launcher_enabled(void)
{
+return 0; //This tells functions that the driver is disabled
if(get_tool_launcher_setting() > 0)

And yes, it is for the verizon .iso

 

[megalosdog#AC]

works great even with custom kernels....many thanks

 

[aitee]

I have the same thing with the AT&T Captivate

All I had done was followed this: Captivate JI6 kernel with "2e recovery" enabled - xda-developers

So as to roll back my 3e recovery to 2e so to be able to root (so it doesn't verify the update.zip). I used Odin3 and flashed the kernel.. If nothing else, I think i might try to flash the kernel. Anyone know where I can find the FROYO.UCKB1 kernel.

Here is also my post on xda:
[Q] Internal System Memory is showing up as a CD-ROM drive in windows 7 - xda-developers

mine shows up as a cd; the cd driver it keeps installing (if it helps) is:
Android UMS CD-ROM USB Device
AND
CDOZMV 4167 CLERKX2B SCSI CdRom Device

The second appears to no bring results on Google, but the first does.. I'll have to look into that.


Anyway I hope I/we can figure out what the heck is going wrong.

 

[anon(94115)]

All I had done was followed this: Captivate JI6 kernel with "2e recovery" enabled - xda-developers

So as to roll back my 3e recovery to 2e so to be able to root (so it doesn't verify the update.zip). I used Odin3 and flashed the kernel.. If nothing else, I think i might try to flash the kernel. Anyone know where I can find the FROYO.UCKB1 kernel.

Here is also my post on xda:
[Q] Internal System Memory is showing up as a CD-ROM drive in windows 7 - xda-developers

mine shows up as a cd; the cd driver it keeps installing (if it helps) is:
Android UMS CD-ROM USB Device
AND
CDOZMV 4167 CLERKX2B SCSI CdRom Device

The second appears to no bring results on Google, but the first does.. I'll have to look into that.


Anyway I hope I/we can figure out what the heck is going wrong.

Not giving you a blow off, but you might have better luck in the Captivate forum. I know the Fassy and the captivate are cousins, but I was reading you're post and was wondering what the heck you were talking about..lol

Then again, maybe someone does know in here, but you chances are better there

 

[beezie42]

Anybody know how i could change the iso? Not delete it but possible change the iso file so it autoboots something different?