I've been running CM9 for almost 2 months now and its been great. 6 days ago my phone started entering docked mode by itself. I'll be doing nothing at all and it just pops up with the dock screen. Most of the time its the desktop dock screen, but once or twice it has been the car dock screen. I found that there was a newer version of CM9 released so last weekend I flashed that following all the camera gps fix instructions as well. I also made sure to remove and re-install "custom car home" and "galaxy dock sound redirector" just in case. The phone has been fine since saturday, but all of a sudden an hour ago it started doing it again.
Can anyone point me in the right direction?
Thanks.
bikewiz said:
I've been running CM9 for almost 2 months now and its been great. 6 days ago my phone started entering docked mode by itself. I'll be doing nothing at all and it just pops up with the dock screen. Most of the time its the desktop dock screen, but once or twice it has been the car dock screen. I found that there was a newer version of CM9 released so last weekend I flashed that following all the camera gps fix instructions as well. I also made sure to remove and re-install "custom car home" and "galaxy dock sound redirector" just in case. The phone has been fine since saturday, but all of a sudden an hour ago it started doing it again.
Can anyone point me in the right direction?
Thanks.
Click to expand...
Click to collapse
Back up to google and try a clean install? make sure .android secure is deleted. wipe data, dalvik, cache, system 3x (Don't forget to backup your angry birds progress.lol)
Okay, I just spent a couple hours dusting off my android skills and I deleted all my downloads for rooting and roms. I started fresh and got the latest odin, cwm, cm9 beta3, and gapps. I used odin to go to a fresh stock EL30 rom. The reason I did this was because I wanted to start from scratch, and also because my PC would not recognize my phone when plugged into the USB cable using a known good cable and uninstalling/reinstalling the Samsung USB drivers. After the fresh install was done, my USB connectivity was working again and I loaded all my new downloads on the SD card to reflash CM9.
I got all done loading everything and in the setup of my phone it asked if I wanted Google to restore my backed up wi-fi passwords, bookmarks, etc. So I allowed it to do so. It then started re-downloading all my apps from the Play store. Those must have been backed up too I thought. Walked away from the phone for a half hour and came back to it. Hit the power button to wake up the phone and its on the dock lock screen with the big clock time and the "set-alarm" option. I also tried plugging into my USB on my computer, nothing. Back to square one after over 2 hours of messing around with this.
Gonna try wipe date, cache, dalvik cache 3x and reflash cm9 and gapps. This time I wont let google load the backup and see what happens.
okay so I reflashed cm9 beta3 like i said i was going to and after about 5 mins of toying around with customization like turning off the widget auto add in play store and adjusting my volumes and ring tones, my phone popped up with the dock screen again.
WTF?
Have you tried cleaning off the USB port? According to my research (took all of a minute on google) car dock mode is triggered when the phone senses a resistance between pins 4 and 5 of the micro-usb of about 619 k. A resistance of about 365k will triggered Desk Dock mode.
So. if you have a bunch of crud jammed into the USB that could be enough to cause the problem you have.
UGH! You are probably correct!
I got fed up so I odin'd to stock and took it into the sprint store to get it swapped out. I gave them the usual "my phone doesn't charge intermittently" which has worked for all my service plan replacements in the past. They did clean crud out of the charge port, but i insisted that it still needed to be replaced. So, he took the phone completely apart (for what readson i dont know) puts it back together and tells me he has to order me one because they are out of stock on replacements. I go to walk out of the store and I have no radio bars. I go back and say hey, i think u forgot to reconnect the antenna. He agreed so he took it apart again. After that the phone would no longer power up so after another hour of trying to fix it, they had to give me a loaner phone (aka 2006 flip phone).
Thanks for the info. Hopefully this thread will be useful to someone else in the future.
Related
So I have been a long time follower of XDA, did all sorts of things with my Vibrant and just recently got the SGS2 from Sprint. A few days ago I flashed Calkulin's E4GT v2.6 and since then everything has gone down hill:
> The phone started acting like it was "charging" with nothing plugged in, red LED light stayed on and the battery had the charge symbol.
> Car mode began coming on over and over again.
> The phone would freeze and after I took out the battery it would automatically restart with me pushing the power button once the battery was re-inserted.
In hopes to just be down with it I flashed it back to stock with ODIN and everything seemed fine...
Now the phone is constantly freezing, Displaying that I have no service, The touch screen becomes unresponsive while charging, Car mode is still trying to launch.. not as frequently but it has happened. Other minor issues was the pattern lock would display when I woke up the phone even though I never set one...but I could do anything with the pattern to unlock it, even just touching a circle. Worse part in my opinion is either the phone will not recognize the PC or the PC will no longer recognize the phone so I can try ODIN again, same PC, drivers and USB cord being is.
Any suggestions on how I can remedy the situation?
Same thing happened to me, when I tried flashing an AIO over Calkulins you're pretty much done. You'll have to unroot and go to sprint. I ended up getting a new one since I was within the 2 week exchange.
monk3yguy said:
So I have been a long time follower of XDA, did all sorts of things with my Vibrant and just recently got the SGS2 from Sprint. A few days ago I flashed Calkulin's E4GT v2.6 and since then everything has gone down hill:
> The phone started acting like it was "charging" with nothing plugged in, red LED light stayed on and the battery had the charge symbol.
> Car mode began coming on over and over again.
> The phone would freeze and after I took out the battery it would automatically restart with me pushing the power button once the battery was re-inserted.
In hopes to just be down with it I flashed it back to stock with ODIN and everything seemed fine...
Now the phone is constantly freezing, Displaying that I have no service, The touch screen becomes unresponsive while charging, Car mode is still trying to launch.. not as frequently but it has happened. Other minor issues was the pattern lock would display when I woke up the phone even though I never set one...but I could do anything with the pattern to unlock it, even just touching a circle. Worse part in my opinion is either the phone will not recognize the PC or the PC will no longer recognize the phone so I can try ODIN again, same PC, drivers and USB cord being is.
Any suggestions on how I can remedy the situation?
Click to expand...
Click to collapse
What exactly did you use when you did this? I flashed it back to stock with ODIN
Maybe link to the file(s) you used?
Also maybe the exact steps you took. None of this sounds right. And if you flashed the complete EG30 tar you would be back exactly to when you purchased the phone. Everything would be overwritten so there really wouldn't be anything left to linger and cause issues.
Try a ##786# reset
Just_s said:
What exactly did you use when you did this? I flashed it back to stock with ODIN
Maybe link to the file(s) you used?
Also maybe the exact steps you took. None of this sounds right. And if you flashed the complete EG30 tar you would be back exactly to when you purchased the phone. Everything would be overwritten so there really wouldn't be anything left to linger and cause issues.
Click to expand...
Click to collapse
Once the device started acting funny, I basically pulled out the battery until I got home where I could flash it back.
This is the stock files I have saved to my computer:
http://forum.xda-developers.com/showthread.php?t=1351761
The phone is still somewhat usable, 3G, voice calls, everything works as normal until some of the symptoms start up again. Primarily the issues I am having is the phone completely freezing and occasionally displaying no service and of course not recognizing any PC connection.
Try a ##786# reset from dialer.
To get your MSL, in adb shell, type "getprop ril.MSL" without the quotes. If you use Android Terminal make sure you aren't using the Swype keyboard or it'll auto capitalize the "I" despite being told not to.
Initially, sounds like the USB port has some **** in it or damaged ;p
First off thank you everyone who has replied, I have definitely looked into all of your suggestions throughout the day. Here is what I have come up with.
I tried the ##786# for a clear reboot, all the symptoms still continued =(
I started figiding with the micro USB port and finally was able to get my computer and phone to connect to each other, I have also been reading that the port also causes the phone to spontaneous "ghost" charge and activate car mode.
So I am pretty sure it is a hardware issue, in particular the usb port. Tomorrow I am going to get the parts and make a jig to reset the binary counter and just take it in to Sprint and get an exchange.
I received a HOX that appeared to be DOA - not able to power on, no LED when charging. Nothing. I plugged it in for a while to see if it would miraculously start charging, and surprisingly, it did after a few hours.
It booted up normally and I began to check the apps. All looked fine and dandy and I threw a SIM card into the phone to check the service. Powered off to restart - and the phone died again.
I left the phone plugged in for a few hours. DOA. I popped it open and pulled the battery connector to reset. Put it back together. Still DOA. I left it unplugged for the night and plugged it back in the next day. The charging LED came back on! It booted up! I checked the apps again, and uninstalled everything that had been downloaded. The phone was not rooted and completely stock. The only app I was unable to uninstall was Cerberus. I attempted to hard reset the phone and of course, it would not turn back on. To me, this seems like an issue with the software security.
I emailed the customer and had him disable the device administration. I'll be able to check again in another 24 hours to see if I can uninstall and see if that does the trick. If that doesn't work, it's RUU time.
My question to you all is, are any of you using this app with the HOX? Could this be the root of the issue? Or has anyone had a similar issue with this phone?
Thanks in advance for any input.
I'm using Cerberus and don't have any problems with it. I think you do have to disable it under device administrator before uninstalling, but from your description, there are deeper problems with the handset. I'd get it replaced under warranty.
Sent from my HTC One X using Tapatalk 2
That was indeed the issue. Maybe it was potentially a bad install, but after it was disabled and I was able to uninstall it, the phone began to work immediately.
I'm going to hold onto the phone for a few more days to ensure it's good, but I caution others about downloading this app.
Never had any issues with Cerberus. Granted, I am rooted and I flashed it from recovery instead with the zip file on their website, so nobody can uninstall the app without overwriting my whole ROM. More than enough time for me to get a picture of the thief, wipe my phone, and get GPS coords
Good to know. The phone I had here wasn't rooted, not sure which method he used to download it. But I guess it was the wrong way!
Hey Guys,
So i've done some research all evening here and I've done nothing different than i'd do any other day with the phone and all of a sudden today around 6 PM eastern the phone started acting up. I came home from work plugged it in and it started to lag and then froze, finally unfroze and got that error " Unfortunately, %1$S %2$S has stopped running. I only have the option to click (ok) So I would do that and I thought all was well, turns out this is not the case. When this error pops up it also disables the phone from charging. I unplug and plug back in, the phone starts to freeze and the error comes back. I've been doing some online re-search some people say it's a synch issue with google and to turn synch of, did so, still same error. Some people have said unplug charger, power off phone wait 10 seconds, plug charger back on and boot up, this also did not resolve my issue. I will say that if the power cable is not in the device, it works fine. After about 2 hours of trying different things, I plugged it back into the charger and the phone started acting out really strange, changing from screen to screen and indicating " The dock is connected" I don't own a dock and the phone has never been into dock. I'm using the stock charger that came with the Note 2.
I will say I have TWRP installed and I've been using the JEDI X Rom for this phone without any problems. I thought, okay well none of this is working maybe it's the rom acting up, so I decided to go into recovery wipe all cache & system and re-installed the rom, same thing. The dock is connected, phone freezing and Unfortunately, %1$S %2$S has stopped running. So, I re-did everything again, wiped all cache systems, fixed permission and put the stock rom back on the phone. Now the phone is indicating in stock mode that the "dock is connected" when really it's just the charger. The phone is going into the time out then pops back on automatically all by it's self. Not getting the Unfortunately, %1$S %2$S has stopped running anymore though. the phone is 3 weeks old, and i'm at a loss here as to what I should do next.
Any suggestions, if not, Is there away to erase the phone "call" time so I can get it down to below 30 minutes so I can return this one for a new one?
Thanks,
Well, after hours of reading, I came across this post for an Android EVO phone and it mentioned something about a connect point of the charging port in the phone and said slightly bend the charger cable when it's attached inside, I tried this at a last cause and everything fixed itself, I re-flashed Jedi X and all errors have cleared itself. I find it strange because I'm very gentle with inserting/disconnecting these cables...
Thanks,
I'm not surprised. I've had similar issues with a S2 and other Sammy phones. In fact my brothers Galaxy S as well. He had to get the whole board replaced. I hate MicroUsb. Although its nice to have a generic sync port that is the same across almost all Android devices, this port needs to change.
Just my $0.02. Glad to see you figured it out. Knock on wood my Note2 hasent had these issues yet.
Sent from my SGH-I317 using xda app-developers app
So the other day I let my n7 die completely, which has happened in the past. Today I went to charge it with my computer and turn it on, so I plugged it into my laptop's USB port. For reference, I just installed Windows 8 and there are no android drivers on my laptop. Anyway, I plug it in and hold the power button and it shows me the google screen, then it goes to a black screen annnndddddddd.... Nothing. It stayed there until I did a hard kill. I can get to the bootloader as well as TWRP. Within TWRP I cleared the caches, and ran a fix permissions. Nothing. I've backed up in TWRP and have yet to wipe my data because that's a last resort for me at this point. Right now its sitting on the charger. When I plug it in I get the battery thing as well as the battery charging thing, however after the battery charging thing goes away I can't call it back up. (usually it'll go away but you can hit the power button and it will come back).
This appears to be a hard brick but I'm not sure. I was running 4.4.2 stock, rooted, bootloader unlocked, with Gravity Box, but that's it. Otherwise I've been running normal user stuff and it has been (up until now) just fine, normal battery life and everything.
nrock2256 said:
So the other day I let my n7 die completely, which has happened in the past. Today I went to charge it with my computer and turn it on, so I plugged it into my laptop's USB port. For reference, I just installed Windows 8 and there are no android drivers on my laptop. Anyway, I plug it in and hold the power button and it shows me the google screen, then it goes to a black screen annnndddddddd.... Nothing. It stayed there until I did a hard kill. I can get to the bootloader as well as TWRP. Within TWRP I cleared the caches, and ran a fix permissions. Nothing. I've backed up in TWRP and have yet to wipe my data because that's a last resort for me at this point. Right now its sitting on the charger. When I plug it in I get the battery thing as well as the battery charging thing, however after the battery charging thing goes away I can't call it back up. (usually it'll go away but you can hit the power button and it will come back).
This appears to be a hard brick but I'm not sure. I was running 4.4.2 stock, rooted, bootloader unlocked, with Gravity Box, but that's it. Otherwise I've been running normal user stuff and it has been (up until now) just fine, normal battery life and everything.
Click to expand...
Click to collapse
I fixed it. Something happened between the battery draining completely and me trying to turn it on that was causing a /system mount failure, thus the black screen after the bootloader. Here's how I fixed it:
I downloaded the full restore zip from Google (Mine was KOT49H at the time of posting this).
Then I opened the package, and the second package within the first one. I extraced the system.img file to my desktop.
After extracting the system.img file, I used fastboot on my computer to flash the system in my bootloader, and now its back to normal. No data was lost, nothing broken. I re rooted and everything seems to be in working order.
Good job! I know none of my 1st gen N7's liked to be drained completely so I make a big effort not to. Phones don't seem to have issues like these tablets sometimes do.
wantabe said:
Good job! I know none of my 1st gen N7's liked to be drained completely so I make a big effort not to. Phones don't seem to have issues like these tablets sometimes do.
Click to expand...
Click to collapse
Noted
Hi all,
I have a vanilla, unrooted tablet which had Marshmallow installed a few weeks ago. It reboots constantly (like I am lucky to get 2-3 minutes out of it). Sometimes it reboots 7 or 8 times in a row until I give up and hold the power button down.
Have cleared cache and factory reset (multiple times). This hasnt solved the problem. I thought this might be an issue with the Google Play Store, as it generally crashes as soon as I run this (as the first thing I do after the reset) - so after one of the resets I downloaded the latest playstore APK and installed it. Also did not login to the play store in case this was corrupted or something. Have tried this without loading ANY apps other than the stock that comes after the reset - but still the issue persists.
All of the above has been done with the SD card removed - and with full charge
Generally it crashes as soon as I try and run any app or go to settings etc. This is even with the completely factory reset and wiped tablet with no additional apps installed.
Having tried everything, am down to the theory of hardware fault - specifically the battery. After the last update (which failed half way through) I had big problems with battery life and the tablet got (and still gets) quite hot. I am thinking something in the new update might have put extra stress on the battery, which after a few weeks has caused it to fail.
Is this possible, and is there anyway in logs etc to tell if this is hardware or software?
Anyway, other than throwing this away and buying a new one - am not sure what the next step to solve this is. (Maybe revert to previous Android?). Any suggestions or help is welcome, but I am thinking of throwing this away and not throwing good money after bad...
(Have emailed Samsung but of course never heard back - so suffice to say my next tab wont be Samsung)
try download your stock firmware and flash it with odin via your pc.
i had problem with my tab...i had restarts always...whatever i do, every few seconds it restarts by itself... but it works normaly on cable so i went to search for a solution and lol i laughed when i saw what was the solution...i removed the backcover fo the device and then just reatached the battery connector cable and thats it and now my tab works normaly even on battery.not sure if u have similar issue but u can try it it will take u 5 min work and also u have video on Youtube how to dissambly galaxy tab S...cheers mate and wish u good luck
I solved this prob yesterday, itb works fine nw, didnt crash since, just open the tablet remove the basttery vlean its pins then reinstall it
U can find vedios explaining hw to remomve z battery
OK - have updated firmware with ODIN (and tried 3 different versions going back to Android 5)
Have undone the back and removed battery and reset cables. Even replaced the battery with one I bought off Ebay
Cant think of anything else, must be a fault on a board somewhere...
I think she is dead. :crying:
Thanks to those who posted and sent me PM's - really do appreciate it.
By the way, it is definitely something to do with the power. When it reboots and it is attached to a USB, the screen flashes up with the empty battery (ie charging from completely empty) symbol momentarily (maybe a second or 2 tops) before flashing up with 64% or whatever the actual battery level is...
michjfro said:
By the way, it is definitely something to do with the power. When it reboots and it is attached to a USB, the screen flashes up with the empty battery (ie charging from completely empty) symbol momentarily (maybe a second or 2 tops) before flashing up with 64% or whatever the actual battery level is...
Click to expand...
Click to collapse
If your battery can go from 0% to 64% in a few seconds, the battery connector needs to be resoldered due to cracked solder joints.
This rework only takes 5 minutes , ask a repair shop or anyone knows how to solder for assistant.
https://www.youtube.com/watch?v=DaAKjmrMR2s