[Q] S2 suddenly shutdown and died after not long after enabling powersafe mode - Galaxy S II Q&A, Help & Troubleshooting

Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?

It's probably a software issue, JB has tons of bugs. What kinda advise do you want? You need to re-install the rom (and clear cache ofc) and if that doesn't work re-install the stock rom via odin and then install neatrom if you want. And just don't use power save mode until you get an update? It's useless anyway... You can also try another kernel, this seems like a kernel problem.

Power saving actually just have a few advantages like turning of un-needed things like haptic feedback and some other stuff which you could do manually, and the main power saving feature is that it limits the CPU to use only 800Mhz max, this might be having some issues with Apollo kernel (as it works fine with stock or stock based kernel like Philz), but Apollo is a powerful kernel and will let you manually adjust the CPU limits even at your preferred limits manually, so if you want to save battery just manually adjust the settings instead of using Power Saving mode.
Sent from my GT-I9100 using Tapatalk

Perphide said:
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
Click to expand...
Click to collapse
It may be a bug in that rom. try another rom

Thank you!
Thank all of you for the help and advise!
I will no longer use the powersafe feature and start using the Apolo kernel again, since that kernel gave me the best battery life.
It might have been a coincidence of course that my S2 died/didn't want to start up no more shortly after using the powersafe feature... however from all of the above advise it seems that I don't need that feature anyway so I feel safe to switch back to the Apolo kernel again with my new installed NeatROM SuperLite 2.4.
If the problem returns I'll be here to post it, it might still be a bug in the Apolo kernel of the NeatROM ... I am not sure. Time will tell, or not if it had to do with the powersafe feature which I won't be using any more.
Thank you all!

Related

[Q] The screen doesn't wake up | CheckRom RevoHD V4

Hi all, this is my first post, and i searched the forum with no luck. I have a CheckRom RevoHD V4 with the Siyah Kernel 2.6.1. The problem is that my screen won't wake up after some time that it's turned off. It doesn't happen always... it's seems a random behavior... The volume keys works because i can hear the sound of volume up and volume down, but the touchscreen, softkeys, power button and home button doesn't work at all and i can't get my home screen back. I need to remove the battery to reboot the GS2... I experienced this problem with te DarkNight kernel too. I tried to call my phone, i can hear the calling tone but the cellphone doesn't ring. I don't know if it's a rom related problem or it's a kernel problem. Hope someone can help me.
Ps: Sorry for my english
Hello I have a CheckRom v4 for my phone.i think that you to flash again with odin DarkNight kernel version 2.5.2 flash only kernel as a pda with odin
i tried to flash the new siyah kernel 2.6.4 trough CWM but not solved my problem... there is some difference between flashing trough odin an flashing trough CWM?
I have System Tuner for tweaking and set the kernel governor... i don't know if there is some incompatibility with this app and other apps like widgetlooker that need root permissions... really i don't know how i can solve this issue...
redirect11 said:
I have System Tuner for tweaking and set the kernel governor.
Click to expand...
Click to collapse
There you have your problem.
so are you sure that the problem it's related to system tuner?
redirect11 said:
so are you sure that the problem it's related to system tuner?
Click to expand...
Click to collapse
Probably. If you undervolt or underclock your phone to much, you wil get SOD's. That is basic knowlegde if you want to use those apps.
ah ok... but i don't use OC/UC or UV/OV... i only use this for change governors... but i have a question about SOD: the volume keys works in these cases? Cause mine works when display doesn't wakeup...
I'm having the same problem with this rom and kernel. I do not uv or oc. I left those settings alone.
It's really annoying and have left me missing calls because I cannot pick them up.

Wifi makes phone go crazy...

