Vendor ID changed - Captivate General

Hi
I've got a strange problem: my Vendor ID has changed from original (Captivate) to this:
Code:
ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Seems because of this I can't connect my phone to the computer - it just doesn't see the device.
It began from an CM 11 reinstallation (weird, yep). IMEI changed too, but I've recovered it with an EFI backup.
But how to deal with this problem? Maybe there's an backup that someone could give me and it will help?
Here's the part of syslog
Code:
Jan 16 00:37:49 blacky-PC kernel: [252350.767430] usb 2-1.4: New USB device found, idVendor=04e8, idProduct=685e
Jan 16 00:37:49 blacky-PC kernel: [252350.767441] usb 2-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jan 16 00:37:49 blacky-PC kernel: [252350.767447] usb 2-1.4: Product: SGH-I897
Jan 16 00:37:49 blacky-PC kernel: [252350.767453] usb 2-1.4: Manufacturer: samsung
Jan 16 00:37:49 blacky-PC kernel: [252350.775814] usb 2-1.4: can't set config #1, error -71
You see that idProduct 685e isn't valid, it's Galaxy SII's one!

I don't understand anything
It's just bout the USB cable! Changed it - all works well

I was hoping you had found a different cause and solution.
I bricked my Captivate two years ago, I was running CM7 at the time, and used that as a reason to buy a SGS3.
About a year ago I revisited my Cappy hoping to revive it as a backup device. I was able to bring it back to life and installed a stock ROM, and immediately installed CM10.1 and have since updated to 10.2.1. I am using as a it as a media player and GPS sports tracker. Since I am not using it as a phone I have never installed a SIM, AT&T took the old one when I activated the S3. Because of the lack of sim I have no mobile network nor network and have not been concerned. My IMEI has never changed, fortunately.
One thing I did notice was a change in vendor ID and device type when connected to my PC.
Code:
[email protected] ~ $ lsusb
Bus 005 Device 002: ID 18d1:4e22 Google Inc. Nexus S (debug)
I wouldn't mind having a Nexus device, but my Captivate still looks and runs like a Captivate. ;-D
I haven't been too concerned about this anomoly since I haven't been using it as a phone. I have mostly thought it was something in the install script for the ROM that was not correctly set by the dev who ported this to the Captivate. I guess I will find out if it is an issue if I ever purchase a sim to use it as a phone, or if I try to change ROMs.

You know, I don't care very much about this issue now, 'cause after USB cable replacement I finally can connect Cappy to the PC and the connection works fine (ADB, file transfer, etc). Cellular functionality had never disappeared, so here's no problem too.
I was just associating my problems with Cappy<->PC connectivity exactly with that Device ID change. Why? I don't know, but there was the only reason I could imagine.
Now it's even funny to see smth like
ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
Click to expand...
Click to collapse
having just Cappy. It's very optimistic from my Linux's side

Related

[Q] USB Host OTG Hack?

