I need some help with this issue. My tablet is stock out of the box. I have been using it since last Friday. But today I turned it off then after an hour later I turned it back on, it gets stuck at x logo. I really dont know what issue is called? I have tried to restart the tablet several times by holding the powerbutton, but it is still stuck at X logo, and I have tried to use recovery mode in bootloading, but I get no command message everytime.
If you don't have a lot on your nexus and don't mind wiping then just hold power and vol up, which will data wipe your nexus. I know when I first started my nexus it would go to the welcome screen and then bootloop if I didn't click the next button fast enough. But you're saying you've been using it so dunno.
or you could fastboot then flash twrp and try to clear cache/dalvik and see if that helps
mmikeee said:
If you don't have a lot on your nexus and don't mind wiping then just hold power and vol up, which will data wipe your nexus. I know when I first started my nexus it would go to the welcome screen and then bootloop if I didn't click the next button fast enough. But you're saying you've been using it so dunno.
or you could fastboot then flash twrp and try to clear cache/dalvik and see if that helps
Click to expand...
Click to collapse
Thank you for replying. I tried like you said holding vol up+power button, but I got no command message.
david84us said:
Thank you for replying. I tried like you said holding vol up+power button, but I got no command message.
Click to expand...
Click to collapse
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Just as a side-note, I've had 2 Nexuses 7 (the older versions) and BOTH of them did this to me when updating to a higher version of Android. I swore like a madman as I had to hard-reset the device thus losing nearly all my data. If anyone reports that this happens with the new Nexus, it might be the deciding factor for me to not buy it... unfortunately...
dark2099 said:
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but I still get no command message screen.
david84us said:
Thanks, but I still get no command message screen.
Click to expand...
Click to collapse
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
dark2099 said:
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for all inputs, but I am new/noob about these stuffs, and im still able to exchange, so I'm going to exchange for another one. Thank you everyone who tried to help me. Have a nice day.
It's really easy to do. I had the same issue as you and a factory reset corrected it. Just make sure to follow the steps and everything will be fine
dark2099 said:
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Wugfresh has the best root toolkit for Nexus, period.
dark2099 said:
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I'm having the same issue since last Saturday when I picked it up. Still running stock and it just would not boot up and it seemed no one else was facing any problems. So I did fastboot unlock, it reset the device and cleared all data. Since then, I've been running stock, and I'm still facing the issue. I'm not sure if it's actually an issue with stock or not.
Just had this same problem on a brand new nexus 7 only a couple of days old. I really can't believe Asus/Google has these problems in 2013. Unbelievable.
Do you have a custom recovery installed?
Just happened to me very weird.
Sent from my Nexus 7 using xda app-developers app
Have you guys tried 1 click factory reset?
It happened to me with old. Exchanged it. And happened today in new one this time I was able to turn it off then try again and it booted. Started after 6 days of flawless use. Weird.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
Just happened to me...
I just had my SECOND one do this to me this morning. I bought the 2nd Gen Nexus 7 last week and it did this within an hour of using it (after an update). I took it back and got another one. This morning the second one did this after a simple reboot. I never had this trouble with my 1st Gen Nexus 7. I'm about to start trying the tips listed in this thread before I return yet another one. I'm wondering if this is the first reboot since the 4.3 update... maybe that is the issue.
Try Fully Charging?
Something similar happened to me on the first one I got, not sure if it will happened to the exchanged one since I only had it for a few days.
It happened after I shut it down one night, battery was about 80% or so. Next morning, I started it up and it actually loaded up fine but after a minute, it just rebooted, stuck at the X, then rebooted to the Google logo, over and over again. Did a factory reset and cleared the cache and still would get into the boot loop after 1 minute of successful boot up. Battery was about halfway when I decided to just charge it fully.
After the battery was fully charged, everything worked fine again. I suspect that the battery was run down next to nothing, but indicated that it was halfway. To me, that indicates a hardware issue so I exchanged it. I am wondering if they are using cheap batteries to keep the cost low. Not sure anyone else has seen this happened to them.
Anyway, if you watch the X, the colors move around, then suddenly stop after a while, it reboots again.
Same thing happened to me this moring around 3 a.m, shutdown and restarted and it was still stuck on the x screen. Tried wiping the cache from recovery and nothing. Had to do a factory reset in order to get passed boot screen. Tablet is working normally now.
Getting stuck on boot screen occasionally occur on 4.3. It seems like an OS issue not the hardware issue. I have seen it once or twice on my stock non-rooted Nexus 4 running 4.3. Never happened on 4.1~4.2.
On the other hand, if you have rooted your 4.3 device, the chance of ****up at boot rises dramatically. The toolkit is, while an admirable work, not perfect and you have no one but to blame yourself.
Related
T-Mobile phone 3 days old.
In the process of rooting my phone everything was going well. Phone went into recovery fine. I tried to do it again and just as recovery starts the Stock bootup takes over. If I continue to hold the volume and power buttons it just keeps vibrating over and over. When I let go the phone boots up normal.
I tried a factory reset to no avail.
The only thing I did was I installed CWM a second time. I thought I deleted them, but it still did this, so then I did the factory reset, wiping everything.
This is realy frustrating because I came from a Nexus One and will NOT own a phone with all of the garbage bloatware and T-Mobile restrictions.
Oh. One more thing when I go into Odin mode, it says I have 4 successful loads of clockworkmod. Even after the reset.
Estimated Prophet Hawk said:
T-Mobile phone 3 days old.
In the process of rooting my phone everything was going well. Phone went into recovery fine. I tried to do it again and just as recovery starts the Stock bootup takes over. If I continue to hold the volume and power buttons it just keeps vibrating over and over. When I let go the phone boots up normal.
I tried a factory reset to no avail.
The only thing I did was I installed CWM a second time. I thought I deleted them, but it still did this, so then I did the factory reset, wiping everything.
This is realy frustrating because I came from a Nexus One and will NOT own a phone with all of the garbage bloatware and T-Mobile restrictions.
Oh. One more thing when I go into Odin mode, it says I have 4 successful loads of clockworkmod. Even after the reset.
Click to expand...
Click to collapse
You are going to have to reflash back to stock. Need to download the odin program. Watch this video! It should help you out.
http://www.youtube.com/watch?v=nzo000J-cmU
Killing Zombies With My Samsung Galaxy S2
darkside79 said:
You are going to have to reflash back to stock. Need to download the odin program. Watch this video! It should help you out.
http://www.youtube.com/watch?v=nzo000J-cmU
Killing Zombies With My Samsung Galaxy S2
Click to expand...
Click to collapse
That link is not for the tmobile version but it should still help you out! For a complete guide on going back to stock.just search the developers forums. Good luck!
Killing Zombies With My Samsung Galaxy S2
I never rooted it!
Bump thread
Are you letting go of the power button when you see the samsung symbal?
Sent from my SGH-T989 using Tapatalk
No. I'm holding down till recovery pops up but it never does.
That video doesn't help. The first thing he does is settings>development. There is no development section in settings. I know there is a debugging toggle in privacy, but it looks completely differenct.
I've tried everything. tried doing everything again and now it doesn't even recognize that there is a recovery on my phone. I really need some help here. If i can't root this phone I don't want it.
Estimated Prophet Hawk said:
That video doesn't help. The first thing he does is settings>development. There is no development section in settings. I know there is a debugging toggle in privacy, but it looks completely differenct.
I've tried everything. tried doing everything again and now it doesn't even recognize that there is a recovery on my phone. I really need some help here. If i can't root this phone I don't want it.
Click to expand...
Click to collapse
Sorry was trying to help. You need to get into download mode and use odin to flash stock recovery! Lots of forums about how to do that.
To put your Tmobile Galaxy s2 phone in recovery mode.
1 ) Turn your phone off. Power it off
2 ) At the same time, press and hold volume up and down and power at the same time. Your phone will come on.
3 ) Keep holding even after the vibration.
4 ) When you see the first SAMSUNG white text, let go of the buttons.
Killing Zombies With My Samsung Galaxy S2
These links will help you. Good luck!
http://forum.xda-developers.com/showthread.php?t=1332103
http://forum.xda-developers.com/showthread.php?t=1311229
Killing Zombies With My Samsung Galaxy S2
Estimated Prophet Hawk said:
No. I'm holding down till recovery pops up but it never does.
Click to expand...
Click to collapse
Lol there's your problem.
Sent from my Hercules using XDA App
I know you were trying to help and it's much appreciated. Using the above method does NOT work, it just blinks and vibrates over and over, then after about a minute, I give up and it boots up normal.
jordanishere said:
Lol there's your problem.
Sent from my Hercules using XDA App
Click to expand...
Click to collapse
Damn! I feel really stupid!
Estimated Prophet Hawk said:
Damn! I feel really stupid!
Click to expand...
Click to collapse
Its ok. Happens to the best of us.
Sent from my Hercules using XDA App
Try letting go of power when you see the Samsung logo come onto the screen. My phone wont go into recovery untilled I do either. It just Vibrates. So hold all three untilled you see the Samsung logo then only release the power button.
Sent from my SGH-T989 using xda premium
Or try to boot to reboot to recovery using adb.
Sent from my SGH-T989 using xda premium
as title says. last night I was simply watching a movie when i noticed the handset was very very hot, which is weird as it wasn't doing anything too stressing, i figured id let it cooldown abit, not two seconds after the video stopped, the audio went all messed up. I turned it off manually, and it restarted all normally. it happened again, although it wasn't particularly hot, however this time I did not manually restart it, I figured id wait to see if it sorts itself out. Instead it turned off. And it refuses to power on, charge or even go into boot. No idea, what's wrong.
Running on Leedroid OneXtreme 6.4.
shamsul007 said:
as title says. last night I was simply watching a movie when i noticed the handset was very very hot, which is weird as it wasn't doing anything too stressing, i figured id let it cooldown abit, not two seconds after the video stopped, the audio went all messed up. I turned it off manually, and it restarted all normally. it happened again, although it wasn't particularly hot, however this time I did not manually restart it, I figured id wait to see if it sorts itself out. Instead it turned off. And it refuses to power on, charge or even go into boot. No idea, what's wrong.
Running on Leedroid OneXtreme 6.4.
Click to expand...
Click to collapse
can you go through adb,fastboot...?responds to PC when is on USB???LED lights when is in the charger?
If not, you can not through the PC...no response then.....
Unfortunately your motherboard is dead...
absolutely nothing, no flashing led, nothing when connect to pc/laptop. no response to anything.
shamsul007 said:
absolutely nothing, no flashing led, nothing when connect to pc/laptop. no response to anything.
Click to expand...
Click to collapse
...
then I'm sure you lost the motherboard...brick your phone...warranty period .... good luck
i have same problem
mehrshad said:
i have same problem
Click to expand...
Click to collapse
Got that twice with ma HOX...trust me...just plug on wall charger and leave it for a while (30mins or so) and when LED starts to flash, try to boot your device again.
i will try
This is weird but yeah I left in charge for about 12± hours, started flashing about a few mins ago and it's working perfectly. Pretty sure my phone is possessed. So yeah leave it in charge until it flashes.
Btw I'm not doing much, and it's already getting a bit warm, anything I can do to make my phone handle more? Is there a way to under clock this?
Sent from my HTC One X using xda app-developers app
ok i will put in charge from now till next 12 or 13 hours
i hope to fix it
thanks
do a full wipe fastboot erase cache and re flash a rom something is doing something naughty
Sent from my HTC One X using xda premium
mehrshad said:
ok i will put in charge from now till next 12 or 13 hours
i hope to fix it
thanks
Click to expand...
Click to collapse
Good luck! Let me know if it starts working, we could have some sort of alternative medicine on our hands here.
Sent from my HTC One X using xda app-developers app
it's in charge about 13 hours
nothing change and it doesn't flashing led
HELP
No idea then, motherboard may be dead if that's how unresponsive it is. If you have warranty send it off for repairs. Can you get into recovery? How about plugging it into a laptop/computer?
Sent from my HTC One X using xda app-developers app
that sounds very bad
Has anyone tried this?
I had the same problem, no warranty because I unlocked it. Got it back, and found this topic.
Note: It can happen you need to try different pc/notebooks before it charges. I had to switch to 3 different pc s.
http://forum.xda-developers.com/showthread.php?t=1658084
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
its done it again, heated up, now its completely frozen, just gonna have to go through the whole process again. the overheating issues with this phone is ****ed up.
Amicushia said:
Has anyone tried this?
I had the same problem, no warranty because I unlocked it. Got it back, and found this topic.
Note: It can happen you need to try different pc/notebooks before it charges. I had to switch to 3 different pc s.
http://forum.xda-developers.com/showthread.php?t=1658084
Hope this helps.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Do not talk nonsense, do not lose the warranty if the unlocked bootloader, but this board is dead aniway , nothing can see. Send to the service and solve the problem.
JohnnyBlack10 said:
Do not talk nonsense, do not lose the warranty if the unlocked bootloader, but this board is dead aniway , nothing can see. Send to the service and solve the problem.
Click to expand...
Click to collapse
Oh yes it does. I Fixed it with that script after i got it back from HTC.
Sent from my HTC One X using XDA Premium HD app
First time I need help, and it's a big one and hope it a positive result.
I come from viper 2.1.0
I wiped 3 times everythnig. Installed CM10 v8. then google addons, than entered fastboot and instal boot.img than erased....
Booted into android made preliminary input. started to download files and restored my old apps from google play. Whet to settings than from settings I pulled down status bar.
HOX frozze and than I presed the power button and thas' it.
NOW it does not wake up, even if I put the power cord in no lights go ON, nothing. It's like a BRICK.
Anyone any ideas.
you guys think if I send this to reapir and play stupit that thay will now that i had unlocked bootloader
Okay so ive been running jmt v8 for about a week on my phone and everything was running great. Then yesterday morning my phone became very slow and unusable. Then i started getting the error message acore system has stopped working and the phone would randomly restart and then it would start vibrating then stop then vibrate again and so on. So i insalled a new rom and i stopped getting the core system has stopped error but i am still getting the random reboots. And the screen also wakes up by itself. Please any help or suggestions would be greatly appreciated.
Sent from my cm_tenderloin using Tapatalk 2
I just had this fixed. There's something wrong with the power sensor, especially if it tries to boot the second you put the battery in without touching the power button.
Unfortunately you've been rooted now and because of the issues, you can't flash stock and reset the root count. So you can't sent to your carrier.
Fortunately, http://www.mobiletechvideos.com fixes EXACTLY this for $35 minus shipping it to them. I got my phone back today and it's just the way it was ROM wise and all my files are there and the issue is fixed.
This is a pretty common T989 issue.
Justananomaly said:
I just had this fixed. There's something wrong with the power sensor, especially if it tries to boot the second you put the battery in without touching the power button.
Unfortunately you've been rooted now and because of the issues, you can't flash stock and reset the root count. So you can't sent to your carrier.
Fortunately, http://www.mobiletechvideos.com fixes EXACTLY this for $35 minus shipping it to them. I got my phone back today and it's just the way it was ROM wise and all my files are there and the issue is fixed.
This is a pretty common T989 issue.
Click to expand...
Click to collapse
That's exactly my problem but are you sure this company is reliable?
Sent from my cm_tenderloin using Tapatalk 2
And can you also give me the link to the exact thing you ordered because i couldn't find it on their site, thanks !
Sent from my cm_tenderloin using Tapatalk 2
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile-power-button-repair/
And yes, I was sceptical too. Josh, the owner, is reachable by email and answers pretty quickly and did an amazing job repairing my phone.
You Can Boot into Recovery? Darkside Wipes, Flash another Rom, Dalvik Cache wipe,Format System,Fix Permissions.
Dennisalex said:
You Can Boot into Recovery? Darkside Wipes, Flash another Rom, Dalvik Cache wipe,Format System,Fix Permissions.
Click to expand...
Click to collapse
I can boot into recovery but its tricky because I have to press the buttons perfect or it'll just reboot. I believe the problem is with the power button and ill probably get it replaced.
Sent from my cm_tenderloin using Tapatalk 2
I have same problem last month, send the rooted phone to Samsung. After 15 days .I get back my phone for free.
I hope this can help you.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
For anyone with key issues and need to get into recovery or download mode there are adb commands that do this. We get too comfortable with apps and forget about the manual way of achieving a lot of the same tasks that apps provide for us.
From a command prompt:
adb reboot recovery
adb reboot download
playya said:
For anyone with key issues and need to get into recovery or download mode there are adb commands that do this. We get too comfortable with apps and forget about the manual way of achieving a lot of the same tasks that apps provide for us.
From a command prompt:
adb reboot recovery
adb reboot download
Click to expand...
Click to collapse
Thanks I will be trying this out.
Sent from my cm_tenderloin using Tapatalk 2
hey guys. after the ics update my phone started to lock up and its not rooted. now all of a sudden when i put the battery in it it vibrates once then starts to load and gets about half way and stops. then it turns off and just vibrates a few seconds and vibrates but the screen never shows anything. tryed using just a usb with the battery out and it skips the load screen and automatically starts vibrate looping. the power button seems stuck but i dont think i can fix it any ideas?
Hey everyone! I have a similar (but not quite the same) problem. Every now and then my phone "tells" me to restart it for maximum performance. Every time I restart or just turn on my phone it goes through the boot cycle, including a message that says "android is upgrading" (I got the ICS upgrade from Kies prior to rooting my phone). Then, all of a sudden, the phone doesn't work, and it starts the boot cycle all over again. This happens several times in a row, which for me is a safety issue because I'm not able to call Big Jon (my husband) to get me from the train late at night. Any fixes for that? Thanks.
sparkie6point0 said:
Hey everyone! I have a similar (but not quite the same) problem. Every now and then my phone "tells" me to restart it for maximum performance. Every time I restart or just turn on my phone it goes through the boot cycle, including a message that says "android is upgrading" (I got the ICS upgrade from Kies prior to rooting my phone). Then, all of a sudden, the phone doesn't work, and it starts the boot cycle all over again. This happens several times in a row, which for me is a safety issue because I'm not able to call Big Jon (my husband) to get me from the train late at night. Any fixes for that? Thanks.
Click to expand...
Click to collapse
You may have to run fix permissions in recovery are you rooted
Sent from my SGH-T989 using Tapatalk 2
Warranty exchange it. Known problem
Sent from my SGH-T989 using xda app-developers app
Same problem
And the vest part is that i can't replace it cause i live in India
Sent from my SGH-T989 using xda app-developers app
Damn! Just found this thread...sounds like what my phone started doing today!!
I was clicking around on gmail, then back to home screen, the camera FLASHED all by itself without me doing anything, then started the boot loop thing. Clicking the power button only made it worse. Finally was able to get into recovery via TWRP...but that was weird too. I did a factory reset/wipe and was going to reinstall The Sith ROM that I was running, but it just rebooted and loaded up The Sith anyway and it should have been cleared. I then tried to restore back to Beastmade ROM, restore was very quick and said successful but it booted back to Sith.
Now the power button is hyper sensitive! All I have to do is brush the power button and it will light up the screen. Touch it too long and it will bring up the boot menu. I'm afraid to actually CLICK the button as it might go haywire again.
WTF is going on!? This all seems really odd that it's going down with some of these new ROMs being released. I wasn't even touching the power button when all this started. The weird clicks and flashes didn't sound good when it was all going on.
Has anyone tried flashing back to and OLD rom to see if it will fix it?
change settings to interactive/deadline
I've had they Hercules for just over a year now but have only been using it for the past four months. I have only downloaded educational apps. However, yesterday i was not using it and came back to find it vibrating every 2-3 seconds. I removed the battery and left it out for an hour. When i replaced the battery, the phone began to reload but stopped during the boot,made a noise I've never heard before and began to vibrate as if going into recovery/download mode. I have been running ics for the past 4 months. The phone does not boot at all and is very frustrating . I have also tried charging it with no luck. Can anyone assist me with this problem??
sounds like you have the dreadful power button fail it gets a little jammed up try sticking a toothpick or something skinny in there and wiggle it a bit see if that works for you if not check if your still under warranty are you rooted or stock ICS?
u have a bad power button. try unsticking it.
Agreed. A friend had a similar issue and his power button was stuck.
I'm rooted and the warranty is up
Sent from my GT-P5100 using xda app-developers app
did u try fixing the button? if not you'll have to pay to get it repaired
So it appears that it's something wrong with the chipset...
Sent from my GT-P5100 using xda app-developers app
Samz1 said:
So it appears that it's something wrong with the chipset...
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
Literally your power button is stuck.
Samz1 said:
So it appears that it's something wrong with the chipset...
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
Strange enough this just happened to me 10 minutes ago. I did manage to get the phone to boot after slapping the hell out if my power button which gave me the only means to get into recovery so now I can comment from experience. Ive been running pac for 3 weeks. Just yesterday my phone started doing really weird ****, dont know if it's just coincidence, calls would go through to random people, every time I clicked gallery I got a random reboot, I couldnt call voicemail, and trying to change wallpapers gave a reboot. Today I was changing a wallpaper and boom random reboot then began the loop and vibrating. A few things I noticed while this was happening, if I attempted to go into recovery the samsung splash screen appeared followed by the stock kernel splash( samsung and the blue bar at the bottom) which made me believe it wasnt the power button but indeed rom or kernel problem, also my led flashed once while going through the vibrate loop and I know the power button has nothing to do with that. I did manage to get pac to boot about 4 times by slapping the hell out of my power button but it went back to the loop after a few seconds so the next time I managed to get it to boot I held the power button and booted to recovery. Once I was able to get in to recovery I restored a liquid smooth back up. Ive powered the phone off and on with no problem. Now I'm just waiting to see what happens through out the day. I was running pac with cerux when this happened. I truly believe this is not a hardware problem at all until I get it again with another set up. If you need help I getting your phone to boot I could possibly be of assistance so pm me unless you want to keep getting responses from people who haven't experienced this at all. This was the single most scariest experience Ive had since I ve been flashing, even worse than my brick because I knew I bricked immediately.
Hello, I am running unofficial Cyanogenmod 10.1 on my DHD and it has been working fine up until today.
This may have started when I took a picture with the phone this morning. The camera flashed 3 times, even though I hit the "take picture" button once. Then the phone was hotter then usual and the battery drained faster. Once the battery was gone, I plugged the phone in to a power source, let it charge for a bit, and turned the phone on. It continually plays the CM boot animation until it runs out of power or has the battery taken out.
Any ideas on how to fix this, or boot into recovery for that matter? Has anyone else experienced something similar?
Hi. My little brother had a similar problem where his phone was working fine and then got stuck on the logo probably cos of a virus or something. So what I did was just take out the battery. Leave it out for about a minute. Put it back in. Boot into recovery. Then wipe data/factory reset. Then reboot your phone and see what happens. Hope it helps. Good luck.
Sent from my Samsung Galaxy Ace 2 GT-I8160 running Cyanogenmod 10.1 Nightly using xda app-developers app
Have you tried rebooting with adb reboot bootloader or adb reboot recovery? Have you tried pulling the battery, then holding power and volume-down?
TellaReese said:
Hi. My little brother had a similar problem where his phone was working fine and then got stuck on the logo probably cos of a virus or something. So what I did was just take out the battery. Leave it out for about a minute. Put it back in. Boot into recovery. Then wipe data/factory reset. Then reboot your phone and see what happens. Hope it helps. Good luck.
Sent from my Samsung Galaxy Ace 2 GT-I8160 running Cyanogenmod 10.1 Nightly using xda app-developers app
Click to expand...
Click to collapse
Factory reset worked. Thanks.
Your welcome. By the way. You should download setCPU to limit the amount of power that goes to your phone at a certain point in time. Because most of the time our phones use too much power especially when not needed mostly on custom ROMs. And this could lead to all sorts of problems. Stay safe yo
Sent from my Samsung Galaxy Ace 2 GT-I8160 running CyanogenMod 10.1 Nightly using xda app-developers app