Related
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
no.. wrong section
try wiping dalvik/cache/factory
No reboots over here.
Sent from my Nexus S
dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
what kernel? And if you're going to ***** about problems with 2.3.3 you should run fully stock to make sure some customization is causing the issue.
Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?
I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.
kenvan19 said:
Never once had a random reboot related to a call. Why do people tend to only pay attention to half of a bugfix and never specify whether their "problem" is related to it and then post it the completely wrong section about the problem without searching for the older threads relating to their issue?
Click to expand...
Click to collapse
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".
Highland3r said:
People don't understand. They just see "reboot bug" and anytime they get a reboot it's "that bug".
Click to expand...
Click to collapse
My G2 (pure stock) rebooted once in a while. In fact I watched it happen while i was in a meeting there day before I got the nexus s. It must be the same bug!
nexus s has not reboot once, though ill give it time its only been three days.
Sent from my Nexus S using Tapatalk
On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\
dinan said:
On CM7 build 12 with netarchy 1.2.7... it rebooted once sitting on the desk doing nothing lol. Haven't had a reboot since but it's only been a day. Battery life seems pretty good but 3D performance took a hit on 2.3.3 =\
Click to expand...
Click to collapse
is this from benchmarks or are you seeing real world performance decrease? I am not trusting benchmarks as my g2 performed better in quadrant, yet real world the ns feels much faster.
Sent from my Nexus S using Tapatalk
Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App
dinan said:
Both. Benchmarks are lower and also when playing games like dungeon defenders its noticeably slower than before.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk
I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Anyway, just had a reboot while trying to do the pattern unlock to wake my phone. It booted with a little "Safe Mode" thing at the bottom left, never seen that before. Then shortly after that it promptly rebooted itself again and it's back to normal CM7, but all my widgets mysteriously vanished from my home screen... great.
[hfm] said:
That's strange, the ns has a good gpu..
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
dinan said:
I'm not saying it's bad, I'm saying the performance is worse than when I was on a 2.3.2 CM7 with the SAME PHONE. Not sure what comparing GPU's has to do with this.
Click to expand...
Click to collapse
True, that was just my impression switching phones. I suppose it was a stability/compatability play as I hope they wouldn't unknowingly release a build with an unknown gross performance deficiency in the display driver.
Sent from my Nexus S using Tapatalk
prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.
cygnum said:
I encountered this problem too, just 3 hours ago; the first after upgrading to 2.3.3 since Thursday.
Stock (but deodexed) 2.3.3, rooted, dalvik,cache-wiped.
EDIT: And oh, it's not a reboot bug -- it was a shutdown bug for me. Wasn't on a call, phone was just on stand by in my pocket, while my wife and I watched Voyage de la Vie. After the show, phone was dead, power button not working. I had to remove the batteries to jack it up again.
I guess I would be wiping my phone again, oh man that sucks.
But in the end, I still love my Nexus S.
Click to expand...
Click to collapse
My phone is doing the exact same thing.
On 2.3.2, CM7 nightly 2.3.3, and stock 2.3.3.
Wiped or not. Rooted or not. Same damn reboot/shutoff.
It just reboot/shutoff with screen off, and hangs dead there sometimes with LED lights on. Have to remove battery to boot. Sometimes takes a dozen time battery removal to get it pass bootloader.
I am fed up. Now I am using wiped non-root 2.3.3 with a broken CMR, and still reboots!
I am going to flash the stock Recovery back and lock the bootloader before sending back to Samsung for replacement.
But seriously, what would you recommend as my next phone. I am thinking about Tbolt or Atrix.
rocketragz said:
prior to 2.3.3 my phone rebooted while in stand by on a daily basis and just once while on a call. i haven't noticed it after 2.3.3, but i'm not holding my breath just yet. i hope it's fixed.
Click to expand...
Click to collapse
It's not.
I have 2 Nexus S, both of them have spontaneously rebooted on 2.3.3.
It was much worse on 2.3.2, though.
Both are stock, not even rooted. Even most of the apps are different (my wife uses very few).
delete....
dudeimgeorge said:
simply said. my phone still reboots
using cm7 2.3.3 #12 and this bastard still reboots.
anyone else?
Click to expand...
Click to collapse
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call. Also You're running CM7, so any random reboots is an issue with CM7 itself. It's still buggy as heck.
And ummm actually for me. Build 11/12 has been strong, not a single reboot. Used to have random soft-reboots, soft-reboot loops, and can't unwake the phone. All needing battery pulls. Haven't had a single random reboot with CM7 build 12.
nxt said:
You do realize the "reboot" bug has nothing to do with just rebooting right? It has to do with rebooting while DURING a call....
Click to expand...
Click to collapse
Except that it's happening to way too many of us, NOT during a call. I call that a "reboot" bug.
My phones are stock.
**Edit: i just posted this in the questions forum -- seemed more appropriate. moderator, please feel free to delete. sorry!
What's up everyone! just needed some advice if you don't mind. lately my phone's been freezing randomly, and it seems like my battery life has been getting crappier..
was wondering if I should just Odin back to stock and re-flash everything, do you think that would cure my ills?
I started with my first ROM -- srf1.1.0 and loved it... tried the vision kernel 1.1, tried genocide 1.0... LOVED vision 1.2 but went back to 1.1 because ppl started getting bricks..
i don't know if it's data corruption (have journalling off), or if it's like artifacts from vision kernel 1.2 (it didn't give me any problems, honestly my fav kernel with insane battery life it seemed)
yesterday i restored a back up that was pre-ext4.. and it when that rebooted i had the "android" flashing over the original sprint bootup animation, so i rebooted and got thrown into a boot loop. pulled battery, booted into cwm and restored into a more recent backup that was post-ext4 and things seem to be fine.. except i've gotten maybe two random freezes since.
so yea, do you think Odin to stock and reflashing srf will bring me back to bliss, or.. am i screwed, or somewhere in between? i've read as much as i could but i know i'm a newb, so i'm grateful for any wisdom y'all can throw my way. THANKS!
This is more then likely a kernel based problem,but you can try using setcpu and limit your min. clock speed to 200mhz not 100mhz,this has helped several people ; My phone loves 100mhz,never had a freeze while using that clock speed,but each phone is diffrent,and might I suggest using Twilight Zone 1.0.4,awesome kernel...
Sent from my MyFrankenstein EC05OCE using XDAP App...
thanks! i will look into using that kernel!
Ya my phone just flatout locked up on me twice within 5 minutes. The second time th screen went bright yellowish tint with an artifact white line running across the screen. Good times.
Sent from my SPH-D700 using XDA App
RushAOZ said:
Ya my phone just flatout locked up on me twice within 5 minutes. The second time th screen went bright yellowish tint with an artifact white line running across the screen. Good times.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
My phone does this too. Screen goes static washed out yellow looking with artifact down the screen. Have to battery pull to fix it, no overclocking or undervolting. Getting ready to odin and reflash myself.
Sent from my SPH-D700 using XDA Premium App
Yea I'm about to brick it purposely and get it replaced. I reflashed and still the same. It just locked up on me while changing wallpapers?
Sent from my SPH-D700 using XDA App
Also I had full battery about 3 hours ago. Now I'm sitting at 18%. ...and they say I'm stupid for wanting a nexus s lol
Sent from my SPH-D700 using XDA App
Are any of you overclocking or undervolting? This will cause data corruption and freezing. I get it all the time at 1.3Ghz but not at 1.2Ghz. Every phone is different.
Do you BONSAI?
Mine did this last week, but I had reverted to rfs on 2.5.1 running Gingerbread that has some issues. When trying to put everything back (couldn't just run backup since I had changed systems), it took a day, stuck loops, stuck nothing, stuck Samsung, etc.
Read how to fix bricked phone, back to EC05, re-rooted, re did cwm 3.0, reflashed Syndicate, now everything smooth again.
I was kicking myself in the a-s for doing that, so hopefully this would help and save you a days worth of problems. Just find that link, read and follow
yea i just odin'd back to sock EB13, went to the EC05 through ODIN, reflashed SRF1.1.0 and everything's been GREAT since... getting superb battery life like i was on the vision 1.2 kernel.. weird, but i'll take it.
What version of ec05 are you guys odining back to? The version I have (EC05 FULL) was causing me all the issues I had. Instead I odined to stock eb13 and upgraded to ec05 ota. Since then im back on midNIGHT [email protected] w/ midnight honeycomb theme and I have to say this thing has never been speedier, or more stable than it is now. Also, I tried to redownload ec05 from the midnight android dev page and I get a corrupt file error when trying to unzip the .tar from the ec05 rar. I feel if ANYONE has any issues, before they blame the kernel I suggest starting from scratch on eb13. Not one freeze yet, no artifacts, no lag, no horrid battery draining. Life is good
Sent from my SPH-D700 using XDA App
I do that often, I just run an Odin back to DI18, upgrade to ec05 over OTA, then reflash the ROM I wanted. It brings my phone back up to full speed.
Overstew said:
I do that often, I just run an Odin back to DI18, upgrade to ec05 over OTA, then reflash the ROM I wanted. It brings my phone back up to full speed.
Click to expand...
Click to collapse
any particular reason by DI18 rather than EB13?
i think i've read in some other threads that it seems DI28 and DK28 are better somehow.. is that true?
so much that i've learned compared to when i was first starting to research what rooting meant.. and yet, still so much more to learn!
I flashed Trigger Redux today... Having many force closes and super fast battery drain. Now that Ive dove into the 2.3 realm, is the CM7 builds any less quirky?
You've done something wrong. There should be no FC's. Build 16 is out too.
s15274n is right, sounds like something is wrong. I had a borked flash once, did a factory reset and it seemed to help out quite a bit. That is the easy fix, try it and if it works then great, otherwise flash again and revert back to stock first if you can for a clean install.
Thanks.. ill try flashing 16.
I'd say CM7 RC1 is your best bet. Ran Trigger previously and CM7 has been amazing--just a bit more refined (especially with glitch kernel).
TheSneakerWhore said:
I'd say CM7 RC1 is your best bet. Ran Trigger previously and CM7 has been amazing--just a bit more refined (especially with glitch kernel).
Click to expand...
Click to collapse
Thanks... What's your avg battery life? I'm getting about 6-8 hours with moderate use. Im conditioning the battery now so hopefully in a day or 2 that number goes up
JD76 said:
Thanks... What's your avg battery life? I'm getting about 6-8 hours with moderate use. Im conditioning the battery now so hopefully in a day or 2 that number goes up
Click to expand...
Click to collapse
With the cm7 rc1 and glitch h1 getting 18 hours with very heavy use. No battery reconditioning.
Sent from my SGH-T959 using XDA Premium App
Glitch should work with Trigger Redux, correct? Ive read it does.. ill try it... Im going away to DC and LA this weekend and would hate to be stuck with a dead phone...
Which voltage app do you use? Voltage Control or Pimp My CPU?
I'm not getting force closes though I am getting "program stopped unexpectedly" on trigger 16 ALL OVER THE PLACE. The browser is completely unusable, and my Gameloft games are saying they can't connect to internet or are not original copies. They are legit FYI! I will try a factory reset but I have my doubts.
JediDru said:
I'm not getting force closes though I am getting " program stopped unexpectedly" on trigger 16 ALL OVER THE PLACE. THe browser is completely unusable and my Gameloft games are saying they can't conncet to internet or are not original copies. They are legit FYI! I will try a factory reset but I have my doubts.
Click to expand...
Click to collapse
That sucks that all that is happening to you. I'm on Trigger Redux build 15 and was on 14 and 13 and will flash 16. I have no problems at all. I have some battery drain but I also may need new battery and I use my phone very heavily.
I'd try to redownload the ROM, check the Md5 sum, and do an ODIN to stock, and flash the ROM again.
Better to start from scratch, make sure you get rid of all the ghosts and see if that fixes ya. If so then you know you had a borked flash or bug in your system
Well I'll be damned.... It worked. Thanks for pointing me in the right direction.
Soooo I flashed Kernel and then installed Voltage Control.. dont know what settings I chose but it cause the phone to reboot and get stuck on the Glitch screen. Guess im taking a flight on Air Odin tonight...
If you're getting force closes go to
/data/app delete a couple of folders. That will stop the force closes.
Sent from my SGH-T959 using Tapatalk
JD76 said:
Soooo I flashed Kernel and then installed Voltage Control.. dont know what settings I chose but it cause the phone to reboot and get stuck on the Glitch screen. Guess im taking a flight on Air Odin tonight...
Click to expand...
Click to collapse
make sure your min. cpu setting is 200. It comes stock with 100/1000. Bump the min. to 200 and you should be good to go.
Sorry if this is already posted around here somewhere, but I found this yesterday and was surprised that I hadn't seen anything here about it:
http://rootzwiki.com/topic/8853-working-sod-fix-from-dalingrin/
I installed the new kernel on both of my TouchPads last night, cleared both caches and fixed permissions, and set my lower CPU speed to 192MHz (from 384MHz to help prevent SoDs previously). I wasn't using SoftLocker, so I can't comment on that.
I haven't had a single SoD yet, and I left one of the TouchPads unplugged overnight to see what the battery drain looked like with the new kernel. I'm pretty sure it drained <1% overnight, and CPU Spy shows that all that time was spent in Deep Sleep.
Obviously this isn't a long-term evaluation, but initial results look promising.
UPDATE: Some folks have reported that applying this kernel breaks sound for them. I know it's happened to some people on alpha 1 and others on alpha 2.1, and I also know it hasn't happened to others (myself included). There's quite a bit of discussion about this on the linked thread, so if it happens to you, please refer to the existing information there.
Just flashed this clearing cache, dalvik and fixing persmission.
No SoD yet but NO SOUND.
I have no sound on my touchpad.
cleaned everything and flashed the fix again but no luck.
Silenus21 said:
Just flashed this clearing cache, dalvik and fixing persmission.
No SoD yet but NO SOUND.
I have no sound on my touchpad.
cleaned everything and flashed the fix again but no luck.
Click to expand...
Click to collapse
I think that may have happened to some other folks on the rootzwiki thread. Read down a bit and see what they say. I believe some of them reflashed CM7 with the new kernel (toward the end of the thread) and that fixed the issue. Worst-case scenario, someone has uploaded a recovery zip with the original kernel so you can roll back.
For what it's worth, neither of my TouchPads lost sound, so it's definitely possible to apply this without that happening.
SCWells72 said:
Sorry if this is already posted around here somewhere, but I found this yesterday and was surprised that I hadn't seen anything here about it:
http://rootzwiki.com/topic/8853-working-sod-fix-from-dalingrin/
I installed the new kernel on both of my TouchPads last night, cleared both caches and fixed permissions, and set my lower CPU speed to 192MHz (from 384MHz to help prevent SoDs previously). I wasn't using SoftLocker, so I can't comment on that.
I haven't had a single SoD yet, and I left one of the TouchPads unplugged overnight to see what the battery drain looked like with the new kernel. I'm pretty sure it drained <1% overnight, and CPU Spy shows that all that time was spent in Deep Sleep.
Obviously this isn't a long-term evaluation, but initial results look promising.
Click to expand...
Click to collapse
I don't think it's been mentioned much because it isn't a common issue anymore, i've never had sod on my touchpad and a lot of people claimed alpha 2 fixed the issue.
Sent from my HP Touchpad using Tapatalk
Alpha 2 definitely didn't fix the SoD issue (otherwise why would Dalingrin have kept working on it?). I think most folks used some combination of SoftLocker and cranking up the minimum clock speed to avoid it, both of which have significant impact on battery life. Hopefully this kernel (or some subsequent iteration if this one doesn't fully address it) will give stability and good battery life, particularly when the device isn't being used.
I've had the SoD on both a1 and a2. Flashed this fix. No SoD yet. Sound is still there too.
Sent from my ERIS using XDA App
according to the rootzwiki thread the fix is not allowing WIFI to go to sleep mode. This was the cause of most SODs.
You'll find in this fix that your WIFI will not turn off during sleep even if you set it to do so.
so after i installed the update it don´t save my "overclock"
i set up 1512 mhz but after reboot it´s gone and back at 1200
any idea for this?
Im not sure if Im the only one. But since Alpha 2 I have yet to see SOD, was there anyone else who saw SOD vanish completely with Alpha 2?
I had one sod with alpha 1 then none with alpha 2. I haven't installed any apps or changed CPU settings it just has never happened to me.
Sent from my HTC Desire HD using Tapatalk
synapses11 said:
Im not sure if Im the only one. But since Alpha 2 I have yet to see SOD, was there anyone else who saw SOD vanish completely with Alpha 2?
Click to expand...
Click to collapse
Not a single SOD here, but i skipped alpha 1.
After playing with it for a while, no SoD, but now I'm having wifi issues. Won't stay connected. Did a restore back. Now no wifi issues, but as soon as it goes to sleep, it wont wake up. Uggh. Can't wait till this gets stable. Getting bored of webos.
Lolento said:
according to the rootzwiki thread the fix is not allowing WIFI to go to sleep mode. This was the cause of most SODs.
You'll find in this fix that your WIFI will not turn off during sleep even if you set it to do so.
Click to expand...
Click to collapse
Sent from my ERIS using XDA App
mouseym said:
Not a single SOD here, but i skipped alpha 1.
Click to expand...
Click to collapse
I get Sod all the time. I put my cpu to 648mhz and it still does it. I even put it up to 1500 min 1700max and it did it. I'll edit this post to see if flashing works. Im charging my touchpad at the moment.
EDIT: flashed. So far no SOD but its a little too soon to tell. We'll see what a few hours does.
Sent from my DROID X2 using xda premium
EDIT: I seem to have all functionality and I have not SODed yet. Looks good so far
Sent from my HP Touchpad using xda premium
mouseym said:
Not a single SOD here, but i skipped alpha 1.
Click to expand...
Click to collapse
Same here, i started on Alpha 2.1
i think the problem is alpha 1 related
im guessing a clean wipe will fix the problem...
I had sod from hell.. I just kept it on the touch stone to keep it awake in between.
This fix worked though. Whole day without death
Sent from my HTC Glacier using Tapatalk
Try No-Frills from Market. He's on here too. No SoD for me. It has some feature that prevents it.
Alpha 2.1 was already out by the time I got my touchpad, only had 2 SOD on it prior to installing this patch and none since. Currently I am using No Frills CPU with 192 min and 1512 max I think. Running great and no other issues to speak of. Sound is working fine and this has not impacted my battery life at all, may even be better.
Op should be updated to state that this kernel breaks sound on alpha1. Make sure you are on alpha2 before flashing.I posted both a revert and a repackaged alpha2 with the fix already applied in the thread on rootz.
Sent from my Sensation using XDA App
cpittman said:
Op should be updated to state that this kernel breaks sound on alpha1. Make sure you are on alpha2 before flashing.I posted both a revert and a repackaged alpha2 with the fix already applied in the thread on rootz.
Sent from my Sensation using XDA App
Click to expand...
Click to collapse
I just updated my original post in this thread with a disclaimer about the sound issue. I think it's also affected some alpha 2/2.1 folks, so basically I'm just making sure folks know about it and know to consult the original thread for information about how to resolve it.
Ya I'm not sure what the common thread is with no sound then. I only experienced it in relation to alpha1.
Sent from my Sensation using XDA App
I've been getting random reboots for a long time now. But it seems to have been getting more frequent recently. Did some research and many said to post up my last_kmsg. Here it is. Hope someone can identify the problem for me. I thought it was the kernel (previously using franco), Hence I dirty flash PA again. It happened on previous versions of PA too and I factory reset from time to time. So I'm not sure whats causing the issue. I cant seem to emulate the reboot. It happens even when my phone is in sleep mode. Let me know if there's any other info that you need. Thanks
Radio: .84
PA Version: 3.99
Kernel: Stock
what apps do you have installed?? is chrome or chrome beta one of them?...i had installed chrome beta and had random reboots as well...if not then try to install a different rom..see if that helps
sometimes it happens i would recommend you a factory reset and try with other ROM.
for example Carbon Rom + Hells Core no deadlocks and very fluid and stable!
they release a nightly per day!
orenzai said:
I've been getting random reboots for a long time now. But it seems to have been getting more frequent recently. Did some research and many said to post up my last_kmsg. Here it is. Hope someone can identify the problem for me. I thought it was the kernel (previously using franco), Hence I dirty flash PA again. It happened on previous versions of PA too and I factory reset from time to time. So I'm not sure whats causing the issue. I cant seem to emulate the reboot. It happens even when my phone is in sleep mode. Let me know if there's any other info that you need. Thanks
Radio: .84
PA Version: 3.99
Kernel: Stock
Click to expand...
Click to collapse
I too have been getting random reboots on PA since moving up to 4.3. I can live with them as they only seem to occur when I'm not using the phone. My guess was it's an issue with 4.3 or PA ... which will be fixed I time, or it's because I restored all apps with titanium, which I don't usually do, and something got ****ed along the way?
acridity said:
what apps do you have installed?? is chrome or chrome beta one of them?...i had installed chrome beta and had random reboots as well...if not then try to install a different rom..see if that helps
Click to expand...
Click to collapse
I just uninstalled chrome beta as you suggested and install chrome in. I'm also suspecting a certain app that is causing the reboot but can't seem to pinpoint which. Hope someone that can interpret the last_kmsg could point out the cause. Will monitor a few days to see how it goes.
alvin182 said:
sometimes it happens i would recommend you a factory reset and try with other ROM.
for example Carbon Rom + Hells Core no deadlocks and very fluid and stable!
they release a nightly per day!
Click to expand...
Click to collapse
Is this ROM battery friendly? Battery is a main factor for me since I don't use much of the customisations like halo or pie. My battery brains reeeealy fast when I turn on 3.5g. Such vast difference compared to when I just use 2g.
Sent from my Nexus 4 using xda app-developers app
nice! if you have uninstalled chrome beta then your problem my friend is solved! ....if you ask me...Vanir Rom by mbq with Hells kernel is a beastly combination. Battery is damn good i get 4-5 hrs of screen on time...and its damn fast too, closest thing to psx compared to speed with almost all the customization you would want
orenzai said:
I just uninstalled chrome beta as you suggested and install chrome in. I'm also suspecting a certain app that is causing the reboot but can't seem to pinpoint which. Hope someone that can interpret the last_kmsg could point out the cause. Will monitor a few days to see how it goes.
Is this ROM battery friendly? Battery is a main factor for me since I don't use much of the customisations like halo or pie. My battery brains reeeealy fast when I turn on 3.5g. Such vast difference compared to when I just use 2g.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yes my friend! i am looking for the battery friendly and this one is so stable! and hells kernel is being a good kernel even in Beta.
use 2G we cant do anything respect this.
You will need to catch a log when the reboot happens, since the last_kmsg is only written when the reboot happens, and is not written in case of soft reboots... So i thinkj last_kmsg won't help...
Mine was rebooting fairly often. By chance i went into settings > date and time and somehow the setting for “automatic date and time" got unchecked. Since I checked it I haven't gotten any reboots yet. Just posting this to see if anyone who has been having random reboots has that setting unchecked.
acridity said:
nice! if you have uninstalled chrome beta then your problem my friend is solved! ....if you ask me...Vanir Rom by mbq with Hells kernel is a beastly combination. Battery is damn good i get 4-5 hrs of screen on time...and its damn fast too, closest thing to psx compared to speed with almost all the customization you would want
Click to expand...
Click to collapse
I took up your advice! But I'm still on stock kernel. Not sure if the jss hells kernel will be compatible with the 4.3 rev3. But it was mentioned on the thread that it is though. Haha. I'm getting 2hr+ screen on time with 2g. Maybe I should flash hells?
destronije said:
You will need to catch a log when the reboot happens, since the last_kmsg is only written when the reboot happens, and is not written in case of soft reboots... So i thinkj last_kmsg won't help...
Click to expand...
Click to collapse
I just fetched all 4 logs using syslog app. Will that be helpful? I'm really a noob in this. Hahaha can't read the codes.
threi_ said:
Mine was rebooting fairly often. By chance i went into settings > date and time and somehow the setting for “automatic date and time" got unchecked. Since I checked it I haven't gotten any reboots yet. Just posting this to see if anyone who has been having random reboots has that setting unchecked.
Click to expand...
Click to collapse
Hm... Interesting. Mine have been checked all these while. Don't think this is what's causing my reboots. I'll keep an eye on it nonetheless.
Sent from my Nexus 4 using xda app-developers app
battery life usually depend on kernel..not so much on the rom..give hells kernel a try and see how much juice you can squeeze from your battery...im running jss kernel on rev 3 and works perfectly fine so no need to worry abt that...matrix, semaphore and franco kernel are good alternatives as well if hells kernel doesnt work for you...Are you still getting those random reboots?
The speed of vanir is craaaazy. But I'm not getting more than 2.5hrs screen on when on 2g. And there's some weird issues with the camera. Like screen tearing. Im guessing that would be from the hells kernel being incompatible to an extent.
How do you get 4-5hrs screen time??
Sent from my Nexus 4 using xda app-developers app