Hello xda!
Lately my phone has been acting real crazy. I've been on Cognition rom for about a month and I never experienced any issue. However, after flashing SpeedMod k12t, my phone kept freezing while on sleep after 1-2 hours of use. I decided to reflash firebird 2 to make sure it wasn't the new kernel, but my phone recently froze in screen off. I am now sure this has nothing to do with a specific kernel. I have been trying to figure out what's wrong with my phone. I am pretty sure it has nothing to do with my modem either, since I have been using jk4 for about a week or three and this issue never came up until now.
All I'm really thinking of would be my setcpu settings. I recently started to use profiles with the following settings :
Screen off : 200-200 performance (now 400)
Charging : 1000
Battery < 101% : 800 - 1000 conservative
Battery < 39% : 400 - 800
I am thinking the screen off settings are causing all of this trouble. I only started using these a day or two before all of this started. Back then I was testing out a couple different kernel (suckerpunch, gb's kernel, firebird, speedmod). I had a rather poor uptime with suckerpunch because it took a while for me to find the correct settings, and when I did, I remember getting a sleep death that I blamed on the kernel because of the history of charge death it had back then.
Also, my original kernel was firebird and my phone was quite stable during the 3 weeks I've used it. I'm leaving the possibility of a bad kernel away because of this.
So here's my question, xda : What's up with my phone? Is reflashing back to stock and back to Cognition the only possible fix for this? Could me flashing kernels without disabling voodoo be the cause of all of this? Could disabling voodoo and reflashing the kernel fix this? Can set cpu be the cause of all of my trouble (i disabled it for now).
Thanks,
I have the same exact problem and it drives me insane. I have no solution for it except if your last 4 IMEI numbers (under your battery) are below 6000. Mine is 8355 so i dont know.
The last four numbers under my battery are 6, 5, 5, and 9. 6559. This only started a day or two ago. I've only had this phone for a month. So far the problem seems gone, but I've noticed my battery went from 67% to 80 after rebooting my phone to check the numbers under my battery. I recently wiped my battery stats though.
I've only had my phone for about a month too, so i don't know any more than you do. The only thing different for me is the shutdowns were already happening, and the the ROM I flashed just increased it.
Yeah, my phone also seems to freeze when alseep but only if its charging. Sometimes if i disconnect it, it will freeze or if i get a phone call while its charging.
My Captivate had sleep death (randomly) and charge death on some ROMs. After flashing several combinations of ROM/kernel/modem, it seems ok now. I think I will keep on finding a better combination.
SetCPU has some issue with OC/UV kernel on my Captivate, so if you have the same problem try to disable SetCPU first and see if the problem goes away.
Hi all.
I've been experiencing a weird issue.
I've been a RocketROM user for a while now, and never had any battery issues.
Yesterday i decided to try the Abyss kernel. As soon as i flushed it (wiping caches before) i started experiencing high battery drain.
BetterBatteryStats showed WLAN_RX_WAKE as the main culprit while the built in battery stats showed Android OS as the culprit.
So I decided to roll back to the backup i've done prior to installing Abyss (FM Kernel - Rocket V11) but noticed that even after restoring i am experiencing the same issue.
I have since tried clean wipe and at least 3 different restore points (all with FM kernel), but in each case i keep experiencing high battery drain and the phone can't get to deep sleep, all the while the only thing that BBS shows is a kernel wakelock WLAN_RX_WAKE and android OS as the highest "spender".
I suspect that Abyss left some file/residue that keeps causing the issue even after i removed it/clean wiped.
Is that possible ?
I know there's a kernel cleaning script for SGII.. never heard a mention of it for the note.
Would appreciate any pointer/suggestion at this point, as i am quite lost.
mfractal said:
Hi all.
I've been experiencing a weird issue.
I've been a RocketROM user for a while now, and never had any battery issues.
Yesterday i decided to try the Abyss kernel. As soon as i flushed it (wiping caches before) i started experiencing high battery drain.
BetterBatteryStats showed WLAN_RX_WAKE as the main culprit while the built in battery stats showed Android OS as the culprit.
So I decided to roll back to the backup i've done prior to installing Abyss (FM Kernel - Rocket V11) but noticed that even after restoring i am experiencing the same issue.
I have since tried clean wipe and at least 3 different restore points (all with FM kernel), but in each case i keep experiencing high battery drain and the phone can't get to deep sleep, all the while the only thing that BBS shows is a kernel wakelock WLAN_RX_WAKE and android OS as the highest "spender".
I suspect that Abyss left some file/residue that keeps causing the issue even after i removed it/clean wiped.
Is that possible ?
I know there's a kernel cleaning script for SGII.. never heard a mention of it for the note.
Would appreciate any pointer/suggestion at this point, as i am quite lost.
Click to expand...
Click to collapse
+1. Exactly the same issue here.
I'm having the same problem, but on my new Skyrocket SGS2. Leaving wifi on drains my battery due to these wakelocks. Tried new roms and kernels, but it still plagues me.
styx66 said:
I'm having the same problem, but on my new Skyrocket SGS2. Leaving wifi on drains my battery due to these wakelocks. Tried new roms and kernels, but it still plagues me.
Click to expand...
Click to collapse
Is your wifi on a Windows 7 network? I fixed my problem by cleaning up some things that were multi-casting from my Win7 desktops and keeping the phone active continually. Check Entropy512's known battery drainers thread in the i777 forums for some stuff I posted (and a lot of other good ideas to track it down).
Yeah i saw that and turned off the WMP network service and others, but after doing a Shark dump i don't think they were responsible.
I reflashed my phone to bone stock and monitored my network packets. 98.4% of the packets recorded are ARP protocol packets. My FIOS router and my computer asking "Who has 192.168.1.2? Tell 192.168.1.1" etc like that. Pretty much every second. During that time my phone was i think 25% in wakelock from wlan_wake and wlan_rx_wake.
It seems to only be polling and asking to find computers that aren't there any more. I turned my PC off and ran another test, and the router blasted my phone with "Who has 192.168.1.9" which was my PC's address. And blasted it so much that time it kept me 50% wakelocked.
Not sure how to stop these but it seems like these could be the cause... Or are they part of every network like that and my phone should be ignoring them? I'm gonna post my data in that Known battery issues thread later too.
I saw exactly the same behavior on my wndr3700 router. It keeps sending Arp requests every second or so. I too wasn't able to find out whether this is normal or not. seeing it happen on a completely different router suggests its normal but a confirmation from someone who knows would help.
Sent from my GT-N7000 using Tapatalk
mfractal said:
I saw exactly the same behavior on my wndr3700 router. It keeps sending Arp requests every second or so. I too wasn't able to find out whether this is normal or not. seeing it happen on a completely different router suggests its normal but a confirmation from someone who knows would help.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Best solution imo is to flash a stock rom with Odin. Let it boot, and wipe the phone with *2767*3855# to original factory settings.
Than you`ll start clean again.
gee2012 said:
Best solution imo is to flash a stock rom with Odin. Let it boot, and wipe the phone with *2767*3855# to original factory settings.
Than you`ll start clean again.
Click to expand...
Click to collapse
Did you even read his post? The issue is his router, NOT the phone.
---------- Post added at 07:24 AM ---------- Previous post was at 07:20 AM ----------
gee2012 said:
Best solution imo is to flash a stock rom with Odin. Let it boot, and wipe the phone with *2767*3855# to original factory settings.
Than you`ll start clean again.
Click to expand...
Click to collapse
styx66 said:
Yeah i saw that and turned off the WMP network service and others, but after doing a Shark dump i don't think they were responsible.
I reflashed my phone to bone stock and monitored my network packets. 98.4% of the packets recorded are ARP protocol packets. My FIOS router and my computer asking "Who has 192.168.1.2? Tell 192.168.1.1" etc like that. Pretty much every second. During that time my phone was i think 25% in wakelock from wlan_wake and wlan_rx_wake.
It seems to only be polling and asking to find computers that aren't there any more. I turned my PC off and ran another test, and the router blasted my phone with "Who has 192.168.1.9" which was my PC's address. And blasted it so much that time it kept me 50% wakelocked.
Not sure how to stop these but it seems like these could be the cause... Or are they part of every network like that and my phone should be ignoring them? I'm gonna post my data in that Known battery issues thread later too.
Click to expand...
Click to collapse
I'm still getting the ARP requests, but they aren't stopping the phone from sleeping and my battery life is excellent now. Cutting down the ones with "destination port: wcbackup" is what "fixed" mine. Try following this: http://www.corrupteddatarecovery.com/Port/8912udp-Port-Type-wcbackup-wcbackup.asp
and see if you can shut off the processes that are the worst offenders.
Thanks a lot for the confirmation. Could you say which rom and kernel are you using?
Sent from my GT-N7000 using Tapatalk
mfractal said:
Thanks a lot for the confirmation. Could you say which rom and kernel are you using?
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Sorry, missed the question - I'm using UnNamed 2.2.1, with Entropy512's 1/30/2012 kernel. At the time you asked, I was running the same ROM, but the 1/2 kernel. And the 1/30 kernel has cut my battery drain in half! Hope that helps.
When using the phone the battery indicator immediately drops from whatever it was at down to %0 and the phone shuts off.
When I start the phone up into recovery (Philz) it still shows the original battery percentage that was reported before the phone shut off. I rebooted the phone back up into system several times and sometimes I am able to use it for a minute or two and then it will repeat all over again: the battery drops back to %0 and the phone reboots, other times it says %0 immediately after bootup and shuts off right away.
It's intermittent, so sometimes I can go for a week or two if I'm lucky without it happening, but sometimes I can only go a few hours without being interrupted by the shutdowns. The only thing that seems to have helped me is charging my phone a little bit more and then it stops for a while, but I don't always have a charger with me so I would like to get this issue resolved if possible.
I know my battery is charged. I was able to sit there flashing my phone over and over trying to fix the issue and the phone kept working 45 minutes and even an hour later. Sometimes reflashing my ROM after wiping system, cache, etc. seems to fix the issue, other times it doesn't work.
I have done the EB40 mod to my phone, but I haven't had any issues with it. It's possible that this problem could be related to that as well, but I'm fairly confident that my battery is in good condition.
This issue has been occurring for quite a while and I have done full wipes and reflashed several times with multiple different ROMs and kernels to see if the issue was related to a certain ROM or kernel. All of the ROMs I have tried were very heavily based on CyanogenMod I believe, so if it turns out to be software rather than hardware then that seems to be the common link.
I need my phone for my job so this is something I really need to get sorted out. I have to use my phone for debugging and testing applications.
I have searched all over the web but no one I have found in any forum was having quite the same issue as me.
Does anyone know how to solve this issue? A suitable workaround if no other solution could be found would be somehow preventing the phone from rebooting when the battery reads %0 if that's at all possible.
Here's a screenshot of my battery history from today when this happened. Notice how the battery level goes right back to where it was after rebooting.
https://docs.google.com/file/d/0B6RpWzK5OKf4SFp1TWd1aUJ4ZlU/edit?usp=drive_web
Some additional info:
My battery is still at %52 as I type this and it's still running without a problem. Battery life is great in the CyanogenMod nightlies when I'm not having this issue.
I am running the October 12th nightly. The issue started while I was using arrrghhh's kernel, and it persisted even after wiping /system, and /cache and then using just the normal kernel that comes with the October 12th nightly.
Try a different rom?
Sent from my PACMAN MATRIX HD MAXX
I have tried flashing quite a few different ROMs and this has happened on all of them. CyanogenMod, PAC, JellyBam, and ProBAM come to mind.
Have you tried wiping every thing and fastbooting back to stock?
Sent from my MB886 using Tapatalk now Free
penser said:
Have you tried wiping every thing and fastbooting back to stock?
Sent from my MB886 using Tapatalk now Free
Click to expand...
Click to collapse
No. Would that really be necessary?
I wiped /system, /data, /boot, /cache, dalvik-cache, basically everything.
This sometimes does resolve the issue temporarily, but it comes back after a while.
UPDATE: I read somewhere that this may be an issue with the battery not being properly calibrated after installation. I don't think I've ever drained the battery all the way down since I got the EB40, so I figured I'd try it.
I tried completely draining it and charging it up to %100 with the phone off and I haven't had any issues so far. Sometimes it went for a week without having issues before though, so I'll be keeping an eye on it in case there are any more issues.
Hello everyone,
I switched my 16 months old 4x to CyanogenMod 10.1 about 2 months ago, and updated to 10.1.3 about a week after the release. About a week later, I had my first problems with rapid battery draining. I have switched kernels thrice, now running the most recent optimus prime for CM, and have tried fiddling with the values TricksterMOD provides, but I haven't found a way to get any decent battery life out of the device ever since. Last night, the battery drained 50% in about 12 hours of non-use (phone was left with display off in my jacket pocket, and that's not even the worst drain I witnessed in the last two weeks.
I'm running BetterBatteryStats to get a clue about the origin of this drainage, and can see that my device seems to me awake far too long when I'm not using it. At the moment, I'm looking at 44.6% awake, 55.4% Deep Sleep after 2.5 hours of not using the phone once (I was driving home from work half of the time). In "Kernel Wakelocks", I see "wlan_rx_wake" with 21:03 minutes on top, in "Partial wakelocks", the highest value is 20 seconds for "AlarmManager".
I have the usual suspects of communication/networking apps - Facebook (set to 2hr update), Google+, K-9 Mail, WhatsApp, plus AndroidWeather (set to 30min update) - and news apps which are allowed to send push messages. I use wifi, but no bluetooth. I never watch movies, play games or listen to music with my phone.
I have attached a BetterBatteryStats log from the 50% drain in 12 idle hours I mentioned. View attachment BetterBatteryStats-2013-10-17_092335401.txt
Can anybody give me any pointers as to what I going wrong here? I really would like to use my phone without having to plug in the power supply every few hours. If you need any additional information, I'll gladly try to provide it.
Anyway, thanks in advance for any help.
Cheers, Pit.
only 3 letters. O M G ! this battery report just made me like this face here
u cant flash kernels one after another. there are bugs this way. dont all kernels use the same names for files. leftover files will cause problems. do the whole procedure. go to recovery , format data, reboot to recovery and install new rom
kessaras said:
only 3 letters. O M G ! this battery report just made me like this face here
u cant flash kernels one after another. there are bugs this way. dont all kernels use the same names for files. leftover files will cause problems. do the whole procedure. go to recovery , format data, reboot to recovery and install new rom
Click to expand...
Click to collapse
You mean you cant flash Android roms one after another. You can freely flash kernels one after another without wiping anything, Its completely modular.
JoinTheRealms said:
You mean you cant flash Android roms one after another. You can freely flash kernels one after another without wiping anything, Its completely modular.
Click to expand...
Click to collapse
then explain his situation... he said he flashed kernels not roms. why does he have such a bad battery drain during night sleep ? in his report i didnt see he has any so "bad" app.... (just asking out of curiosity, its good to have knowledge generally)
kessaras said:
then explain his situation... he said he flashed kernels not roms. why does he have such a bad battery drain during night sleep ? in his report i didnt see he has any so "bad" app.... (just asking out of curiosity, its good to have knowledge generally)
Click to expand...
Click to collapse
Not sure about the battery drain, it could be caused by a kernel, but its not because hes flashed multiple kernels.
some background:
Android kernels are packaged into boot.img's (these .imgs can be placed in .zips with instructions on how the custom recovery should handle flashing it) Inside a boot.img you will find a zImage (kernel) and a initrd.img (This stands for initial ram disk, its simply a basic file system that the kernel mounts, containing mainly scripts that handle mounting all the necessary partitions etc, then handing control over to Android. )
The boot.img is stored in a emmc partition (/dev/block/mmcblk0p*). When you press the power button, the bootloader is initialized , it then powers on necessary hardware devices, the bootloader than pulls the boot.img from its partition, extracts it and boots the zImage(kernel), which will start initializing less necessary hardware, but mainly mounts the initrd.img and runs the containing instructions.
Bootloader -> Kernel --------------------->
.........................Initrd.img-> ........Android
To move back on track, the zImage and initrd.img only operate within RAM, they only lie in emmc when they are achieved as a boot.img. When you shut your device down, nothing from the kernel persists in the next boot (maybe /proc/last_kmsg ), this is why you dont need to wipe anything on your device between kernel flashes.
JoinTheRealms said:
Not sure about the battery drain, it could be caused by a kernel, but it's not because he's flashed multiple kernels.
Click to expand...
Click to collapse
Thanks for clarifying that; it saves me some trouble.
Does the BatteryStats log give any indication as to why the phone is awake half of the time?
Cheers, Pit.
Dont know, but maybe O Prime is one of these kernel which hides the xmm baseband wakelock.... that would be the missing awake time in your log
OnAir783 said:
Dont know, but maybe O Prime is one of these kernel which hides the xmm baseband wakelock.... that would be the missing awake time in your log
Click to expand...
Click to collapse
Yep optimus prime hides the baseband wakelock
Sent from my LG-P880 using xda app-developers app
OnAir783 said:
Dont know, but maybe O Prime is one of these kernel which hides the xmm baseband wakelock.... that would be the missing awake time in your log
Click to expand...
Click to collapse
Is there a different kernel you would recommend I should try out? I selected the OPrime because it claims to be focussing on stability and battery life instead of raw power.
Furthermore, what would the baseband wakelock tell us in terms of how the fast drain happens?
Cheers, Pit.
Hello all,
just to try it one more time: is there any way I can get decent battery life out of CM10.1.3 on my 4x? This is my profile from today, where I unplugged my phone from the charger around 7:30 a.m. and didn't use my phone thereafter until 5:30 p.m. where the phone was down to 38% already (stats taken around 8:30 p.m.) . The governor is set to conservative and the max frequency to 1.1 GHz, which already makes the UI a bit sluggish. The other settings are unchanged from above.
Secondly, if there really is no chance of improvement under CM10.1.3, which ROM (and kernel) would you suggest for my phone, so that I can at least get a full 24 hours of battery life when I'm not using my phone most of the time?
Thanks in advance, Pit.
Format SD card and wipe everything before flashing new ROM. When I say everything I mean : catche - dalvik - format system - format sd card (sd card is 11gb internal memory of device and external sd card is your inserted sd card). Try latest liquid rom i have good battery life with its stock kernel.
Sent from my microwave.
The baseband wakelock is hidden at his kernel
Gesendet von meinem LG-P880 mit Tapatalk
Try rebooting again after first reboot installing kernel
I'm not sure why but when wiping dalvik and cache the phone has trouble going into sleep
Flash -> wipe cache/dalvik -> Reboot -> Reboot again
Hi everyone,
well, that was a bust. After spending the better part of a day formatting and installing over and over again, I'm now running CarbonRom [20131023] - and having the same battery problems as before.
I tried LiquidSmooth (2.23), but I never got it to work properly; after installing I always got "application someName was teriminated" every few seconds (while the Play Store app was redownloading and reinstalling my apps, but also when I tried to activate SwiftKey, which calls the settings app at one point, which abruptly quits before I can type in anything. I then tried
ParanoidAndroid (3.99, which I didn't like UI-wise)
and SlimBeam (1.9, where the Google apps I downloaded as stated would install fine, but then not appear for some reason - at that point I didn't spend much time trying to fix it, because I was already fed up with it all)
before finally installing CarbomRom, which worked fine. Thus, after downloading my apps, I tried out my battery again. I unplugged the phone, turned the display off, and went shopping for about two hours, touching the phone just once for a few seconds.
The result is again about 30% awake time during these two hours, losing 10% battery in the process (BetterBatteryStat included). That is pretty much unchanged from my experiences with CM10.1.
What am I repeatedly doing wrong that I don't get halfway decent battery runtime out of my 4x (which used to run fine battery-wise for a year when I used the original LG firmware (which had other issues, but could last 36 to 48 hours, depending on usage? As I don't see hordes of 4x owners throwing the device against the wall in frustration, I must do something other don't. But I haven't got the slightest clue what that might be.
I will try PACman (nightly 20131021) next, but if anyone has any pointers, please please help! I'm running out of ideas.
This was my procedure, by the way:
Reboot into CWM
Format system, cache, data, sd card
flashing ROM
Rebooting
after bootup reboot again into CWM
add the Google apps
reboot again
After bootup, reboot again into CWM
just to be sure, reset to factory defaults
reboot, connect with Wifi and Google and start redownloading the other apps
Frustrated greetings, Pit.
Hi again,
PACman is even worse. First off all, the UI is laggy as h*ll; sometimes, it takes more than two seconds for a button touch to be recognized.
That would be somewhat tolerable if the battery life was better. But in 2.5 hours of leaving the device lying idly on my table (display turned off), more than 50% of the time, the phone was active. BetterBatteryStats are again included as an attachment; perhaps someone can find out what the problem is with them. At least, this kernel doesn't hide the xmm_baseband wakelock, though I have no idea what that means whatsoever.
This is getting ridiculous - is there really no way to get the phone to last more than ten hours (doing nothing with it - when I use it even for occasional browsing/e-mail checks, it's way less than that) anymore? Why is no one else having problems on that scale?
Typing this post cost 3% of my battery. And I'm typing it on my computer, not on my phone.
Depressed greetings, Pit.
When i watch your battery stats its your wifi did your try to install then wifi update of demetris? Try then samething with your wifi off i think it would increase slot of your battery
Sent from my LG-P880 using xda app-developers app
moneyvirus said:
When i watch your battery stats its your wifi did your try to install then wifi update of demetris? Try then samething with your wifi off i think it would increase slot of your battery.
Click to expand...
Click to collapse
Thanks, for the info, I will investigate that, though I haven't found this "wifi update of demetris" on first Google try yet, just recommendations what to do with your WLAN router and PC settings.
But I my second-to-last try - where I was out shopping - the wlan_rx wakelock wasn't the problem, rather the xmm_baseband wakelock, where I still am clueless as to what that means at all. I fear that getting rid of the wlan wakelocks wouldn't help my general problems, just the problems I had at home last night in my last try.
Furthermore, if I can use the phone only by carefully switching off and on wlan manually whenever I leave the house, the phone will become pretty much useless to me. Yesterday alone, I forgot switching wifi back on twice. That way, either notifications would go through mobile data connection or not happen at all.
I will reflash my device again this morning - as the PACman UI lags are unbearable for me - and see what I can do about the wlan drain. I cannot reconfigure all the wifi networks I connect to, as some of them aren't mine to configure.
http://forum.xda-developers.com/showthread.php?t=2425455
Look in the seccond post your will zee a long story but at then and of that story you see 3 zip files flash then then nvida 4.3+ broadcom driver update by cwm dunno if it solves your probleme for me its great
Goodluck
Sent from my LG-P880 using xda app-developers app
I don have any problems with liquid rom. Also I flash gaps imidiatly after flashing rom without reboot. Try flashing 4.2.2 android it is better for our prone then 4.3 builds.
Sent from my microwave.
dimi89 said:
I don have any problems with liquid rom. Also I flash gaps imidiatly after flashing rom without reboot. Try flashing 4.2.2 android it is better for our prone then 4.3 builds.
Click to expand...
Click to collapse
I tried that earlier today, and the LiquidSmooth 2.9 (Android 4.2.2) installed fine by your instructions. But it didn't help at all with the battery usage. Phone is running on conservative governor limite to 1 GHz, and I even tried the Broadcom Wifi Update mentioned here earlier (otherwise, I'm on the LS standard kernel).
It all doesn't help, the BetterBatteryStats are still full of wlan wakelocks (even though I switched to static IP as someone mentioned that might help). Result: 10,8% battery drop per hour of leaving the phone with display off on the table.
Before I flash another ROM for the 14th time this weekend, I will collect some results with wifi turned off. Not that that would be a feasible option for me, but I want to get to the bottom of this.
Cheers, Pit.
Hi,
A few days ago I upgraded my Note from a very ancient (stock) Gingerbread ROM to (stock) Jellybean. I hadn't been getting OTA updates because the Gingerbread was originally German rather than UK, so quite a long time had passed without any updates. Anyway, because of the no OTA, I used Odin. Everything went fine and I had a nice few days of usage, although the battery consumption seemed to suddenly be quite high, mainly due to additional wakelocks from the new Google Search it looked like. The night before last at about 3% the phone turned itself off, which is unusual as normally the battery will run itself lower than that. BTW, it's an official battery bought just a few months ago to replace the one before, which was getting old.
Yesterday evening when I went to use the phone it was dead. Completely unresponsive. It wouldn't charge either. (The battery had been at about fourteen percent I think, so it should have still had a lot of juice left.) Turning it on would leave it stuck on the Samsung logo only. Recovery mode didn't work, but I could get download mode up, so I installed the Philz kernel as people have said, and then did a reset using that, and all was okay again and after reflashing the ROM I could use the phone again, although because of the reset I had to set everything up again.
Just wondering what people think caused it. Just a weird coincidence, or something else? As far as I'm concerned, the problem has been sort of mitigated for now, but definitely not fixed, because what's to stop it happening again? Has anyone heard of strange things going on with Jellybean? I know there's an issue with flashing/resetting from ICS, but I never used that so I don't think that's an issue, and it looks like it was just a soft brick only. Still, a bit weird and worrying. Does anyone have any ideas?
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
XxPixX said:
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
Click to expand...
Click to collapse
I didn't take the battery out though. It was low but not dead.
Since then it has happened once again, a few days ago, this time at 93% full. I was doing nothing at all taxing to the phone. I was just in a shop listening to an mp3 with the screen off, and then it stopped and the next thing I saw was the bootloop. Luckily (thanks to the new kernel?) I could just delete cache/dalvik and be back up and running again without having to reinstall everything. Today my screen temporarily went a weird purple colour like in this thread: http://forum.xda-developers.com/showthread.php?t=2216867 . Sounds like it's just dying in general really, rather than anything else. My phone contract upgrade date is in two days. Purely a coincidence of course. Weird how phones tend to last about the length of a mobile phone contract. Until then I'm just running on power saving mode and hoping for the best.