I've been having this problem for the longest and just been dealing with it but its extremely annoying. Phone will randomly reboot whenever so I can't really get a logcat .. I always need to do a battery pull otherwise it stays on the red M. I've tried SBF'n back to stock and unlocking and re-rooting. It happens on EVERY ROM I try. And only started to happen after I unlocked boot loader. I even tried freezing modem fast dormancy. Idk what else to try. Any suggestions?!
Sent from my MB855 using xda app-developers app
Reflash full sbf and unlock with this sbf - http://d-h.st/BkJ
is using the stock 198_7 fine?
I fixed my random reboots by wedging a thickly (~0.5mm thickness?) folded piece of paper along the side of the battery closest the pins. It's a manufacturing defect in the connector pins versus battery pin contacts where even the slightest of impacts somehow causes one of the four pins to lose contact with the battery contacts, causing a seemingly random reboot/shutdown condition, or a frozen M screen, OR a battery logo with a question mark. Removing the cover and trying to shift the battery side-to-side replicated my problem. I could feel some wiggle in the battery.
I still have reboots with mild impacts (relax, my Photon is in an Otterbox case) on the back or front of the phone. Side impacts no longer cause me anymore reboots.
May not be your issue at all, but my phone was behaving similarly. A slightly loose battery is something I doubt many people look for right away. My phone is root, but bootloader is still locked because I have to use Wimax.
peetr_ said:
Reflash full sbf and unlock with this sbf - http://d-h.st/BkJ
Click to expand...
Click to collapse
So far ive only had one sleep of death experience and no random reboots
Sent from my MB855 using xda app-developers app
psychotropic said:
I fixed my random reboots by wedging a thickly (~0.5mm thickness?) folded piece of paper along the side of the battery closest the pins. It's a manufacturing defect in the connector pins versus battery pin contacts where even the slightest of impacts somehow causes one of the four pins to lose contact with the battery contacts, causing a seemingly random reboot/shutdown condition, or a frozen M screen, OR a battery logo with a question mark. Removing the cover and trying to shift the battery side-to-side replicated my problem. I could feel some wiggle in the battery.
I still have reboots with mild impacts (relax, my Photon is in an Otterbox case) on the back or front of the phone. Side impacts no longer cause me anymore reboots.
May not be your issue at all, but my phone was behaving similarly. A slightly loose battery is something I doubt many people look for right away. My phone is root, but bootloader is still locked because I have to use Wimax.
Click to expand...
Click to collapse
So far the sbf has worked well but if I do continue to have issues I'll try this thanks
Sent from my MB855 using xda app-developers app
Still having the issue now but the phone heats up
Sent from my MB855 using xda app-developers app
You may have a dud phone. My first photon was all stock and it randomly rebooted for no reason at all. It was mainly after I locked the screen. All of the sudden I would hear the SD card mounting sound. Happened quite often. I took the phone back to radio shack and swapped it out. Have had no problems since. Only reboots are caused by me tweaking and such.
atroph said:
You may have a dud phone. My first photon was all stock and it randomly rebooted for no reason at all. It was mainly after I locked the screen. All of the sudden I would hear the SD card mounting sound. Happened quite often. I took the phone back to radio shack and swapped it out. Have had no problems since. Only reboots are caused by me tweaking and such.
Click to expand...
Click to collapse
I'm afraid to get a replacement cause I'm sure it's gonna bee permalocked
Sent from my MB855 using xda app-developers app
Related
Has anyone had the problem that their Galaxy S2 randomly turns itself off when it's in their pocket.
It's happening quite often now, twice today, several times yesterday.
Take the phone out of my pocket and it's got a blackscreen that doesn't respond to being woken.
Holding the power buttons makes it reboot and all is fine again.
At first I thought it was because of the position of the power/wake button being pressed while in my pocket, but I've tried recreating this and it's not easy to do.
I am running Widgetlocker, so not sure if this is causing an issue.
It's an O2 branded phone, not rooted.
Cheers
I had it happen to me once, the first day I got it, but it hasn't happened since.
The only thing I can think of was that the phone was very very warm in my pocket, so I guessed that it might have overheated.
Yes, I did wonder if it was a heat problem. But it would have been sat there doing nothing so shouldn't have got too hot.
Sent from my GT-I9100 using XDA App
Now that's 3 times today. Within 5 minutes of being in my pocket.
Checked it straight away and it wasn't particularly warm.
Sent from my GT-I9100 using XDA App
Hi,
Happened to me few times, its not something very wrong with the phone.. What i did and after that I have no such reboots:
opens the back cover, cleaned the battery contact point (electric points) on battery and phone, put it back tightly, closed the back cover so there is not gap (not even a very small gap) between cover and phone..
after this never have reboots even having the phone in my pocket. hope this helps
Bobbajob said:
Has anyone had the problem that their Galaxy S2 randomly turns itself off when it's in their pocket.
It's happening quite often now, twice today, several times yesterday.
Take the phone out of my pocket and it's got a blackscreen that doesn't respond to being woken.
Holding the power buttons makes it reboot and all is fine again.
At first I thought it was because of the position of the power/wake button being pressed while in my pocket, but I've tried recreating this and it's not easy to do.
I am running Widgetlocker, so not sure if this is causing an issue.
It's an O2 branded phone, not rooted.
Cheers
Click to expand...
Click to collapse
nasgilani said:
Hi,
Happened to me few times, its not something very wrong with the phone.. What i did and after that I have no such reboots:
opens the back cover, cleaned the battery contact point (electric points) on battery and phone, put it back tightly, closed the back cover so there is not gap (not even a very small gap) between cover and phone..
after this never have reboots even having the phone in my pocket. hope this helps
Click to expand...
Click to collapse
Thanks for the tip. I've given it a good clean and put it back together and I'll monitor the situation.
Bobbajob said:
Thanks for the tip. I've given it a good clean and put it back together and I'll monitor the situation.
Click to expand...
Click to collapse
please post back with your findings - i've had the same a few times recently and it's annoying to say the least ...
This has never happened to me but hopefully nasgilani's method would work for you
nasgilani said:
Hi,
Happened to me few times, its not something very wrong with the phone.. What i did and after that I have no such reboots:
opens the back cover, cleaned the battery contact point (electric points) on battery and phone, put it back tightly, closed the back cover so there is not gap (not even a very small gap) between cover and phone..
after this never have reboots even having the phone in my pocket. hope this helps
Click to expand...
Click to collapse
I've seen this happen on other phones. The original Palm Pre needed a foam spacer in the second hardware rev. Maybe a piece of paper or two between the battery and the cover to make better contact. I'm happy saving 30 grams (and a better phone period) but this does chalk up a point to the Sensation build quality.
It's been okay so far today after cleaning the battery contacts and reseating the battery. But it has spent most of the day sat on my desk at work. So hardly a good test.
any update ? mine turned off again today. :-(
Mine has been doing this randomly as well. Its very annoying.
sohanlon07 said:
Mine has been doing this randomly as well. Its very annoying.
Click to expand...
Click to collapse
glad to hear that it's not just me. i really hope that it doesn't turn off in the middle of the night otherwise ...
It's been fine now for the last 3 days after cleaning the battery terminals and refitting the battery.
It looks like the battery was losing connection briefly while in my pocket causing it to turn off.
Sent from my GT-I9100 using XDA App
I also have the same issue. It's really hard to replicate the error and some days it doesn't happen. For some guy in this forum it turned out to be a faulty RAM... I hope this isn't the issue for us too!
A good way to check this is by enabling USB debugging, connecting to a pc and run "adb logcat" in the command console... then you wait for the phone to crash and post the logs here, hoping that someone will spot the error for you.
Sent from my disappointing GT - I9100
yup mine does too. some days 4 or 5 times some days not at all.
Have you tried giving the battery contacts and clean.
It might also be worth wedging a bit of paper folded up at the top of the battery to slightly increase the pressure on the terminals.
Mine only ever did it while the phone was in my pocket so a bit difficult connecting by usb.
Sent from my GT-I9100 using XDA App
This seems to be a widget locker problem for me. It opens with the home button even when locked does it not?
Just guessing.
Mine happened the last 2 nights, when i wake up I have to switch it on,
I have widget locker.
But i'm gonna uninstall it and see if it resolves it.
I had this going on but in my case I soon figured out that it was overheating from something that I'm guesssing had the phone at 100% although it was idle. Never did figure out what it was as a logcat showed nothing after the fact but that the phone was very hot to the touch if caught just after shutdown. That had been on villian rom which I liked but without being able to see a smoking gun in a logcat and never catching an app or system process running amok I ended up changing roms and the problem was gone. It should be noted that several people have reported doing a system reset and ridding themselves of this problem.
Alright, so this phone is becoming extremely frustrating.
The very first day i got the rezound I had it for literally five hours right from the store and I figured i would restart it to freshen things up after messing around with setting up my home screens.
Upon my phone turning back on, it booted up to the lockscreen... froze... turned itself on and then restarted itself and it LOOPS... it does NOT get past this point it bootloops the process
So I pulled the battery a few times, then did a factory reset in hboot and the problem fixed itself, so I gave it the benefit of the doubt and thought maybe it was just a fluke so i reset everything back up... now three days later... I restarted the phone... upon turning it back on... SAME THING... BOOTLOOPING for no reason
I have never tried to temp root my phone or do anything whatsoever. This is a 100% legit phone but its becoming extremely annoying. Im returning this thing to VZW tonight and exchanging it for another one but im torn between exchanging it for a different rezound or just straight up returning it and waiting for the nexus december 8th to come out.
There have been ALOT of reported problems with this phone from my bootlooping... dead pixels... horrible battery life... etc
Dont reboot it anymore. There is an app in the market called fast reboot.when you need to freshen the phone just push the icon and it wiill get all the free memory in about 10-15 seconds.
Sent from my Galaxy Tab 10.1
im supose to be locked into a phone for the next 2 years that i cant reboot because it bootloops?
I have seen several people with boot-looping issues.
I'm not one of them and I don't think it is rampant with this phone. As for dead pixels and horrible battery life - those issues are even fewer and far between.
I wouldn't say there have been ALOT; probably a normal percentage of definite defective units mixed with people being unfamiliar with "how things work" on a phone like this.
..... my $.02
yeah im returning it at VZW tonight for a new unit... if the second one has any issues at all that have been described on this forum so sorry i gave them two chances... returning and waiting for nexus
You also gotta realize your hearing about a ton of issues with the phone, because only people with issues are posting about it. The other 90% that dont have issues arent posting.
Anytime a new phone comes out about 10% of them are duds with the same problems you are describing. When the nexus comes out their forum will be full of threads about problems with that phone. Read thru the android forums and no matter what the phone, you will see complaints about the phone. i have been reading them for years.
Sent from my Galaxy Tab 10.1
I had the phone for about 7 hours three have been fighting loops. My temporary solution is to disable LTE and put my standard size battery in the device ? I don't know why, but I have a hunch that my specific device may be verry sensitive to heat issues.
I called Verizon and they show the boot cycling a known issue and that it was submitted to HTC.
The phone does not seem overly hot to Me so my hunch could be wrong
Sent from my ADR6425LVW using Tapatalk
Well my first Rez was a dud. It got as hot as 130F at one point! Returned it, now this second one will boot to a certain point then bootlop!! My evo never did this ****!!
Sent from my SCH-I510 using XDA App
Ok here's what I did. I shut down, removed the 4G sim and rebooted. It fully booted with no cell service of course. I went into the LTE switch and set it to CDMA auto. I shut down, re-inserted sim, booted up and it's working. Not sure if all that was necessary, but that's what I did...
Sent from my ADR6425LVW using Tapatalk
Ok phone getting better but loops still persist.I am giving up and getting a replacement in the am. BTW. THE tmo vibrant with stock headsets and voodoo sound 10 blows the beats gimmicks away.
Sent from my ADR6425LVW using Tapatalk
Bootloops = Heat
In my experience, Bootloops are a result of heat. The phone heats up (or the radio heats up), the phone reboots on the thermal warning, but the bootup time is not nearly long enough to cool down a phone that hot, so once the OS (or kernel) loads to the point where it starts checking for thermals, it sees a heat issue, and reboots.
I have this on my DInc which I was hoping to replace with a Rezound because of these bootloops, but of course I am going to have sit and see if this subsides (or what the Nexus people say) because ...
... you are right, you do NOT want a phone for 2 years which bootloops when you use it for 15 minutes. It is hell.
What is causing all the heat on your phone ??
Sent from my HTC
LTE 4G Rezound
deleted
I asked and called Verizon again. I found someone with a little more info.
it seems that an above average amount of devices where sent out with a corrupted OS.
The corrupt Rom is having issues with its signal acquisition and causing issues.
its heating up from consistently trying to cycle thru signal acquisition etc etc.
I kinda believe they have nailed the issue- as we booted up the device with no back cover on,and bam!- a perfect phone that functions without the reboots ( Obviously no signal),but it works.
I have a replacement coming Tuesday.
Hmmm i think mine has something like that. BUT i dont do it so much.
Had the same issue with mine last night. Removed Sim disabled all network services and replaced Sim and it worked when I enabled networks again. Mine has been set to cdma only also. I think it might be an issue when authenticating with Verizon that somehow crashes the phone.
chkn said:
I asked and called Verizon again. I found someone with a little more info.
it seems that an above average amount of devices where sent out with a corrupted OS.
The corrupt Rom is having issues with its signal acquisition and causing issues.
its heating up from consistently trying to cycle thru signal acquisition etc etc.
I kinda believe they have nailed the issue- as we booted up the device with no back cover on,and bam!- a perfect phone that functions without the reboots ( Obviously no signal),but it works.
I have a replacement coming Tuesday.
Click to expand...
Click to collapse
Let's hope that is the problem since I haven't had it and would hate to see it be a hardware problem. That is something that can be fixed with an update. I think phones are getting to thin for their own good. Cases problem don't help either.
For what it is worth, my phone is charging, streaming music, and I'm on the internet with auto brightness on. The temp is reading 100F. When I first got it, I was trying to kill the battery so I streamed Netflix over 4g and it got warm but never rebooted. Hope they figure this out for y'all.
Sent from my ADR6425LVW using Tapatalk
I got stuck bootlooping related to the fb chat widget. As soon as it would load, sense would restart and after 10-20 the phone started rebooting.
Non stop. I got it to boot with battery cover off (no reception).
Cover on, it would restart as soon as the lock screen was up.
Battery pull, no help.
So I did a battery pull, guessed volume down +power and choose factory reset.
No fb chat widget and no issues so far
Sent from my ADR6425LVW using XDA App
struggling radio = heat = reboot = still hot = reboot ...
Same as I currently have on my incredible.
They may be able to do something in software, but it is really hardware. the radio struggling to get a signal is not a software issue.
Sent from my ADR6300 using XDA App
So my bro's had an Atrix for a little over a year.
Some time back, it started exhibiting this behaviour where the whole screen would just become totally unresponsive.
Searching around, I see issues where people lose responsiveness with a fraction of their touch screen, or the entire screen starts spazzing out with all these presses and swipe actions the user did not enter...
...but his just seems to have these periods. He'll be stuck at the lock screen from anywhere between 1 minute and a whole day... I can usually get it to work with random rapidfire hardware commands... and when it works, it works completely for a certain amount of time.
Thing is, that's only temporary, and the touch-screen ends up going back to an unresponsive state.
Any clue what's going on, or how to resolve it?
What's the software is he currently on? Is the phone bootloader unlocked and/or rooted?
Sent from my ATRIX using the Premium XDA App
You know what's (not so) funny about this? All of the things that you think are causing this sound really complicated. Is my phone corrupt? hardware defective?? etc etc.
You know what I found it caused this behavior after numerous factory resets and weeks of research and tweaks to my phone?
The f-ing goddam screen protector.
Yep, that's right. The over-priced, highly (over)rated $20 iShields brand one. I know for a fact that was the cause, after I figured it out and started talking to other atrix owners (minus the liar fanboys that lurk in every forum saying "works fine for me derp!" whenever someone dares to suggest a product has flaws).
Problem immediately went away, forever. I've gone naked since May /11 without a single scratch. IMO screen protectors on gorilla glass is for people who wear a seat belt in a car wash. I'm not sure, but I suspect the problem happens when the screen protector starts to age, and/or when it gets really warm. I also suspect it's a problem with certain phones and the types of touchscreens on those phones not playing nice with screen protectors. Started happening on mine after just one month.
omnius1 said:
You know what's (not so) funny about this? All of the things that you think are causing this sound really complicated. Is my phone corrupt? hardware defective?? etc etc.
You know what I found it caused this behavior after numerous factory resets and weeks of research and tweaks to my phone?
The f-ing goddam screen protector.
Click to expand...
Click to collapse
That rant's nice and all, and I'mma let you finish... but there's no screen protector. He's been going bare gorilla all since he got it...
Voelker45 said:
What's the software is he currently on? Is the phone bootloader unlocked and/or rooted?
Click to expand...
Click to collapse
Just to offer some backstory, this started a couple months ago back when he just had the stock AT&T rom (2.3.X or 2.2.X I think? I can't recall clearly) During one of it's "working" periods (last week), I unlocked his bootloader and flashed it with CM9...
Probably won't mean much since the problem existed before I unlocked+CM9'ed it, but while it's not freaking out, I can give you some numbers:
• Model Number: MB860
• Android Version: 4.0.3
• Baseband Version: N_01.77.15P
• Kernel Version: [email protected] #47
• CyanogenMod Version: 9.0.0-RC0-olympus-KANG
omnius1 said:
The f-ing goddam screen protector.
Click to expand...
Click to collapse
Yeh, I have had this problem with screen protectors interfering with capacitive screens before, I am now using some really cheap protectors (5 for £3) and have had no such problems since and have a good bit of pocket money left .
TLRtheory said:
That rant's nice and all, and I'mma let you finish... but there's no screen protector. He's been going bare gorilla all since he got it...
Click to expand...
Click to collapse
ah ok in that case, I have nothing else, I'm only good for ranting. GL!
My touchscreen randomly does these freak outs and stops working:
Usually for me it is caused when the phone is really warm (like on the charger in the car) or when my hands are sweaty (also could just be the the phone is warm in this case as well)
Once it's done with its freak out, I turn off the screen (my power button still works) and clean off the screen with my shirt, wipe the sweat off my hands and turn it back on...everything is then fine.
Also, with my old phone (dell streak) if I kept the phone in my pocket with the screen facing towards my leg it would exhibit this behavior (probably again a case of the screen becoming really warm) but if I kept it screen out it was fine.
I have the same exact problem and have gone back to my Captivate because I couldn't figure it out.
Sent from my Touchpad using XDA
News on this? Here's my experience.
Any news on this, guys? I'm going insane. Here's my experience: I used to get these touchscreen-stops now and then but then they started getting more and more often. What I do to make them stop for a while is a clean restore, that is wiping boot, system, preinstall, cache, userdata with fastboot before installing a new ROM or restoring from backup. Whenever I do that, it comes back to life. If I flash a new ROM without all those wipes, it doesn't work. What sucks so bad is that, even though that fixes the problem, it's only temporary. It starts again after a few weeks. There is NO way this is hardware, and there's also NO way we can't find a solution for this!!!! Come on, guys!!! HELP US OUT, PLEASE!!!!!!!
Have you tried the raindrop fix? I was having similar problems and it worked for me.
Sent from my MB860 using xda premium
My screen has ghost fingers if my hands are even the slightest damp.
A buddy of mine had really bad touch screen issues and had to send back for warranty.
Sent from my MB860 using xda app-developers app
I'm having the same issue
I'm having the exact same issue. It sometimes works, sometimes doesn't. Anywhere from one minute to a whole day, everything you described exactly. No screen protector. I wiped it once and it worked temporarily, but it's back to the old sporadic unresponsiveness again.
I'm still not convinced that it isn't a hardware issue. I'm going to buy a T5 Torx Screwdriver and open her up and see if one of the connections is loose. Has anyone else done this?
I'll post tomorrow night with my results.
Here is a handy trick to determine if your digitizer it going out.
1. Find an appliance like a cable set top box, AV receiver or computer for example
2. Lay your phone face down in the warm air that emits from devices like this.
3. Leave it alone for about 10 to 15 minutes.
4.Pick your phone up and perform some finger swipe heavy tasks.
If you notice its a lot more sensitive like you remember when you first got it then you have a digitizer that is going bad. If nothing changes then its most likely software related.
Okay so I took it apart (removed the motherboard, disconnected the radio and 3 cables, then put everything back together. It's not fixed 100% but it's a lot more consistent than it was. youtube dot com/watch?v=kxuF_73YIIY
cjmillisock said:
Okay so I took it apart (removed the motherboard, disconnected the radio and 3 cables, then put everything back together. It's not fixed 100% but it's a lot more consistent than it was. youtube dot com/watch?v=kxuF_73YIIY
Click to expand...
Click to collapse
Could be the ribbon behind the digitizer, if its loose or moves it can kill all response to touch. You may have to replace your digitizer to fix this.
Sent from my MB860 using xda premium
I'm dying here
I opened it up like the video explained. Everything looked OK. I used a heat gun at 50 C to eliminate any trace of humidity and put back everything in its place. Then, I did a full wipe and a new ROM flash. STILL NOTHING!!! This phone is a little over a year old! This is not possible :crying: Any new ideas???? THANKS!!!!
pichualvarez said:
I opened it up like the video explained. Everything looked OK. I used a heat gun at 50 C to eliminate any trace of humidity and put back everything in its place. Then, I did a full wipe and a new ROM flash. STILL NOTHING!!! This phone is a little over a year old! This is not possible :crying: Any new ideas???? THANKS!!!!
Click to expand...
Click to collapse
I would also suspect the digitizer. I replaced mine for $45 (frame pre attached attached highly recommended).
The connections are very small, so there is much that can go wrong while doing this kind of brain surgery and the ribbons will rip easily.
Sent from my MB860 using Tapatalk 2
Same problem here. It is like some Ghost is operating it without my permission
Sometimes feels like is should hit the phone on the wall.
I know its not gonna help.
Anybody there who has solution for this
I just got my new DNA yesterday for a whopping $1.00 through my workplace, and a few hours after activating I started getting completely random hard reboots. The screen would lock up, go black, and commence restarting on its own. These became increasingly frequent but are still hard to reproduce and are frequent but random. No rhyme or reason. I did multiple factory resets, have unlocked the boot loader, flashed a new Rom, and am going to try an aftermarket kernel, but so far nothing has fixed it. They're still persistent and irritating, making the phone nearly unusable as a daily driver. Im more than likely going to have to exchange the phone, but does anyone have a clue what could be causing this? I'm so far beyond disappointed. I love the phone but this is unacceptable. If I can fix this without having to wait another half a week or more to get a replacement I would be more than happy to.
Sent from my HTC6435LVW using xda app-developers app
And to elaborate on my issue, when it freezes up, tgeres typically white flickering "tears" on the screen before it reboots. Whatever is currently on the phone freezes there and then it looks like tearing artifacts in the screen start to show up in a few spots before it reboots. I'm completely lost here.
Also, flashing a new kernel didn't help st all, so I'm out of options.
Sent from my HTC6435LVW using xda app-developers app
My phone is completely stock and some apps can lock up the device and cause a reboot. I can replicate it everytime. Walmart app is the worst one, evrrytime I set the store and return to the main screen, boom! It is exactly what you describe, looks like a jarbled mess or random tears.
Sent from my HTC6435LVW using xda app-developers app
Sounds like a problem with the phone. I don't think the stock ROM on the DNA suffers from random reboots. I would just exchange it.
That said, my wife's DNA (although not mine) did reboot a couple of times in over a month. She has all sorts of funky live wallpapers and other stuff running though.
Sent from my HTC6435LVW using Tapatalk 2
Unfortunately mine isn't simply app related. I put in an order for a replacement device so hopefully that will take care of it. It's gotten progressively worse over time and it was to the point that it would lock up on reboot instantly and would start running incredibly hot while frozen up. I'm positive there's a serious hardware defect in mine at this point. Hopefully the replacement fixes all this.
Hello! I have had my Galaxy S2 i9100 for a while now and have had all sorts of issues with it.
Most of them have been resolved, many through factory resets.
One problem that has been gone for a while but has returned, is that:
The phone shuts off/does randomly. Commonly when it gets a minor impact.
For a while it appeared that it was related to the battery moving and losing contact. I have however made sure that its snug and tight, and the phone still occasionally shuts off.
I have reset the phone several times and am running Stock ROM.
Could this be ROM related? Is there in that case a way to restore a clean install of the Stock ROM, if by any chance, old files from prior updates are causing this corruptness?
Sent from my GT-I9100 using Tapatalk
Replace USB board/port.
Is that the only possible reason to why this might be happening?
Sent from my GT-I9100 using Tapatalk
Blomberg said:
The phone shuts off/does randomly. Commonly when it gets a minor impact.
Click to expand...
Click to collapse
Do you mean it just power off immediatly without shutting down ?
I suggest you to clean gold contacts on battery and on phone. After that , you can try to put a piece of paper between battery and cover, just to test if you solve your problem if the cover help keeping battery in place.
Thank you sksbir, I actually did something similar. I cleaned the gold contacts on the battery with isopropylalkohol. Then i put a paperpiece between the battery and the bottom section.
I don't think it has shut down after that, but I am not sure, as I am so used to it by now.
Sent from my GT-I9100 using Tapatalk
Or change the battery with an original Samsung 2100mAh. I solved many problems with this change, unfortunately the battery drain is still present, but I think it's a problem of almost all the ROM not of phone