USB & Debugging Stay in Notification Bar - Vibrant Q&A, Help & Troubleshooting

Even after removing the USB cable about 90% of the time. Turning off Debugging turns off the debugging icon, but it comes back as soon as I turn it back on. This started as soon as I upgraded to 2.2 via Mini Kies, and persists even now that I've factory reset multiple times, flashed multiple kernels, and even a ROM.
Currently running Trigger 2.7 on top of OverStock 1.3, skinned with High Voltage theme. Any ideas how to fix this?
Thanks!
Sent from my rough sketch of a Vibrant on a brick I like to pretend is running Trigger 2.7 on OverStock 1.3...

Weird.......... Based on what information you have given I would Odin back to Stock and then reflash your setup. I sounds like a "ghost" of corrupted data left over.

its a bug in rom (or threme) i had this before . try wipe cahce partiton but not sure if it will help

I get this every now and then too. When it happens I just plug it back up and unplug it, and it goes away.

Thanks guys, I'm going to try wiping the cache partition, and if that doesn't work, I suppose I can live with it.
On an unrelated note, I am now getting a horrible scratchy sound when dialing, instead of tones... But that's for another thread

I've had this problem in the past as well and have nailed it down to me unplugging the phone while it is locked. If i unlock the phone then unplug it gets rid of the usb connected and usb debugging icons.

Pulling the battery fixes this issue for me.

I have the same issue!! I have tried all of these, but the issue still remains. I have even tried cleaning the USB ports, but no change.

bartek25 said:
its a bug in rom (or threme) i had this before .
Click to expand...
Click to collapse
enough ? ;p

chadhoard said:
I have the same issue!! I have tried all of these, but the issue still remains. I have even tried cleaning the USB ports, but no change.
Click to expand...
Click to collapse
It still persists for you Chad? Man, gonna reiterate what I said on Facebook, may be time to call TMo and demand a replacement.

Br1cK'd said:
It still persists for you Chad? Man, gonna reiterate what I said on Facebook, may be time to call TMo and demand a replacement.
Click to expand...
Click to collapse
I am not going to call them. It is not a big deal, just a pain in the ass to see it every time I use my phone. If it start causing my battery to drain faster, then I will call the idiots over there!

Related

[Q] SOD when talking on the phone

I hope this is a simple fix, but I've been googling to no avail...
After bringing back my Atrix from the dead (see an earlier post if interested), my phone seems to suffer a SOD when I talk on the phone. This is the only time. I did see a similar problem on another site that gave me some insight. I don't have to do a battery pull--if I simply plug the phone into a power source, it comes right back. But, for some reason, when I talk on the phone, the conversation continues without problems, but the screen won't come back. Needless to say, I can't hang up on someone. If I plug in, suddenly all is well. If I cam away from a power source, a battery pull works.
Does anyone have any idea what would cause the phone dialer to go to sleep and not come back unless I plug in?
To be fair, I realize this isn't exactly a SOD, as it comes back to life when I plug in. But, I don't know if it is useful to describe my Atrix as narcoleptic...
What rom are using? cm9?
Sent from my MB860 using XDA
giqbal said:
What rom are using? cm9?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Not anymore. I am waiting for something more stable. I am using CM7...specifically "update-cm-7.2.0-RC1-olympus-signed.zip"
Minor update...
So, the problem still isn't solved, but I found a setting that lets me use the power button to end a call. So, when I get to the end of a phone call, if I hit the power button to end the call first (going to make me popular with friends and family), the call is ended and the phone wakes up normally. If I don't end the call first by hitting the power off, then I have to either do a battery pull or plug in.
Any clues???
It might be an issue from flashing the CM7 rom over the previous rom. Did you try clearing the davik cache and reflashing the rom?
I've tried clearing the Dalvik cache, but I just got all of my apps and settings the way I like them...I'd hate to re-flash unless I absolutely have to.
brogdonbr said:
I've tried clearing the Dalvik cache, but I just got all of my apps and settings the way I like them...I'd hate to re-flash unless I absolutely have to.
Click to expand...
Click to collapse
Try clearing the cache partition too. Titanium Backup may be worthwhile if you decide to reflash (which would be the best way to solve your problem).
Sent from my MB860 using XDA App

[Q] my.phones issue.

