When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance
Which rom are you using?
I get what I call ghost notifications of text messages kind of the same way. I'll look at the message which clears the notification bar. When I turn off my phone at night and then back on in the morning I sometimes get a notification of the message I have all ready looked at. I think this was a problem in the international 2.2 roms hence the update to 2.2.1.
Oh, I'm using Cognition 4.1.1 ..... for now.
I am using the stock one. I haven't messed with the phone at all.
Oh ok thanks, to me it only happens when i turn it off it resends txts that i previously sent. It's kind of annoying not a big deal but gets old after a while. Thanks
I never had this problem with all ROMs I flashed. Or possibly I never noticed that happening. But I have to say that sometimes I still get double notifications for messages I have received previously after rebooting. personally I don't know why. I've tried cognition, phoenix, serendipity and now on firefly.
Sent from my SAMSUNG-SGH-I897 using XDA App
droid_07 said:
When I turn off my phone because the memory gets real low even when i auto kill my apps or my phone simply dies due to low battery, i turn it on but somehow it resends a bunch of txts to my friends that i was txting with. I was wondering if this happens to anyone else and if there is a way to fix it? Thanks in advance
Click to expand...
Click to collapse
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?
modest_mandroid said:
What do you mean by "I turn off my phone because the memory gets real low even when I auto kill my apps"? Are you checking how much ram is free and shutting your phone down because of that?
Click to expand...
Click to collapse
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.
droid_07 said:
well when my phone gets to a certain point as far as RAM it will turn off on its own. kind of like it resets itself i guess or i will turn it off myself and turn it back on otherwise it will be really slow and that's when the resent text message thing happens.
Click to expand...
Click to collapse
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.
modest_mandroid said:
That doesn't sound right at all.. Android is supposed to try to fill up the ram with the most recently used apps for quick access, but still manages a pool of free ram to keep things running smoothly. It should never get to a point where it "runs out" or shuts itself down, or even causes the phone to 'run slow'.
If you're running the stock official KB1 rom, then it's probably some app you're running that launches a very poorly coded service in the background that is eating all of your resources. You can try using a program called "Watchtower" that will tell you how much memory and cpu cycles each program is using to debug your situation, or simply uninstalling suspect apps until the situation improves.
Also, what batch is your phone from? You can find the build number under the battery, it's a four digit number like 1007, 1008, etc. Some of the earlier batches have a random shutdown problem affecting them (hardware defect), and if yours falls into the range of affected phones, you can go to an ATT store and they'll replace it with a new one.
Click to expand...
Click to collapse
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help
droid_07 said:
Let me try the watchtower app first and I'll see if that helps me find the issue.
My build number is 1012, do you know the range for the ones affected by it? Thanks for your help
Click to expand...
Click to collapse
I don't know the specific range, but I remember hearing that if you bought your phone before Nov 2010, you were eligible for a replacement. I could be wrong though.. I think there's a thread about it in the general section.
Related
What is going on here? It either freezes when:
1) slide-to-unlocking
2) switching between programs
3) google sync icon shows up in notification bar
4) in apps
Need to pull battery all the time! What's going on?
I've had this ever since the FRF50! I'm so annoyed and want to go back to 2.1, but I do love the battery life I'm getting with FRF91.
Any help please?
Sorry, realized I posted this in the wrong forum. Can MODS transfer the thread to Q&A?
I'm getting freezes on the same situations you have posted. However not with the same frequency as you. Mine is 1-2 daily.
Sent from my Nexus One using XDA App
strange, my phone is stock and ive had none of these issues, i actually thought my battery life had worsened since 91. It seems like the green meter doesnt drain as quick but the actual percentage drains faster than ever for me, at least i think so
This should unusual and should not be happening. Wipe everything and reflash.
That's Strange... I haven't had any freezes since installing the FRF91 OTA.
galaxys said:
That's Strange... I haven't had any freezes since installing the FRF91 OTA.
Click to expand...
Click to collapse
Yepp, same here! Never had a single freeze/lock-up since I manually updated to FRF91 from EPF21.
Hardware Issue
Seem to me you either have a defective apps or widget, a defective SD or a hardware issue like defective video ram or something like that, you could try to use a benchmark app like quadrant this may help pinpoint the exact subsystem that cause crash (video, cpu, ram) and try running stock OS with almost nothing loaded ...
This is assuming you are running from a clean install, When you have issue it's always a good idea to clean install (full wipe etc...)
Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.
Mine is stock and sometimes it freeze when I tried to unlock. I had to turn the screen off and on 1-2 times to make it work again
Following your advice and let me monitor for a day or so. If doesn't work I will wipe everything and reflash.
Thanks!
mingkee said:
Try to go to bootloader (press and hold trackball when power on), then go to recovery and clear out cache.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
wipe everything and flash both FRF91 and the latest gapps.
1. How many app you have and 2 are they on your SD? If you have alot of apps ittaking up your internal space causing you to freeze.
Sent from my Nexus One using XDA App
I actually installed spare parts the same day i installed stock frf91, so i am not sure who is the culprit. It didnt happen today, but froze yesterday and the day before.
turned off all the animations (transition/window) to get maximum speed out of my n1 using spare-parts maybe thats causing the craziness no?
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.
still froze twice today....wiped + reflashed FRF91..now resetting up my phone .... hope this will stop the freezes...will report back
Xialis said:
Same here, 2 or 3 times per days.
I have found that cpu is burned by com.android.email ! This apps eat all cpu power when there is no wifi/data connections available and it try to sync mail...
The phone become unresponsive or very slow until connection return or I kill the app.
Click to expand...
Click to collapse
I think I found a solution.
Go to email account, settings
Auto check->off
DarkDvr said:
I have same issues with that process. Setting both gmail and exchange to PUSH solves the problem.
Click to expand...
Click to collapse
Thanks, It works
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
random shutting down
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
ice3186 said:
Okay so i had this problem but it only arises for me when i do a few things. i have spent hours scratching my head about what it could be and through process of elimination i found on my phone it was one of two things.
1.) make sure that if you are using the auto kill feature in ATK that its not set to anything above safe
2.) if your using setcpu with profiles selected and have a very low profile for when the screen is off then try ramping that profile up a little bit to give the phone a chance to run background processes a little easier and actually wake up when you want it to!
hope it helps and if you give me info about what is going on then that should help us help you.
Click to expand...
Click to collapse
I havent been using ATK at all. Also does SetCPU really work with the hummingbird processor? When it boots it always kicks down to 19.2 which is obviously too low. I removed it just in case. I also set it back to the default settings. I would really enjoy SetCPU to save battery if it works of course. I thought it only works on HTC devices and Motorola devices?
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
domin8 said:
i had setCPU on my phone yesterday and it was freezing like you describe when trying to bring it out of standby. I pulled the battery twice before i said F-it and took the program off. If you were using setCPU i'd say that was your problem.
Click to expand...
Click to collapse
I deleted SetCPU and I thought it might be Screebl so I disabled it. Sure as hell it just went to a black screen and shut off again. God this is beyond annoying. I dont want to have to bring back this great phone but I need the phone to work.
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
madjsp said:
We've also got to think, Samsung just released this phone. The more we do to it from the market, the more things are gonna happen.
Most devs haven't had the time to really test and relay bugs from this phone that would cause other errors.
Click to expand...
Click to collapse
Yes but if I am correct none of these issues will be fixed until they decide to release FroYo?
EDIT: I just tried removing the MicroSD to see if that resolved the issue. Shocker...it didnt...
spyz88 said:
I was wondering if anyone else's Captivate has shut down automatically? It happened 3 times yesterday the screen goes into standby mode but if you try waking it up you had to pull the battery.
Last night I let it completely drain then completely charged it. When I picked it up it read 99% battery immediately. I went to get ready for work and check my email and it was shut off. I had to restart it again. Since then it seems as if the battery is lasting longer.
Click to expand...
Click to collapse
This has happened to me once. Came out of a meeting, pulled it out of my pocket, and couldn't get it to wake from sleep. I have not installed SetCPU, so it's not that. Not sure what the root cause was.
What apps do you have installed would probably be the more relevant question. And what have you changed?
Mine is doing the same **** and it is driving me NUTZ!!! I thought SetCPU first so I uninstalled and rebooted. Phone is still doing it. Please someone figure this out quickly. I am going through my apps one by one and uninstalling them to try to pinpoint the problem. Subscribing to the thread.
Interesting.... I haven't heard this happen to me yet so its probably an application or process your guys all have in common.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have a feeling it is setcpu. I just did a reboot after installing and now it is not happening. Cross my fingers!
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Like a lot of you, I started uninstalling my apps one by one when this happened. It stopped restarting after I finally uninstalled Launcher Pro. After that, the phone stayed on the whole night last night. It's weird because it worked with Launcher Pro for a good 2 days.
I'm also experiencing this issue, ad i've only downloaded a few apps.
Has anyone exchanged their phone over this yet?
Teklock said:
I'm having the same issue and I never had setCPU installed. sucks..
-Teklock
Click to expand...
Click to collapse
I reflashed to stock firmware and I'm still having an issue. I noticed that if you take the battery cover off the battery and push on it then it seems like it has a little give to it. Can anyone who is not having this problem confirm? Also, anyone who has this issue, please see if your battery has a little give to it.
It should be on the side WITHOUT the contacts. Also, if this doesn't work I'm bringing the phone back. I already had a problem with the first one and since this is my 2nd exchange AT&T wont exchange it anymore. They told me I need to go through the warranty. They are out of their minds the phone isn't even a week old. Never had these problems with HTC...
EDIT: I uninstalled ADW Launcher as a test to see if thats it.
EDIT 2: Make sure the battery door is covered tightly. I pushed mine all the way down until it clicks. Hold it down and then close the slider. I think this actually might fix the issue.
Anyone figure out why this keeps on happening? I've reflashed the stock as well and it still occurs randomly.
Strange this dosnt happen to me, and i installed setcpu(performance governor 1ghz/800mhz) but uninstalled it after seeing that it ****'s up gles 2 rendering...
I found this thread via Google search, and I just wanted to add that my phone started doing this last night, however, I have not added anything to my phone, nor is it modded in any way. It's completely stock. The only thing I have done thus far was remove all of the extra home pages and rearrange some app icons, and that was on Thursday and Friday. It does it both when it goes to sleep normally or if I hit the sleep/power button.
I narrowed mine down to SetCPU being underclocked while asleep. Bumped up the minimum clock and took off the profile I had set, phone hasn't rebooted in 4 days.
I've had the Captivate for about a week now and has powered off about 4-5 times for seemingly no reason. Each time it has happened has been when the device was idle/locked. Battery level has not been the culprit, as my charge level has been nowhere near low when it has happened. I've been missing phone calls because my phone has just shut off.
Has anyone else experienced this or do I just have a bad phone? Between this and the GPS issues I'm really starting to think about taking it back. Shame though because I love the screen!
i unroooted did a factory reset and everything im just getting a replacement so yeah
Haven't experienced that. Are you running an app killer or something?
I had the same problem. Last night and this morning it would go to sleep and I was unable to wake it up. Had to pull the battery and then it powered up. I had "setcpu" on it and I have since removed it. It hasn't shut off since. We will see if it holds up.
Citznfish said:
Haven't experienced that. Are you running an app killer or something?
Click to expand...
Click to collapse
I have Advanced Task Killer Free, but I do not have the 'Auto Kill' enabled. So it only kills apps when I run it.
Had the same issue like 5 days ago without a task killer or SetCPU. Not sure what it was, but hasn't happened since.
Try a full restore, and make sure it's not an app that is making your phone crash. If not AT&T has a 30 day return policy in store. They may want to do the restore, and have you try it for a few days. Just let them know you tried that already. If you take it back and have them check it out, if they can't fix it, they'll replace it.
I just replaced my phone due to battery issues, never had a reboot.
This morning I was listening to pandora at the gym and it just rebooted on me. Then again I never use pandora, but slacker was having issues this morning.
I will wait for it to happen again before I take action
I have pandora installed as well, but it's never happened while the player was running. I'm keeping an eye on the task killer and pandora, but so far it hasn't shut down yet.
Any gurus know if there is a shutdown/crash log anywhere to view?
My Captivate has shut off twice, ONLY when Pandora was running and it was plugged into the car charger. When I run with Pandora running, it hasn't shut off. I think it's a Pandora problem.
Ok, mine just crashed three times in a row. Two of the times I was changing the wallpaper. The third time, well I dunno. I've removed the Pandora and ESPN Score Center widgets to see if that has any effect.
I'm going to load the stock ROM when I get home to see if it is truly a hardware or software issue.
I'm almost positive it has to do with setcpu.. I was setting up my friends captivate and it was doing that to several times. When i restarted and checked setcpu just on a whim, the settings were all wacked out from what i had set.. the max was all the way to the left (lowest clock speed) and the min was also set all the way to the left.. when i slid the sliders the availible min/max values suddenly changed to 1000000 for both of them..
So im thinking setcpu is not getting along with some of the captivates..
I don't have setcpu installed. I haven't even rooted my phone yet. I only have a very small number of applications installed. Here's the list:
Advanced Task Killer Free
AppBrain App Market
Barcode Scanner
Facebook
Foursquare
Goggles
Google Sky Map
Google Voice
Pandora
ScoreCenter
Shazam
Alright, I did a complete wipe, restored the factory ROM, and haven't installed any apps and it's still happening. Guess I'm taking it back. Hope they're not a pain in the ass about exchanging it.
Its not SetCPU. The reason is the battery door is loose and not clicked in properly. When you place the battery door in push on the bottom part when you close the slider.
After that, no troubles. I ran into the same problem.
Game hero of sparta made my phone wack out.. even paid the 5 for it.... darn
Try to remove Advanced Task Killer Free. Once I did it on my phone the problem went away.
spyz88 said:
Its not SetCPU. The reason is the battery door is loose and not clicked in properly. When you place the battery door in push on the bottom part when you close the slider.
After that, no troubles. I ran into the same problem.
Click to expand...
Click to collapse
As far as I can tell, the cover is on correctly. The two clips are underneath the bottom slider so I don't think this is the issue.
dirtblade said:
Try to remove Advanced Task Killer Free. Once I did it on my phone the problem went away.
Click to expand...
Click to collapse
Again, Stock ROM with no third party apps installed and it's still happening. I'm lead to believe it's a hardware issue.
zorphnog said:
As far as I can tell, the cover is on correctly. The two clips are underneath the bottom slider so I don't think this is the issue.
Click to expand...
Click to collapse
Push harder. Trust me on this one.
Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.
I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.
Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.
Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?
Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).
I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.
My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).
Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.
I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908
I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk
My Note has started crashing regurlaly, I have had it since release and have a lot of software on it. I am not sure when it started happening but it is definatley getting worse as time goes on.
Is there any log file or event browser that can be installed to tell me what is causing the problem?
When I say crashing I mean literally crashing dead not a force close. I either find it in my pocket turned off and then have to hold the power button for an age to turn it on or sometimes it is sat on the desk and I suddenly hear the noise it makes when it re boots.
Any suggestions for finding out what the problem is that don't involve uninstalling software until the problem goes away?!
Thanks
Have you tried better battery stats? It gives a list of processes that have been running.
Definitely strange - do you have an anti-virus program you can run to see if it can help?
That sounds like a Sod (Sleep of Death) issue that's been reported many times b0t with no definitive solution of yet..
Some said changing modem helped, others with changing kernel or even ROM but no consistent solution across all users
Try to fix permissions through advenced menu in recovery but am afraid there is not much I can help with
wingnutLP said:
My Note has started crashing regurlaly, I have had it since release and have a lot of software on it. I am not sure when it started happening but it is definatley getting worse as time goes on.
Is there any log file or event browser that can be installed to tell me what is causing the problem?
When I say crashing I mean literally crashing dead not a force close. I either find it in my pocket turned off and then have to hold the power button for an age to turn it on or sometimes it is sat on the desk and I suddenly hear the noise it makes when it re boots.
Any suggestions for finding out what the problem is that don't involve uninstalling software until the problem goes away?!
Thanks
Click to expand...
Click to collapse
Omfg, I don't think your alone cause I have the exact problems at times when the note just freezes up and you have to manually boot up...lets hope the upcoming pics update will solve this ongoing problem... I'm getting this about 3-4 times a week
Sent from my GT-N7000 using XDA
it is starting to make the phone a liability as I keep finding it turned off in my pocket!
Is there no software that will produce a crash log of some sort?
wingnutLP said:
it is starting to make the phone a liability as I keep finding it turned off in my pocket!
Is there no software that will produce a crash log of some sort?
Click to expand...
Click to collapse
I hope there is...
Sent from my GT-N7000 using XDA
this is driving me nuts. The phone is unusable.... is there no possible solution??
At this point I will try anything. It crashed during the night on Thursday, didn't restart and so there was no alarm and I was late for work!
Please post your current configuration Kernel, Anti Virus program if any, undervolting, overclocking ?
By any chance are you using easy task killer... if you are just change the auto optimize to nothing - I did that and it stopped sleeping...if your problem is persisting then you could just do a factory reset and use default settings...
Sent from my GT-N7000 using XDA
My note recently started crashing as well, whenever i turn on my mobile data plan or the wifi it will crash right away
However this is ironic because when ever i put my mobile in charging mood than i have no problems at all.
So im thinking ,is this the battery problem or the software problem?
mumuxy said:
My note recently started crashing as well, whenever i turn on my mobile data plan or the wifi it will crash right away
However this is ironic because when ever i put my mobile in charging mood than i have no problems at all.
So im thinking ,is this the battery problem or the software problem?
Click to expand...
Click to collapse
battery problem.Try to see what is the output of ur battery in full charge by messure it with electric potension meter (sry for bad english).
If the meter say less than 1850mAh in full charge than u need a new battery.