Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
In late December my first 9000M died on me (internal sd failure). I sent it directly to Samsung and they replaced the phone with a new one. I got the new phone about a couple of weeks ago and now some problems are starting to show up. Both my old and new 9000M's were manufactured in 10.08. The new one came back with JL2 installed and I haven't done anything other than unlock and root.
Last night I went to go use Google Goggles. When I launched it, it went to a black screen and the phone vibrated a few times then force closed. I tried it again and the camera view would show up then go black and then show up again and keep repeating this cycle. So then I tried the camera and that was doing the same thing (flashing on/off). I rebooted the phone and tried again. This time Google Goggles would take a picture but it would keep scanning forever. I reinstalled Google Goggles and it worked for one picture last night
Now skip ahead to today. Goggles force closes again. When I start the camera it seems like it is going to work but when I try take a picture, the camera starts flashing on/off and then a warning comes up and it says "camera failed" then eventually the camera app closes.
Does this sound like the start of an internal sd card failure? I had similar problems with my last Galaxy S before it died but it was different apps failing just before the phone went completely black and never woke up again.
This is a bit ridiculous and I don't think I would buy another Samsung phone anytime soon. I'm not sure what I will do if this one is dead because I would rather not have to deal with the same problem a third time.
Thanks for your input.
Could definitely be the start of the SD card failure. The good news is you'd be able to call Bell, and they'd ship a new phone to you within 3-5 days and apply a $100 credit towards your account, so you wouldn't have to deal with Samsung.
I'd try performing a factory reset to rule out a problem with the software, and if the FCs keep occurring I'd flash a different ROM. If the problems still persist on a different ROM, seems like you should give Bell a call sometime soon.
seeARMS said:
Could definitely be the start of the SD card failure. The good news is you'd be able to call Bell, and they'd ship a new phone to you within 3-5 days and apply a $100 credit towards your account, so you wouldn't have to deal with Samsung.
I'd try performing a factory reset to rule out a problem with the software, and if the FCs keep occurring I'd flash a different ROM. If the problems still persist on a different ROM, seems like you should give Bell a call sometime soon.
Click to expand...
Click to collapse
Actually I'm not a Bell customer so no good news there. I will try a factory reset.
The factory reset worked but then I used Titanium Backup to restore all my apps and settings and then my camera was broken again. It is highly likely that my camera files were corrupt already the last time I backed up. So I did yet another factory reset and this time I won't restore backups and I will see how long it lasts.
Here we go again... Yesterday the video camera would fail to record. Now the still camera either says "Camera failed" or the viewfinder screen flashes between the camera image and black until it force closes.
I'm starting to hate the 9000M.
Hi,
I am using an un-rooted Nexus One phone with Froyo (2.2.1).
The camera has stopped working unexpectedly.
Whenever I start the camera app, it gives me the error:
"Activity Camers (in application Camera) is not working"
It gives me the option to wait, force close or report.
If I select wait, it just hangs in there and pops the above msg again.
If I force close the app, and try to start it again, I get the error:
"Cannot connect to camera"
The phone did not fall down and is always handled properly.
This happened all of a sudden.
The last thing I did with the phone was to copy songs to the SD card.
I have factory reset the phone twice and formatted SD card, even swapped SD cards, but no luck yet.
I am based in India, the phone was bought in the US, I have no warranty.
Any help will be appreciated.
Thanks.
Sorry but I think your camera just died it is possible for the camera to die without any physical abuse but it is uncommon. The only other thing I can recommend would be to root and install a custom ROM (or at least a kernel) and see what happens but I don't think it will fix it.
Resolved....
Thanks Dude Random21..!!
Actually, I just resolved the issue about 30 mins ago.. Was downloading the apps and restoring its state as it was before I had factory reset it.
Well, after doing everything related to software to fix the issue, I concluded that it might be a hardware issue.
So, I started to search for threads involving camera hardware issues.
I took hints from the following post:
Google "Camera on my Nexus One not working - no flash either...all apps that use camera also not working - Help!?!?! " and you will be lucky..
(I cannot post links as I am a newbie)
Saw all videos on youtube about nexus teardown and just finished doing it.
I checked all the connections/internal wiring on the phone and once done, rebooted the phone and it worked..
Unfortunately my phone received a couple of scratches along the way, so others should be more careful about it.
Thanks for your help.
--- sent from my nexus one
No problem, I do what I can to help out. And good for you for having the guts to fix your nexus one's hardware cause I'm pretty sure that if I had an issue like that I would't have the guts to tear it down myself even with ifixit.
Remove (renaming is better) the DCIM directory from SDCARD. It is probably a corrupted (or incompatible with 2.3) file. After that, the camera cames back to life, then you can copy your “Camera” directory to the new DCIM directory created by your phone.
HTH
Hey everyone,
I'm getting this error when I try to switch on my LG 4XHD.
"Security Error
Error !!! Read morningcall"
To give you a background, I actually happened to drop my phone on a very rough and uneven concrete surface, screen-first. This developed cracks on the glass, but everything else was perfectly normal (the touch sensitivity, screen, camera, etc.) so I stopped using the phone and removed the SIM card until I could get the glass replaced. But a few days ago I switched it on (without the SIM card) just to make sure everything was still OK and also turned on the WiFi. I then went into Google Chrome and tried to open google.com, but my phone hung up, so I had to remove the battery and start the phone again, and that is when I started getting this error. Since then I've been getting this error whenever I try to switch on the phone and it does'nt get past that, not even allowing me to switch it off.
There is a lot of important data in the internal storage of which I would like to take a backup before doing anything.
Can someone please help me fix my phone?
Thanks a lot for your help in advance...
Likhit6 said:
Hey everyone,
I'm getting this error when I try to switch on my LG 4XHD.
"Security Error
Error !!! Read morningcall"
To give you a background, I actually happened to drop my phone on a very rough and uneven concrete surface, screen-first. This developed cracks on the glass, but everything else was perfectly normal (the touch sensitivity, screen, camera, etc.) so I stopped using the phone and removed the SIM card until I could get the glass replaced. But a few days ago I switched it on (without the SIM card) just to make sure everything was still OK and also turned on the WiFi. I then went into Google Chrome and tried to open google.com, but my phone hung up, so I had to remove the battery and start the phone again, and that is when I started getting this error. Since then I've been getting this error whenever I try to switch on the phone and it does'nt get past that, not even allowing me to switch it off.
There is a lot of important data in the internal storage of which I would like to take a backup before doing anything.
Can someone please help me fix my phone?
Thanks a lot for your help in advance...
Click to expand...
Click to collapse
One more thing that happened before it hung up is that Whatsapp gave an error saying the date was incorrect and also the Onavo data monitoring app said I used up 325% of 3G my data. Just wanted to mention these in case there are any known bugs related to these.
Likhit6 said:
One more thing that happened before it hung up is that Whatsapp gave an error saying the date was incorrect and also the Onavo data monitoring app said I used up 325% of 3G my data. Just wanted to mention these in case there are any known bugs related to these.
Click to expand...
Click to collapse
Can someone please at least help me take a back of my files in the internal storage when the phone is in this condition?
I think you would not be able to make any backup now ( I personally had this morning call problem as well but it was because of some other problems) the only thing that you can do is restart in software update mode and re flash with LG Flash Tool. You can find the thread named under "Rollback to ICS by SnXo.
I hope it can help you and don't forget to thank him for his post.
Sent from my LG-P880 using xda premium app.
Like what I said hit " Thanks" Button.
sPEADy said:
I think you would not be able to make any backup now ( I personally had this morning call problem as well but it was because of some other problems) the only thing that you can do is restart in software update mode and re flash with LG Flash Tool. You can find the thread named under "Rollback to ICS by SnXo.
I hope it can help you and don't forget to thank him for his post.
Sent from my LG-P880 using xda premium app.
Like what I said hit " Thanks" Button.
Click to expand...
Click to collapse
Sad to know I cant backup my files now. But, nevertheless, thanks a lot for the reply and suggestion...
Hey all,
I ran into an issue with this message and was able to resolve it. My round-about story (with all the details, some immaterial to the issue)...
The issue: Anytime the phone would be accessed/woken up after a few minutes of not being used, I would get the message to check the battery cover. I also would get the message when rebooting but that one appears to be normal. The one that appears each time after minutes of inactivity is not normal. I would only get the message to check the charging port cover after removing the charging cable, so that always remained normal and as it should.
I did the usual: ensured that the battery cover was on correctly, securely and entirely...several times. I figured it was an issue that I was going to have to live with. I also noticed that I would intermittently get a message about my SD card. Sometimes the error would say that it is blank, sometimes it would say it is blank or has unsupported files on it, other times it would simply tell me it was safe to remove my SD card. All for no apparent reason. I placed my card in my daughter's S5 and it worked. Placed it in my wife's S5 and it worked. Checked it on my PC and it worked. I even went so far as to wipe it out, format it and try again. Still received the error message on my phone. Not frequently but often enough to where I began to wonder if I was sold a bad phone.
I read some folks recommended doing a factory reset. I had nothing to lose so I did. I was reinstalling everything and things went well for the first few minutes and then the screen died. The phone was live, the buttons would light up but the screen would never turn on. I immediately headed over to the store and spoke with a really cool manager would agreed to swap out the phone for a new one since I have only had it 3 weeks (as opposed to sending me to the circus tent that is the maintenance facility). New SIM, new phone. Was a happy camper.
Got home, installed everything...and again....the messages started coming to check the battery cover. Frustrated I just decided that it was an issue I was going to have to live with afterall. Hopefully a fix will come about later, right? Well, it wasn't too much longer that the SD errors started again but this time more often. This can't be good. So, I decided to try swapping out the SD cards on my phone and my daughter's phone for a longer period of time. Let's do it overnight. So, in the morning I checked my phone (with her SD card). No messages at all. I checked her phone with my SD card. Hers now had the check batter cover message. I let both sit for a few minutes and checked them again. No messages on mine, but hers once again had the check battery cover. No errors regarding the SD card tho and it was able to access the content on the SD card just fine. Both SD Cards are 16GB SanDisk.
So, to further test, I swapped the SD cards again, putting her card back in her phone and mine back in my phone. Sure enough, mine was getting the check battery cover and hers was not.
So, long story short, it turns out that my SD card is causing the check battery message. It was throwing SD card errors on my phone but not on hers. So, for those people getting the constant battery cover message but not getting the SD card errors....try swapping out SD cards and see if that resolves the issue.
Hope that helps and wasn't too wordy...just wanted to make sure all the info was there.
EDIT:
SD Card that went bad was SanDisk microSD 16GB. Was replaced with an identical card and works fine. It has been a couple of weeks now and the replacement SD card in my GS5 continues to function properly and I no longer get the pop-ups unless I reboot or have actually removed the battery cover. I left the bad one in my tablet this whole time just to see and sure enough it was giving errors for a week and now it simply no longer works.
TQWorld said:
Hey all,
I ran into an issue with this message and was able to resolve it. My round-about story (with all the details, some immaterial to the issue)...
The issue: Anytime the phone would be accessed/woken up after a few minutes of not being used, I would get the message to check the battery cover. I also would get the message when rebooting but that one appears to be normal. The one that appears each time after minutes of inactivity is not normal. I would only get the message to check the charging port cover after removing the charging cable, so that always remained normal and as it should.
I did the usual: ensured that the battery cover was on correctly, securely and entirely...several times. I figured it was an issue that I was going to have to live with. I also noticed that I would intermittently get a message about my SD card. Sometimes the error would say that it is blank, sometimes it would say it is blank or has unsupported files on it, other times it would simply tell me it was safe to remove my SD card. All for no apparent reason. I placed my card in my daughter's S5 and it worked. Placed it in my wife's S5 and it worked. Checked it on my PC and it worked. I even went so far as to wipe it out, format it and try again. Still received the error message on my phone. Not frequently but often enough to where I began to wonder if I was sold a bad phone.
I read some folks recommended doing a factory reset. I had nothing to lose so I did. I was reinstalling everything and things went well for the first few minutes and then the screen died. The phone was live, the buttons would light up but the screen would never turn on. I immediately headed over to the store and spoke with a really cool manager would agreed to swap out the phone for a new one since I have only had it 3 weeks (as opposed to sending me to the circus tent that is the maintenance facility). New SIM, new phone. Was a happy camper.
Got home, installed everything...and again....the messages started coming to check the battery cover. Frustrated I just decided that it was an issue I was going to have to live with afterall. Hopefully a fix will come about later, right? Well, it wasn't too much longer that the SD errors started again but this time more often. This can't be good. So, I decided to try swapping out the SD cards on my phone and my daughter's phone for a longer period of time. Let's do it overnight. So, in the morning I checked my phone (with her SD card). No messages at all. I checked her phone with my SD card. Hers now had the check batter cover message. I let both sit for a few minutes and checked them again. No messages on mine, but hers once again had the check battery cover. No errors regarding the SD card tho and it was able to access the content on the SD card just fine. Both SD Cards are 16GB SanDisk.
So, to further test, I swapped the SD cards again, putting her card back in her phone and mine back in my phone. Sure enough, mine was getting the check battery cover and hers was not.
So, long story short, it turns out that my SD card is causing the check battery message. It was throwing SD card errors on my phone but not on hers. So, for those people getting the constant battery cover message but not getting the SD card errors....try swapping out SD cards and see if that resolves the issue.
Hope that helps and wasn't too wordy...just wanted to make sure all the info was there.
Click to expand...
Click to collapse
"Xposed G-Touchwiz"
https://play.google.com/store/apps/details?id=com.gertlily.xposed.touchwiz
This app removes those pop ups must be rooted and have exposed.
galaxy s4 nutjob said:
"Xposed G-Touchwiz"
https://play.google.com/store/apps/details?id=com.gertlily.xposed.touchwiz
This app removes those pop ups must be rooted and have exposed.
Click to expand...
Click to collapse
Did you even read what he posted or skimmed through it?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Megadoug13 said:
Did you even read what he posted or skimmed through it?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
If you get rid of the pop ups then they're won't be SD card errors correct?
galaxy s4 nutjob said:
If you get rid of the pop ups then they're won't be SD card errors correct?
Click to expand...
Click to collapse
Um no. Obviously there was an SD card issue. That needs to be taken care of. Oh somethings wrong here let me get rid of the warnings. That's not how things are done. Whether you take the pop ups away or not doesn't fix the problem. It's just not allowing to tell you the problem
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
TQWorld said:
Hey all,
I ran into an issue with this message and was able to resolve it. My round-about story (with all the details, some immaterial to the issue)...
The issue: Anytime the phone would be accessed/woken up after a few minutes of not being used, I would get the message to check the battery cover. I also would get the message when rebooting but that one appears to be normal. The one that appears each time after minutes of inactivity is not normal. I would only get the message to check the charging port cover after removing the charging cable, so that always remained normal and as it should.
I did the usual: ensured that the battery cover was on correctly, securely and entirely...several times. I figured it was an issue that I was going to have to live with. I also noticed that I would intermittently get a message about my SD card. Sometimes the error would say that it is blank, sometimes it would say it is blank or has unsupported files on it, other times it would simply tell me it was safe to remove my SD card. All for no apparent reason. I placed my card in my daughter's S5 and it worked. Placed it in my wife's S5 and it worked. Checked it on my PC and it worked. I even went so far as to wipe it out, format it and try again. Still received the error message on my phone. Not frequently but often enough to where I began to wonder if I was sold a bad phone.
I read some folks recommended doing a factory reset. I had nothing to lose so I did. I was reinstalling everything and things went well for the first few minutes and then the screen died. The phone was live, the buttons would light up but the screen would never turn on. I immediately headed over to the store and spoke with a really cool manager would agreed to swap out the phone for a new one since I have only had it 3 weeks (as opposed to sending me to the circus tent that is the maintenance facility). New SIM, new phone. Was a happy camper.
Got home, installed everything...and again....the messages started coming to check the battery cover. Frustrated I just decided that it was an issue I was going to have to live with afterall. Hopefully a fix will come about later, right? Well, it wasn't too much longer that the SD errors started again but this time more often. This can't be good. So, I decided to try swapping out the SD cards on my phone and my daughter's phone for a longer period of time. Let's do it overnight. So, in the morning I checked my phone (with her SD card). No messages at all. I checked her phone with my SD card. Hers now had the check batter cover message. I let both sit for a few minutes and checked them again. No messages on mine, but hers once again had the check battery cover. No errors regarding the SD card tho and it was able to access the content on the SD card just fine. Both SD Cards are 16GB SanDisk.
So, to further test, I swapped the SD cards again, putting her card back in her phone and mine back in my phone. Sure enough, mine was getting the check battery cover and hers was not.
So, long story short, it turns out that my SD card is causing the check battery message. It was throwing SD card errors on my phone but not on hers. So, for those people getting the constant battery cover message but not getting the SD card errors....try swapping out SD cards and see if that resolves the issue.
Hope that helps and wasn't too wordy...just wanted to make sure all the info was there.
Click to expand...
Click to collapse
Damn I was hoping for something different. I'm getting the same messages,
But I haven't put a SD CARD in yet. Still have my Note 2 running, S5 is a work phone. I've tried different ways to install cover. Mostly following the pressure point indications that flash up with the message pops up.
I'll monitor it, I can't remember when the last time I've seen them. Forgot phone at work yesterday charging it.
If I don't get messages any more, my fix was putting the cover on starting at the top. You definitely need to hear the clicks on all sides. I noticed sometimes I would not hear the top click if I started putting cover on from the bottom or sides.
Good find on the SDCARD issue though. Can you edit your first post and add in make/model of the cards that are working for you, and the one that is causing errors as reference.
It would be interesting to know if it's specific makes/models/sizes of cards that cause the message.
.
Megadoug13 said:
Um no. Obviously there was an SD card issue. That needs to be taken care of. Oh somethings wrong here let me get rid of the warnings. That's not how things are done. Whether you take the pop ups away or not doesn't fix the problem. It's just not allowing to tell you the problem
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I agree the issue will still stand but I see two issues being addressed and I solved one
dicksteele said:
Damn I was hoping for something different. I'm getting the same messages,
Can you edit your first post and add in make/model of the cards that are working for you, and the one that is causing errors as reference.
.
Click to expand...
Click to collapse
Done. Both the bad one and the replacement were the same make/model.
galaxy s4 nutjob said:
I agree the issue will still stand but I see two issues being addressed and I solved one
Click to expand...
Click to collapse
Actually, you were treating the symptom, not the cause. That's the same as if your car was leaking oil in the driveway and you simply put a pan under the car to catch the oil. Sure, you are no longer getting oil on your driveway but it doesn't change the fact that your car still has an oil leak and will eventually lock up the engine if not fixed. By fixing the actual problem (bad SD card), I was able to resolve the pop-up notices.
Fix the problem and the symptoms go away.
TQWorld said:
Actually, you were treating the symptom, not the cause. That's the same as if your car was leaking oil in the driveway and you simply put a pan under the car to catch the oil. Sure, you are no longer getting oil on your driveway but it doesn't change the fact that your car still has an oil leak and will eventually lock up the engine if not fixed. By fixing the actual problem (bad SD card), I was able to resolve the pop-up notices.
Fix the problem and the symptoms go away.
Click to expand...
Click to collapse
When everything is working properly do you get the "check battery" pop up after reboot and "check charging flap" after charging? YES it's built in annoying I was offerin a suggestion to get rid of those annoying pop ups that is all.
What's the title of this article?
galaxy s4 nutjob said:
When everything is working properly do you get the "check battery" pop up after reboot and "check charging flap" after charging? YES it's built in annoying I was offerin a suggestion to get rid of those annoying pop ups that is all.
What's the title of this article?
Click to expand...
Click to collapse
Yes, the message does now appear only when it is supposed to and no longer appears when it is not supposed to. When it appears as designed, it is not a problem. It may an annoyance to some, but is in no way a problem because that's what it was designed to do. When the pop-ups do appear at times when it is not supposed to then it is considered a problem because that isn't what it was designed to do. Mine was doing it when it wasn't supposed to. This is why the title of the post was called "Check Battery Cover message problem" and not "Check Battery Cover message toggle to shut it off from showing up when it's supposed to."
TQWorld said:
Done. Both the bad one and the replacement were the same make/model.
Click to expand...
Click to collapse
Wow that's a trip. I was expecting it to be an issue with maybe the top of the card being slighter fatter.
I was beginning to question whether the I-Balson case I put on it was tripping a sensor.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Me Too!
OMG! I've been having the same issue for a few weeks now. Same phone, same message errors and a SanDisk SD card (but 4GB)! I am taking the SD card out of my phone RIGHT NOW! Thank you SO MUCH for posting this! -Corrie
Slightly bend connectors - Samsung S5 - check batteri message
Hi!
I´ve also had the same issue for some time and it started when I got a new flip wallet case. Now I got real tired of this and I tried to solve the issue by simply and carefully BEND the two connectors on the back of the phone nearby the camera. And that SOLVED my issue - the message is gone!! Before it came frequently all the time. :good:
Hi!
I´ve also had the same issue for some time and it started when I got a new flip wallet case. Now I got real tired of this and I tried to solve the issue by simply and carefully BEND the two connectors on the back of the phone nearby the camera. And that SOLVED my issue - the message is gone!! Before it came frequently all the time.
Click to expand...
Click to collapse
Hi,
May i know which direction did u bend the connectors?
galaxy s4 nutjob said:
I agree the issue will still stand but I see two issues being addressed and I solved one
Click to expand...
Click to collapse
I know this is an old thread, but oh man! is this guy for real? can't tell if it's a poor attempt at trolling, or a poor attempt at issue comprehension and resolution.
Old thread but I just got bit in the butt by this one. I was only getting the message about the back cover on reboots. I would have thought that you would never see this message unless there was an issue, but did some reading and it seemed that this was normal behavior. So I took the phone snorkling (yes I know you're not supposed to take it in salt water but figured I could clean out the headphone jack). By the time I took it out of my pocket to take pics, it was dead (no more than 5 minutes). Took off the back cover, found water which left salt behind after it dried. Phone has not recovered, I am going to try to take it apart this weekend and clean out the salt. It was a work phone and already been replaced, but I'd like to try to get the pictures off of this from my vacation. It would be nice if there was a way to know for sure if the phone is properly sealed up before going into the water with it. Work gave me another S5, but I won't be exposing it to any water because I can't trust that it's properly sealed.