Hopefully somebody can shed some light for me.
It does not matter which Custom Kernel I try my SGS 2 suffers from random reboot and lockups also sometimes the battery will drain completely in a matter of minutes.
It is getting quite frustrating I have tried Siyah and NEAK numerous times with the sane results.
This is always from a fresh install.
It happens on multiple Roms CM9 AOKP and Foxhound (I am using the correct Kernel)
Is there a stable
I am not overclocking or fiddling with any settings either ?
Sorry misread
Sent from my GT-I9100 using xda premium
lordjubblydave said:
Hopefully somebody can shed some light for me.
It does not matter which Custom Kernel I try my SGS 2 suffers from random reboot and lockups also sometimes the battery will drain completely in a matter of minutes.
It is getting quite frustrating I have tried Siyah and NEAK numerous times with the sane results.
This is always from a fresh install.
It happens on multiple Roms CM9 AOKP and Foxhound (I am using the correct Kernel)
Is there a stable
I am not overclocking or fiddling with any settings either ?
Click to expand...
Click to collapse
Try flashing a completely different rom such as Resurrection Remix, Paraandroid, RebelROM etc.. and leave the stock rom see how you go.
Make sure do a full wipe
/wipe data/factory reset
/wipe data
/wipe dalvik cache
/format system
/format emmc
Then reflash the ROMs accordingly.
/wipe cache
/wipe dalvik
See how you go from there..
Also it is always good to check what is going on in your system by using Better Battery Stats.
Check task manager for application running in background and kill what you dont need.
At the end you may want to use Titanium Backup to permanently stop and/or remove unwanted services.
EDIT: did it also happen on any of the official ROMs? If so you may consider hardware (battery?) malfunction.
Related
i m using darkside Rom ,and my phone reboots almost in every hour, i am new to android please solve my problem ,its very annoying,thanx!
Ahmed Zahoor said:
i m using darkside Rom ,and my phone reboots almost in every hour, i am new to android please solve my problem ,its very annoying,thanx!
Click to expand...
Click to collapse
gingerbread 2.3.5
have you tried to flash the rom again to c if thats the problem
Hi there,
1. Did u do a full wipe before installing the new rom?
2. You could try installing faux123 1Ghz kernel LINK use "Enhanced Stock Kernel, Max @ 1.0 GHz". Install the one for GINGERBREAD
Link to Faux123 1.0 GHz kernel
[ Installation procedure: ]
[ CWM Method ]
1. reboot to CWM
2. Clear cache
3. install zip from SDcard
4. Reboot
Hope this helps
P.S.: "Wet Dream" is the new version of "The Darkside" might be worth to take a look
Grtz
Faux kernel will prevent boots but will erase every widget at every reboot...
I has the best results with the stock intl kernel (see GingerMod Rom). I don't have reboots anymore...
Sounds like the rom didn't install properly, I'd go through the wipe and factory reset/dalvik once again and reinstall. Just make sure to do a backup just in case it backfires.
DannyBiker said:
Faux kernel will prevent boots but will erase every widget at every reboot...
Click to expand...
Click to collapse
That's just not true. I've used both .23 and .24beta kernels and the widget thing rarely happens. It does happen, but not on every reboot.
troycarpenter said:
That's just not true. I've used both .23 and .24beta kernels and the widget thing rarely happens. It does happen, but not on every reboot.
Click to expand...
Click to collapse
Hey, do you know where I can find faux123's 0.24 beta kernel? I looked but couldn't find it. Thanks.
mabe try differnt Kernal too
Sent from my MB860 using Tapatalk
Ahmed Zahoor said:
i m using darkside Rom ,and my phone reboots almost in every hour, i am new to android please solve my problem ,its very annoying,thanx!
Click to expand...
Click to collapse
As has been already mentioned, make sure you do a full and proper wipe of your phone before flashing roms, but another problem could be that you're being too extreme with undervolting. Try reducing your undervolts if you have been undervolting. Or, if you have an extreme overclock kernel, consider lowering clock speeds because each phone is different, and some (even ones of the same type) can't handle as high of clock speeds as others. But, I suspect that your main problem is that you didn't follow the proper steps before flashing.
1. Boot into recovery (hold the volume down button while booting, then press down until you see android recovery, and then press up)
2. Do a factory reset
3. Clear cache partition
4. Clear dalvik cache
5. flash the zip
Note: factory reset will erase all your data, so backup any files you want to keep before doing so.
To flash a new kernel, do what denbeutels said, except you should clear dalvik as well. Android needs to recompile certain things to optimize them for the new kernel, so it's a very important step.
Atrix_Owner said:
Hey, do you know where I can find faux123's 0.24 beta kernel? I looked but couldn't find it. Thanks.
Click to expand...
Click to collapse
Are you following the faux123 kernel thread in development?
http://forum.xda-developers.com/showpost.php?p=22178618&postcount=2965
Ok, after running a few days on the new faux 0.2.4 1.45GHz kernel, I've experienced quite a few reboots as well (ok, an order of magnitude more than before). Right now I have gone back to faux 0.2.3 1.3GHz and haven't seen any problems yet. I was mainly getting reboots during undocking (all dock types), but also sometimes during normal use. And I'm talking about 3-5 reboots throughout the day.
Edit: And of course, as soon as I posted this, I got another reboot (this time while using webtop in the lapdock and simply closing a Synaptic window). Next I'll have to start tracking down anything I installed recently that may be doing this.
I was running UnNamed v2.2.1 and flashed the Siyah Kernel. However, after flashing the new kernel, in Settings > About the kernel version doesn't display that its Siyah but the CWM does change. Does this mean the kernel is not installed?
I assumed it was installed so I flashed the Init.Doh script. After it installed, my status bar was missing.
Since everything was messed up, I ran the Init.Doh uninstaller and tried out a new rom.
Did a factory reset, wiped cache and Dalvik cache, then installed SHOstock. Within 5 minutes, I lost signal.
Flashed back to UnNamed, but the signal loss was consistently happening. So I formatted system, did a factory reset, wiped both caches and installed SHOstock again.
As of now, I constantly lose signal. Tried flashing compatible modems but nothing is working. Does anyone have any idea of what to do?
I use CPUspy to see whether or not a specific kernel flashed successfully. As far as he signal loss..no idea sorry. I would start from scratch and flash bts and go from there maybe..
Sent from my SGH-I777 using xda premium
I would say the signal loss has nothing to do with the phone but your area if it happens on multiple roms
And the cwm is supposed to be different on siyah, it flashed fine and the kernel version in about phone should not change, changing your rom was silly
Sent from my SGH-I777 using XDA App
Nick281051 said:
I would say the signal loss has nothing to do with the phone but your area if it happens on multiple roms
And the cwm is supposed to be different on siyah, it flashed fine and the kernel version in about phone should not change, changing your rom was silly
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Thanks for your replies. I think my post is confusing so I'll try to clarify.
Signal was prefect on UnNamed. After flashing Siyah and the Init.Doh script, the status bar went missing.
So I did a factory reset and wiped everything before installing SHOstock. When it booted up, my phone kept losing signal. So I wiped again and went back to UnNamed but the problem persisted.
I'm wondering if the problem is caused because I was never sure if Siyah flashed properly. In Settings > About Phone, the kernel version never said it was Siyah. BUT my CWM changed to the Siyah version. However, even if this was the case, I don't know why the signal problem continued after wiping everything and formatting /system.
dngen said:
Thanks for your replies. I think my post is confusing so I'll try to clarify.
Signal was prefect on UnNamed. After flashing Siyah and the Init.Doh script, the status bar went missing.
So I did a factory reset and wiped everything before installing SHOstock. When it booted up, my phone kept losing signal. So I wiped again and went back to UnNamed but the problem persisted.
I'm wondering if the problem is caused because I was never sure if Siyah flashed properly. In Settings > About Phone, the kernel version never said it was Siyah. BUT my CWM changed to the Siyah version. However, even if this was the case, I don't know why the signal problem continued after wiping everything and formatting /system.
Click to expand...
Click to collapse
See below...
Coreym said:
I use CPUspy to see whether or not a specific kernel flashed successfully. As far as he signal loss..no idea sorry. I would start from scratch and flash bts and go from there maybe..
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
CPUSpy displays large amounts of information not displayed by Settings->About Phone.
Although I would've expected Siyah to cause a version bump to 2.6.35.14... odd
Time without signal is a known gingerbread bug, if that's what you're referring to signal loss. It doesn't affect your battery life, just the android battery stats is all around messed up.
The big solar flare has a lot of people blaming 33204803428 different things on signal loss... basically everything BUT the fact that we're experiencing one of the largest CMEs to hit Earth for a few years.
After multiple factory resets, cache wipes, system formatting, and flashing ROMs, everything seems to be running properly again. Thanks for the suggestions!
To anyone getting battery drain issues with custom ROM like had. Would like to share a method that helped me get my battery stable. First wipe cache partition followed by wipe dalvic, then factory reset. Now go to mounts and storage and select system format after this step flash ROM and Gapps as usual. After this I wipe cache partition and dalvic one more time and reboot. I knw it seem like a lot to do but it has work for me I now get 10+ hrs of battery life. Just remember to use titanium backup or Go Backup app otherwise be ready to reinstall apps and layout settings all over again. Hope this help and if any questions Pm me an I will do what I can to help. :beer:
Sent from my SGH-I777 using xda premium
those dont fix battery drain issues, those are instructions on flashing a rom....
Pirateghost said:
those dont fix battery drain issues, those are instructions on flashing a rom....
Click to expand...
Click to collapse
Yes I agree with you but sometimes during install battery goes hay wire and installing this way it seems to fix it. A few others and I have had this issue and this had fixed it. Issue with a few AOKP RELEASE. Thought I put it out there for those who have had this issue and don't format before install
Sent from my SGH-I777 using xda premium
VICIOUSVIC1 said:
Yes I agree with you but sometimes during install battery goes hay wire and installing this way it seems to fix it. A few others and I have had this issue and this had fixed it. Issue with a few AOKP RELEASE. Thought I put it out there for those who have had this issue and don't format before install
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
but they have been told time and time again, if you dont fully wipe before flashing, then dont report anything....its simple.
you posted instructions on flashing a rom, the same as any ROM OP should.
BTW, wiping cache and dalvik is placebo. when you boot after changing system, the dalvik cache gets rebuilt....doesnt matter if you wipe it or not. what can matter is /data partition if you have rogue app or rogue settings that are incompatible with the version of the rom you are upgrading to.
this thread is just a common sense thread:
if you have problems fully wipe then flash again.....
even says so in the AOKP OP......
Totally agree but still you and I know that reading through AOKP page the question comes up and at least with this they will avoid asking the question on thread page. Please PM for further comments.
Sent from my SGH-I777 using xda premium
Closed per op request
Hey guys,
I've just instelled cm10 a few days ago,
and it's making me crazy, hope you can help!
Most of the time it works great. BUT when I
play some games or use Facebook, it just
Shuts-down the phone, and when I turn it on
it says it got 1-5% Battery left. (it's not true)
When I plug the charger, the battery level
get's back to where it was.
I've tried updating to CM10.1 and the problem
presists.
so,
1. What's cousing those shutdowns?
2. How can I fix the battery problem after the shutdown?
Thanks!
You installed it with a full wipe?
Sent from the Matrix
Doorman404 said:
Hey guys,
I've just instelled cm10 a few days ago,
and it's making me crazy, hope you can help!
Most of the time it works great. BUT when I
play some games or use Facebook, it just
Shuts-down the phone, and when I turn it on
it says it got 1-5% Battery left. (it's not true)
When I plug the charger, the battery level
get's back to where it was.
I've tried updating to CM10.1 and the problem
presists.
so,
1. What's cousing those shutdowns?
2. How can I fix the battery problem after the shutdown?
Thanks!
Click to expand...
Click to collapse
Have you checked to see if this also happens with non-CM roms?
The first thing you should be doing is counting out a hardware problem so install a non-CM rom like a Samsung stock or based rom.
Also do a clean install or your roms to avoid issues. (Wipe data/factory reset in recovery, ONLY USE IF YOU HAVE A CUSTOM KERNEL/RECOVERY FLASHED).
Donnie Sins said:
You installed it with a full wipe?
Sent from the Matrix
Click to expand...
Click to collapse
I came to cm10 from stock, so yes.
CC10.1 - was updated from the ABOUT
menu (OTA update), So I couldn't wipe,
I just did "Factory reset" from Settings
after the update.
TheATHEiST said:
Have you checked to see if this also happens with non-CM roms?
The first thing you should be doing is counting out a hardware problem so install a non-CM rom like a Samsung stock or based rom.
Also do a clean install or your roms to avoid issues. (Wipe data/factory reset in recovery, ONLY USE IF YOU HAVE A CUSTOM KERNEL/RECOVERY FLASHED).
Click to expand...
Click to collapse
There was no Problems at all on 2.3 stock,
So I don't believe it's an hardware issue.
factory reset from the OS is the same as
Full Wipe, right?
calibration might help. Hardly hardware issue.
a korean guy told me so, they are from the future you know; already got the JB and all.
sent, and now this app cra.........
HAHA I know
but What do you mean by Calibration ?
battery calibration, or kernel stweaks.
sent, and now this app cra.........
Battery calibration - yes.
Kernel stweaks - How can it help?
It seems like a problem with the cm10 rom,
Anyone here using the CM10 nightlies?
Can you tell me if yours is stable or
has such isues ?
I think it's the battery info picked up by the ROM. Wipe bat stats to force it start from scratch.
sent, and now this app cra.........
Double post- Sorry
gastonw said:
I think it's the battery info picked up by the ROM. Wipe bat stats to force it start from scratch.
sent, and now this app cra.........
Click to expand...
Click to collapse
Hey, I've tried battery cal. again - it didn't help.
The main issue though is the random shutdowns not the battery stat.
It mainly happens with the Facebook app, Is it a known bug in CM10 ?
Just an update: I've flashed 2 other Stock based roms and the problem is worse Now!
It shuts down like 10 times a day now, on every screen even on Lockscreen sometimes.
The phone was 100% good before I flashed cm10! Did i do something wrong ???
What do you think's wrong with it?
Help! Please?
Does the screen flicker issues on cm 10.1 effect the phone in long term..Wil it damage the screen ?
First of all: I have had my S II water damaged some months ago. It works fine that far (exept that the sensor keys are dead). Not sure if there is some other hardware malfunctioning...
Currently im running on MIUI and everything is fine, but recently I found out that no other ROM will work on my Phone:
- Samsung stock ROM runs extreme (!) laggy. Took me about 5 Minutes to go through the menus and enable USB debugging.
- CM9/ AOKP will reset immediately after system startup
- CM10 shows laggy boot animation for few secs, then bootloops
Only other ROM that works is "cMIUI". Which is a CM10 based ROM only with a MIUI userinterface...
What can I do to find out whats the problem with my phone??
Thats weird. Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache. Also, have you tried using those kernel cleaning scripts, etc?
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Thats weird.
Click to expand...
Click to collapse
YES :laugh:
Spiralzz said:
Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache.
Click to expand...
Click to collapse
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
Spiralzz said:
Also, have you tried using those kernel cleaning scripts, etc?
Click to expand...
Click to collapse
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Rottnroll said:
YES :laugh:
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Click to expand...
Click to collapse
Only one option I can think of is to go back to stock samsung rom then claim your warranty if you have it. Or, make a logcat and paste it here (upload to Dropbox or somewhere then past a link over here) and someone experienced might take a look.
Since you've already wiped everything, I'm more inclined to think that it's a hardware problem now. However, let's hope someone more experienced pops in and helps. Good luck
Sent from my GT-I9100 using Tapatalk 2
See two logs below, trying to boot cm9. One with default kernel, one with Siyah. Would be great if anybody could find out whats the issue.
https://www.dropbox.com/s/z7q3wbz1h9uhhvg/logcat_cm9_s2.txt
https://www.dropbox.com/s/r1l9umovmxx7jpo/logcat_cm9_s2_siyah.txt
In both logs the phone booted and showed the Pin dialog, then after few seconds rebooted.
As the Phone had been waterdamaged Im pretty shure warranty is absolutely void Also I think that the problems are due to some Hardware malfunctioning. Just want to know what and if theres some way to workaround.