yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 Q&A, Help & Troubleshooting] DavidinCT:
Nothing yet :(

Nokia said something about their users getting it in a few weeks but, it was pulled back and though it was going to be Tango. No one is sure on that.

I bet we get it from here (XDA) before we get the offical one. I want it on my custom rom :)
[Windows Phone 7 Q&A, Help & Troubleshooting] boudhayan:
Yes all existing windows phone device will get windows phone 7.8 according to microsoft.
[HTC Sensation] Mesaman2012:
By chance does anyone know when a final stable Rom will be done for cm9 nightlies. :)
[HTC Sensation] Pvt WhoOkid:
No eta and this is the dev section.....
[HTC Sensation] k0zmic:
First rule of CM is don't ask for ETA's.
[HTC Sensation] Flashmaniac:
Wrong section plus you will never see a finale Version.
[HTC Sensation] Mesaman2012:
I

Wasn't sure what section it went in but now I do.and the reason I asked the qwestion was because usually everyday they had a update out but the last one was on the 21st.sorry for all the confusion I just haven't been able to get a hold of my cm9 tech authority.
[Sprint HTC EVO 4G LTE] kronemerk:
Although Anandtech has not yet reviewed the LTE EVO, most of the battery and performance benchmark tables in their recent review of the Gallaxy S III have results for the EVO included in the table. See here:

http://www.anandtech.com/show/6022/samsung-galaxy-s-iii-review-att-and-tmobile-usa-variants/3
[Sprint HTC EVO 4G LTE] sgt. slaughter:
What I dont understand is how the ATT OneX varied in the WiFi battery test compared to our ELTE....almost 2hrs better...
[Sprint HTC EVO 4G LTE] DarkManX4lf:
It looks like the Evo 4g lte isnt much worse or better than the SGS3. Pretty much expected that.
[Sprint HTC EVO 4G LTE] supers2k:
I think it's because they have a updated radio 1.75 to 1.85 while the Elte hasn't had any updates to its radio or any software updates at all yet. Maybe
[Sprint HTC EVO 4G LTE] Saneless One:
While the cell radios aren't transmitting data, they're still on, waiting for texts and calls. I think GSM radios are more efficient than CDMA ones, so that could be part of it. Or maybe the Sprint signal just wasn't as good.

A more accurate test would have been to turn on the phones' airplane mode, then enable wifi, but since the test doesn't mention it it's very possible the cell radio was left on while doing the wifi test.
[Sprint HTC EVO 4G LTE] ckoadiyn:
I'd guess it's due to they have got updates on their radios and software.
[Sprint HTC EVO 4G LTE] lamenramen:
Anandtech, while clearly, CLEARLY, the best review site available on the internet, has always posted battery life claims on their laptops and smartphones that I never get in the real world.

I take them to be relative comparisons under standardized test conditions, but not real world test conditions.

In other words, do I think that I could browse over 3G for 6 hours? Unequivocally not, which is what their test results show. I've got an international HTC One X and under no circumstances can I ever get 7 hours of 3G web surfing as their graphs show.

What I take the results to mean is that the EVO 4G LTE is among the most battery efficient smartphones out there right now. In other words, if anyone has a problem with the battery life (raises hand), they would have a problem with all smartphones' battery life.
[Sprint HTC EVO 4G LTE] fastmikey1969:
The sprint phones always seem to lag behind their gsm counterparts. I remember that was the case with my Epic 4G.
[Sprint HTC EVO 4G LTE] sgt. slaughter:
while pulling your main data over the wifi test i have a hard time believing that the gsm radio yields almost 2hr better when its not being used hardly at all....if it was doing the 3G data battery test then maybe, but not during the wifi one...
[Galaxy S III Q&A, Help & Troubleshooting] Geoff.Costello:
Hi :)

For some reason I am now getting a Driver Installation Failure error for my S3 when I plug it in to USB on Windows 7. The driver is SAMSUNG Mobile MTP Device, which fails after a long (3 minute or so) install attempt.

This means I can't access the Phone via USB for file tranfers etc, either Windows Explorer or Keis. Though I can use ODIN to Flash if I put the Phone in Debug Mode.

I have tried all sorts. Un-installing the Samsung Drivers, rebooting and reinstalling, and getting Kies to try a driver repair.

It wasn't like this when I started with the phone. Something changed - after I rooted it. I am currently on the Omega ROM 6.0 with standard kernel. For a while I was on 5.1 with Syloa 1.1 and then 1.26. I realized it was wrong when I couldn't copy Omega 6.0 ROM ZIP over to Flash.