Hello awesome people
I`ve been looking for people with the same problem as me, but my problem seems to be opposite of everybody elses...
I have been using GoLauncher for a while, but decided to try apex, since i think golauncher has gotten to much bloatware lately. also decided to try a new sms program called Pansi, then the fun started... I tried to send an mms with pandi and the phone for the first time in a month rebooted... then after the boot, the phone suddenly started go into a freezelock everytime the screensaver came on, sometimes i could use the power on button to get the phone to restart or shut down. and after a while i could not get past the pin code screen, so i did a factory reset, installed the lastest official update, phone booted and everything was appearing ok, but no... Did some searching and found out that some that was having the same problem used the "#*0011* and select wifi and turn the power saver off. So no I got rid of the freezelock, but my wifi is all stupid, and disconnects me all the time saying that there is a poor connection even though the signal strenght is excellent. If i turn power saving mode on, the wifi works great, but the phone will freeze on screen unlock
I also used the Toolkit from Mark Skippen to root and maybe the fix was there but still problems, any help would be appreciated...
/chrtn
tl;dr
phone freeze with wifi power saving mode on
wifi not working when wifi powersaving mode off
GT-I9300
4.0.4
i9300XXLH1
3.0.15-554452-user
[email protected]#1
SMP PREEMPT sun may 13.....
build
IMM76D.I9300XXBLH1
Hi, I think i've got the same issue.
I had the i9300XXLH1 stock rom (no problem so far)
But then I used the mskip's Toolkit to root it (insecure ALE8 Kernel + CWM Touch recovery)
Then the wifi problems starts :
If wifi is on and connected to an AP -> ok
if wifi is on but not connected -> freezelock (be patient and the touchscreen will come back)
sometimes i can't get wifi working at all...
Any idea ?
Use CF (chainfire) root. It won't mess with the kernel that is supposed to go with the latest rom. Now you are using old kernel with new rom.
Hope this helps
Thank you, will try a factory reset full wipe and try again with chainfire
Sent from my GT-I9300 using xda premium
UXELLR said:
Use CF (chainfire) root. It won't mess with the kernel that is supposed to go with the latest rom. Now you are using old kernel with new rom.
Hope this helps
Click to expand...
Click to collapse
That did it thank You again for your help

[Q] Power Saving Mode Not Working

Hi guys. I really enjoy the Power Saving mode that comes with the stock samsung Rom. I find it to be very usefull, when it límits the cpu clock to 400mhz.
Now i am using the WanamLite Stock Deodexed Rom Xxemr2 (Which is a version of wanamlite that is simply the stock samsung rom, Deodexed and rooted). My Kernel is also a stock bases Kernel. But i noticed that after install this Rom, the Power Saving mode is not working. The toggle button Works, and i get a toast confirming that Power Saving mode is enabled. But when using the system monitor app, i see that the CPU is running on full clock. (oscilating up to 1.4mhz when i oppen big apps). This proves that Power Saving mode is not working. I tried changing the Kernel to Siyah Kernel (Which claims to suport Power Saving mode) but it still no diferente betwen enabled and disabled. Can anyone help me? Anybody knows a solution?
My opinion is power saving mode is useless. It slows your phone down for no reason.
Go to the Play Store and download yourself Clean Master and a battery saving app,
they are the most that would help, power saving will slow your phone down to much and
is not really necessary.
yurividal said:
Hi guys. I really enjoy the Power Saving mode that comes with the stock samsung Rom. I find it to be very usefull, when it límits the cpu clock to 400mhz.
Now i am using the WanamLite Stock Deodexed Rom Xxemr2 (Which is a version of wanamlite that is simply the stock samsung rom, Deodexed and rooted). My Kernel is also a stock bases Kernel. But i noticed that after install this Rom, the Power Saving mode is not working. The toggle button Works, and i get a toast confirming that Power Saving mode is enabled. But when using the system monitor app, i see that the CPU is running on full clock. (oscilating up to 1.4mhz when i oppen big apps). This proves that Power Saving mode is not working. I tried changing the Kernel to Siyah Kernel (Which claims to suport Power Saving mode) but it still no diferente betwen enabled and disabled. Can anyone help me? Anybody knows a solution?
Click to expand...
Click to collapse
Why are you double posting?
http://forum.xda-developers.com/showthread.php?t=2219081
i will ask a moderator to remove your first post.
First thread removed.
Please refrain from double posting in the future
Kind regards
Lady Android
Forum Moderator
squ89r97 said:
Why are you double posting?
http://forum.xda-developers.com/showthread.php?t=2219081
i will ask a moderator to remove your first post.
Click to expand...
Click to collapse
Sorry, my first post was with the title f*cked up by autocorrect... hehehe

[Q] NeatROM v6.4 Black Screen of Death

Hey guys,
I have a Samsung Galaxy S2 (GT-i9100) running NeatROM 6.4 (firmware: XWMS3) with Jellybean 4.1.2 with the kernel XWMS3-5.15.9-PhilZ. Basically I have been getting black screens of death while the phone's idling and not being used - the only way out is to hold the power and home button until it boots back up. I managed to fix the issue initially by swapping kernel and installing Dorimanx v8.43 instead and experienced no BSODs but the problem with the Dorimanx kernel is that I can no long use NeatROM's inbuilt call recorder then (which is a pretty nifty option really). Is this a hardware or software related problem? And is it fixable without changing the philZ kernel or if not, what other kernel can I use?
PS: The NeatROM installer also comes with these three kernels:
- XWMS3-5.15.9-PhilZ
- Apolo Light v4.14
- Apolo Regular v4.14
Should I re-install the ROM and pick another kernel to see if it fixes the black screen problem?
Thanks in advance,
Kyle.
Update: I have reinstalled the rom without the bloatware, didn't install apps like Freedom, Lucky Patcher and Aptoide this time and I haven't had this BSOD hot phone problem since. But now my SD card keeps getting unmounted and remounted several times and this does eat some battery. It wouldn't recognize my external card a couple of times and I had to take the battery out, then the card, clean and blow at it some before putting it back for it to work again. Dying SD card or hardware issue? I have moved my things from it and formatted it from the phone itself since - waiting to see if the unmounting/remounting problem happens again now.

Deep Sleep Issues, event wakelocks 0-8

Hey everyone. redoing my thread now that we have tried alot of solutions, hopefully someone has a vague idea of what we can do to my phone lol.
So then, my phone (redmi note 3 snapdragon) refuses to go into deep sleep no matter what combination I've tried.
Tried Combos
1. RR+ radon and agni
2. Miui 8 stable and dev preview (7.1.5 and 8.1.1.0)+ stock, radon, and neon kernel (flashing using miflash with unlocked bootloader official)
3. Cm13 latest nightly+ radon, stock, and agni
4. Nitrogen os+ nagato kernel (current rom)
All combinations we're tried with clean installs (factory data, system,cache and internal storage)
Hardware methods tried
1. Physically disconnecting fingerprint sensor (goodix)
now then, with wakelock detector, we can see im troubled with a 99% awake time, along with 100,00's of event wakelocks over 6hours, now event wakelocks deal with the actual hardware of the phone from what i've seen, which makes little sense to me because the screenshot i am attaching was just over an entire night of not touching the phone. so why it has any activity is bizarre to me. so heres what we have tried so far on my previous thread.
Tried methods of fixing event wakelocks
1. Greenify, force doze, wakelock blocker and blocking everything in frustration. deep sleep battery saver.
2. physically deleting events one by one (going into dev/input/eventx (x being wakelocks 1-10) after deleting some my display eventually stopped working, most likely because i just deleted the event that controls the lcd i assume. rebooting fixed the problem and remade the events in their directory so no harm done.
3. removing zram usage figuring it was a thrashing problem (saw a thread in the hd desire of the same issue. didnt help sadly.
4. flashing modem in radon thread, ended up making my phones earpiece not work for calls and still had the wakelocks.
5. disabling gps, along with auto brightness and auto rotate
so then if anyone needs any other information just let me know, currently using an iPhone for the time being so im desperate lol. but still id rather fix and find the problem then go for returning the phone. better to solve a problem for future people in my shoes then just thrust it away is how i see it. also someone bug the strix and darkstrix about this maybe they know the solution. anyway thanks for reading and i hope we can fix my phone soon
^Update^ now using epic rom 7.1.12 from the xda thread, still got wakelocks on stock without any other apps.
I have same problem in all versions of stock MIUI Rom. I too tried all sorts of combination but the problem remains. Finally I'm using RR Rom 5.7.4 (20161113 build) + radon Kernel. My deep sleep problem have been solved (though not 100%). Now my phone looses very little battery in standby time like 1-2% over a night. Before RR Rom I tried many custom Rom but had same problem. If you have not tried the ROM (RR Remix 20161113) I've mentioned above give it a try. Best Of Luck.
Thanks rj I'll install and post logs after work. Fingers crossed that it fixes my problem.
use the rom android 6.0.1 with module powernap , u can fix it !!
http://repo.xposed.info/module/net.jzhang.powernap
Small update: testing stamina mod currently with xposed. ressurection remix will be next only because xposed seemed a bit easier lol
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Then once try nexus rom i am getting good battery life in this rom too.
rjrulz007 said:
Then once try nexus rom i am getting good battery life in this rom too.
Click to expand...
Click to collapse
surer rj which one?
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
That happens to me when background data enabled . when i disable backround data through data usage settings , the battery backup gets better, but sure my social apps wont sync.
It seems the wakelock come from android system itself , go check logcat and you will get messages like "ANDR_PERF_RESOURCES FAILED TO APPLY PERFORMANCE" , the likes of "decided to move IRQ from cpu0 to cpu1" , and the likes of "FPC listener : waiting..." , thats all that i notice and thats happening every single milisecond on every MM roms i have tried so far....
Well when i used miui 7 LL global didnt get that much messages on logcat , but its LL ...
I guess the problem is related to source code , i dont know .
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
D4xel said:
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
Click to expand...
Click to collapse
yes sir still nothing
rohit4kk said:
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
Click to expand...
Click to collapse
hey dont worry man you'll be the first when we find an answer lol
Zaccary said:
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Click to expand...
Click to collapse
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
deltatux said:
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
Click to expand...
Click to collapse
thanks for the tip but we are running on airplane mode only at this point just to make sure we don't have more things to worry about battery drain. i appreciate the information though ^_^
Mine kenzo, tried all miui version, always the same.
sbor-si said:
Mine kenzo, tried all miui version, always the same.
Click to expand...
Click to collapse
I'm not alone!!!
Hey hopefully we find an answer buddy
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
sbor-si said:
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
Click to expand...
Click to collapse
i believe last time i tried 7.3.2.0 it gave me constant reboots and lagged quite a bit. but i also heard it was the best for battery so i can try flashing through miflash again after work. im also going to be trying this rom here https://forum.xda-developers.com/re...nzo-lldlm18-1-3m866beta-real-factory-t3375250. since it uses edl mode instead of fastboot so hey maybe that will knock something lose?
Well, right now I'm trying to get it working - without luck. I can flash 7.3.2. with miflash via edl without troubles, phone started normaly, all seems good, until "No service" for gsm signal. Bad luck. I think that modem version from that old flash is not compatible with hardware.
But it looks so good - Android takes 20% and Android system 6%...

Categories

Resources