Develop Bugs

big problem, my phone is haunted by a ghost headset!

So my dash has worked great for the 4 years of its life that I have had it with minor hiccups. This new one has me stumped though...
The phone seems to think it has a headset connected to the device when there is no headset connected. This "ghost" headset is preventing me from making/receiving calls; what is a phone that cannot function as a phone?
I am running an older version of EVO's ROM (havn't had access to a cord to try flashing to the new version because I am on holiday) but I have tried a hard restart and that did not work.
here is the quirky part... Sometimes if I reboot the phone it goes away, briefly. It may go away for a few min or it may only go away for a few seconds after the boot. If I reboot and it turns off, then I try calling someone really quick, the ghost may come mid call and essentially drop me because I can neither hear nor speak anymore.
My gut says its a hardware problem but I wanted to get some other opinions before I start opening things up.
Thanks in advance.

what happens when you do connect your headset? it seems like a hardware problem..

never have had a headset, whether bluetooth or physical... thus I am scratching my head even more...

*knock on wood*
I managed to find a usb cable and I hooked it up to my computer. The few restarts while connected to my computer in the effort of updating the rom seemed to make it stop. I am wondering if maybe the SDA unlock may have done the trick? None the less I was a version behind on my ROMs so I update to the latest EVO ROM and seems to be smooth sailing.

well, i woke up this morning with an error on my phone that went away after i accidentally hit the w/e button only to notice the ghost headset was back... will try to find the error but suggestions are still welcome...

a hard reset with last 3VO's ROM may work

tried that, it booted up with the headset icon on the top lol

JHaste said:
tried that, it booted up with the headset icon on the top lol
Click to expand...
Click to collapse
So definitely is hardware for sure huh,

gmaniac2008 said:
So definitely is hardware for sure huh,
Click to expand...
Click to collapse
JHaste,
Lets forget testing a phone with a custom ROM, go back to your stock and see if happens?
Also in this process flash stock & hard-reset... & install nothing
Now if all is fine you have a clean base for custom ROM NAND flash has issues and can have residual stuff left from flashing to which is why i say flash stock etc.....
Good luck

stylez said:
JHaste,
Lets forget testing a phone with a custom ROM, go back to your stock and see if happens?
Also in this process flash stock & hard-reset... & install nothing
Now if all is fine you have a clean base for custom ROM NAND flash has issues and can have residual stuff left from flashing to which is why i say flash stock etc.....
Good luck
Click to expand...
Click to collapse
good idea.. I agree

check switch of headset jark and phone headset slot they may be damaged.

Phone Clicking During Re-Boots

I was in the process of rooting today and I wound up having to do a battery pull during one of them as the root process stalled out.
Everything is working properly, but now, ever since the battery pull, the phone is making a clicking noise any time it re-boots or powers on.
Is this something I need to be worried about?

matpal said:
I was in the process of rooting today and I wound up having to do a battery pull during one of them as the root process stalled out.
Everything is working properly, but now, ever since the battery pull, the phone is making a clicking noise any time it re-boots or powers on.
Is this something I need to be worried about?
Click to expand...
Click to collapse
is it clicking or like the it vibrates shortly, mine does that and my hero did as well

No, this is more like the CPU inside is making a clicking noise. Best I can describe it is something like your hard drive working too hard to read something.

The only thing that clicks when activated is the camera. If you listen closely while opening up the camera a light click is heard when the application is opening. Odds are the root that got messed up screwed with the camera, which they are infamous for doing. Do a clean wipe and reinstall.

Mine does the same thing I am not worried about it
Sent from my PC36100 using XDA App

rutter9 said:
The only thing that clicks when activated is the camera. If you listen closely while opening up the camera a light click is heard when the application is opening. Odds are the root that got messed up screwed with the camera, which they are infamous for doing. Do a clean wipe and reinstall.
Click to expand...
Click to collapse
I re-ran the stock RUU and it happens with that as well.
I'm just worried that something major will fail on it when it is out of warranty if I do not identify and fix/replace what is wrong.

matpal said:
I re-ran the stock RUU and it happens with that as well.
I'm just worried that something major will fail on it when it is out of warranty if I do not identify and fix/replace what is wrong.
Click to expand...
Click to collapse
well if your phone becomes a brick because of hardware issues, how would they know its out of warranty?

