Okay, so I have s2 i9100. I have installed neatrom lite version, it is jb 4.1.2. I have fully nuked phone before installing this rom and installed dorimanx kernel afterwards. By using stweaks i choose performance profile for my phone. Even though I have disabled animations from developers menu, and I do not use any applications which would eat a lot of processing power, my phone is very slow. It was not this slow before. I mean honestly, every single damn move is with at least a minimal lag, freeze or something. What the hell is going on here? Does JB 4.1.2 on S2 is supposed to be like that.
You guys, I need some tips from your experience write here. I really have like no time for testing roms and maybe you can help me out by recommending some kind of rom, which would not have **it load of bugs and would not lag as much as this one does. I heared about CM 10.2 4.3JB but I am afraid about bugs and all that, so I think it would be a better idea to stick with 4.1.2 or 4.2.2. So, any tips? I would really appreciate some. Thanks you guys.
I highly doubt it is caused by your rom, because almost every user is satisfied Neatrom (me included).
What kernel do you use? And what happens when you use another profile than Performance?
Donnie Sins said:
I highly doubt it is caused by your rom, because almost every user is satisfied Neatrom (me included).
What kernel do you use? And what happens when you use another profile than Performance?
Click to expand...
Click to collapse
Dorimanx kernel. Same things are happening.
Maybe my phone is damaged or something. A few days ago i dropped it and it was a little bit wet, but it did not turned of or anything and I can use it. About a few hours ago, something weird happened: phone was at idle, sleeping and out of nowhere that sound, when you start charging your phone appeared and backlight turned on... No reason, just happened.
Anyway, do you have any recommendations how to get rid of these issues?
Pull battery out now put in hot place in bowl of rice and leave it there for a week. Water damage...probably mb replacement now mate. Water and s2's dont mix.
I9100/I9300
Well, I used to have a rom that was causing me trouble after I dropped my phone. The battery for example was terrible after it. A full wipe and a fresh install of a new rom (although I'm pretty sure you've made a good choice with Neatrom) cleared these problems.. Maybe you can try that?
Edit: and if you try another kernel?
Related
I have two galaxy s2s. one is i9100 and the other one is i777 on at&t.
SoD happened once on each phone. The i777 was running stock gingerbread and the i9100 was running resurrection remix 1.9.1 with the siyan kernal I believe.
The screen just wouldn't turn on so I just pulled the battery out (is it safe for the phone?)
This doesn't happen often,well just once each on each phone as stated before, but it does bug me as it makes me think there's something wrong with my phones, and pulling the battery out doesn't seem like it's good for the phone.
I searched around the forum a bit and saw other people are having this issue as well. And not just the galaxy s2, but other phones too.
only sleep of death in almost 10 months of use is when i tried xwlp9.
so no its not common
It's fairly common yes, a lot of people running non-stock ROMs get this. I had this ~25 times on numerous Resurrection Remix ROMs, but since v1.9 I haven't had this issue fortunately. If it's causing you a big problem, try fixing permissions from CWM recovery, that seemed to make a big difference when I was having the problem.
SOD usually occurs when the kernel UV the CPU or GPU a little to much. Not every device is the same and not handle same kernels, UV values etc
Sent from my GT-P6810 using XDA Premium HD app
From the sound of it, it seems to be a software problem.
I got it on the i777 which wasn't running a custom rom. But I think it could be caused by that battery management app that I installed.
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
It's normally a firmware issue, or a conflict between an app & the firmware. You'd find it's pretty rare for an 'untouched' (I.E not modded) phone running stock firmware to have SOD's. And obviously if you're flashing custom firmware that's constantly evolving/changing, then sometimes you're going to get SOD's, tho with most well crafted firmware these are fairly rare.
I reckon I've probably had <10 in the 8 mths I've had my phone & I've been running non-stock firmware the whole time save for the week I got my phone, which is nothing when stacked up against all the mucking around I've with my phone.
Edit to add - One way you can test to see if SOD's you're having are possibly hardware related is to do a completely clean install of stock firmware & see if they still happen. If they don't, then it's obviously whatever firmware you were running. If they do, then it might be hardware-related. Re: your question about pulling the battery after a SOD, normally this shouldn't cause you any problems (it's sometimes the only way you can successfully reboot the phone).
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
victorator said:
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
Click to expand...
Click to collapse
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Ray_Grey said:
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Click to expand...
Click to collapse
Or just flash the newer build. No SOD there.
wanewon said:
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
Click to expand...
Click to collapse
How about this?
I answered your question. Read the edit I made to my post.
wanewon said:
How about this?
Click to expand...
Click to collapse
MistahBungle said:
I answered your question. Read the edit I made to my post.
Click to expand...
Click to collapse
Thank you for the answer.
Since it's kinda hard to recreate the SOD. I'll reflash the rom and kernal and do a wipe and see if the SOD still happen
victorator said:
Or just flash the newer build. No SOD there.
Click to expand...
Click to collapse
Victorator, forgive my ignorance, but are you saying i should just flash the latest build, XWLPD, onto my fone rather than re-rooting it using a different kernel (i.e. CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip) in order to stop the SOD?
Never faced such issues ever.
Sleep of death
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
MX 007 said:
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
Click to expand...
Click to collapse
bah bye
SOD
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
?
darkm1st87 said:
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
Click to expand...
Click to collapse
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
tkrokod said:
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
Click to expand...
Click to collapse
Hi,
I'm also trying to solve this problem, since weeks.
My observations:
SOD happens most on higher battery status (e.g. more SOD's at 80% battery then at 20%
The Phone gets hot after SOD and also before the SOD comes.
While loading the Phone SOD's happen more often
The battery status drains rapidly while SOD (cause of the resulting heat)
My SOD's are independent of kernel, rom, firmware or what ever.
I think it's a hardware problem, but I've no warranty and what to solve the problem without changing the mainboard. It couldn't be a really defective of an important part, cause the phone works apart of this SOD-problem.
Maybe we could find out together howto solve these anoying sod's
Hey. Im trying to solve the SOD problem myself cause its been happening every day and its really annyoing since the phone isnt even a month old.
I got the newest cyanogen mod running.
The phones model is GT-i9100
Android is 4,2,1
I still have warranty on it, do you think I should go back to stock, go exchange my phone where I got it and see if the new one has SOD too or should I just try fixing it first.
Also apps I use constantly : go launcher and dragonvale
I have a 8 gb micro SD inside as well, dunno if that could cause this.
Hello all,
I've been experimenting with custom roms lately. First I tried resurrection since it got lotsa attention and then I tried sensation, all causing the same problem.
I was lucky to have a NAND backup so I quickly went back to my stock rom. But now I am wondering why are these roms causing heating problems but not the stock rom? Interestingly, many people are using them without any complaints.
I thought this might be a problem with my phone. I contacted amazon and asked for a replacement, they were nice to replace the product even after 3 months! (kudos to them).
But now I'm wondering if this will solve my problem. Moreover, I sometimes had heating while charging the phone, bolstering my thesis that the phone is faulty. Any ideas anyone?
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
atifsh said:
you returned your phone for no reason!
If it works fine on stock, phone is fine.
Learn how to use custom roms, read how to flash each Rom in their thread.
Basically, modem and kernel are related to heat. Plus one needs to wipe his/her phone completely at least once before going to custom.
Click to expand...
Click to collapse
Lol calm down! I've not returned it, I am going to replace it. I've had heating problems with stock rom as well, especially while charging. I've changed the battery, thinking the problem was the battery but it didn't help at all. Also today, after being back to stock rom, it still heats up even with simple tasks. So I assume there is some kind of fault.
It's normal for your phone to heat up. If it heats up its perfectly normal because the cores are working fine. If u got battery heating warnings or any other phone heating warning thats the problem and you should investigate =D
Hi guys, I'm running the latest version of Slim Bean with stock modem XXLE8 and whatever kernel comes with Slim. I've noticed that there is a 1.5-2 second delay upon hitting the power or home button to the screen turning on and being ready to use. It's pretty annoying as you can imagine, I've actually figured out what the problem is, my phone is going to deep sleep too early and is taking up to 2 seconds to wake up, I wouldn't mind this if the phone has been left alone for 2 hours or so, but if I leave my phone for 5 minutes I shouldn't have to wait 2 seconds to unlock it. I came to this conclusion by using the app softlocker from the market, which disables sleep, and the lockscreen is perfectly fine with no lag, so should I try a new modem or a new kernel or is there something else I have to try to solve this issue?
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
DeadVirus said:
There are already some discussions about that problem:
http://forum.xda-developers.com/showthread.php?t=1687328
http://forum.xda-developers.com/showthread.php?t=1636680
It is a very annoying problem and I don't really understand how a top range device like the Galaxy S3 has such a problem.
I was hopping that the official Jelly Bean update would fix it... If it does not, I will contact Samsung (as should everyone who is annoyed by the wake up lag).
Click to expand...
Click to collapse
I've read both but neither seem to provide much of a solution. It is pretty ridiculous a phone like the S3 with such powerful hardware suffers from unlock lag. My HTC Desire Z used to unlock instantly... Kinda disappointing.
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
theslashy said:
I'm totally annoyed because of this problem, too.
isn't there a kernel or something where this doesnt happen??
Click to expand...
Click to collapse
I've been looking but can't seem to find one. The delay is about 1.5-2 seconds on Siyah, was about the same with YANK kernel.
jj92942000 said:
No issues with Omega v34, instant
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmmmmm I might flash a stock rom and check it out because I don't remember it happening when I was running stock, tho that was for a grand total of 3 days lol.
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
0semaj0 said:
This has always been a particular issue surrounding the Android software in terms of the optimisation of the OS...Keep in mind that kernels and ROMs with plently of adjustment may also mean plenty of variables, as small settings adjustments may alter and cause detrimental lags and issues as such. I use Phenomenal which is pretty good as there is little adjustments, disabled logs and undervolted...very good battery and response...I would recommend looking at something like that...unfortunately, should you wish not to root your device and keep it as standard, you may look at if there is an app that might be causing your the issue...but please note that slow unlocking/wake is because the device is in deep sleep.
Click to expand...
Click to collapse
sure, but i own quite a view other android phones and none behaves like the s3, not even the superlow-budget htc one v
i installed the omega 4.2 AOKP rom today, but the lag is there, too....i got back to arhd for now...
theres a app called softlocker, but with that the cpu never gets to deepsleep, my s3 gets warm and the battery drains badly
Hello,
I'd like to share some doubts about this rom, and get the anwsers if its possible. I know this should probably go on the rom's thread but I cant post on developing yet. Yesterday I installed XWLS8 on my phone but the result was definitely bad; I had huge battery drains and what I thought it was a media bug, media was consuming more than screen. I tried fixing some stuff by freezing what I thoght it was making this drain,but it didnt make it any better. Also read some things about compiling something that Google wrote on some code for 4.2, but that was dangerous for now, as Im completely noob.
Then I looked for near stock roms, and found NeatRom. I thought it was a good option. Flashed but same thing happened with media, I started thinking my phone had something wrong or that I dindnt flash correctly. Is this possible? I had this same media thing happening on both roms + overheating.
Hours later I was decided to apply my backup and go back to stock ics as what Im looking for is battery legth not extreme customization. But surprisingly NeatRom is not consuming that much; in fact it seems to go pretty well. Can it happen? Could it have stabilised or something similiar?Media has just consumed about 2% wich I consider normal.
Some more stuff I'd like to know: In the rom's thread theres posted a zip file with a fix for media scanner by Mr. Greg but its for the leaked rom. As theyre quite similirar I think, should I apply it?should I wait to see if I dont have any more problems with media stuff?
Finally, Id like to know if there's a kernel that consumes less battery on this rom, I've been considering dorimanx or siyah but I prefer waiting for someone who knows advice.
Thank you very much and sorry for wasting your time.
Hello, I'm new here..
and new too for using any custom rom..
Week ago tried the whole instructions for installation using
Latest build : RR ROM 5.5.8
Gapps-L-4-21-15.zip
Everything's working fine and great, thank you for developer..
But the thing is, why my SGS2 get OVERHEAT often every time there's application running?
Is it normal? Or did i do something wrong?
Thks.
ps: sorry if i don't get this post right.
GT-I9100 Lollipop
A lot of Lollipop custom roms have this issue......They tend to require a lot of power to run.....as these custom roms become more 'polished' battery usage should decrease, which will lead to the phone running cooler.....
In the long term, having a battery overheat, is not going to do it much good, and micro-electronics tend to dislike regular overheating too......
If you are worried about it, I'd suggest rolling back to a JB or KK based custom rom.....They do run cooler.....
http://i.imgur.com/rVnFwJM.jpg
I9100 tends to heat from back cover. As long your fingers arent burning, you are ok.
Sorry fella.....gonna disagree there.....
I had an S2 for 3 years, and it never suffered from overheating.
And to re affirm one of my other points.....
(Speaking as someone who knows/has experience in this field) Longterm overheating WILL damage batteries and micro electronics..........
(That is why an Xbox/PS4/PC/Laptop has a cooling fan)
http://i.imgur.com/rVnFwJM.jpg
We cant know what does OP mean with overheating, so its hard to say is his/her phone overheating or not. At least mine works on normal temperatures with CM12.1.
If OP says phone is overheating, we have to take him at his word and advise him accordingly......
We're not here to 'second guess' what is happening, we're here to provide advice/solutions......
http://i.imgur.com/rVnFwJM.jpg
Thank you sir @keithross39 & @Bapsu, both of you for explaining to me. Its not my battery that overheat.
Around the camera (top of the back of my sgs2) that quite often to get overheat everytime some apps/browser is running. Is it normal?
Thank you.
If I remember correctly, the location you are describing is pretty much where the CPU is.....If it's running hot, it's because you are asking it to work at the limits of what it was designed to handle.....
As I said in my earlier comment, my phone was fine for the 3 years I had it.....no heating at that location that I can remember. My current device (S5) sometimes gets too hot for my liking, but never my S2......
My advice......
Treat the heating as an 'early warning' sign, and rather than let it continue like that, do something to stop it happening.....
It'll be better for your device in the long term....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
If I remember correctly, the location you are describing is pretty much where the CPU is.....If it's running hot, it's because you are asking it to work at the limits of what it was designed to handle.....
As I said in my earlier comment, my phone was fine for the 3 years I had it.....no heating at that location that I can remember. My current device (S5) sometimes gets too hot for my liking, but never my S2......
My advice......
Treat the heating as an 'early warning' sign, and rather than let it continue like that, do something to stop it happening.....
It'll be better for your device in the long term....
Click to expand...
Click to collapse
Yess, i tend to give my s2 some time to cool down if that happen. Be cause i don't wanna overused it. Anw, thank you ?.
Hm, for my reference only. May i know what ROM+Gapps, PIT size your s2 currently using right now sir?
My S2 currently is running rooted, debloated stock......
I *never* changed the pit ratios, and the last custom rom it ran was Markox89's CM11 + the GApps recommended in that thread....
http://i.imgur.com/rVnFwJM.jpg