Related
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
We are going to need some more information to better assist you.
1) What Build are you using
2) Are you running Apps2SD
3) How much space do you have left on your internal storage?
Sure, thanks
Jf 1.5
Radio: 26I
No A2SD
31MB free
Nothing crazy.
I wipe every time I flash.
I've tried factory resetting too.
I try to keep the system clean.
he3 said:
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
Click to expand...
Click to collapse
Something like this happened to me about a month or more ago. It was everytime I try and use my phone when I was charging it, it would reboot. After a few days it would just do it at random. I just called tmobile and they just sent me a new one out.
the same thing is happening to me. my phone randomly crashes/reboots and i was starting to think it is the Haykuro build im using. is there any way to test the hardware? is there something like that in an app?
help
Are you using ahome or someting like that cause those programs cause problem with 1.5 uninstall all your theme apps if you have any
No, no themes.
Called t-mob, since I've had the device (sans insurance) less than a year, they are sending new hardware without a battery to replace mine. I decided to add insurance to the new hardware just incase. Thanks for the input! Glad I called!
Now to virginize the phone... heh
I have the same problem. There's a lot of this going around. It sure seems like a coincidence that it started with Cupcake for most all of us.
This has been something that has been happening since the RC33 load it...
Now I got the stupid random reboot problem. This is a warranty replacement and my first one never did this. I guess I gotta get another warranty replacement. Anyone find a definitive cause for this yet?
almost 100% sure you have a hardware problem
savethechicken said:
This has been something that has been happening since the RC33 load it...
Click to expand...
Click to collapse
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
rikupw said:
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
Click to expand...
Click to collapse
RC33 was the OTA was in March I believe maybe Feb. This didn't happen as much on RC30 and then RC33 came out and this started to happened more often. Obviously it is not the ROM doing it as not everyone has the problem but something seemed to trigger it on some devices.
alapapa said:
almost 100% sure you have a hardware problem
Click to expand...
Click to collapse
Going to have to agree. This is starting to seem like a Hardware problem, considering all the feedback we are being given.
I have the same exact problem.
It's definitely a hardware issue.
I was thinking it was because my extended battery pack is a little loose or some loose wiring. It happens when the phone is bumped a little. Like putting it on a table too roughly or flipping the screen up too quickly or it shaking in my pocket. Probably going to replace it.
I have this same problem...i had it originally with RC33 then it went away with the cupcake update and I recently root and install cynogen's build and its back to screw up my day
i don't think its a hardware thing ...at least in my case doesn't make sense to be gone for a month and then come right back after rooting
I also experience random reboot issue. Usually when the phone hang first then next thing you know, it is rebooting. Sometimes the phone will be just sitting there and it will reboot by itself. I always thought it is the ROM issue, never suspect hardware. I am running an old version of Dudes v1.3a build.
For me too
I am getting too many reboots too, just got a replacement phones(previous one did this too), same with this phone, first i thought it was Hardware but now it think its the roms. On hero it rebooted 3 times while booting the first time, on cyanogen it rebooted in a couple of hours, just dont know what the problem is, maybe abusing the phone
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
charnsingh_online said:
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
Click to expand...
Click to collapse
Makes me wonder on the apps your using in the background or settings you have up, or even the ROM. Do you have any extra info whats up before it reboots? Does it choke out due to low memory maybe?
Hi guys,
Just wanted to see if anyone else had this issue. I installed SGS Tools to check my product id and a couple other things, and i had some issues with it. First after installing it, my internal SD card wouldnt mount, unless i rebooted and tried again. Then sometimes it would just leave it unmounted after i disconnected the USB cable. I also noticed some heavy battery drain while this app was installed.
Did anyone else experience this? Or was this just some freak thing that shouldnt happen?
Im on Cog2.3b8.
Thanks.
theMaDHakkeR said:
Hi guys,
Just wanted to see if anyone else had this issue. I installed SGS Tools to check my product id and a couple other things, and i had some issues with it. First after installing it, my internal SD card wouldnt mount, unless i rebooted and tried again. Then sometimes it would just leave it unmounted after i disconnected the USB cable. I also noticed some heavy battery drain while this app was installed.
Did anyone else experience this? Or was this just some freak thing that shouldnt happen?
Im on Cog2.3b8.
Thanks.
Click to expand...
Click to collapse
Never noticed any battery drain due to the program. Have never seen it running or starting without me opening it.
RE: The mounting issue.....i would suggest it has absolutely nothing to do with the SGS Tools program. The more likely culprit is something that occurred during your flash process. The only time i have had mounting issues was after a bad flash.
None of that has ever happened with my SGS Tools; was running stock 2.1 up until recently with the Rogers 2.2. Maybe it'll happen now?
This is just strange. Ive been running cog for almost 2 weeks with 0 issues until I installed this. And once removed the issues seem.to be gone. I'm baffled.
Sent from my SAMSUNG-SGH-I897 using XDA App
Strange. SGS tools is one of the basic apps I install whenever I flash a new ROM. Never noticed this drain.
I have done some research here and on Google on a really odd problem...
My wife has a NC I updated to 1.0.1 then rooted. About a week later on her way to work it restarted and unupdated (?) back to 1.0.0... So I thought it was a fluke, root was gone but most things still worked, not Youtube or market but other apps I installed while / did.
Now twice, 2 days in a row I have checked out the device, I installed Clockwork, did a backup and the next morning on the way to work (She works in manhattan, takes the train in) it is bootlooped "touch the future of reading" so last nite I ran the clockwork restore and it was fine then again this morning... same thing stuck in a boot loop.
As happy as I am about her being able to restore it on her own...it takes a while and shes at work by the time its done! and the maddening part is that I booted it multiple times the nite before in both cases...
What could be causing this? Things I haven't tried yet?
I checked the SD to make sure there weren't any update.zips or similar,
I have not formatted the SD, that I will do tonight.
I read the whole thread regarding Clockwork I didn't see anything I might have messed up...Does this have to do with uSD boot priority and maybe I have a hidden file on the SD?
And I have really searched for something similar, people have bootloops but not like mine that I can see.
Sorry for being long here but this is frustrating, I'm not all that new at this I've been voiding my warranties for a long time and this one has me stumped...
Thanks in advance for any reasons, suggestions.
EDIT: Looks like I am not alone, I am seeing more of these problems pop up now.
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
eyecrispy said:
Did you disable OTA updates?
I'm on 1.0.0 and haven't had issues at all. Seems that folks having this issue are all on 1.0.1 (or at least from what I've noticed). So, perhaps, to go 1.0.0 and root?
Click to expand...
Click to collapse
I have disabled OTA but if this is a registration/ auth problem I guess it wouldn't help.
I have NOT gone the 1.0.0 then root path and that sounds like a good next step, thank you.
First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)
Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.
To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.
I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.
Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state
I can't believe I'm the only one with this problem
lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?
I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.
unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.
Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.
Well, strange that only two or three of us noticed this strange problem.
Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...
I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
My vote is to go with a custom ROM. It will solve all of these problems. Cognition is the most similar to stock and is quite easy to flash. As for the problems you are having, I don't know what to tell you.
Try Cognition 4.5.3. You won't be disappointed.
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Well, not busy tonight. Watching pre-season football.
Flashing a Froyo rom is not too bad. Since you have stock 2.2 it will be a little more tricky than if you were still on 2.1.
First, what is your build number? look on the sticker under your battery to see a four digit number beginning with either 10 or 11.
I will private message you with more.
taltal13 said:
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Click to expand...
Click to collapse
Make sure you READ EVERY LINE OF THE OP. When you think you got it, read it again, then give it a shot. For the time being just factory reset your phone, should clear up some of your issues. Good luck
sent from long ago, in a Galaxy far, far away.
^^^ he's right. READ, READ, READ... until you're sick of it. It will pay off and keep you from bricking. Sorry I didn't mention that. But I will be glad to help you if you need.
and if (or when) you manage to brick it do not panic,, go back and read some more,, seems that almost everything an idiot like me can do is fixable,, and most normal people are pretty safe,, they are not going to kill their phone,,,,if they read and follow instructions,,,not doing those two have found my phone in some pretty unresponsive states,, but I am running mosaic VI now and loving it,,but have been on so many I had to go look,,and have finally I hope learned the value of reading ( and those other people probably do know more than me so I should not think I know better ,,,yet)
taltal13 said:
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
Click to expand...
Click to collapse
Not sure how much of knowledge you have gained before doing these attempts of changing some values to enable side-loading...
I would suggest to do factory reset since you are still on FROYO and see if this does the magic.
If it gets locked back to AT&T, I suggest just talk to AT&T rep to unlock & side-enabling. Once all is well, you can do rooting as you did before. Hope this helps to solve your problem.
For any other help, we have XDA here and get some time to go through forums. As others suggested, please read, understand and act.
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
taltal13 said:
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
Click to expand...
Click to collapse
Just for a bit of encouragement ive been using Cognition 4.5.3 as my daily driver for the past 4-5 months and have never had a single issue with great battery life. Ive tried numerous other roms on this forum and always have run into a boot loop, force close, or other random issue that makes my phone unstable but with Cognition I experience what my phone was meant to be like.