Would it be possible to hack the infuse to support USB OTG? The SGS II is already factory supported and I was wondering if there was any way to implement that feature into the infuse for the use of external memory, USB keyboards/mice/headsets, etc. I also know that someone already hacked the Nexus One to support this. Also, would the HDMI out tell us if its supported (Since the phone is sending an image to a TV screen?)
Nothing at all?
Just wanted to give this a nudge up towards the top. Is this something that could be added via rom/kernel or does it have to be supported in hardware? Really interested in if this is possible given the recent release of DSLR Controller.
Do have any other first-gen SGS phones been modded to support it?
If so, it might be possible to get these mods implemented in our kernels - point me to a kernel for a first-gen SGS phone (NOT an SGSII) with this capability and I'll look at it.
Our hardware is fairly similar to the original SGS series, so a lot of things that work on those phones will work on ours. The SGSII is VERY different so backporting features like this is unlikely due to lack of hardware support.
Entropy512 said:
Do have any other first-gen SGS phones been modded to support it?
If so, it might be possible to get these mods implemented in our kernels - point me to a kernel for a first-gen SGS phone (NOT an SGSII) with this capability and I'll look at it.
Our hardware is fairly similar to the original SGS series, so a lot of things that work on those phones will work on ours. The SGSII is VERY different so backporting features like this is unlikely due to lack of hardware support.
Click to expand...
Click to collapse
Thanks for the reply. I'll keep an eye out and see if support gets added to any of the SGS phones, sadly for right now all I know of is support on the SGS2 and possibly on the Nexus S.
dotpkmdot said:
Thanks for the reply. I'll keep an eye out and see if support gets added to any of the SGS phones, sadly for right now all I know of is support on the SGS2 and possibly on the Nexus S.
Click to expand...
Click to collapse
Nexus S hacks MIGHT be bringable to our phones - but far less likely than GS phones.
USB OTG mode is initiated by shorting USB pins 4 and 5. The phone can do it hardware wise. It's a matter of having the drivers for the accessory connected.
You don't just "have" OTG capabilities... It's a matter of what devices you support.
This would not be something which would occur at the device level. The hardware is connected to the phone, the phone runs Linux. Linux handles connections of the devices. Grab kernel modules from Linux for OTG devices.
If thats the case it would seem odd that so many developers work towards adding the support to phones.
The SGS2 doesn't have drivers built in to support connecting to canon DSLR's yet its the only phone at this point to officially support it... because it supports USB Host OTG mode.
AdamOutler said:
USB OTG mode is initiated by shorting USB pins 4 and 5. The phone can do it hardware wise. It's a matter of having the drivers for the accessory connected.
You don't just "have" OTG capabilities... It's a matter of what devices you support.
This would not be something which would occur at the device level. The hardware is connected to the phone, the phone runs Linux. Linux handles connections of the devices. Grab kernel modules from Linux for OTG devices.
Click to expand...
Click to collapse
dotpkmdot said:
If thats the case it would seem odd that so many developers work towards adding the support to phones.
The SGS2 doesn't have drivers built in to support connecting to canon DSLR's yet its the only phone at this point to officially support it... because it supports USB Host OTG mode.
Click to expand...
Click to collapse
Check out the GalaxyS hack pack for the USB chip. I can verify that the kernel knows when something OTG is connected. It brings up UART messages and you can see it in dmesg.
here you go... here's the relevant dmesg output from my device right now.
Code:
<4>[11037.766990] fsa9480_interrupt
<4>[11037.767292] [FSA9480] FSA9480_ReadIntRegister
<6>[11037.815966] ldo38_control : turn ON LDO3 and LDO8 (cur_stat=0, req=1)
<4>[11037.816113] [otg_clock_enable] clk_enable(otg_clock) OK.
<4>[11037.829314] FSA9480_ProcessDevice function!!!!
<4>[11037.829428] [FSA9480]FSA INTR = dev1 : 0x80, dev2 : 0x0 , Attach : 0x1
<4>[11037.829528] USB OTG
The last dmesg log was with no device attached. Here's with a USB Flash drive attached.
Here's one with a flash drive plugged into my little test setup.
Code:
<4>[12679.047442] maxim_vac_connect: disconnect status skip
<4>[12679.210991] fsa9480_interrupt
<4>[12679.211262] [FSA9480] FSA9480_ReadIntRegister
<6>[12679.266909] ldo38_control : turn ON LDO3 and LDO8 (cur_stat=0, req=1)
<4>[12679.267071] [otg_clock_enable] clk_enable(otg_clock) OK.
<4>[12679.280247] FSA9480_ProcessDevice function!!!!
<4>[12679.280375] [FSA9480]FSA INTR = dev1 : 0x80, dev2 : 0x0 , Attach : 0x1
<4>[12679.280476] USB OTG
<4>[12682.348957] [email protected] Total=32768bytes PrdSz=2048 #Prds=4, dmaEnd 0x4f168000
<7>[12682.442657] touch_led_control: 1
<4>[12682.929923] xrun: occurred buffer xrun[0]
<7>[12685.436920] touch_led_control: 2
<4>[12690.544885] [TSP] TA NON-Detect!!!
<6>[12690.559635] [BAT]:Vol=3893, Temp=330, SOC=63, Lv=63, ST=0, TT=0, CS=0, CE=0, RC=0, FC=0, Hlth=1, DS=0x800, VF=590
it does not create any new devices.
Right now USB host is not compiled in the kernel at all, so I'd expect this.
That's why I was asking if someone had found an example of a first-gen SGS with USB Host/OTG support compiled in. With an example kernel's defconfig and source I can analyze, it shouldn't be TOO hard to port that functionality to our device.
The current state is: FSA9480 tells the kernel that an OTG device is connected, kernel says "I dunno what that is. I'll give up and do nothing."
Usb otg through micro dongle
I think you people should try for this. I think it will work for ur device.
www.tombom.co.uk/blog/?p=124
vishal24387 said:
I think you people should try for this. I think it will work for ur device.
www.tombom.co.uk/blog/?p=124
Click to expand...
Click to collapse
No, it won't. See the posts above - there are software components missing.
Again - if someone can point me to an example of a kernel where host mode is working on a first-gen GalaxyS device, I'll try to port it over. I'm not going to try and backport anything from a GSII.
Convincing the FSA9480 to signal host mode is only a tiny piece of the puzzle - see HDMI on Rogers Gingerbread as an example.
would these help entropy?
http://forum.xda-developers.com/showthread.php?t=1450298
http://forum.xda-developers.com/showthread.php?t=1468531
this is an old thread. but things have changed since then. its been successfully integrated into the galaxy s and nexus s. hopefully it will result in a port since its atleast plausible now.
been awhile since this has been looked at, was wondering if anyone had any luck with this, would be greatly appreciated if i got any kind of response

[Q] Bluetooth RFCOMM fix?