I have searched and searched. This seems to have happened to other phones as well but be intermittent. A few other phone on XDA have reported this in the last couple of weeks (so maybe a Microsoft change to Windows 7?)

As a weird related issue sometimes when I plug the Phone into WIndows now I get two removable drives showing, which are "Samsung USB Gadgets" using a 2006 Microsoft Driver... They show as removable drives with no drive in them. Again all my tricks of disabling uninstalling, re-installing etc these seem to make no difference.

Anyway - any ideas / fixes help appreciated!!!

Cheers
[Galaxy S III Q&A, Help & Troubleshooting] rohan999:
So here is the cure. First connect your phone to your pc. Now right click my computer and select manage. Go to device manager and expand the universal serial bus controllers tab. Now you should see something like unknown device with a yellow exclamation mark. Right click it and select uninstall. Now reconnect your phone and try it.

Now again check in device manager after installation. It should look like the one in the attachment.
[Galaxy S III Q&A, Help & Troubleshooting] rizzo1001:
I've got the same issue; can't get the MTP drivers to work on my Win 7 machine or my work XP box. Both had the Galaxy nexus drivers on them previously (I think, came from ICS Captivate).
[Galaxy S III Q&A, Help & Troubleshooting] pruhster:
Are you sure USB debbuging is unchecked in settings?

If that's not the problem, you could try a different pc or os (a live ubunt cd for instance) to see whether it's the phone or the computer thats messed up.
[Galaxy S III Q&A, Help & Troubleshooting] rizzo1001:
Fresh windows 7 install and still nothing. Could the phone be messed up?
[Galaxy S III Q&A, Help & Troubleshooting] -NT:
Have you tried a different USB port?
[Galaxy S III Q&A, Help & Troubleshooting] rizzo1001:
Yeah tried all the ports/cables I've got lying around. In safe mode it will install everything okay but Kies still won't connect. :/
[Galaxy S III Q&A, Help & Troubleshooting] fredphoesh:
Same here!

I also have Omega ROM 6.0 but the problem started BEFORE Omega ROM.

Did you also back up your efs folder using SGS Toolkit 2.0?

I seem to have had the problem after flashing the "insecure image" which one has to do using the SGS Toolkit in order to backup efs.

Ive also uninstalled and reinstalled pretty much EVERYTHING, drivers, Kies, SGSToolkit etc...

I have 5 pc's at home. ALL of them cannot connect to my SGS3, and ALL could connect to my SGS2 a couple of days ago!

tx

Mark.

---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------

Thanks, but process does not work in this case. Not on 5 PC's in my house.

BTW Kies by WIFI seems to work, but it is obviously very limited...
[Galaxy S III Q&A, Help & Troubleshooting] rjnolberto83:
Try this

This worked for me follow link

tomshardware.com/forum/242140-44-device-refuses-installed-please
[Galaxy S III Q&A, Help & Troubleshooting] fredphoesh:
hi link does not work

it takes me to toms home page...
[Galaxy S III Q&A, Help & Troubleshooting] rjnolberto83:
To fix the problem, follow the next steps:*1) Go to http://www.microsoft.com/en-us/download/details.aspx?id=19153

2) Press the*Continue*button (Near the validation required button)*

3) Press the*Download*button (Near the genuine Microsoft software)*

4) In case that the download hasn't started automatically within 30 seconds, press the*Start Download*button.*

5) Save the file.*

6) Execute the file (Double click on the mouse's left button).*

7) Next -> Repair -> Repair -> Finish -> Choose "Yes" so the system restarts itself.*

That's it, now the MTP devices should work correctly.*
[Galaxy S III Q&A, Help & Troubleshooting] Ripper574:
I've got the same issue and this did not work.

Reinstalling windows fixed my problem.
[Galaxy S III Q&A, Help & Troubleshooting] fredphoesh:
cure is to wipe phone, dalvik, re-flash rom

Hi there

This may work in other situations, but I have found out what caused my MTP to start working again, and it is NOT the computer, it is the phone for 100% sure.

I had this issue on 5 PCs in my home, ALL of which worked fine with my SGS2.

I did a factory wipe, wiped dalvik, and re-installed Omega v6 rom, and it now works on all 5 computers.

I do not know why it started, but the thing I did before the problems started was to use SGSToolkit v2 to flash an "insecure image" so I could backup efs folder. I have a feeling it is related to this, but I do not know for sure, and the maker of that software says 20000 people have used his software without this issue, so it cannot be his software.