Phone continues to lock up

Alright so ive used the search and couldnt find anything. I have a rooted s2 running eagles blood v1.1 and last night i flashed over lite'ing theme and now my phone screen will shut off and wont allow me to turn it back on, i have to hold the power button and it restarts. Ive reflashed eagleblood even recovered back to stock with just root and it continues to do it.
Any help would be much appriciated :/
Sent from my SGH-T989 using XDA App

Probably best to post this in the rom developer's thread. Any number of things can cause this behavior.

I would but my post count is low and i am unable to post there, so for now i am seeking help here.
ive tried un-rooting the phone, flashing the stock rom and no root, but have the same issue.

Did you wipe the caches in recovery?

treo...not! said:
Did you wipe the caches in recovery?
Click to expand...
Click to collapse
sure did, every time i reflashed/flashed i wiped everything

still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.

IProbablyDidit said:
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
Click to expand...
Click to collapse
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"

bhowanidin said:
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
Click to expand...
Click to collapse
setcpu ? youll have to bare with me a little bit as i dont know probably all i should

odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers

movieaddict said:
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
Click to expand...
Click to collapse
i have tried this already, does not work :/

I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.

KaneHusky said:
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
Click to expand...
Click to collapse
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )

IProbablyDidit said:
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
Click to expand...
Click to collapse
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also

tigerz0202 said:
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
Click to expand...
Click to collapse
im starting to think it is a phone issue myself, going to find out Tuesday when my new one arrives though i am hoping it was an error on my part because this phone has the chance to be fantastic.

I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium

htc2364 said:
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
i do appreciate the feed back, and from everyone who did give it. after lots of research and back and fourth between stock and custom roms i definitely wanted it to be the rom so it was fixable but im about 96% sure its the actual phone its self.

Reboot Loop NEW FINDINGS