*Posted in the wrong forum initially so asking again in the right one now*
Yes, I admit I am a noob, and I'm going to guess there should be an obvious answer but I'm not finding it. I switched to my Galaxy S 4G after my Crackberry died, but I had gotten an InPulse watch for the Blackberry to keep me alerted to critical messages at work (I work in a children's hospital, and the nurses in the Neonatal ICU tend to get mad when one's ringtone causes all the babies heart-rates to jump at the same time....)
I have discovered that the watch needs RFCOMM to communicate properly, which from what I can tell the Galaxy does not implement correctly if at all. What I could use help understanding is do any of these ROM's have a fix that allows devices that need RFCOMM to work properly? I can see all sorts of builds out there for the Galaxy S, but it isn't clear if they can help fix this issue or if they will work for my specific model (the 4G variant) If they all do then I apologize for the really stupid question and you may berate me as you see fit.
Here is the specifics for my phone
Carrier : T-Mobile
Manufacturer : Samsung (obviously for this forum)
Model : Galaxy S 4G (SGH-T959V)
Firmware : 2.2.1
Baseband : T959VUVKD1
Kernel : 2.6.32.9
Build : FROYO.VUVKD1
Thanks for the help, I'm new to the Android.

Broken screen

Hello there!
I have an HTC one S, the beats audio one.
The only problem is that the screen and the glass are completely broken, so the screen is always black.
I don't know if it is working or not.
if i connect trought usb and I launch lsusb command, this is the output:
Code:
Bus 003 Device 002: ID 13fe:1a00 Kingston Technology Company Inc. 512MB/1GB Flash Drive
Bus 003 Device 004: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
So it is recognise, but I can't mount it, the red led on top is always on.
If i press volume up or down, I hear a sound.
So, based on my opinion, it is working, what do you think?
also, do you know how to repair it? and where I can buy online a repair kit?
Thanks everybody in advance.
http://www.youtube.com/watch?v=b0jGY2N2h1U&feature=youtu.be
video for you to decide if you want to try. If it is under warranty I would send it back.
Yeah! Already see it, in your opinion,the phone is working? And where I can buy at the Best price a screen with glass?
Sent from my LG-P500 using xda app-developers app
Ya, I think it is working. I don't know anything about replacing a screen. Maybe someone more knowledgeable will read this thread and respond. Good luck to ya.
Someone know how much Will htc charge me for a screen replacement?
Sent from my LG-P500 using xda app-developers app
I change the screen on galaxy S2 and was easy, but the One S is more complicated. The screen will cost you from $140 to $180. If you decided to buy new screen, buy with bezel(frame). That way you will not have to mess with adhesive - just put the board back and hook up connectors. It is not for everyone. Cost of repair could be more that working phone from Swappa or Craighlist. I would just get another and keep this one for spare in case you brick it.
Thanks everybody, i called htc costumer Service, and they tell me that the repair cost will be more or less 170 €
Sent from my LG-P500 using xda app-developers app

[Q] Is anybody using OTG connected CDC-ACM driver to get internet?

Hello everybody!
There are some people talking about using external USB dongle on non-3G version of NEXUS-7 or -10 through PPP protocol. but until now, It seems that nobody is talking about using CDC-ACM to connect an old phone to the internet.
I am simply curious of Howto, because according to the experience I got from openwrt platform, old phone like Nokia E series, acting as ACM device under Linux, is even easier to use to get internet occasionally. it needs no PPP dialing part. I think a lot of people still keep a old Nokia phone(it is not so easy to break them right?), for those Pads without 3G module, I believe using CDC-ACM class driver is quite handy.
I would really appreciate any information you give!

Hannspad SN1AT74 - Ethernet and Cloning

Hi all,
I have a two Hannspad SN1AT74, one a little older one, the other is new.
When I attach a ethernet adapter using a USB OTG cable it will work on the "old" one (Build Number 2014...).
I can see ethernet settings in the Settings screen.
But... this functionality is not supported in the new one (Build 2015*), here is no ethernet supported!
The support department of the manufacturer told me, that the first version is a special version for a project which was not released officially
Android version is 4.4.2 on both tablets.
Is there any possiblity to create an image from the old tablet and put it 1:1 onto the new tablet?
I'm an absolutely newbie in Android, so have to begin from scratch
Thanks
Wrzlbrnft
wrzlbrnft said:
Hi all,
I have a two Hannspad SN1AT74, one a little older one, the other is new.
When I attach a ethernet adapter using a USB OTG cable it will work on the "old" one (Build Number 2014...).
I can see ethernet settings in the Settings screen.
But... this functionality is not supported in the new one (Build 2015*), here is no ethernet supported!
The support department of the manufacturer told me, that the first version is a special version for a project which was not released officially
Android version is 4.4.2 on both tablets.
Is there any possiblity to create an image from the old tablet and put it 1:1 onto the new tablet?
I'm an absolutely newbie in Android, so have to begin from scratch
Thanks
Wrzlbrnft
Click to expand...
Click to collapse
Cloning should be possible. But is the hardware the same...

Categories

Resources