Issue with connecting to Wifi topic

This isn't a major issue, but I don't seem to be able to connect to a college's WPA2-PSK network. I can establish a connection, but I'm never able to access the Internet. I've gone through the login page, and yet it refuses to work properly. I didn't have any trouble connecting on my Nexus 7 and laptop, yet my MotoX has trouble.

I just recently upgraded to 4.4.2, using the Safestrap method. I'm obviously rooted. I can't think of any apps installed on my phone that aren't installed on my tablet that could be causing this issue. I don't know if its a 4.4.2 issue, because my GF has a MotoX (AT&T) and she's on 4.4, and has been connecting fine for months. I upgraded to 4.4.2 just two days ago... And this is the first time I've tried connecting to this type of network.


Any ideas? I appreciate any and all help.

[Q] connecting 3g data card in android 4.2 topic

Please help me in connecting my lava xtron+ which has android 4.2 ,am unable to connect my ZTE MF 190 .when I connect tab shows signal and data card shows connection light green,after that signal goes off in the tab ,but green still glows in the device but no net connectivity.

[Q] USB Not Connecting after CWM Installing topic

Hi Team,

I just rooted my phone with ODIN3 and Installed Super user with CWM Recovery


During installation in ODIN3, l Left tick in f.Reset Time my phone unlocked but i am not able to connect my Quottro to pc i am not able to copy or move files both ways

During Reboot of installing CWM Recovery it asked to keep or flash Flash Memory i selected NO

Before Install i was able to copy files to quattro and viceversa but now iam notable to copy


i followed steps in thread : http://forum.xda-developers.com/show....php?t=2494471


Details:

Model : Samsung grand Quottro i8552
Version : I8552XXAMH2
Hardware : Rev 7

Attached Thumbnails

 

Question about connecting to tv topic

My tv only has av slots, so how can I connect it to the TV to mirror it?

I already have an otg cable if I need it.

[Q] WiFi not connecting. topic

I have an Xperia Play. It is a UK model that has been unlocked. It is a dev model.

I am having problems connecting to WiFi. My brother (who gave it to me) says it was connecting in the UK. He bought over two of these phones niether of them will connect.

It wont list the available networks, thought it does scan. The mobile network/ internet is working fine.

Am I missing something?

Camera not connecting topic

I am running stock ROM and franco kernel and sometimes the camera doesn't connect, and I have to reboot to make it work. Here's the log...

