I've seen a couple of mentions about ActiveSynch 3.7 being more finnicky (sp?) about synching, sometimes not being aboe to get a synch going without rebooting either the PC or the XDA.
Here's my observation, in case it helps others diagnose the issue. If I put my laptop on standby or hibernate, when it comes back to life, AS will probably not work. That's the only time I seem to have the AS3.7 problem.
I've been using AS 3.7 since the day it was released, and yesterday had my very first and only failure to connect. I reset the device, and connected. I hibernate and use standby on my laptop regularly and don't have issues with that ever.
I'm going to bet it has something to do with ****ty USB host controllers in some computers. My last laptop, a Sony, had frequent AS issues. It also had occasional issues with other USB devices. My girlfriend's desktop had AS issues until I gave her a new USB card to use instead of the onboard USB, no issues at all any more.
Related
Has anyone had this problem?
After three trouble free months, my phone has developed a a very strange problem.
After charging, it behaves as if I'm constantly connecting and disconnecting the phone to a PC. It bleeps whilst showing the battery being connected to a charger and then imidiatly acts like its been disconnected by bleeping and running media scanner on both SD cards. It also shows that its connected via Kies, even though all this is happening whilst only being connected to a charger!
I've already done a full reset, which helped for a few days before it came back. It normally sorts itself out after a few minutes but the period before it "calms down" is getting longer. This morning I removed the battery for an hour but it continued in its "loop". Another, possibly related symptom is that as soon as the battery is installed, the phone boots up without being switched on. The same thing happens if I shut the phone down, it just powers up again!
Any thoughts?
had you if ever dip the bottom part of your phone? sounds like short-circuit issue or I maybe wrong.. try bringing in on to the nearest service center for warranty
Sounds a plausible theory but as far as I can tell, it hasn't got wet. Its been doing it for a few day now, so I think if it was damp, it would have dried out by now.
Thanks anyway.
I got the same problem. Let me know if you figure it out.
Sent from my GT-I9100 using xda premium
my friend had a simmilar issue and it was damage to the usb port , it kept thinking it was connecting to the pc or charger , it also wouldnt charge when plugged into a wall point and went into usb mode and vice versa when he put it into a pc
he sent it back for repair and they sent him a new phone
it may not be what you have but it does sound simmilar
i would try a few things like a reset , format the mass memory , install firmware again , dont restore back ups but set phone up fresh like you would do if you just bought it , then see how it goes , it could just be a corrupted file or system error that could be fixed bya full wipe and fresh install or it could be like my friends and the usb could be on the way out
on the topic of usb ports i do think they could have been better designed and iam hoping mine doesnt break as its needed for hdmi out , charging , docks , etc etc
Thanks Buxz,
As a follow up, I put the battery back in after taking it our for about 3hrs and all seams fine. I know that it isn't a permanent fix but I think it points more to software than hardware, which in a way is more annoying as its all about trial and error, as you described. A mechanical fault is more straight forward.
I just dread having to charge it again!
Regards, Woolly.
UPDATE
Charged it overnight and no problems when disconnecting it this morning. So far!
If anything, the battery life it better than before the problems. The fact that removing the battery for 3hrs broke the cycle of connect/disconnect, makes me think its soft/firmware related.
Woolly.
Hello.
It seems something changed in GingerBread release that changes either how phone communicates with PC or whatever, but if you plug it into PC that runs Windows 7 OS and then put PC in sleep mode, the phone will still show charging icon, but will rapidly discharge.
I've noticed this on Atrix 4G, when it had Froyo 2.2 it would stay 100% charged overnight, but once it got updated to GB 2.3, I can't leave it connected to PC anymore, by the morning it's completely dead. (by the way it can last at least 12 hours if unplugged and laying on table)
Unfortunately Atrix 4G is the only phone I have that can get Froyo to confirm this, but all others phones I've tried so far all have GB 2.3.x and all suffer the same issue.
Any ideas?
Thank you.
Two obvious options:
1- Plug the phone to the wall, or 2- don't leave laptop on sleep mode
Actually there is a third option:
3 - ignore useless replies.
You could try going into the device manager. Check all the USB Roots and disable the option for power management that lets windows control power to the ports. It might keep them alive when the PC sleeps.
This actually already been done.
The thing is, Froyo has no problem being charged, while GB can't. So it's doesn't sound like Windows OS related issue.
I dunno. I personally wouldn't expect PC USB ports to stay alive while they're sleeping. The lights on the external keyboard I use on one of my laptops always die when I close the lid and let it sleep
On a laptop, yes, unless the USB port is also a "charging" port. On a PC, it's depends on motherboard and OS settings.
Anyhow, the fact that the same phone with installed Froyo treated by the same PC differently then with installed GB, would automatically discard any accusation towards PC as the problem, wouldn't you agree?
Maybe GB is more power hungry and sleeping pc not able provide enough juice?
The Atrix 4G is indeed suffers sever (IMO) battery loss with GB compare to Froyo, in my tests it's near 50% loss through out day.
.
Thread moved. Would advise you to read forum rules and post in correct section.
So today out of the blue my Nook Tablet has been giving me grief. Google Framework Services crashes every few hours and my nook refuses to charge when connected to a computer but the same cord will charge it on a wall charger. Also when I connect to my PC its asking me if I want to scan and fix my Nook like there is an issue. I rooted using Indirects method and have made no other modifications at all. Has anyone else experienced issues like this because I tried trolling for similar issues but didnt see anything. If I missed it a link to the thread would be greatly appreciated.
This is the information I know about your concerns:
-When I was rooted Indirect's method at 1.4.0, the Google Framework force closed almost every time I booted my NT up (never did any harm).
-While connected to a computer via USB, the NT barely charges anyway, probably only getting a trickle charge.
-It's not uncommon for a PC to recommend you scan a removable disk. As long as you get the AutoPlay right after that, it's not a problem.
Hey everyone, I could use some help with a few Thunderbolt issues I have.
Here's a few points of description about the issues:
Whenever I use data on the phone (either 3G or 4G), the phone browses fine for about 3-5 minutes, then suddenly powers off. When I power it back on, the phone says it has 0% battery left, and will very quickly turn itself back off. When I plug it in to charge, the phone will turn on without issue and say it has whatever % battery it had before it turned off suddenly the first time.
If I simply use the phone for calls or non-internet things, the phone works fine. Once it's turned off once, though, it'll think it has 0% battery and not even offline things will work.
The phone seems to work OK for short-burst internet browsing, like checking email, but anything continuous (web browsing, streaming music) will shut it down within a few minutes
While plugged in, I can browse the internet, stream music, etc. just fine without the phone ever having any issues.
As a less serious and potentially unrelated problem,
The phone is not recognized by any computer. I have tried changing USB cables, computers, laptops, installing drivers, etc., but the phone only lists itself as "Charging" and never says anything about USB connections / USB debugging.
The issues first started when I tried out LiquidSmooth ICS about a month ago, with the recommended newer radio. I tried running the MR2 and MR2.5 radios on LiquidSmooth, and that didn't seem to change anything, so I went back to my old Gingerbread AOSP ROM, but the problems persisted.
Now I'm running stock with the stock radio (S-ON unrooted), and once again the problems are the same. The phone has been trying to download the ICS OTA update, but it always says "DOWNLOAD FAILED."
Anyways I'm not sure if the hardware on the phone has just broken, or if it's possible to fix through software. Anyone have any ideas? It would be much appreciated.
Sounds like you have a bad battery. Only thing I can say is you must not have properly unrooted your device or you have one of the few phones that will not do an ota update. I had this happen to my original droid when froyo came out. They try pushing the update but just wouldn't accept it. Also maybe your battery issue is causing your update issue. So just get a new battery and go from there.
Sent from my Nexus 7 using Tapatalk HD
I replaced my batt and my problems (the same as yours) went away!
Sent from my iPad using Tapatalk
Ok, I saw a lot thread about simular problems, biut nothing resolved my problem. So here it is.
Tried to connect my generic Galaxy S3 (no carrier) to my PC (and also my PC at work), with 3 different USB cables. As i connect, charge indicator worksand cahrges, but nothing else. No data connection, no driver istall attempt, no sign of connection on the notification bar. Tried going to download mode, and still not recognized by the PC. Drivers were uninstalled and reinstalled on both PC.
And to top of that. Battery drains faster then it charges. Only way to charge it is to shot the screen of. But it takes a lot of time to charge fully.
ROM: OmniROM 4.4.4, stock kernel, philz touch 6