For the last two days my phone has been anything off at random... nothing has been changed... I'm on the cm9 nightly from the two days ago... this is the thing tho... If I gentely tap the phone it will shut off or shake it... so I figured maybe after time the batter is lose... but it also is turning off if it sits completely still...unless its playing music. It has not turned off since Round 8 ad I have just had it playing music this full time ...any ideas??
I already did a full wipe and re install and when I get home I'm going to Oden back to stock and redo everything.
ipeench said:
For the last two days my phone has been anything off at random... nothing has been changed... I'm on the cm9 nightly from the two days ago... this is the thing tho... If I gentely tap the phone it will shut off or shake it... so I figured maybe after time the batter is lose... but it also is turning off if it sits completely still...unless its playing music. It has not turned off since Round 8 ad I have just had it playing music this full time ...any ideas??
I already did a full wipe and re install and when I get home I'm going to Oden back to stock and redo everything.
Click to expand...
Click to collapse
My only suggestion at this point is odin back to stock 2.1.
Unfortunately this sounds like symptoms of hardware failure. I had a phone (cliq) which would do the exact thing as you described...the phone would vibrate shut off and reboot unexpectedly. I would open the physical keyboard and it would also shut off...this is totally hardware related from my understanding. But that is the worst case scenario.
Hopefully it is a software related issue in your case. Not much else i can say.
Sent from my Galaxy Nexus using XDA
Overclocked? Voltages changed at all from default? If you have anything set in voltage control or setcpu, get rid of them and try it. You could also try booting into recovery and see if you can reproduce the problem. That should also help determine if it is software or hardware related.
If the phone is plugged in it does not seem to reboot. i have not had time to mess with it i will check it out this weekend. Weird because it only seems to be doing this at work? I have not had it restart on me at all while at home.
Also if i have the music playing it will not turn off. This weekend im going to oden back to stock and see how it goes. otherwise gonna try to deal with it long enough till the gs3 comes out, ha.
ipeench said:
If the phone is plugged in it does not seem to reboot. i have not had time to mess with it i will check it out this weekend. Weird because it only seems to be doing this at work? I have not had it restart on me at all while at home.
Also if i have the music playing it will not turn off. This weekend im going to oden back to stock and see how it goes. otherwise gonna try to deal with it long enough till the gs3 comes out, ha.
Click to expand...
Click to collapse
You ever find a solution, I have a vibrant with the same problems. probably dropped mine too much lol
drago10029 said:
You ever find a solution, I have a vibrant with the same problems. probably dropped mine too much lol
Click to expand...
Click to collapse
hey i know its been a while but i havent been on here at all. Never found a solution for it but for some reason it doesnt turn off random anymore
ipeench said:
hey i know its been a while but i havent been on here at all. Never found a solution for it but for some reason it doesnt turn off random anymore
Click to expand...
Click to collapse
thanks for the response. and I found my problem already too, I had a bad power ribbon inside the phone that was torn.

MHL kernel wakelock problem

