After my phone has been on for a while, when I pull down the notification bar the device will be unplugged and plugged back in.
I have no idea why it happens, I've tried with several cables and ROMs. It seems to only happen after the phone has been up for a day or so.
It's kind of an annoying problem because if I have it set to Disk mode and pull down the notification bar it'll remount the SD card and revert to Charge only.
I couldn't find any related threads so I wonder if there is any fix for something like this?
happened to me also, had incredible s and now desire s. i bet all the roms you try are with sense 3.5, i think that is causing that.
try a sense 3.0 rom, it doesn't unmount.
shadiku said:
After my phone has been on for a while, when I pull down the notification bar the device will be unplugged and plugged back in.
I have no idea why it happens, I've tried with several cables and ROMs. It seems to only happen after the phone has been up for a day or so.
It's kind of an annoying problem because if I have it set to Disk mode and pull down the notification bar it'll remount the SD card and revert to Charge only.
I couldn't find any related threads so I wonder if there is any fix for something like this?
Click to expand...
Click to collapse
This is a well-known problem with Sense 3.5 ROMs, especially those which have some form of the RCMix Tweaks integrated in them.
Read my posts below detailing the problem and the solution :
http://forum.xda-developers.com/showthread.php?p=20100408#post20100408 from post #1268 onwards
and this one:
http://forum.xda-developers.com/showthread.php?p=20103855#post20103855
Thanks for the solution.
I enabled it, yet it still disconnected. I suppose it probably needs a reboot before it takes effect.
Related
What the hell is going on. I tried resetting and everything, even exchanged the device and the new one is doing the same thing! Also vibrating and force closing it is getting on my nerves! The followig seems to happen after a while I am TIRED of having to turn of my phone and turn it back on! ~ I go to play a .mp3 it says " FIle type not supported"...My .mp3 ringtone does not work the phone just vibrates the selected ringtone doesnt work. I got too take a picture or record video it says "Camera Failed"....I get a visual voicemail....the "play" button is grayed out and I have to turn off phone turn it BACK On just to check my voicemail. Also occassioally my sms wont work either. I turn my phone off and on every morning and throughout day I notice this and its getting REAL annoying !
Well first off, this isn't a software flaw, this is specific to you, as we have many users here including myself who are using these phones daily without the issues you are describing.
You had said that the issue was with an mp3, can you upload that somewhere for us to test on our phones?
As far as the camera and visual voicemail, I've never heard of that issue before, perhaps you ended up with a bad phone again?
I am getting the frequent force close with messaging. I also have had problems with the camera and idk about the mp3 stuff I haven't put any ringtones on the phone yet. This is getting really annoying I agree.
I don't have any issues with mine? Have you guys done anything like rooting or flashing anything?
Nope, completely stock. The most I have done is take a screen shot lol.
hmm maybe some have a defect? It's not all SK4g's though, as some of us have no issues at all. I would suggest getting it replaced by T-Mobile, as this is a factory defect. not sure why that happened to you guys. has anyone else had these issues and found any fixes?
That's kinda tough the hearest t-mobile is like 4 hours from here /:
One of my friends who went with me on the trip to get the SK also got one and he says he's never gotten a force close so you may be right. But could it have anything to do with the amount of texts I send/receive? Because I have to admit it is pretty excessive. The failing to send messages when I am receiving one simultaneously is expected, but not the force closes in my opinion.
It shouldn't force close on you. I know mine fails to send every once in a while too, as I text a lot (kinda the reason I got the phone). failing to send isn't as big of a deal, as it notifies you and you just have to click resend. Not entirely sure why it's force closing though? I wonder if a logcat might help? if you have adb installed, you can try adb logcat and see what shows up when you force close? if we can find the issue there, it might be fixable from our end. all depends on where the flaw lies/if it's just a bad apk somehow or if there's an actual hardware issue or something.
I'll do a log next time there is a fc, I'm having another issue or it may be related, but this one is with WidgetLocker I believe. Sometimes when I go to unlock the phone it'll freeze up and then I dont know how to explain it, but it almost seems like it resets but it really doesnt. The phone will blackout for a little then the homescreen will pop up and service will gone for a while until the cards are read just like if I rebooted.
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
sduvick said:
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
Click to expand...
Click to collapse
Yeah I know it does that from time to time, but on my previous phone it wouldn't do that reboot thing where it would lose connection then resend my latest text messages once it reconnected.
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
sduvick said:
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
Click to expand...
Click to collapse
That's what I was thinking too, I'm gonna uninstall it for a bit and see if anything changes.
is anyone else having an issue with notification volume? everytime i reboot my SK, my notification volume gets pushed all the way down to nothing, so i don't get a sound notification for texts, emails, etc, until i move the notif. volume back up in my settings. i did root with the one-click for the Epic 4G.
This is a new UI so alot of the apps i.e. widgets you may put on will cause issues. If you like certain apps contact the dev so your device is supported correctly. Still to new to get mad at it till sum of the bugs get worked out. I did notice a couple of times when I left screen on in pocket on accident that when I go to use it again it doesn't respond to any touch but can move courser around till rebooted then its ok. If some don't already know the sk4g is almost the same as the epic. The sk4g is still a badass phone for 100bucks.
Same as the OP
I know this is a little old, but I've experienced the same problem as the OP so it seems they are not alone with this problem.
I actually tried two different newly formatted SD cards (because I thought it may have been the SD card), and still would have the problem. Then I actually did swap phones about a month ago and it seemed the problem would now take several days to resurface instead of several hours. And I could deal with that.
Since the OTA update about 2 weeks ago, the phone has been back on it's original BS as the OP posted and it's driving me nuts. I actually missed some emergency calls last night because the mp3 ringtone didn't work so I'm finding a solution to this issue today or trashing this phone.
My belief is that there is something interfering with the phone's ability to read the SD card for media. Because other apps I have that save to the SD card or read from it work fine. So I'm going to master reset it and not download any of my apps and see what happens when I set an mp3 ringtone. If it makes it through the day with no hiccups, I'll slowly add back one app at a time until hopefully I can find the culprit.
bipoler if you'd like, we can exchange via PM what apps we both have downloaded and see if we have some in common that may be problems.
I'll post back with any progress.
I've been having the problem with ringtones not working, just getting silence when I get a call. for me it seems to happen when I set a ringtone from the app Zedge, I don't think it happens when I use ringtones from the Android System, which would make sense if the issue is related to reading the sdcard. gonna go back to a system ringtone and see what happens today.
Yeah my phone had all those problems, but I installed the Lightning rom and all those problems went away, except for the ones about messages failing...I text A LOT
Lightning ROM
Thanks for that info on the Lightning Rom. I will check that out. Phone has been working flawlessly all day with the mp3 ringtone and no extra apps besides the master reset. I might give it until the morning before I start putting them back on.
On stock id install so many apps that ran on the background that id get delay from opening closing swiping and turning onthe phone.. so I wiped it installed a custom rom and just kept the essentials.. havnt had a problem since... well.. occasionly ill have to odi but that's on purpose
Sent from my SK4G
my notification panel totally disappear no matter how many times i restart it.
lunze86 said:
my notification panel totally disappear no matter how many times i restart it.
Click to expand...
Click to collapse
do u mean the bar (batt, signal, time...blah) that stays put up there or the thing that you pull down with ur finger?
lol i hope that makes sense
yeapzzz that bar
It happened to my wife's HTC sensation this morning. All the icons in the top taskbar disappeared and she could not pull down the notification panel. I told her to remove the battery and restart the phone. The taskbar is back to normal. You must first disable Fast Boot (Settings, Power) if you want to restart phone without removing battery. If Fast Boot is enabled, the phone merely goes into hybernation mode when you power off.
I am still trying to figure out what caused the disappearance of the taskbar. Have not found any answers in the internet.
Incidentally, I also encountered a strange issue with my HTC senation. When I opened the camera application, the screen kept flickering (i.e. turning on and off repeatedly) making it difficult to take pictures. I read somwhere in the internet that the issue may be caused by geo-tag or GPS or google location. Nothing conclusive yet. I suspected that it was the Latitude application which I had signed in previously. I signed out of Latitude and the issue is gone for now.
hey! that happened to me too!
Thanks mostly to this forum I successfully rooted my HTC Status (the AT&T version of the ChaCha) and was able to finally remove some bloatware via Titanium Backup. (The internal storage had been so full it wouldn't even download Facebook or Calendar updates and couldn't update Marketplace apps.)
Anyway, I'm super stoked that this is taken care of, but I've discovered a few odd things about the phone post-root, and I'm wondering if there's any way to fix these issues:
Keyboard layout slightly different. I'm a USA AT&T customer, and I have US English selected in the phone settings, but the keyboard layout is different now. When I press the @ key, the phone shows the British Pound symbol. When I press the .com key, the phone enters camera mode.
When I plug the phone in to charge, I just get a black screen and the LED is always orange. It used to show an animation with a battery and indicate how far charging is complete. It DOES still charge the battery, but the visual feedback's definitely broken. The LED never changes to green, even when the phone's completely charged.
If I turn off the phone and then plug it into a PC for a charge, I cannot power the phone back on without pulling out the battery first. (And if you own a ChaCha, you probably know it's not very fun to get the battery cover off this phone.) I can live with the other issues, but this is really bizarre and a bit of a pain. Anyone know why this is happening and whether there's anything that can be done about it? I have tried different computers (one with the Android SDK/drivers, one without) and see the same behavior. Also, I have disabled the "USB Debugging" option on the phone, and the default USB Connection method is "Charge Only."
1. Common issue. Just look around for a thread containing flashable keyboard files. Mikevhl or iDarek posted one I think.
2. Might have been that you have removed something which displayed that (bloatware specific)
3. I've seen the exact same thing on my phone. It gets stuck in some sort of charging state; can't figure out what's wrong (didn't checked it that much either). It seems to be S-OFF related only..
Alex C. said:
1. Common issue. Just look around for a thread containing flashable keyboard files. Mikevhl or iDarek posted one I think.
2. Might have been that you have removed something which displayed that (bloatware specific)
3. I've seen the exact same thing on my phone. It gets stuck in some sort of charging state; can't figure out what's wrong (didn't checked it that much either). It seems to be S-OFF related only..
Click to expand...
Click to collapse
I will search for the keyboard files. Thanks!
The items I've removed with Titanium Backup are: AT&T Family, FM Radio, HTC Likes, Live TV, Quick Lookup, Shop Music, Transfer, Voice Dialer, Voice Search, and YP.
I may try restoring individual apps to see if one of them was somehow linked to the charging anims.
If you find out how to resolve the keyboard issue on the status, let me know. I've tried all the flashable zips as well as pulling the files directly from a temprooted S-On Status and none of them fully resolve the issue. It still retains the EU english layout regardless. I'm not sure people realize that the actual keyboard layout differs significantly from the english layout of the European Chacha model. To further compound things, I've diffed the .kl and kcm files between the chacha and the status and they're identical, which leaves me scratching my head. Any help would be greatly appreciated.
My phone did that freeze charging orange light thing before I s off'd...
Sent from my ChaCha using Tapatalk
So it's a phone issue then...
It's apparently a semi common problem.
My Wildfire running CM7 will always open up the clock app when I press the home button. Freezing the clock stops this happening.
Similarly, when I answer or make a call, the speakerphone is automatically activated. From what I can tell, the phone thinks it's docked, and indeed, if I set the phone to make a sound when it's docked, you do hear the notification.
If I plug in the power cable and wiggle it around, I can get it to activate/ deactivate this, but I dont have this problem at all if I go back to the Sense backup I have. (Should note, I've cleaned out the power socket with all manner of stuff, to no avail (thought it might be lint etc))
Basically, is there any way I can stop the phone from thinking it's docked/ just remove the dock facility entirely?
I found a thread somewhere that said something about changing the name of a dock related apk somewhere, but I can't for the life of me find it again.
Thanks!
I would start with a fresh install if you haven't tried that already.
Hit that thank button if I helped!
Yup, should've mentioned I've done that numerous times with different versions of stable CM7. Did a full wipe and cleared the dalvik cache each time too.
The problem doesnt happen until the phone has fully loaded i.e. the home button works normally for the first 10 seconds or so of the phone being on. Then I hear the notification to say the phone has been docked, and the problems begin.
Have you thought of uninstalling the docking software, and then rebooting?
Hit that thank button if I helped!
Well that's what I'm asking - how exactly do I do that?
I would download this,
http://www.apkapplications.com/2011/07/root-uninstaller-pro-apk-v121-download.html
Then look for the docking .apk
Hit that thank button if I helped!
Well I used that to freeze the clock before and that worked to stop the home button going to the clock, but the speakerphone issue remained.
There was no docking apk as far as I could tell.
Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?
flamph said:
Okay, I've "solved" this, and I feel compelled to share how I did it, since EVERY thread on this on every forum is unresolved.
My problem was something in the USB jack - I thought I had cleaned it properly, but after some WD40 and jamming a paperclip in there, I no longer get the problem...at least for now.
I still find it bizarre that I never had this problem with the stock sense ROM (and didnt have it when I reverted back to my backup of it), but what can you do!?
Click to expand...
Click to collapse
Glad you got it fixed!
Sent from my DROID3 using XDA App
same problem here, tried everything, reflashing, data wipe, cache wipe.
and same as OP sense based roms do not show this symptoms.
I have this problem with CM7 and almost on every rom based on it.
I searched in many places, but there aren't any positive solutions.
please help.
P.S.- cleaning the USB port also didn't work for me..
I found a way to disable dock mode. there is an app called NoDock which disables the dock mode at OS level.
It requires root permission to disable the dock. so your phone must be rooted.
unlike apps like DockNothing this actually does the job.
no more auto speakerphone modes, no more home button taking to clock app.
m.appszoom.com/android_applications/tools/nodock-free-trialneed-root_ogod.html
Soo.... I'm guessing there's no good solution, but posting anyway..
Suddenly, whenever I do a battery pull (frozen device or just swapping batteries) .... when I boot the phone back up, the date/time has reset to sometime in 2006 at 6:00pm...
I have the checkbox to automatically update date/time checked in Settings... this happened with CM7 and is also happening with MIUI now..
I downloaded an app to auto-sync date and time, but it doesn't kick in until several minutes after bootup if at all... so whenever the clock is fixed, all sorts of apps are affected - anything that tracks by date thinks 7 years just passed! Alarms go off, app alerts go off, etc..
I suspect this may be a capacitor/small battery used for keeping the time, inside the phone going bad ... anyone else had this happen to their g2x? Am I wrong in suspecting there's no fix?
lotherius said:
Soo.... I'm guessing there's no good solution, but posting anyway..
Suddenly, whenever I do a battery pull (frozen device or just swapping batteries) .... when I boot the phone back up, the date/time has reset to sometime in 2006 at 6:00pm...
I have the checkbox to automatically update date/time checked in Settings... this happened with CM7 and is also happening with MIUI now..
I downloaded an app to auto-sync date and time, but it doesn't kick in until several minutes after bootup if at all... so whenever the clock is fixed, all sorts of apps are affected - anything that tracks by date thinks 7 years just passed! Alarms go off, app alerts go off, etc..
I suspect this may be a capacitor/small battery used for keeping the time, inside the phone going bad ... anyone else had this happen to their g2x? Am I wrong in suspecting there's no fix?
Click to expand...
Click to collapse
Actually this happens to me everytime I swap my batteries, but date and time always correct themselves once the sync with a network, for me usually under a minute. I don't have any app issues though because of the incorrect time at start up. Very odd.
Sent via Sosei "III" BakedBean Iconia A100/4.1.2 AOKP/AOSP Hybrid