Anyhow, by reflashing omega, and wiping the phone, it now works.

Mark.
[Galaxy S III Q&A, Help & Troubleshooting] Geoff.Costello:
Worked for me too.. It was the phone.

Mark,

Thanks. I too had Omega 5.2.

I wanted to upgrade modems but found I couldn't connect via PC as I had lost Root.

I too downloaded Version 2.0 of the tool kit and downloaded the insecure kernel and flashed it.

After that I could not get any PC to recognise the phone.

I got Omega 6.0 on wirelessly

But connection problem remained.

So your full wipe worked. The phone is now behaving and connecting to any PC I try.

Thanks

Geoff
[Galaxy S III Q&A, Help & Troubleshooting] dougdragon:
Possibly the USB cable?

I ran into this issue as well. When I connected my phone to my (Win7Prof64) computer, the OS recognized and downloaded the drivers and my phone's directory came right up. When I tried the same the next day - I received the "unknown device" message. After about an hour of troubleshooting I learned something interesting - I was using a different USB cable than the one I received with my phone. I connected the USB cable I got with the phone and everything automagically worked again. The USB cable must use another wire that "regular" USB cables don't? Here's a chat with Samsung support regarding the cable:

Gavin: Yes, the USB cable supplied with the device is Samsung recommend and is the Original. So, we request you to use the USB which is supplied with the device.

Doug: will i damage the device at all if i use a different cable to simply charge the device?

Gavin: No, it will not damage the device while charging.

Gavin: But, it can face some issues in connecting in mass storage mode.

Hope this helps!
[Galaxy S III Q&A, Help & Troubleshooting] timebomb:
Here's what I found about about my problem.

Samsung Galaxy S3 does not like USB 3.0 ports on my laptop.

Plugged the phone into the USB 2.0 port and it worked perfect.

Hope this helps out some of you!
[Galaxy S III Q&A, Help & Troubleshooting] Vytookas:
The same device on Win7 OK, on XP not.

4 me it happen after Android upgrade to ICS 4.0.4 but only on XP PC. Win7 found new drivers online automatically.