--------- beginning of /dev/log/system
02-21 11:29:52.259 D/ConnectivityService(789): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
02-21 11:29:53.769 I/ActivityManager(789): Start proc com.viber.voip for broadcast com.viber.voip/com.viber.service.KeepAliveReceiver: pid=336 uid=10127 gids={50127, 3003, 1028, 1015, 3002, 3001}
02-21 11:29:59.209 W/ActivityManager(789): Unable to start service Intent { act=com.google.android.gms.analytics.service.START (has extras) } U=0: not found
02-21 11:30:00.369 W/InputMethodManagerService(789): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@6625f618 attribute=null, token = android.os.BinderProxy@66066c68
02-21 11:30:00.409 W/InputMethodManagerService(789): Ignoring showInputMethodPickerFromClient of uid 1000: com.android.internal.view.IInputMethodClient$Stub$ Proxy@66ba2c90
02-21 11:30:01.039 I/ActivityManager(789): Start proc com.google.android.deskclock for broadcast com.google.android.deskclock/com.android.alarmclock.DigitalAppWidgetProvider: pid=483 uid=10033 gids={50033, 1028}
02-21 11:30:01.789 W/InputMethodManagerService(789): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@65fd19f8 attribute=null, token = android.os.BinderProxy@66066c68
02-21 11:30:01.789 V/InputMethodManagerService(789): Adding window token: android.os.Binder@668613b8
02-21 11:30:02.819 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:02.819 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:04.009 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:04.009 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:04.219 W/ActivityManager(789): Unable to start service Intent { act=com.google.android.gms.analytics.service.START (has extras) } U=0: not found
02-21 11:30:09.439 I/ActivityManager(789): Waited long enough for: ServiceRecord{65ebe4a0 u0 com.viber.voip/com.viber.service.VoipConnectorService}
02-21 11:30:09.509 I/ActivityManager(789): Waited long enough for: ServiceRecord{66070508 u0 com.viber.voip/.api.billing.InAppBillingService}
02-21 11:30:24.059 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:24.059 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:30.309 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:30.309 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:34.699 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:34.699 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:35.949 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:35.949 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:40.019 W/InputMethodManagerService(789): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@6628ec90 attribute=android.view.inputmethod.EditorInfo@664a beb0, token = android.os.BinderProxy@66066c68
02-21 11:30:41.409 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:41.409 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:41.459 W/ActivityManager(789): Exception when unbinding service com.android.chrome/org.chromium.content.app.SandboxedProcessService1
02-21 11:30:41.459 W/ActivityManager(789): android.os.TransactionTooLargeException
02-21 11:30:41.459 W/ActivityManager(789): at android.os.BinderProxy.transact(Native Method)
02-21 11:30:41.459 W/ActivityManager(789): at android.app.ApplicationThreadProxy.scheduleUnbindS ervice(ApplicationThreadNative.java:874)
02-21 11:30:41.459 W/ActivityManager(789): at com.android.server.am.ActiveServices.removeConnect ionLocked(ActiveServices.java:1713)
02-21 11:30:41.459 W/ActivityManager(789): at com.android.server.am.ActiveServices.unbindService Locked(ActiveServices.java:860)
02-21 11:30:41.459 W/ActivityManager(789): at com.android.server.am.ActivityManagerService.unbin dService(ActivityManagerService.java:12771)
02-21 11:30:41.459 W/ActivityManager(789): at android.app.ActivityManagerNative.onTransact(Activ ityManagerNative.java:869)
02-21 11:30:41.459 W/ActivityManager(789): at com.android.server.am.ActivityManagerService.onTra nsact(ActivityManagerService.java:2071)
02-21 11:30:41.459 W/ActivityManager(789): at android.os.Binder.execTransact(Binder.java:404)
02-21 11:30:41.469 I/ActivityManager(789): Process com.android.chrome:sandboxed_process1 (pid 31553) has died.
02-21 11:30:41.789 I/ActivityManager(789): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.google.android.googlequicksearchbox/com.google.android.launcher.GEL} from pid 789
02-21 11:30:44.809 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:44.819 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:45.269 I/ActivityManager(789): Delay finish: com.android.chrome/com.google.android.apps.chrome.snapshot.gcm.GcmRec eiver$Receiver
02-21 11:30:45.279 I/ActivityManager(789): Resuming delayed broadcast
02-21 11:30:45.289 I/ActivityManager(789): Delay finish: com.android.chrome/com.google.android.apps.chrome.snapshot.gcm.GcmRec eiver$Receiver
02-21 11:30:45.289 I/ActivityManager(789): Resuming delayed broadcast
02-21 11:30:45.689 D/ConnectivityService(789): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
02-21 11:30:45.949 I/PowerManagerService(789): Going to sleep by user request...
02-21 11:30:46.829 E/NotificationService(789): Not posting notification with icon==0: Notification(pri=2 contentView=null vibrate=null sound=null defaults=0x0 flags=0x1 kind=[null])
02-21 11:30:46.829 E/NotificationService(789): WARNING: In a future release this will crash the app: com.rageconsulting.android.lightflowlite
02-21 11:30:46.869 E/NotificationService(789): Not posting notification with icon==0: Notification(pri=2 contentView=null vibrate=null sound=null defaults=0x0 flags=0x1 kind=[null])
02-21 11:30:46.869 E/NotificationService(789): WARNING: In a future release this will crash the app: com.rageconsulting.android.lightflowlite
02-21 11:30:50.979 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:50.979 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:53.119 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:53.119 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:30:57.294 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:30:57.294 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:31:28.624 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:31:28.634 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:31:32.510 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:31:32.520 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:31:40.514 E/NotificationService(789): Not posting notification with icon==0: Notification(pri=2 contentView=null vibrate=null sound=null defaults=0x0 flags=0x1 kind=[null])
02-21 11:31:40.514 E/NotificationService(789): WARNING: In a future release this will crash the app: com.rageconsulting.android.lightflowlite
02-21 11:31:40.514 E/NotificationService(789): Not posting notification with icon==0: Notification(pri=2 contentView=null vibrate=null sound=null defaults=0x0 flags=0x1 kind=[null])
02-21 11:31:40.514 E/NotificationService(789): WARNING: In a future release this will crash the app: com.rageconsulting.android.lightflowlite
02-21 11:32:48.414 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:32:48.414 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:32:49.564 I/ActivityManager(789): Delay finish: com.android.chrome/com.google.ipc.invalidation.external.client.contri b.MultiplexingGcmListener$GCMReceiver
02-21 11:32:49.564 I/ActivityManager(789): Resuming delayed broadcast
02-21 11:32:50.024 D/ConnectivityService(789): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
02-21 11:32:54.305 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:32:54.315 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:33:15.116 I/PowerManagerService(789): Waking up from sleep...
02-21 11:33:15.146 I/WindowManager(789): Lock screen displayed!
02-21 11:33:15.986 W/InputMethodManagerService(789): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@6679de60 attribute=android.view.inputmethod.EditorInfo@666f e118, token = android.os.BinderProxy@660fcf70
02-21 11:33:17.506 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:33:17.506 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:33:19.976 W/InputMethodManagerService(789): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@663ddf08 attribute=null, token = android.os.BinderProxy@660fcf70
02-21 11:33:21.406 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:33:21.406 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:33:24.616 I/ActivityManager(789): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=pt.sapo.mobile.android.newsstand/.Newsstand bnds=[57,519][291,781]} from pid 1179
02-21 11:33:24.646 I/ActivityManager(789): Start proc pt.sapo.mobile.android.newsstand for activity pt.sapo.mobile.android.newsstand/.Newsstand: pid=1140 uid=10145 gids={50145, 3003, 1028, 1015}
02-21 11:33:26.866 D/MobileDataStateTracker(789): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
02-21 11:33:26.866 D/MobileDataStateTracker(789): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
02-21 11:33:27.166 I/ActivityManager(789): START u0 {flg=0x20000 cmp=pt.sapo.mobile.android.newsstand/.activity.CoversPreviewActivity} from pid 1140
02-21 11:33:29.536 D/MobileDataStateTracker(789): default: setPolicyDataEnable(enabled=true)
02-21 11:33:30.016 W/InputMethodManagerService(789): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@66118050 attribute=null, token = android.os.BinderProxy@65aa2aa0
02-21 11:33:32.566 D/MobileDataStateTracker(789): default: setPolicyDataEnable(enabled=true)
02-21 11:33:33.296 W/InputMethodManagerService(789): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@66