I am totally stock, unrooted.It all started after I turned on Google Now. I was trying it out for a few days, didnt like it so I turned it off. After that, I noticed a considerable dip in battery life. After checking with better battery stats app I found that the phone would no longer go into deep sleep and the culprit was "mhl-kernel-wakelock". I have tried everything to get rid of this wakelock.
I have tried: phone reboot, battery pull, wipe data from all media player apps and usb service, deleted all my apps, reinstalled them. I tried a full data wipe/reset and wiped cache.I tried charging my phone while off. I deleted all my media off of my sd card and got a new sd card. I tried connecting to windows based pc. Nothing works, the wakelock remains.
I have never used my note 2 to connect to the tv or anything like that. Also my usb functionality no longer works. It wont talk to the computer. The phone will charge though. I have searched google extensively and there is very little information regarding this wakelock. I'm afraid it might be at the hardware level. The only other thing I can think of is buying an MHL cable to HDMI and hook it up and hopefully when I disconnect it it will shut off the MHL mode that it is stuck in. Obviously I could also root and flash a ROM with a different kernel, but I really enjoy stock and the spen features etc.
If anyone has any suggestions im wide open. Thanks
EDIT (2/1/13): I also realized that when I tried Google Now was around the same time that my house lost power during the night and the power flickered WHILE my phone was charging from the wall outlet. I initially attributed the problem to Google Now, while in actuality it makes much more sense that a power surge fried my USB port on my phone.
I know this probably isn't the answer you were hoping for but I think it might be a good idea to go ahead and, assuming you're comfortable doing this, root and unlock your device. I recommend you try out Jelly'Beans' Build 4 ROM. It has all the great features of stock with the bonus of being much lighter on your phone (smaller system ROM file) and you can set it up to look like AOSP Jelly Bean. Or if you really don't want that look and prefer TouchWiz, you can do that too.
I would do this anyway as imho, it's better to be unlocked and free for the remainder of days you own this device, rather than get an OTA and lose the possibility of unlocking ever again.
And this has a good chance to resolve your situation as you would be totally wiping the system partition and chances are thats where the issue is.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
droidstyle said:
back up whatever you dont want to lose and wipe data/factory reset from stock recovery. you can try a cache wipe first, but a data wipe will fix guranteed.
Click to expand...
Click to collapse
Thanks.I already tried this several times. I tried it from the OS and from the recovery. I also lost my usb functionality so im not even sure if I can flash a new rom with odin.
I think I'm screwed. I can't even access the hidden menu from the dialer pad to attempt change the USB mode. It looks like a hardware failure, even though I haven't done anything out of the ordinary. It would explain why its stuck in MHL mode with the constant wakelock (despite multiple factory resets and data wipes). and why no USB ( tried 3 different cables) cable or any number of computers (3 different computers) cannot recognize, connect, or exchange information with it via USB. This blows.
I registered with Samsung and am trying to fill out a service request through their website, but it just says the troubleshooting guide is unavailable right now and it won't let me get past that step to actually request a service repair. FTW
Just an update in case anyone has this problem. I was able to get the battery drain under control. However, I'm not absolutely sure which setting it was, but under screen settings it was either auto-rotate or screen timeout, but I pretty much changed them all back to default, rebooted and changed them back to the way I liked them. For some reason it disengaged the MHL mode that it was stuck on. This is even after 3 factory resets and data wipes.. all it took was to switch one of those on and off.
The other problem I had was that my USB hub quit working, although it would charge, but not communicate with any computer. After a couple more days though, it stopped working altogether. It wouldn't charge my phone or do anything. I tested my charger and cord with another phone and computer it works/charges flawlessly.
After that, I took it into Verizon (crossing my fingers, since I got my Note II on release day with no insurance... so way passed the 14 day return period) and told them that I did get my phone back in late November, but I had never tried to plug it into my computer since I got it (even though I had and new about this problem for awhile) so I told them it was probably defective from the release date, I just didn't know about it. Long story short, after talking with 3 of the reps and them mindlessly googling dead-end solutions that I had already tried, the manager issued DOA on my device and shipped me a new Note II for free.
F yeah... very happy at this point. The new one I got is not a refurb, runs flawlessly. I rooted, unlocked, and running Clean ROM... all right before the OTA hit.
facing same problem with mhl wake lock and my n7100 note 2 is not detected any more when connecting to PC

Help. My phone is stuck in a boot loop

So I was charging my phone, and it restarted itself and now it's stuck in a bootloop!
I can't access download mode or recovery, it keeps restarting before I have the opportunity to press any buttons (hardware or on screen) and removing the battery does nothing either, as soon as I put the battery back in, the phone resets without me even pushing the power button
I'm using Temasek CM11 v8 with the "201113-1248-cm11-i9300-r3p2-linux30101-BOEFFLA-temasek" kernel
Is it recoverable?
I've managed to get it into both Recover and Download mode briefly, but both times the phone restarted within a few seconds back to the bootloop
Sounds like the power button is shorted out, fairly cheap repair if so.
Sent from my GT-I9300 using Tapatalk
Thanks for the reply. What makes you think that it's the power button shorting?
Holding power button for 5 seconds acts as a hard reset, everywhere.
That's a good starting point actually. There's no reason for download mode to reboot automatically. If it loaded then it waits for the events. Either it works until you do anything with a PC, or doesn't work at all.
hi
try using a universal battery charger and then try again
JustArchi said:
Holding power button for 5 seconds acts as a hard reset, everywhere.
That's a good starting point actually. There's no reason for download mode to reboot automatically. If it loaded then it waits for the events. Either it works until you do anything with a PC, or doesn't work at all.
Click to expand...
Click to collapse
Ah Well I suppose that makes it pretty conclusive. 2 hours later and it's still bootlooping... I'd take it apart but I don't really know what i'm looking for and I suspect if it's shorting, something will need replacing or soldering etc. Thanks very much
eltonpestana said:
try using a universal battery charger and then try again
Click to expand...
Click to collapse
I don't think I have one, I shall check though. Thanks very much
The issue of having it shortly resetting once reinstalled the battery sounds to me like a hardware failure, most probably hard resetting all the time.
A hardware repair should help fix this.
tweetatoo said:
The issue of having it shortly resetting once reinstalled the battery sounds to me like a hardware failure, most probably hard resetting all the time.
A hardware repair should help fix this.
Click to expand...
Click to collapse
It's funny you say that, after hours and hours of trying to get my phone to work, somehow through more luck than judgement I managed to get it into recovery and flash WanamLite 7.2 (I figured it was the next best thing to stock, as I couldn't access download mode) and well... since then, touch wood my phone hasn't restarted itself even once... now granted in that time i've only touched the power button once, to turn on the device, but it seems like progress to me
So my question is, is it possible that I could of had a bad flash or something? It seems too coincidental to me, and I don't actually think the different ROMs have anything to do with the problem (that is still lingering beneath I suspect), but the optimist in me REALLY wants it to be fixed haha
EDIT: Oh and thank you tweetatoo for your reply
So my question is, is it possible that I could of had a bad flash or something? It seems too coincidental to me, and I don't actually think the different ROMs have anything to do with the problem
Possible its the well known multipleromflashed problem .
JJEgan said:
So my question is, is it possible that I could of had a bad flash or something? It seems too coincidental to me, and I don't actually think the different ROMs have anything to do with the problem
Possible its the well known multipleromflashed problem .
Click to expand...
Click to collapse
Interesting, thanks. It's just a bit confusing, it seems plausible because I flashed the ROM earlier in the day but at the same time, im not sure how much control the new ROM would have over the phone entering Download Mode... Mind boggling.
I'll keep an eye on it for a bit... and im still too scared to use the power button haha
Thanks very much
Download mode is entirely separate to the rom, I still think your power button shorted out (stuck down) as it's been reported many times before. If you have warranty then now would be the time to triangle away and return to stock for a while, just in case.
Sent from my GT-I9300 using Tapatalk