May be XP is to old 4 ICS :(

One solution I found here: http://androidforums.com/4819200-post7.html however don't want to hard reset my device

Some body can try driver pack 4 all phones here: http://www.mobiledit.com/downloads.htm?show=14
[Galaxy S III Q&A, Help & Troubleshooting] Nnyan:
I had this happen on occasion in the past and just now (moved to new laptop). What I have done that works for me is that you open up the details (where it says that it's installing your device click here for more details) and let it find/install all the drivers. Eventually it will fail with the MTP driver, KEEP that window open. Now unplug the usb cable FROM YOUR PC (don't ask me why but this works 100% from the phone side not always) and then plug in again. You'll see the MTP driver search start again and this time it should install.
[Galaxy S III Q&A, Help & Troubleshooting] drdionysius:
FIX

1. Download and install the s3 Toolkit here: http://xdaforums.com/showthread.php?t=1703488

2. Don't run it but browse to \Samsung Galaxy S3 ToolKit\drivers

3. Run USBDeview and uninstall everything with Samsung or i9300 in the description (right-mouse)

4. uninstall Kies and USB drivers.

5. Disconnect phone

6. Install \Samsung Galaxy S3 ToolKit\drivers\Samsung_USB_Driver.exe

7. Connect phone.

Tadah!
[Galaxy S III Q&A, Help & Troubleshooting] khaledelfeki:
Solution

Here is the only solution that could resolve the problem for me after days and days of trials and errors.

Just go to device manager and manually install the driver after selecting it from the already available drivers.

over and done.
[Galaxy S III Q&A, Help & Troubleshooting] surendra_aggarwal:
MTP Driver failure

I have been having this issue since I bought this phone 2 weeks ago when I down loaded and installed Kies v2.3. This is what I did and finally met with success in resolving Samsung MTP USB driver failure.

Deleted driver from Control Panel/system/device driver, removed Kies,left Samsung S3 phone connected and rebooted PC. Windows installed the driver and phone showed up in Explorer as a device - with correct name. I could access the phone and all the files on the phone. I then reinstalled Kies (latest 2.5) and isaw nstallation process installing USB drivers on top of Windows drivers. Installation again reported failure in installation of MTP driver.

Followed thru the steps again- uninstalled Kies, uninstalled driver, left phone conneted and rebooted PC. Once again Windows installed the driver and it recognised the device.

This tiem I made a change. I downloaded Samsung Kies v1.0 for Windows 7 64 bit (my PC is 64 bit). Installed it on PC. Wow - Kies now is able to connect to my Samsung S3 Phone. "Now this is crucial what happened next."

Kies then went to upgrade Kies to v2.5 - NO DRIVER UPDATE. I thinkbecause his is a software not device drivers upgrade. All finally good. It synced my phone with Outlook.

So the analysis is : The device driver in later versions of Kies was added and it is "wrong & incompatibel with Windows 7". Simply put the whole thing "simply sucks". Samsung should have done this analysis by themselves and fixed it. Looking at other posts on other forums, Samsung is aware of this issue for a few months now. But is failing to do fix it - just remove its own drivers and use Windows drivers.

The Kies 1.0 does not installs any driver (didn't see any message) and uses Windows driver. Hence it works. Kies later versions have usb driver whichoverwrite Windows driver and this is the ROOT CAUSE of PROBLEMS.

Hope this help all the users everywhere!!!!

ALL Samsung Usrs - please uninstall Kies later versions, and after lettin

--------------------------------------------------------------------------
[Galaxy S III Q&A, Help & Troubleshooting] k288:
Hi there, I am having the USB problem for a couple weeks and it was working fine before all along. I am using Windows 7, how do I exactly remove the Samsung driver in the Control Panel? I do not see any Samsung item listed there. I have tried many uninstall and install and on different pcs. so really hoping your fix can fix mine as well.

By the way, I had removed Kies many times and yet Windows did not detect the S3 or install any driver, so the drives are not showing up in Explorer...

thanks

Thanks
[Galaxy S III Q&A, Help & Troubleshooting] fifamaniac:
Doesnt work for mee...

Weird because at home on my laptop it works...

Thanx anyway
[Galaxy S III Q&A, Help & Troubleshooting] play-doh:
Try opening Regedit and deleting UpperFilters entries from the following Keys if they exist.

- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}

- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{EEC5AD98-8080-425f-922A-DABF3DE3F69A}

disconnect your Phone if it is connected and reconnect it. Drivers should install correctly.
[Galaxy S III Q&A, Help & Troubleshooting] bbayless:
Please Help

Hey I have tried to resolve this issue with the solution but it still does not work. I dont shave the upperfilters in my regedit either.

thanks

QUOTE=play-doh;34421478]Try opening Regedit and deleting UpperFilters entries from the following Keys if they exist.

- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}

- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{EEC5AD98-8080-425f-922A-DABF3DE3F69A}

disconnect your Phone if it is connected and reconnect it. Drivers should install correctly.[/QUOTE]
[Galaxy S III Q&A, Help & Troubleshooting] farrukh494:
I was getting the same problem. Just replace the usb cable and it might fix. Worked for. Me
[Galaxy S III Q&A, Help & Troubleshooting] jezzabart:
Thank you very much for this suggestion. I spent days trying to connect and was starting to think that I would have to reinstall Windows. Finally, I changed from the Samsung provided USB cable to the one that came with my Kindle Keyboard and it has worked perfectly ever since.
[Galaxy S III Q&A, Help & Troubleshooting] Israelleite:
Solved! For real!

For some reason, any of those options helped me to make it work:

- Reinstall Windows Media Player

- Remove registry key

- Clean up old usb drivers

- re-install 100 times drivers from Verizon, Samsung. Even old versions.

- Install from Windows Update. I tried to do that 1000 times. Gosh!

- enable UMT access (mass storage) on the phone.

The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.

Windows 7 x64

Attached the files. Go to the devices manager and update the drivers.

Israel Leite
[Galaxy S III Q&A, Help & Troubleshooting] rojogan:
I've been having the same problem with my Galaxy Note. Tried this and it worked, at least so far. Thanks for the tip.
[Galaxy S III Q&A, Help & Troubleshooting] dakunclear:
Originally Posted by rohan999

So here is the cure. First connect your phone to your pc. Now right click my computer and select manage. Go to device manager and expand the universal serial bus controllers tab. Now you should see something like unknown device with a yellow exclamation mark. Right click it and select uninstall. Now reconnect your phone and try it.

Now again check in device manager after installation. It should look like the one in the attachment.

I did most of everything that you told but you can see samsung blah blah in there uninstall that in device manager by right clicking it you will see this option and then just execute the file and it will make you restart your computer and bam problem fixed....this method works for the Samsung galaxy note 2 as well for anyone who has one of those phones.

