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.
Related
I have a problem when I do the anchor network function on the phone so I miss good and I turn it off if I want to use it again and light it does not work gets stuck and I have to restart the phone to work.
Another problem is that the kernel siyah not work on my phone stays analisando the sd and therefore did not I get the external memory and clear the applications that were installed there. I tried to the last version of this kernel.
and I would like to have some aplicaiones as dln samsung and wanted to know how to install them.
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
eranyanay said:
I have a serious issue with both my I9100 devices.
it suddenly freezes and requires reboot. when i do it, it stuck on boot screen (Where the yellow triangle would be if using unofficial firmware)
nothing helps, only wipe data. once I wipe, device loads fine and starts working again.
I tought at first its rom/kernel related, I switched everything and even tried stock rom.
it keeps happening...today, I tried to swap batteries as one got empty, I took the battery out of the stocked-rom device (after turning it off) and then later when i switched it on, it had to be wiped.
same as with my other device.
Anyone has any clue what this is about?
Its became a big issue for me, I cant flash/wipe every few days...
One device is on Neatrom 4.4 lite, the other stock-everything, both 4.1.2
Click to expand...
Click to collapse
u can just rewert to stock ICS 4.0.3 firmware on both the phones and check for the issue (whether its firmware related or any hardware issue as such)
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
eranyanay said:
thanks for your help,
It did not happen on 403, tough it didnt happen on 4.1.2 for some while either.
what else would you suggest me to test?
Click to expand...
Click to collapse
1) with 403 for some time once again to ensure no issues of freezing.
2)then a different 4.1.2 stock/custom rom altogether to check for the same(freezing) issue.
stay for some time on those firmwares and see (may be one or two charge cycles).
3) do not install any mods on top of the firmware, just stay stock and see
One of the devices is already back to 403, while the second one on stock 412
the hardest thing to tell if 403 solves it or not, as it happens occasionally, once in a week or two.
I tried two different stock roms, so that would rule out #2.
The weird thing is that wiping data is enough.
data is separated from the rom itself, yet it causes the entire device not to boot anymore.
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!
I have been using Blisspop since early December with frequent [dirty] flashing to latest versions and occasionally get kernel panics or OOM issues causing the phone to go to a Green or Blue screen that only goes away by holding the "Down" volume and hard rebooting it.
I recently wiped my phone completely (apps, data, dalvik, etc) and flashed the latest ROM with (Blisspop 2.0; Build Date Feb. 7, 2015) with hope that the issue I thought was there would be corrected but the issue still persists through the new ROM.
This issue continuously plagues me and mostly get the Green screen with it saying "Apps Watchdog Bite!". This isn't a huge deal from me and I don't ever plug it into a laptop/desktop to debug the issue or find the root cause. I have just attempted to change the OOM Kill and Kernel Panic settings in sysctl.conf in hopes that the phone would just auto reboot instead of hang on the green/blue screen.
Is there any way to disable this debug mode and force the phone to auto-reboot instead? or has anyone experienced this issue on a consistent basis and has an alternative fix?
Thread with ROM and Gapps: http://forum.xda-developers.com/sprint-lg-g3/development/rom-rating-5-12-18-14-t2977726
Ive flashed an unofficial gt n7100 cm12.1 yesturday(7-06 build).
since sime error made the rom unbootable, i flashed a custom kernel called widzard kernel2.5
I'm appreciated with the great features and ui.
however i found out that when i plug the cable with my phone powered off, it boots up. It really bothers charging
also sometimes when charging(**only when charging**) my lockscreen(not a custom lockscreen) crashes or says to try unlocking after 30seconds then my phone suddenly reboots.
I think this is a problem with the kernel.
Guys tell me how to fix this problem!!!
I cant even recalibrate my battery!!!!!