[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014

[Q&A] [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Q&A for [ROM]【4.4.4】Google Play Edition 【KTU84P】- 09/30/2014
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
gpz1100 said:
I gave up trying to calibrate my compass. I have issues with it in any rom including stock TW. Some of these chips are just broken.
Click to expand...
Click to collapse
After trying many of the suggestions on this thread to fix the compass (my GPS lock is fine), I thought I might have messed up the hardware somehow. However, last night I flashed the 7/12 KT GE kernel, and the compass now correctly points in the right direction.
Germany?
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
TheSt33v said:
Hi Dan (or whoever else reads this). Love the ROM! It's amazing. Do you know if it will work in Germany? I went to Mexico a few months ago, and the latest build at the time would not get reception anywhere. Flashing a TW ROM solved the problem, but I would much rather use yours.
Thanks!
Click to expand...
Click to collapse
Well in case anyone is curious, this ROM gives me great cell service (full signal on Vodaphone.de) but no data in Munich. I tried airplane mode, disabling/enabling data roaming several times and setting the network mode to GSM preferred, but no luck. Flashing the latest release of Hyperdrive ROM allowed me to use data. Oh well.
flashing google edition on verizon s4 on nc5
I'm a noob and can't figure out if i can use safestrap to flash the dandvh google play edition rom.
verizon galaxy s4 on nc5 build, rooted with towel root and running safestrap 3.75
Viper Audio Working?
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Hi everyone, hoping you all can help me with a problem I'm having with my phone. First, some specs:
ROM: Danvdh GPE 9/30
I am one of those lucky MDK users, I got the phone in May 2013 and rooted early
I had been running the NC5 modem for a while now with no issue. The problem started after I flashed the NG6 modem (from Surge1223's thread) in TWRP. Just fyi, here are the steps I took to flash the modem. Within TWRP, I flashed the zip file, cleared Dalvik/cache, then rebooted.
Almost immediately I started getting random reboots. It rebooted twice, then seemed to settle down, so I decided to wait a day or so to see what my phone would do. Sadly enough, it started rebooting again, so I gave up last night and reflashed the NC5 modem in TWRP using the same method as before. The phone was fine after that, until this afternoon. About an hour ago, my phone froze, and rebooted, but the screen cut off at the Samsung custom padlock boot screen. It seems to be off at this point, but I can't power on the phone without pulling the battery. After pulling and replacing the battery, the phone powers on by itself, but again cuts off at the Samsung boot screen, about 3-4 seconds into the boot process. I've tried booting into TWRP and download mode, with the screen turning off and the device seemingly freezing after 3-4 seconds. I'm at a loss as to what to do at this point.
I'm at work right now, but when I get home, I will see if Odin3 can make some sort of contact with the phone. Any help in the meantime would be greatly appreciated!
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Alxoom33 said:
Sounds like you may have a bad dl. Re download. Turn phone off. Then boot into TWRP and reflash the modem zip. Not the non-halos.zip.
Click to expand...
Click to collapse
I would love to, but I can't.
I put a video up on Youtube showing what the phone is doing right now. I don't have 10 posts yet, so I can't post links, but if you go to youtube.com then add "/watch?v=3ey5xD9LodY" at the end of the URL, you can see what the phone is doing.
It is the only thing the phone will do. I've tried doing a hard reset by holding the power button, but nothing happens. All I can do is pull the battery and start this process again. If I hold the correct button combos, I can begin to boot into TWRP or download mode, but the phone cuts off/freezes like clockwork after 3 seconds.
I tried to get Odin3 to recognize the phone, but my desktop doesn't recognize that anything is plugged in when I connect my phone to it, so Odin3 by extension doesn't see anything.
Did you install the Samsung apps on your computer? You need them for the computer to recognize your phone.
To hard boot into recovery you need to hold power button and volume up at the same time, then let go of power button once blue writing appears on upper corner of phone.
Sent from my Xoom Wifi using Tapatalk
I'm sure I have. I've been able to send adb commands to the phone in the past. Now however, my PC doesn't even see that a device has been connected to it (nothing shows up in the device manager, not even an unrecognized device).
The phone will no longer charge when I plug it into an AC adapter either (or at least the LED no longer lights up indicating it's charging).
I have tried booting into recovery several times. Each time, it will begin to boot into TWRP, the blue text, "RECOVERY BOOTING...", will display, then immediately afterwards, the screen will cut off and the phone will freeze, just like in the Youtube video I posted.
I'm afraid the thing is bricked...
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
marioluigi64 said:
So, I was talking to a friend about what's been going on with my phone. During the conversation, I started goofing around and smacking the back of the phone like 4-year-old me would an NES to try and make it work (ah, good times...). Believe it or not (and I did not touch the power button while doing this), the phone powered up and successfully booted!!!
It showed only 2% battery life, so I connected it to the AC adapter, but then a few seconds later the phone died again.
This occurrence leads me to believe there is something wrong with the battery, and leads me to another question. Can the S4 (or any other smartphone) run solely on USB power?
My roommate has a Galaxy SIII, I read the SIII battery can be used in the S4, so I will test the phone out with his battery when he gets back tomorrow, and update you then.
Click to expand...
Click to collapse
Have you tried a different USB cable/transformer? It sounds like you might just have a charging issue. Not enough juice to get it started.
Allowing a battery to cool down will give it more usable power, which as it heats back up will deplete again. This sounds like your situation... Power off for a few, restart it has enough to begin booting, then depleted again.
The phone cannot run on USB alone it needs the battery to sustain it's operation.
I have tried 3 USB cables, 2 AC adapters, and 2 PCs.
When this started on Friday, my phone was hooked up to my PC at work and showing about 50% battery, but it's possible something went wrong with the battery and it's stopped delivering any significant amount of power or accepting a charge.
So it turns out it wasn't the rom or new modem that was the problem, my battery has decided to kick the bucket. I tried my roommate's battery in my phone and it booted right up as if nothing was ever wrong! Strange that an OEM battery would just die like that, but I suppose that does happen from time to time. Thanks for the help!
matycakes said:
Does anyone else use Viper Audio with this rom? I find that the audio driver frequently stops processing when I stop playing music and then come back and play again. It will start processing again if I reboot the phone or even kill the Viper gui process. I've tried installing it as a user or system app but hasn't seemed to matter. Anyway, just curious if anyone else was having the same kind of results.
Click to expand...
Click to collapse
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
TheSt33v said:
I use it, and I've never had any issues with it. I would recommend reinstalling, but you've probably tried that already. Are you using the latest version of the app?
Click to expand...
Click to collapse
Yeah, I have tried reinstalling it, and I am using the latest version of the app. The fact that you haven't had any issues is encouraging. I'll continue to troubleshoot and see what I can find.
I keep getting this (in CWM touch)
Flashing Google Play Edition
Android 4.4.4
Enjoy!
format() expects 5 args, got 4
E: Error in /storage/sdcard1/danvdh-GE-4.4.4-09-30-2014-VZW.zip
(status 7)
installation aborted
Is it just a bad DL?
EDIT: Tried a new DL, same issue. I want to get this fixed asap
Is cm11 theme manager included in this rom?
brd912 said:
Is cm11 theme manager included in this rom?
Click to expand...
Click to collapse
It is not.

Categories

Resources