so follow through everything except step six will be you uninstalling in drivers that are on the computer for your Samsung device with device manager, then install that thing he told you just follow it through then type in windows update in your windows search and looking for updates there should be one that comes up with Samsung blah blah MTP install that then restart the computer and your good to go.
[Galaxy S III Q&A, Help & Troubleshooting] kayamemet:
I have tried lots of things and nothing worked until now. Thanks a lot, much appreciated!! :good:
[Galaxy S III Q&A, Help & Troubleshooting] dakunclear:
Best thing I tried is I went up to my computer and smashed it to bits then I bought a new custom built one and it works fine
[Galaxy S III Q&A, Help & Troubleshooting] GR0S:
Kies is broken (at least it was)

Try uninstalling samusng drivers and remove device via usbdeview, then plug phone. Windows should use generic ones now
[Galaxy S III Q&A, Help & Troubleshooting] romanegloo:
Thanks. This solved the issue in my case. My phone was plugged into a USB hub. Once I connected it to my pc directly, it worked. :laugh:
[Galaxy S III Q&A, Help & Troubleshooting] Homeuser66:
I'm not sure if you got this issue resolved or not yet...but I installed SAMSUNG KIES and it resolve the issue completely for me...

Hope this helps!
[Galaxy S III Q&A, Help & Troubleshooting] MaxQuiro:
Deam u are good!!!!

DEAM MAN!!!, you finally found the fuc...nnn answer, I'm really Happy, u are the best. Thanke you MAN! My respects for U.... MASTER !!!
[Galaxy S III Q&A, Help & Troubleshooting] wickedmx:
I ran into this issue and tried all of the suggestion I could find(including this one), none of which worked. Eventually I got it working again for my Galaxy S3 by doing the following:

1) Plugged phone in and let MTP install end with failed installation notification

2) opened Windows Update and forced a check for updates

3) this returned an update for Samsung MTP Devices

4) installed Windows update

5) unplugged phone and then plugged back in

6 Voila, drivers installed with no issues
[Galaxy S III Q&A, Help & Troubleshooting] hapa8o8:
:good::good::good::good::good::good:

WOW!!! I was deleting the filters from the wrong registries (don't worry, they didn't cause any errors)

THANK YOU for posting the correct classes to delete the upfilters from. I have tried practically every way to get my phone back with my computer, and now it is all good :fingers-crossed::fingers-crossed::fingers-crossed:

THANK YOU again
[Galaxy S III Q&A, Help & Troubleshooting] ShutteN:
I have the same problem, I have tried every solution in this thread and even other solutions, I CAN'T fix it!? Someone help me :/?
[Galaxy S III Q&A, Help & Troubleshooting] m80116:
I can tell you what it was in my case. I had exactly the same symptoms, with MTP Device could not start (error code 10) on my Windows Vista 64bit OS. Was it Vista's fault, was it Galaxy's (I have a SGS II Plus) ? Nope... it was my fault for disabling the automatic startup of the MTP Application, seemingly useless startup item that could have been recalled by the system on first demand: hold off, that service is there to stay in the autorun at startup.

So if you like me have installed a Startup Manger and with Super User privileges started disabling system services, double check the the "MTP Application" service is left the way it's intended to be: autorun at startup.
[Galaxy S III Q&A, Help & Troubleshooting] lensman76:
Dont mean to revive an old thread unnecessarily, however I found the only thing that worked for me was something not mentioned here.

Apparently the 'Windows Driver Foundation - User-mode Driver Framework' service was incorrectly setup, however the fix involves using regedit to alter the registry settings for it.

Go to this reg key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wudfsvc\Parameters

there you should see a setting called 'ServiceDllUnloadOnStop' set it to 2 ie 0x00000002.

This fixed it for me, my Galaxy S2 and S4 now connect via MTP....

Good luck

:)
[Galaxy S III Q&A, Help & Troubleshooting] howardhb:
:o I too had disabled MTP Application in startup application manager (ES Task Manager) Doh!

(S5 G900H)
[Galaxy S III Q&A, Help & Troubleshooting] marco alexandre:
thanks , thanks , thanks.

It was the only thing that worked for me.

And I have really tried everything in the WEB - Google to make it work.

Was driving me nuts.
[Galaxy S III Q&A, Help & Troubleshooting] turbare:
Sorry for the necro, but this annyoing issue is still happening.

What fixed it for me was, disable the dev options in the phone, on plugin to PC make sure it's set as media device, and then try the steps above by Nnyan, that worked.

PS: Not original cable.