Enviado do meu Nexus 5 através de Tapatalk

[Q] Problem connecting to network after aborted root topic

Hi I'm looking for help with my i9300. I had an aborted root, the phone froze during root and eventually I had to restart, I was able to re-install the stock ROM and the phone seems to work fine, apart from one major problem: It won't recognise any mobile networks. The phone won't recognise my network (3), or simcards from any other network. I have re-entered the APN information manually, but this has made no difference.

All other aspects of the device work fine, wifi, apps etc.

I'd appreciate any advice on steps I can take to resolve this.

I have obviously tried standard stuff such as full factory reset.

The phone still displays coverage bars as if it was connected to a network, but when I try to dial out or send messages I get an error message "unable to register on network"

Re: issue when connecting with vpn client topic

1. Uninstall your Cisco VPN Client.
2. Download and Install the file WinFix ftp://files.citrix.com/winfix.exe 3. Reboot the computer.
4. Install the DNE Update

ftp://files.citrix.com/dneupdate.msi for 32-bit ftp://files.citrix.com/dneupdate64.msi for 64-bit 5. Install your Cisco VPN Client

6. Restart Computer

On Monday, June 8, 2009 1:45:35 PM UTC+5:45, Steffen Brandsborg Jensen wrote:
> Hello all,
>
> Im getting an 442: Failed to enable Virtual Adapter.error when im trying to
> connect using my cisco vpn cilent..
>
> Does anyone have an advice on this issue?
>
> My log is:
>
> Cisco Systems VPN Client Version 5.0.05.0290
> Copyright (C) 1998-2009 Cisco Systems, Inc. All Rights Reserved.
> Client Type(s): Windows, WinNT
> Running on: 6.0.6001 Service Pack 1
>
> 44 09:53:39.552 06/08/09 Sev=Warning/2 CVPND/0xE3400003
> Function RegisterPrivateInterface failed with an error code of
> 0x00000000(DRVIFACE:3212)
>
> 45 09:53:39.552 06/08/09 Sev=Warning/2 CM/0xE3100008
> Failed to register private (virtual adapter) interface
>
> 46 09:53:39.755 06/08/09 Sev=Warning/2 CVPND/0xA3400015
> Error with call to IpHlpApi.DLL: CheckUpVASettings: Found IPADDR entry
> addr=10.4.1.158, error 0
>
> 47 09:53:40.769 06/08/09 Sev=Warning/2 CVPND/0xA3400015
> Error with call to IpHlpApi.DLL: CleanUpVASettings: Was able to delete all
> VA settings after all, error 0
>
> 48 09:53:41.580 06/08/09 Sev=Warning/2 IKE/0xE300009B
> Failed to active IPSec SA: Unable to enable Virtual Adapter
> (NavigatorQM:936)
>
> 49 09:53:41.580 06/08/09 Sev=Warning/2 IKE/0xE30000A7
> Unexpected SW error occurred while processing Quick Mode
> negotiator:(Navigator:2263)
>
> 50 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 51 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 52 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 53 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 54 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 55 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 56 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 57 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 58 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 59 09:53:41.580 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 60 09:57:03.678 06/08/09 Sev=Warning/2 CVPND/0xE3400003
> Function RegisterPrivateInterface failed with an error code of
> 0x00000000(DRVIFACE:3212)
>
> 61 09:57:03.678 06/08/09 Sev=Warning/2 CM/0xE3100008
> Failed to register private (virtual adapter) interface
>
> 62 09:57:03.866 06/08/09 Sev=Warning/2 CVPND/0xA3400015
> Error with call to IpHlpApi.DLL: CheckUpVASettings: Found IPADDR entry
> addr=10.4.1.158, error 0
>
> 63 09:57:04.880 06/08/09 Sev=Warning/2 CVPND/0xA3400015
> Error with call to IpHlpApi.DLL: CleanUpVASettings: Was able to delete all
> VA settings after all, error 0
>
> 64 09:57:05.472 06/08/09 Sev=Warning/2 IKE/0xE300009B
> Failed to active IPSec SA: Unable to enable Virtual Adapter
> (NavigatorQM:936)
>
> 65 09:57:05.472 06/08/09 Sev=Warning/2 IKE/0xE30000A7
> Unexpected SW error occurred while processing Quick Mode
> negotiator:(Navigator:2263)
>
> 66 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 67 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 68 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 69 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 70 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 71 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 72 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 73 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 74 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158
>
> 75 09:57:05.472 06/08/09 Sev=Warning/2 IPSEC/0xA370001F
> Cannot find binding for the private address: 10.4.1.158