Hey guys, my gnex has just been stricken (for the second time) by the boot loop. Managed to fix it last time with a flash of the google image, but this time it isnt working.
Same as usual, mine features the greyed out wifi toggle as well, and reboots every time the screen goes off (which makes sense that I've been noticing it go off every 2 minutes).
I have found that the device will not reboot if it is plugged in and set in the dev options to "stay awake" while charging. This seems to keep it running, same if I set the time-out to longer. My theory has to do with the distribution of power...I think that something is telling the phone it doesn't have enough power to function.
Like everyone else I've done endless factory resets, flashed the goog image and such and such to no avail. Currently stock but I left my bootloader unlocked atm. I can still boot into recov and everything and even flash other roms.
Has anyone else noticed this, or could someone who is also having the problem confirm the screen thing?
I think last time I posted I was on winmo, missed this forum.

Bump? Anyone else having this issue?

Just send it in for warranty. I sent mine in and Samsung exchanged the phone

I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?

My Nexus has been stuck on "Turning WiFi on.." since I've had it. It would also constantly boot loop itself whenever the screen went off. I flashed the new AOKP build to avoid this issue, however, the WiFi still does not work If I'm ever on stock again, I'll give stay awake a shot.
I live in the U.S. with the GSM GNex, so warranty is out of the question unfortunately.

Fixed the loop by flashing aopk again with franco's kernel. Brilliant but my Wifi is still messed up. I flashed a new baseband XXKL1 and no improvements. I'm gonna just wait it out for a bit because I've seen some threads elsewhere where that has actually worked, but who knows. I'll probably cave and send it out soon.

RogerPodacter said:
I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?
Click to expand...
Click to collapse
Yes and no. It happened twice and the second time I fixed it by going FROM stock to AOPK with included kernel. Now it happened on THAT setup so I went back to stock and no dice. Its a very weird problem....

I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.

mastergrifis said:
I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.
Click to expand...
Click to collapse
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.

ShatteredAxe said:
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.
Click to expand...
Click to collapse
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating

mastergrifis said:
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating
Click to expand...
Click to collapse
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!

ShatteredAxe said:
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!
Click to expand...
Click to collapse
I have a Desire Z by my side, but of course I want my Gnex back as new. The only thing that scares me is the warranty. I'm not sure if it's still valid. I mean, apparently there's no sign of root/bootloaderunlocked, but how can I explain that suddenly my phone has started rebooting itself without any reasons?

Yeah, only option is to just try and see what happens.

[Q] My phone is possessed

Alright, I have a weird one.
PROBLEMS:
First off, the phone won't stay off. If I turn it off, it reboots. If I pull the battery it obviously shuts off, but as soon as the battery is back in, it boots itself up without me touching anything.
But the MAIN problem is that it's... haunted. Without me touching it, the screen will turn on, displaying the home screen before backing out to the lockscreen. When this happens, an icon shaped like a steering wheel appears in my notification bar very briefly. Also, I get some kind of "startup, shutdown" noise, but not one I associate with any program or process I can think of. It's a doo doo DOOT. Then, DOO doo doot.
I don't even have any kind of car mode on this thing.
This happens with such frequency, it's basically a low-key strobelight. I end up pulling the battery because I feel bad for the poor thing flipping out.
WHAT WERE YOU DOING WHEN THIS HAPPENED?:
When this first cropped up, I had just finished using the phone to navigate me somewhere. It was plugged into my car charger, because it had randomly dumped a lot of charge before the trip (while I was napping...), so it was at about 12% battery.
PHONE FACTS:
AT&T SGS3, bought on launch day. Rooted, running Aristodemos III, which is an ICS ROM.
WHAT HAVE YOU TRIED?
Battery pull, turning off the gps, airplane mode, turning off all active processes, RAM dump, waiting, charging, sighing heavily. I haven't been home since this happened, but I will try flashing a new ROM later if I can't fix this - with a full wipe.
Any suggestions??

ManiacalShen said:
doo doo DOOT. Then, DOO doo doot.
Click to expand...
Click to collapse
Sounds like the old man who plays song of storms(in zelda)is haunting your phone! Quick play song of the sun! Right down up, right down up!!!
In all seriousness though, why not just factory reset? Or better yet go to your carriers store, show them, and get a new Samsung galaxy s3/send in for warranty.
AT&T SGS3 Marble White
AoCP The Collective 4.4 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter

Just restore a nandroid?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

The steering wheel is most likely "driving mode" goto settings, language and input, Text to speech, driving mode.. Is it on?
Sent from my SAMSUNG-SGH-I747 using xda premium

Driving mode is indeed off, at least right now. It's probably on when the phone freaks out...
I did a factory data reset, wiped the cache and the dalvik cache, fixed permissions, and then tried installing the Hellfire ROM. No dice as of yet, am getting an "assert failed: getprop" error. I can't plug the phone in to the computer to move files around, either. It just makes the "You plugged in a USB thing!" sound over and over but never lets the phone appear on Windows Explorer. Pretty sure this is a hardware issue at this point, but I'll get this damn ROM working if I can, just to be sure.
I'm not afraid to mess with software, but ugh, I don't know where to start with a hardware problem. Might have to see what the people at Best Buy have to say, since they sold me this phone.

ManiacalShen said:
Driving mode is indeed off, at least right now. It's probably on when the phone freaks out...
I did a factory data reset, wiped the cache and the dalvik cache, fixed permissions, and then tried installing the Hellfire ROM. No dice as of yet, am getting an "assert failed: getprop" error. I can't plug the phone in to the computer to move files around, either. It just makes the "You plugged in a USB thing!" sound over and over but never lets the phone appear on Windows Explorer. Pretty sure this is a hardware issue at this point, but I'll get this damn ROM working if I can, just to be sure.
I'm not afraid to mess with software, but ugh, I don't know where to start with a hardware problem. Might have to see what the people at Best Buy have to say, since they sold me this phone.
Click to expand...
Click to collapse
Have you tried using the Odin software in the DEV section and flashing over the stock software with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

ManiacalShen said:
Driving mode is indeed off, at least right now. It's probably on when the phone freaks out...
I did a factory data reset, wiped the cache and the dalvik cache, fixed permissions, and then tried installing the Hellfire ROM. No dice as of yet, am getting an "assert failed: getprop" error. I can't plug the phone in to the computer to move files around, either. It just makes the "You plugged in a USB thing!" sound over and over but never lets the phone appear on Windows Explorer. Pretty sure this is a hardware issue at this point, but I'll get this damn ROM working if I can, just to be sure.
I'm not afraid to mess with software, but ugh, I don't know where to start with a hardware problem. Might have to see what the people at Best Buy have to say, since they sold me this phone.
Click to expand...
Click to collapse
What you need as stated before is a complete factory restore. Not reset.restore. unless you'd rather spend another few days with these problems figuring out what it might be. find ucalg1 and flash via Odin this will fix all your problems. in case you missed the thread here you go:
http://forum.xda-developers.com/showthread.php?p=28019751
AT&T SGS3 Marble White
Team AoCP The Collective ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter

Dankest said:
What you need as stated before is a complete factory restore. Not reset.restore. unless you'd rather spend another few days with these problems figuring out what it might be. find ucalg1 and flash via Odin this will fix all your problems. in case you missed the thread here you go:
http://forum.xda-developers.com/showthread.php?p=28019751
AT&T SGS3 Marble White
Team AoCP The Collective ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Click to expand...
Click to collapse
Assuming that there is no faulty hardware.

I'll try Odin when I get home from work... but I have my doubts, since my computer won't recognize the phone correctly. I can probably replace the micro USB port, though. Haven't found the instructions particular to this phone yet, but I have a few days before the part gets here.
Thanks, guys.

Don't use your car charger again!! I've had this with 2 Samsung phones. My S2 and Skyrocket. Both of them have damaged micro usb ports because of a Rocket fish car charger.
Luckily I caught the problem and my S3 wasn't damaged.
Sent from my SGH-I747 using xda app-developers app

Okay, so I got Odin to work, but I still can't connect my phone to my PC while it's awake. XD Just while it's in Download Mode. No more repetitive "USB in!" noise, just "Device not recognized." But whatever, I flashed ucalg1, installed the newest ClockworkMod, used Dropbox in the browser to put get Hellfire and the relevant CM gapps on the internal SD, wiped everything, and installed those with the now-effective CWM.
Good news is that I have Hellfire now. Yay Jellybean.
The bad news is that it's still randomly waking itself up with the car mode notification like before, AND it won't stay off, AND trying Titanium Backup's shiny new zip feature created a brand new problem where I get random popups telling me certain processes have stopped. Going to mess with that some more. Odin sure didn't fix it.
But at least it's usable as a phone right now, and maybe when/if I replace the micro USB port, some of this madness will stop.

g2tegg said:
Don't use your car charger again!! I've had this with 2 Samsung phones. My S2 and Skyrocket. Both of them have damaged micro usb ports because of a Rocket fish car charger.
Luckily I caught the problem and my S3 wasn't damaged.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ha, actually the Rocketfish charger died last month. I've been using a random microUSB cable and a car-to-USB adapter I had lying around. If you're right, though, I might need to get a new cable.

ManiacalShen said:
Okay, so I got Odin to work, but I still can't connect my phone to my PC while it's awake. XD Just while it's in Download Mode. No more repetitive "USB in!" noise, just "Device not recognized." But whatever, I flashed ucalg1, installed the newest ClockworkMod, used Dropbox in the browser to put get Hellfire and the relevant CM gapps on the internal SD, wiped everything, and installed those with the now-effective CWM.
Good news is that I have Hellfire now. Yay Jellybean.
The bad news is that it's still randomly waking itself up with the car mode notification like before, AND it won't stay off, AND trying Titanium Backup's shiny new zip feature created a brand new problem where I get random popups telling me certain processes have stopped. Going to mess with that some more. Odin sure didn't fix it.
But at least it's usable as a phone right now, and maybe when/if I replace the micro USB port, some of this madness will stop.
Click to expand...
Click to collapse
I definitely sounds like a hardware problem. Just curious have you tried other ROMS other than hellfire and the other one you mentioned in the op? Like aokp or paranoid or cm10?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Bruce Lee said:
I definitely sounds like a hardware problem. Just curious have you tried other ROMS other than hellfire and the other one you mentioned in the op? Like aokp or paranoid or cm10?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Well, from Aristodemos, I used ClockworkMod to restore to an old Nandroid backup (some other ROM), then went stock with Odin, then went Hellfire. And Hellfire is CM10-based.