Related
I recently upgraded to wm6 from the t-mobile site. At first it was running flawlessly and very fast. I have installed windows live, resco and tcmp and still things were quick. after a few weeks, strange things started happening. When i went to my SMS/MMS and began to write a message, the flashing cursor would move along as i typed but no letters would show up on the screen. If i saved this message inot drafts then opened it again, i could then see all the text i had written and was previously hidden.
Soon aftet this started happening, the same began in windows live, then word etc...
recently, my athena has started to crash within an hour of a reset. Most of the time, if i start a program, just the bar at the top will load and nothing else, this is most serious in SMS/MMS. also, when this happens and i got to memory (the start menu and setting tab are still quick) it shows that i always have over 50 meg of ram left. Although, if this helps at all, the device runs slowest when turned on from sleep mode. Before i put the device in sleep mode, when i goto file explorer i can hear the microdrive fire up and this programme runs slow. after if has been in sleep for 20 mins or so, file explorer will never boot up properly and there is no noise from the microdrive.
I have tried hard rest, starts fast again, then slows to nothing after few days. I have tried various tweaks i have seen on here, such as disabling autooff and disabling the x-button programme. I have run spybot and antovirus software and nothing. Anyone got any ideas? thank you in advance
more
not sure if this is related but using pocket hack master; firstly, this programme hangs on all bu the last speed test. also, in the processes, there is one with a large red x picture with it. not sure if this is normal but jus thought id mention it
ballsquid said:
not sure if this is related but using pocket hack master; firstly, this programme hangs on all bu the last speed test. also, in the processes, there is one with a large red x picture with it. not sure if this is normal but jus thought id mention it
Click to expand...
Click to collapse
There are many many programs out there which hangs my devices and cause the behaviour you described. pocket hack master is one of them, which strangely works for others but not my device. Anothe is Touch Commander.
I usually uninstall the software once they cause freezes.
Try installing and testing your software one at a time to isolate it.
got a feeling it could be windows live. Unfortuantly, this is probably the programme i use the most. Is there any known issue with this?
ballsquid said:
got a feeling it could be windows live. Unfortuantly, this is probably the programme i use the most. Is there any known issue with this?
Click to expand...
Click to collapse
I personally have had no problem with it, but sometimes one person's experience is not definitive. Try turning it off and see what happens.
mysterious double post deleted
i uninstalled all programmes and it seemed fine but when i put windows live back on. the problem started again. im using build 10.00026 i think. is there a later version than this that could help?
ballsquid said:
i uninstalled all programmes and it seemed fine but when i put windows live back on. the problem started again. im using build 10.00026 i think. is there a later version than this that could help?
Click to expand...
Click to collapse
I think PK ROM is likely to have the latest version, but Powell is the one who could confirm this.
eaglesteve said:
I think PK ROM is likely to have the latest version, but Powell is the one who could confirm this.
Click to expand...
Click to collapse
yes my roms have the latest build(18533 even though theres newer builds not available to public or been ported yet to athena) and the aboslute latest live 33.600 which is still latest in the roms i have from latest devices like polaris and dual
Hi,
i just had a try on Windows 7 RTM.
I plugged in the Blackstone and it downloaded the mobile device center and synced.
A day later it doesn´t even find it anymore. I de/re-installed the mobile device center, but no change?.
Any ideas?
Thx,
nearly
Damn. I found it. If i switch off fast sync on my Blackstone it works.
But why is that? I never had to do that and now syncing takes ages.
thx,
nearly
hi
you must instal Windows Mobile Device Center
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/device-center-download.mspx
it worked for me
I did, as i wrote above.
I´m syncing now since 5 hours with no visible progress.
I tried to de/re/uninstall everything, differnet drivers ect.
No way. I think i´ll have to go back to XP for another 8 years...
nearly
WOW. I found it. Very stupid. it was my Outpost Firewall. As i never had to do anything on XP, i haven´t thought about that.
Took me 6 hours to find that out. ouch.
Please close that thread.
nearly
I just noticed the new update when I opened the Kies in the PC and happily updated in my XP machine hoping that my long pending FW update which I was unable to do can now be done.
But you will not believe, my xp still struggles to detect my device even in this new update, I wonder what kind of update Samsung makes and if you see the version number there is a huge jump between .10071 to .10074 but for what.
Now I am trying to update my Windows 7 machine and let me see if I can succeed atleast there.
i had good device detection in previous version of kies
but in the new version it sucks
also the download said 123mb but went to almost 200mb
in both versions samsung apps store doesnt work, maybe its just for bada os.
UPDATE: yes finally I succeeded with the update from Kies. The upgrade worked fine like a breeze on my Windows 7.
People try the new update, as far as I can see the new update is not available in the samsung websites. When you open your Kies on your PCs it automatically notifies of an update. Goodwork Samsung atlast, Kies works and now I am ready for the froyo release.
sany said:
People try the new update, as far as I can see the new update is not available in the samsung websites. When you open your Kies on your PCs it automatically notifies of an update. Goodwork Samsung atlast, Kies works and now I am ready for the froyo release.
Click to expand...
Click to collapse
I would try, if I could download it some day in the near future. Now I have got 266 MB of 123 MB and sit several hours to watch those little pieces to flow from internet to my hard disk. It is senseless waste to update it for downloading a file at a time. Doesn't Samsung anymore can make an installation package?
Installed the Android SDK and now after the update on KIES, it won't go past 'detecting phone'.
My phone won't connect completely via Kies mode anymore. Oh my.
_
Sent using my Samsung Galaxy S i9000 using the XDA App
Same lost my connection but not sure it was an application installed previously or Kies.
Uninstalled Kies and installed the previous version but still no go same problem.
Has to be something on my Galaxy causing the issue.
I read someone said to format the internal SD and external SD to ensure no files are on it then sync.
That would mean re-installing or backup restore all my applications again.
This is just nuts.
can't find the URL to download this
Some people are sleeping over at Samsung. What a crappy software!!
I hope there will be some good Kies alternatives soon..
Hi All, I've been trying to get this phone working since Monday. I have installed and uninstalled the different versions of KIES a number of times. Still no joy. Once, today, it recognized the connection, but wouldn't sync to outlook, for me to be able to transfer my contact details across. Great phone (I think!), but awful software. I hope there's a 'breakthrough' soon!
Kies works fine if you proceed like this:
Check: Galaxy > Settings > About Phone > USB > Kies (ask for BlaBla will not work)
WakeUp the phone from sleep mode
Plug the bloody thing...
... and wait
... and wait
... and wait
... and wait UNTIL you can see the device in Windowz (about 2 minutes)
Start Kies
e volià
hanzi54 said:
Kies works fine if you proceed like this:
Check: Galaxy > Settings > About Phone > USB > Kies (ask for BlaBla will not work)
WakeUp the phone from sleep mode
Plug the bloody thing...
... and wait
... and wait
... and wait
... and wait UNTIL you can see the device in Windowz (about 2 minutes)
Start Kies
e volià
Click to expand...
Click to collapse
Not necessarily. Kies is one of the WORST applications I EVER USED! Terrible from the word go, NEVER been able to sync from phone to Outlook. Also, Outlook to Phone might happen once in a 100 times you try. Else it will give errors like "value does not fall within expected range". What the hell does that mean, hopefully Samsung knows and better improve the product.
Prankey said:
Not necessarily. Kies is one of the WORST applications I EVER USED!
Click to expand...
Click to collapse
I can't resist asking... have you used Nokia PC Suite or - even better, a lot better - the latest, freshly compiled Ovi Suite?
Tears flood my eyes just thinking about using it once again. And I know I'll have to. Kinda like that nasty job you hate but keep having to shuffle yourself to since you depend on it due to lack of skills, education or any fu"#$ing alternative ideas/options....
Yes. You hate it. But you'll use it again. And again. You all will.
Beowulf_pt said:
I can't resist asking... have you used Nokia PC Suite or - even better, a lot better - the latest, freshly compiled Ovi Suite?
Tears flood my eyes just thinking about using it once again. And I know I'll have to. Kinda like that nasty job you hate but keep having to shuffle yourself to since you depend on it due to lack of skills, education or any fu"#$ing alternative ideas/options....
Yes. You hate it. But you'll use it again. And again. You all will.
Click to expand...
Click to collapse
Nokia PC Suite is/was horrible and slow but at least it connected, can't say the same about KIES... personally I've only had little trouble with it but there's a whole lot of people who haven't been as lucky. Thank god we can use mass memory without starting up KIES
I have encountered the connection issue as well but that was after i installed Launcher Pro. into my i9000. Once i remove it, the connection run smoothly without any problem.
Hope this help.
when i updated kies i couldnt connect either , my phones said it was connected but kies begged to differ.
i uninstalled kies and all reg keys and downloaded the full kies and voila it worked again.
to the above poster get homeswitcher from market and you wont have to uninstall launcher pro , just switch when you want to connect to kies
regards
I think it's software conflict which are causing the issues.
I had a fully working Kies with the exception of the Calendar sync but after several application installations I can now not connect to my computer by USB.
I'm thinking of noting down all my software installations and resetting my phone as well as formating my internal memory. See if Kies comes back up.
Then I will install my software bit by bit testing each time to see which software might be causing the conflict.
chtan said:
I have encountered the connection issue as well but that was after i installed Launcher Pro. into my i9000. Once i remove it, the connection run smoothly without any problem.
Hope this help.
Click to expand...
Click to collapse
I installed home switcher so i can use the default launcher when i need to use kies.
Yesterday i updated kies and it took over 3hrs to download using the update function.
I wish Samsung would learn the magic of OTA.
(and remove all kinds of bloatware like touchwiz)
I wish i still had my old N1.
akselic said:
Nokia PC Suite is/was horrible and slow but at least it connected, can't say the same about KIES... personally I've only had little trouble with it but there's a whole lot of people who haven't been as lucky. Thank god we can use mass memory without starting up KIES
Click to expand...
Click to collapse
Yes mine did connect last week. I'm glad I installed the latest suggested upgrade build with the "Several Stability Enhancements" on the change log. It did connect fine this time.
And after the nicely animated Synch I'm now busy deleting the several randomly-added duplicated entries to both my calendar, notes and contacts on both the device (E72) and Outlook 2007.
That was useful, because it connected. And plus, sorting out all the mess manually will be a great past-time and distraction while I await for Samsung and Broadcom to figure out why gps tracks look like something your 3 year old drew on the living room wallet when you left that CD pen forgotten on the table.
Its been like 2 hours now downloading kies from the update popup while trying to run previous kies. Says its 100% dowloaded but still keeps downloading files like 980mb/123mb and to make it worse i keep having this popup from kies saying "The Internet is not connected. Do you want to check the connection and try again?" theres a Retry button i press in order to continue the download. I have windows 7 x64 and internet speed of 16mb so i dont get it. I thought of going to sleep and let it download all night, but its impossible since i need to press the retry button every minute when i get the pop up.
TheCarl said:
I installed home switcher so i can use the default launcher when i need to use kies.
Yesterday i updated kies and it took over 3hrs to download using the update function.
I wish Samsung would learn the magic of OTA.
(and remove all kinds of bloatware like touchwiz)
I wish i still had my old N1.
Click to expand...
Click to collapse
Thanks for the home switcher suggestion, for whatever reason i don't actually have to switch out of launcher pro when i use KIES.
Also, someone i correspond with here in PMs since we are both English speakers in Korea, hasn't installed KIES because he's on a mac. Yesterday we were talking about Swype and since i had asked him about his fw he brought up that he received an OTA update. I was shocked to say the least, and his firmware is as current as mine, however he didn't get the first three updates that i did through KIES.
I believe there are significant HD2 users who have updated thier handsets with (official) ROM 3.14. Following your ROM update are you experiencing any bugs? If yes, let us report them here and simultaneoulsy suggest any solution (if so).
I have FIVE HD2 handsets, between me and my colleagues which we bought simultaneously (it was with ROM 1.48). Four of us updated to ROM 3.14.720.3 on 5th November and ALL the four of us are witnessing these similar bugs, which suggests that it is an anomaly with the said ROM 3.14.
I am listing few important such bugs (and possible solution) here:
1). "Weird scrolling": This is withnessed specially while scrolling programs (>Start). And it CAN BE CORRECTED with suitable registry tweaks. (Its here: http://forum.xda-developers.com/showthread.php?t=629388)
2). YELLOW TINCH: Camera NOW has a YELLOW tinch, which is even more conspicuous with AUTO FLASH on. Also I observed that the picture quality is NOT appreciable if ISO settings are AUTO (as compared to ROM 1.48, with similar settings!!!). Lowering the ISO to 100, does help, however yellow tinch is not yet solved.
3). The Long Press End Key (power off) is many a times UNRESPONSIVE (actually it is responding with a significant lag), such that when we long press it once it does not respond however when we press it immediately again, it then pops up the power off menu.
I have already reported these bugs to HTC and am awaiting their feedback.
Whats your experience??
I have the weird scrolling.
Along with a camera problem posted in my other thread.
Read SMS messages still marked as unread. See my thread about this.
Also experiencing the sudden change of time, clock and date. Is working now after turning off all the automatic syncs described in other threads.
sending successful
I cannot remove the sending successful indicator. I unselected everything in sounds and alerts but still.
shemeri said:
I cannot remove the sending successful indicator. I unselected everything in sounds and alerts but still.
Click to expand...
Click to collapse
Look at this thread: http://forum.xda-developers.com/showthread.php?t=831866
Either change the registry manually or download and run a cab file.
I used the goldCard to install it,besides the scrolling my WIFI is worst than before,I think I will install back the HSPL.Im going back home...to my previous ROM I think it was awsome.
My date set itself to October 2010;
Had a buzzing noise and then it reset itself;
Will not send SMS on first attempt - but is sucessful on second attempt.
Any ideas?
ADC
I have also upgraded to the 3.14 rom this week. Previously 1.48 original vodafone rom with hotfixes.
Everything has been perfect, no poor scrolling, no yellow camera.
However since yesterday I cannot the phone via USB. The option to select
activesync, disk drive, or internet sharing will not appear.
going into the usb to pc settings everything is fine.
But when I connect to several different pc's and with different cables they all say "usb device not recognised"
however the device charges perfectly.
Very odd. I have to keep taking out the sd card and putting it in a reader.
anyone else experienced this?
Alarm setting
The biggest thing i have found so far is the setting of the alarm, if i tap on the alarm tab on the home page it just flashes on nothing happens?. To set the alarm i have to go "Start-Settings-More-All Settings-Clocks & Alarms".
Also on the home page tap the time and nothing happens, they all worked on rom 1.66
Anyone have any fixes??
While listening to music with earphones, I cannot answer any call......When someone call me when I'm listening to music with earphone plugged in, after pressing the call button, nothing can be heard, nor the caller can hear my voice.
My Location Weather Not Updated!
Since I has upgraded my HD2 to the latest ROM version 3.14 and I start having this issue that is "My Location" weather not updating via GPRS, 3G and HSPA mobile network! Its only updating via WIFI! Others country weather was updated fine except "My Location" weather! Strange!!! Has been contacr HTC Customer Support and they just no solution to this and said will passed my case to the technical support team and get back to me soon!! I even bring it back to Vodafone Ireland and reported Network Problem. Exchange new unit for me but the problem still the same! was fine before with the ROM version 1.66 WWE! hmm..I am having wrong time changed issue too!! NEW not necessary GOOD and OLD not necessary BAD!
Thank the universe I did not upgrade to 3.14. Still on 1.66 and running smooth. Only issue is time jump but hopefully this will be corrected somehow sometimes .....................
A week or so after installing the 3.14 ROM I suddenly have no sound via the internal ear-speakers. Possibly a driver issue, but can't figure out a cause for this problem. I now have to perform my phonecalls with a headset.
Hmm, the update has been available for some three weeks now. Yet, the number of issues reported and their frequency seems rather low.
Could it safely be concluded that the bugs reported here are incidents rather than structural problems?
And how about moving back to the previous ROM should the new one appear buggy, is this possible at all?
Elmo-85 said:
......
However since yesterday I cannot the phone via USB. The option to select
activesync, disk drive, or internet sharing will not appear.
going into the usb to pc settings everything is fine.
But when I connect to several different pc's and with different cables they all say "usb device not recognised" however the device charges perfectly.
Very odd. I have to keep taking out the sd card and putting it in a reader.
anyone else experienced this?
Click to expand...
Click to collapse
Exactly the same behaviour here!
I bought my first hd2 back in March when they first launched. Somewhere down the line that hd2 malfunction it wouldnt let me use my camera, kept getting a error message. It would freeze on boot up screen. So I called tmobile and swapped it out... I receive this hd2 and all was well until the update. I updated and I started having sense problems sense will always refresh itself after I would tap into different windows and folders. And sometimes it will not refresh itself it would say sense unable to launch or something like that. And I would have to pop the battery. I reflash back to the original rom which was 2.14 i believe or 2.12 and im still having the sense problems. Ive flash a custom elglancia max sense and still a sense problem android mode works like a charm but its a battery hog. Is there a way to fix the sense problem that ive missed in anyone of these fourms
Elmo-85 said:
However since yesterday I cannot the phone via USB. The option to select
activesync, disk drive, or internet sharing will not appear.
going into the usb to pc settings everything is fine.
But when I connect to several different pc's and with different cables they all say "usb device not recognised"
Click to expand...
Click to collapse
Had this as well, after some tweaking i got the PC (note PC) to update its driver for the phone - ie it(the PC) updated the drivers that was altered on the phone acc the new ROM.
Yes,
Again my alarm is not working. It was the same with 1.48, 1,66 and now with 3,14. Totally unpredictable!!!!
After flashing 3.14 the "BePolite" (Quiet ring when pick up) isn't working regularly. Usually, the first call after its off/on is going well, than function works from case to case (no dependence traced). Checked at RUS and WWE roms without any apps. Some people from 4pda.ru confirm such behaviour, some not.
Any ideas? Thanks in advance.
Another interesting observation I have had is that while setting up mail accounts, when we setup any GMAIL account, its has IMAP in AUTO SETUP instead of POP3, which subsequently can not connect. To correct this, one will be required to setup the GMAIL account MANUALLY entering the POP3 setting as pop.gmail.com, as recomended by GMAIL team.
Is it that HTC has developed this ROM so carelessly such that they have done a typical "COPY-PASTE" error, while they would have ported the gmail seetings from their ANDROID based ROMS (which they may have developed for HTC Desire!!!), otherwise how else one would justify such an error??
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...
BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists
When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta
Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.
tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post