XDA-Premier App Not Connecting topic

XDA-Premier App Not Connecting . when i install and try to connect says contact the administrator. i try installing Xda-Premier app and tap talk app as well please help.

[Q] Not connecting to KIES 3 topic

Hi,
This is Soham Roy,
I facing one problem related connection from my s3 to my kies 3... Neither kies nor odin 3.09 is detecting my device.... But I can able to browse my s3 via my PC's windows explorer... I have not rooted my phone and I'm using the official rom from samsung.... Just I have did factory reset, then also KIES 3 is not detecting my phone.... I have also tried by uninstalling kies and odin.... But it doesn't worked......
My another phone, Grand is detected by kies 3 but not by odin 3.09..... I am using windows 8 on my pc..... and want to use odin 3.09 but i can't due to this problem.....

My Phone Version:
AP: I9300XXEMF6
CP: I9300XXEMA5
CSC: I9300OJVEMF1

Attached Thumbnails

 

Camera not connecting. topic

Anybody having the camera can't connect issue? I'm on Droidkang v18 and getting this error pretty frequently. Only fix is to reboot the device. Was just wondering if anybody had a fix! I've tried both PA gapps and Banks gapps.

Thanks!

Nothing happens when connecting Ativ S on PC topic

My Ativ S used to work great, but two days ago I accepted a Samsung update. Since then my phone was without sounds on speaker and not charging. To make it charge I had to turn it off and then connect the cable. Today I decided to do a hard reset (lost my here drive+ :( ) and now everything works well. Except my phone is not recognized when plugged on any pc (I tried 2 windows 7 and 1 windows 8). That way I can't downgrade or do anything else via cable. Can somebody help me?

Edit: It does however charge while connected to the computer