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.
Related
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
I can't put my finger on this issue I've been having with my Note.
Don't get me wrong, this device is a godsend!
The problem I've been having is that sometimes when I take my Note out of my pocket and try to press the unlock or menu button it doesn't show anything on the screen. I've read about people having issues with delay before it pops up, but it doesn't pop up even after 10 seconds or a minute, it feels like the device 'hangs' or doesn't want to wake up. The only way I can turn the phone on again is by pressing the unlock button for like 10 seconds and the phone reboots.
I thought it was a problem with Green Power, I thought it maybe had issues turning off the wifi or data when the screen was locked and that the service would cause the OS to crash or 'hang'. When I look at my battery history after the reboot it shows that I lost a significant amount of battery (5-15%, depending on how long it took for me to 'discover' the crash) and there's a 'jump' in the graph.
Things I've tried:
Stock rom - problem persists
Different kernels - tried all the kernels available in the market including stock, problem persists
Add a bit of paper between back-cover and battery (to make sure it doesn't lose contact)
Checked if there was dust between battery connections
Tried different sim card
Tried disabling wifi and data all day (mysteriously persists)
DIfferent governors (ondemand and interactive) (the phone reverts to default governor after the forced reboot, normal? i have my phone set to interactive on boot, but somehow it skips that after the forced reboot)
I've attached a picture of the battery graph. According to the stats there's a 25 minute gap where the phone was 'stuck' and you can see that the screen was on and active for that duration.
There are NO funny apps running in the background, this is is a clean install with some standard Samsung apps frozen.
tl;dr version: phone randomly won't wake up; battery loss after forced reboot;
I might have found the issue myself. Now when I come to think of it, I think it always occurs after I've been in my car for like a 30 min drive... Maybe the phone is having trouble switching networks? Anyone know what might be causing this?
Or better yet, how can I research this issue? Can I enable some logging somewhere to track this?
I had the note for about 10 days and today, about 1 hour ago it happened to me for the first time. I tried the home button to wake the screen but nothing, tried the power , nothing and holding the power but nothing happened. I had to pull the battery.
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
tamarian said:
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
Click to expand...
Click to collapse
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
I'm on stock room and unrooted. Like I said first time it's happened.
i've had the GNote since 4 days now , and yesterday same thing happened as the device was in my pocket and i couldnt wake it up at all , battery pull solved it.
im on stock , non rooted
I can't believe that we are the only ones with this issue. Anyone else? OR better yet, how did you resolve it?
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
kirkla79 said:
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
Click to expand...
Click to collapse
Thanks for your reply. I did some research, and apparently it had to do with static being built up in the screen from wearing it towards your body in your pocket.
This issue was that you couldn't swipe the lockscreen cause the touch screen wouldn't respond. The problem we are having is that the screen won't even turn on and that the system locks up.
Same issue here with my 2 days old Galaxy Note, that's how I found this forum. In my case it went from not waking up occasionally to every time WIFI was ON (I did some experimenting with settings to see which one could be the one causing the problem). But then...occasionally it would not wake up even with WIFI OFF: very annoying. And this is my first Android, so I didn't have any custom anything, pretty much same as out of the box when I got it The only solution was to reset the handset. And definitely has nothing to do with having it in my pocket as I don't carry it in my pocket. Rang Samsung, they told me it was faulty, I returned it. Now I'm concern the next one is going to have screen issues? As so many people complain in this forum? we'll see.
My issues have been resolved after flashing AbyssNote 1.4 and when I stopped using System Tuner. I've started using Voltage Control instead and now I'm not even having problem @ 100Mhz undervolted 50mV from stock.
Same problem with my wife's Gnote, totally stock, just a small handful of apps installed. Happened twice, about a week apart.
She does a lot of travelling, maybe you're right about that. But it happens after she gets home when it's still OK.
Had the same same issue twice in two days and had to do a battery pull, just did a master reset and re -installed the applications manually, so far so go.
YOu guys think its a hardware or a software issue?
Hmm.. Happened to me too about three times in the last two weeks. I am on stock rom but rooted, and running Green Power. Hopefully samsung will fix it in the next updates. Seems like a software bug to me. Maybe not enough juice when in deep sleep?
metus666 said:
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
Click to expand...
Click to collapse
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
neunzehn77 said:
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
Click to expand...
Click to collapse
problem is it also happens on stock rom.
mfractal said:
problem is it also happens on stock rom.
Click to expand...
Click to collapse
It's very well possible that the stock kernel has faulty settings for the CPU. Haven't had the problem again with AbyssNote 1.4 and Voltage Control (even with custom cpu frequencies)
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
qazkamakazi said:
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
Click to expand...
Click to collapse
at this point we're just guessing, there haven't been any official confirmations of the problem as far as i know.
But if it's so accute that it keeps happening all the time you must have a faulty device.. call samsung ?
I'll try to keep this brief. Earlier tonight I downloaded the Nova Launcher on the google play store. It worked fine, I set it up how I wanted, etc etc. Well I went to looking for an app to replace the circles app on stock ICS. I found an app called "Fancy Widgets" and downloaded it. Practically as soon as it finished downloading my phone rebooted. I thought, maybe, it just needed to reboot for the app to take effect. I had to do that with a previous phone.
But no, Now my phone is just in a constant loop of boot and load to the home screen, wait 10-20 seconds and reboot. It just keeps going through this over and over so basically my phone is useless at the moment.
Does anyone know how to help this? I'm lost. If I can't get it figured out I'm going to have to stay up all night trying to figure it out because my phone is my alarm clock and I'll oversleep otherwise. So.. Please help!! Thanks!
Parham112 said:
I'll try to keep this brief. Earlier tonight I downloaded the Nova Launcher on the google play store. It worked fine, I set it up how I wanted, etc etc. Well I went to looking for an app to replace the circles app on stock ICS. I found an app called "Fancy Widgets" and downloaded it. Practically as soon as it finished downloading my phone rebooted. I thought, maybe, it just needed to reboot for the app to take effect. I had to do that with a previous phone.
But no, Now my phone is just in a constant loop of boot and load to the home screen, wait 10-20 seconds and reboot. It just keeps going through this over and over so basically my phone is useless at the moment.
Does anyone know how to help this? I'm lost. If I can't get it figured out I'm going to have to stay up all night trying to figure it out because my phone is my alarm clock and I'll oversleep otherwise. So.. Please help!! Thanks!
Click to expand...
Click to collapse
Already tried power and volume down button (6 sec)?
Good news is the att sound works as a good alarm. I found out when mine did that. Restart in safe mode by holding down power and volume rocker then do a factory reset.
Sent from my MB886 using xda app-developers app
funny, I've had nova launcher working with fancy widgets when i updated my phone and it went into a reboot loop. it only happened to me when i updated the phone though
My first Atrix HD rebooted itself daily, sometimes bootlooping and causing me a lot of grief. The phone was fine for the first two days. After that, it went haywire. I would run logcats to try to determine the causes of the bootloops. I always found an error with some random app. I'd uninstall it and the phone would be fine for awhile. Eventually, I came to the conclusion that a problem with the wifi radio was the underlying cause. If not, the wifi problem and reboots were co-morbid, so to speak, and related to the same problem. I was pretty sure the real problem had to do with faulty hardware. I exchanged the phone for another. I've had this one for three days now and it just rebooted itself about 15 minutes ago. That bugs me.
I like the phone, but I think there may be an unusually high number of defective units out there. That's based solely on anecdotal information, but I believe it to be true. If anyone has any additional theories or has an explanation for these reboots, that would be a great help to me.
McEwen.
McEwen said:
My first Atrix HD rebooted itself daily, sometimes bootlooping and causing me a lot of grief. The phone was fine for the first two days. After that, it went haywire. I would run logcats to try to determine the causes of the bootloops. I always found an error with some random app. I'd uninstall it and the phone would be fine for awhile. Eventually, I came to the conclusion that a problem with the wifi radio was the underlying cause. If not, the wifi problem and reboots were co-morbid, so to speak, and related to the same problem. I was pretty sure the real problem had to do with faulty hardware. I exchanged the phone for another. I've had this one for three days now and it just rebooted itself about 15 minutes ago. That bugs me.
I like the phone, but I think there may be an unusually high number of defective units out there. That's based solely on anecdotal information, but I believe it to be true. If anyone has any additional theories or has an explanation for these reboots, that would be a great help to me.
McEwen.
Click to expand...
Click to collapse
Yeah, I wish someone knew what the problem was. After I posted this originally at the beginning of October, I deleted Fancy Widgets and didn't have any more problems with boot loop until this week. I blamed it on my two newest apps and un-installed them, but the problem is there somewhere and I randomly reboot after installing Nova back.
This really bothers me. I had just gotten used to how I had everything set up in Nova. The stock launcher is disappointing in comparison now that I've experienced something better.
Parham112 said:
Yeah, I wish someone knew what the problem was. After I posted this originally at the beginning of October, I deleted Fancy Widgets and didn't have any more problems with boot loop until this week. I blamed it on my two newest apps and un-installed them, but the problem is there somewhere and I randomly reboot after installing Nova back.
This really bothers me. I had just gotten used to how I had everything set up in Nova. The stock launcher is disappointing in comparison now that I've experienced something better.
Click to expand...
Click to collapse
Replying to myself, but yeah..
It now looks like my issue has something to do with DoubleTwist music player. Nova worked until I tried to put a DoubleTwist widget on my homescreen and it IMMEDIATELY went into boot loop.
Hi there,
just wondering if anyone else are having issues of their phone randomly rebooting? does anyone know of a fix?
also, sending photos as an attachment does not work. in order to send a photo to anyone on your contact list.
found a work around by going through gallery and sending it directly from there.
if anyone know of a fix for either issues. the help would be greatly appreciated.
Thanks,
kevin
I've had several random reboots. Oddly enough, they usually occurred overnight when I wasn't using the phone. I would hear the vibration on my windowsill and saw it was rebooting. I did a factory reset yesterday and while in the midst of setting everything up on my phone, it rebooted again. I thought that maybe there was too much going on and it overloaded. But last night when I was out and not using my phone, it rebooted again. I'm gonna have to go to Verizon to swap the phone.
It keeps happening on mine, but almost always in the car while attached with BT. I'm wondering if BT has something to do with it, in my case.
Same thing
I am also experiencing the issue specifically at night. I have yet to actually have it interrupt me in anything but its still a concern. Just curious about whether for those of you who are experiencing it are using the Assist app or Android Assistant?
I only use the Assist app for when I'm in the car. It's not setup for night time. I exchanged my phone at Verizon today and so far so good. One of the employees tried telling me that the reboots could have been because I had Better Battery Stats installed on my phone and the battery saver apps can conflict with the OS. I blew his mind when I told him that BBS wasn't a battery saver app and simply lets people know about specific wakelocks. Seemed like no one there had any idea this phone even existed.
For the reboots, I guess tonight will be the big test.
It happened again to me this morning as soon as I got in the car and it connected to Bluetooth. Once it reboots, it's solid.
MVPete1 said:
I only use the Assist app for when I'm in the car. It's not setup for night time. I exchanged my phone at Verizon today and so far so good. One of the employees tried telling me that the reboots could have been because I had Better Battery Stats installed on my phone and the battery saver apps can conflict with the OS. I blew his mind when I told him that BBS wasn't a battery saver app and simply lets people know about specific wakelocks. Seemed like no one there had any idea this phone even existed.
For the reboots, I guess tonight will be the big test.
Click to expand...
Click to collapse
Please report back. I have gone 24 hours without a reboot with no changes to the device which is a first. If it doesn't have a Samsung or Apple logo no one seems to care anymore.
I can't get Assist to work at all. I typically listen to podcasts in the car and when texts come in I get a notification sound but I've never had one read to me. I disabled Assist to see if this was the cause of my Bluetooth reboots, and it's not.
With Assist disabled entirely, each time my phone pairs with Bluetooth it connects but the moment I start to play something it reboots. It's very consistent.
Phibaroptik said:
Please report back. I have gone 24 hours without a reboot with no changes to the device which is a first. If it doesn't have a Samsung or Apple logo no one seems to care anymore.
Click to expand...
Click to collapse
Just wanted to let everyone know that I haven't had any reboots with the new phone. I exchanged my old one for this one on Monday and so far everything's been good.
I have now had 3-4 random reboots that I have seen. I have also witnessed a complete lock up of the phone. I will be heading into Verizon today to exchange my phone.
Just wanted OP to know more people are having issues.
ricwhic414 said:
I have now had 3-4 random reboots that I have seen. I have also witnessed a complete lock up of the phone. I will be heading into Verizon today to exchange my phone.
Just wanted OP to know more people are having issues.
Click to expand...
Click to collapse
Same here and wondering if that's "Normal" too...
My Moto X turns off at night during charging.