Related
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!
Well, to tell the truth, I like this phone. Dual-core CPU, perfect screen, HDMI output etc.
But as soon as I get this phone, I found it cannot be wake up from sleep.
I heard that LG has released a update software to fix this problem, but after I had connected my phone to the computer and opened the LGMobile Update, it told me there was no newer update available.
So I'm trying to figure out the reason of this problem.
This problem does not happened every time when I push the ON/OFF button to put the phone to the sleep mode. If I just reboot the phone, and then turn off the screen, there will never be any trouble, even I put it on the desk for the whole night.
But if some programs has been run, like the games, map, internet browser, or even a call or SMS, then lock the screen, it will never wake up. Or if I plug in the charger or connect the phone to the computer, it works great with no trouble.
What's more, after the phone has 'dead', the temperature of the phone became high, and even became higher and higher, very strange.
So I try these way to solve the problem with no success:
-replace the battery with another one.
-wipe the battery information by using ClockworkMod and then re-calibrate the battery.
-flash a different version ROM, including MCR ROM and LG Stock ROM.
-flash a different version baseband.
-force the CPU frequency to stay in 800Mhz by using 'pimp my CPU'.
-lower the voltage of the CPU.
-forced the frequency to stay about 400Mhz when the screen is locked.
-remove any applications installed by myself.
-disallow any background applications.
-put the phone in the rom with air conditioner turning on which the air temperature is about 25°c.
Then I guess this problem is caused by power management bug.
There will never be any problem when the phone is awake, or the charger is plugged in, so I don't think it's a hardware bug.
Must be a bad unit. :-(
Sent from my LG-P990 using Tapatalk
As I said before.
When you press power button to wake-up the screen, and the screen is black (bsod), press power button again (so it would power off the screen, even tho the screen is black), count till 20/30sec and press power button again....
There yoy go, phone working again!
Ive overwon my bsod since I know this trick!
Sent from my LG-P990 using XDA App
Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk
Sckank said:
Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
No, no work.
Now, after playing games or using Google Map, I must turn off the phone, and then turn it on again to avoid this issue.
OK, now I can almost confirm that this issue is caused by overheat.
I boot the phone, then put it on the desk without any operation, it will remain OK.
Then I put it into my jeans pocket for about 1~2 minutes, it will be dead.
Again, after playing games, I put the phone just near the air conditioner, it will be cooled down very soon, and the issue will not happen.
So, is there any way to make the ‘temperature protection’ or something like that higher? Or just remove it from the Android OS.
I don't think removing any sort of temp failsafe would be a good idea.
I just had a bsod and the phone was really hot. If anything, it needs a proper failsafe put in, so it at least reboots in stead of hanging on the black screen
Sent from my LG-P990 using XDA App
I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym
TrymHansen said:
I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym
Click to expand...
Click to collapse
Thanks for reply dude.
But I've tried almost every version of baseband and rom already.
I'm from China, newest version of baseband I got is V10S, which is a Korean version, and the newest Chinese version is V10K. I have tried to flash the phone back to V10A - a European version ROM, and then update the phone using LG Mobile Update software to V10D, and this did no help to the issue.
As I said, this problem always happen when the temperature of the phone is high. I'm not sure whether the CPU/GPU temperature or the battery temperature will cause this issue (I prefer to believe it's because of the battery temperature, cuz the Google Map won't use too much CPU and GPU resource)
Another interesting thing I found, is that if I leave the music playing in background, then lock the screen, the phone will never meet any issue.
So now, my solution is to avoid the high temperature, or playing the music in background, muted, and then lock the screen. This may drain the battery faster, but at least I will never miss any call.
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
I noticed it yesterday once (and I just got the phone then too ;-; ), and it was while I was opening the camera app, I decided to open the keyboard for some reason (I don't know why), the phone locked up for a minute and then just rebooted. I also had a temporary lockup while opening up the keyboard while opening Handcent, but it regained responsiveness after about 15 seconds. For me it happens to be something to do with the keyboard while opening apps. We need more people to reproduce this problem so we can get down to the root cause :|
Got two droid 3`s in my house and haven't experience any random boots.
Sent from my DROID3 using XDA Premium App
Happened to me while talking on the phone a few times. Got a replacement and it happened again. Never with the keyboard though. Very troubling especially with the second handset.
I have experienced reboots with the camera and camcorder apps lagging, and just general issues with those apps anyway.
Sent from my DROID3 using XDA Premium App
I haven't had it happen since I originally posted until today. Today it rebooted in my pocket.
Perhaps it could just be a heat issue. I noticed that another thing along with my other conditions I posted was that the phone felt really hot.
Immolate said:
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
Click to expand...
Click to collapse
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
justinsaunders57 said:
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
Click to expand...
Click to collapse
1. Everyone knows that it's dual-core.
2. It runs Android 2.3.4. (Hence no root yet)
3. To the OP, no reboots. Had it since the 13th.
Sent from my DROID3 using XDA Premium App
I haven't seen another reboot since the 28th but I did have the odd experience last night of not being able to get a new wallpaper to take. In fact, I noticed that it had one of the stock wallpapers on it, the diagonal black and grey bars, but couldn't change it. Then this morning I thought about it and rebooted the phone. The last wallpaper I'd tried to change it to came up on reboot. Interesting but not alarming... unless it starts doing that frequently.
FYI I haven't noticed it running hot at any point.
Thanks for all the input everyone.
Probably seen it do it half a dozen times. IIRC it's not a full reboot, just the Android stack (i.e., same Linux kernel instance).
Have a logcat of one and don't seen anything that suggests where the problem is..just a whole bunch of "com.xxxxxx.xxxx has died" followed by normal restart log messages.
Odd that you all are experiencing this. I have not had a single reboot.
Sent from my DROID3 using XDA Premium App
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
I went into wifi settings and chose to forget all the connections. No more random rebooted.
rustynutzz said:
I went into wifi settings and chose to forget all the connections. No more random rebooted.
Click to expand...
Click to collapse
I wouldn't count on that being the issue.
I've had the problem out in the field (not connected to WiFi) and have had random reboots as well.
Heres a tip for troubleshooting this issue which i 90% guarantee - factory reset your phones put zero apps on them and tweaks, use it for a week and see if u get a reboot.
Then each week after add a single tweak or app(install/uninstall/freeze), may take a yr for some of us since we can't seem to stop downloading random badly coded apps lol...
-smc
For me at least SMC, I've had random reboots from stock during the first week. I'm putting it down to bad software for now.
I usually get 1 a week, sometimes less.
tliebeck said:
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
Click to expand...
Click to collapse
The same thing was happening to me, the whole rebooting and I went to Verizon for a replacement and got a refurbished DROID 3 Not a New :\
I really hope they fix this because its really bugging me. >:\
-eXsoR
Sent from my DROID3 using XDA App
I get a random reboot usually once a week or sometimes twice a week. It depends on how often I use my camera too.
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Latonya1 said:
i had same problem and what i did is i opened battery from the device and inserted its again and did a factory reset on my device
Click to expand...
Click to collapse
Removing the battery on the kindle isn't an easy feat. Are we talking about the same device, or did you attempt this on a phone? Because if this worked with the kindle, I am more than happy to put the time into trying but I want to make sure.
Thanks for the reply.
dlenoxx said:
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Click to expand...
Click to collapse
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
itouchables said:
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
I should have read over what kinology was before flashing it.. I'm sure it's a great rom, but I'm wanting something more android-e. Went great though, as far as the install- and thanks for the tip. Worse case I'll have that file to fall back on.
stunts513 said:
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Click to expand...
Click to collapse
As I've been doing a bit more testing trying to figure out what is going on, it does seem to happen more often when under 100~75mg of memory available. Idling now at 550 memory available now, thanks to a few tweaks here and there which has almost erased the problem when doing things like browsing the internet, youtube, netflix, etc. It's just happening now during games. Not as much- but still, in the middle of a game of Kingdom Rush it's a little frustrating to all of sudden have no control. And currently I've still got almost 7 gigs of space available as far as harddrive goes so that doesn't seem to effect it by much (at least for me).
Setting the I/O to noop, overclocking to 1500 (leaving the minimum to 350), and setting the zram compression to 28% were the tweaks. Also having Task Killer by rechild set to kill tasks when screen off has been a great fix when I do lose the touch pad controls as it'll free up some memory when I turn it off, leave it off for a minute, then turn it back on without really interrupting progress in several apps.
Still searching for a true, 100% fix so tips are still welcome and I'll keep everyone posted if I run across anything myself.