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?
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.
[Q]
Out of the blue my Bionic just started rebooting. 8-10 time per day, who knows how may time at night. I am using the stock ROM. I am looking for a stable ROM that I can use to fix the problem. I also have the problem of disapearing apps that I move to the ext card.
Feedback on possible cures will be welcomed.
I just experienced my first unexpected reboot. It was after plugging in my USB to my computer.
This seems like the sort of thing that would have a 50% chance of being related to your hardware, and a 50% chance of an unstable app screwing something up. The stock software is at least stable enough that it's not very likely to be the cause of your issues, and flashing another ROM (which will have the same kernel) won't help if it is a hardware issue.
A factory reset followed by staggered reinstallation of apps (one or two at a time, to see if one in particular might be causing issues) would be my first step for a problem as extreme as random reboots. The next step is through warranty channels. I might even do that first- I don't think I could put up with a phone that rebooted on me.
And the cure for disappearing apps is to not use media area for storage. The phone dedicates 4gb for apps, that should be more than enough until they patch a fix.
i may have to add that my phone was completely stable until i purchased and installed the extended battery then i started to experience reboots and a few locks here and there.
i did a few factory reset on the stock but the phone was still acting up with the new battery.
i then decided to root and run roms and to be frank no locks and or reboots running the same battery that seemed to be causing the problems based on that being the only change to my phone before the reboot and locks.
i am not saying that there is something there with the stock as there would be more reports on this but rooting and going back to stock is a single click now making it a fast process to trouble shoot the software.
i am experiencing a bad or short life with the extended so in my case it could have been the battery screwing up the reads on the software (guess) but the first 3 charge from full to dead just about 3 days after that same extended only last one day.
in general it seemed that my issue could have been a bad battery and wiping data and playing with roms may had help but in the end i will be calling verizon for a battery replacement as i doubt that in two weeks the battery charge for an extended could only last 1 day of medium use.
sorry long response and by no means i'm i encouraging to root and rom just speaking out of my experience.
Hi - first post here. After 4 Thunderbolts - Verizon sent me a Bionic. Much better however, after rooting with 43v3r and de-bloating with The Black Hat App - I'm having random reboots. Initially, the reboots were several times per day increasing in frequency to several times an hour. Y u c k - My Thunderbolt could do that too.
So in troubleshooting:
1 - I've reverted to stock build - no add'l apps: No reboots in 48 hours. So - I doubt it's hardware.
2- After reverting - I then rooted w/43v3R, then debloated - just using stock apps - no reboots in 24 hours. So, I really doubt it's debloating or rooting
3 - After adding a few apps - Stitcher, Enhanced email, SVOX w/voice, Beautiful Widgets (w/clock selected) - I get a reboot.
4 - Remove everything but stitcher. No reboots - 24 hours.
5 - Add Enhanced Email yesterday
Today, I had a reboot.
6 - So culprit 'looks' like Enhanced Email OR perhaps a switching problem between 3/4g (The Thunderbolt - Stitcher used to drop connection in this particular location so, there IS an issue w/3G-4G.
Questions:
1 - If it's not a 3g/4g issue; could it be related to where Enhanced email or Stitcher chooses to install itself?
2 - Is there a log somewhere where I could find 'boot' times and any issues relating to reboots? Like a 'minidump' in Windows...
thanks
I, too, have started having unexpected reboots. I can't pinpoint it exactly, but I have also recently isntalled Enhanced Email (trial version).
Reboot Logger
Hey Google is our friend - don't know why I didn't look before but I found this in Android Market.
"Reboot Logger" by Watanabe,Masayuki.
Just installed it - will report back after Thanksgiving (in the U.S. - Thursday)...
(I would post a link but I'm a noob here - and, now I know why I hate myself.)
Looks like promising -
Have yall installed any themes or different battery icons, or anything like that to yours? Mine is 43v3R rooted with the liberty romv2. I was changing a cpl of the icons and experienced a reboot just out of the blue. I got rid of the icons I changed and stayed with the icons that came with the liberty rom and have no issues at all. I do not have enhanced mail on mine.
most bionics will turn off and wont turn back on till you do a battery pull. Its a known issue, all you have to do is google it and it turns up. From what ive read putting the battery on performance mode and putting on detect in pocket will help. Personally it doesnt help, i had the issue with the stock battery so purchased a extended thinking it was the battery, but after doing research i found out it isnt. They say the new OTA should fix it
icons - reboot logger
Thanks - haven't changed any icons BUT I am using HTC Thunderbolt wallpaper. I had a Thunderbolt that had a reboot problem until the OTA before Gingerbread - Verizon offered me the Bionic when I called about my Thunderbolt issues (I had three replacements - all with the same issues).
I will try different wallpaper -
Reboot logger works well but doesn't offer a clue as to what is causing the reboots. Mine has rebooted 2-3 times per day since I installed Reboot Logger(RL).
3 times a day is tolerable but, I would like to get to the bottom of what's causing it.
What IS helpful with RL is that it does show that the reboots are not occuring in any obvious time sequence.
They may be related to push emails coming in from my Exchange server. Not sure - I'll post more as I learn more. Hopefully the upcoming OTA will fix - though my experience with HTC's OTAs does not give me a lot of hope.
Update - Last night, I uninstalled Stitcher - Stitcher frequently throws errors requiring a FORCE CLOSE. I also have kept Blueooth off.
No reboots in 24 hours -
Will reinstall Stitcher in the morning (I need it at the gym)...
Update tomorrow/Monday
Turned Bluetooth ON - no reboots in 36 hours so, It looks like Stitcher may be the culprit - I wonder if Stitcher has issue with the internal/external SD storage scheme.
As I noted previously, Stitcher reports 'force closes' frequently - especially when it's not even active (when I have not loaded it or used it).
(No sooner than I posted this - my phone rebooted. And again, and again will switch off BT - I'm in my office so, there's could be an issue with 3g/4g switching or other interference...)
Have you tried setting the phone to run strictly 3g? I have had no issues at all with mine jumping back and forth between 3g/4g.. I leave mine on 3g to keep it from trying to search for a 4g signal. I never turn bluetooth on, nor do I ever really use the compass. hmmmm... Can you tell me everything you have done to the phone. Apps you have installed, what ROM you using, if you have .886/.893 etc? I'm willing to see how close we are as for as how our phone's are setup and help as much as I can. I have not had a single issue with mine other then that one reboot after changing the battery icon.
After nearly two weeks of monitoring restarts - it appears that the problem is more related to where I am. At my home, restarts are rare and related to Stitcher.
At work in Beverly Hills, CA; restarts occur frequently. I assume it has something to do with 3g/4G switchover/crossover or interference.
I had lots of problems with the Thunderbolt dropping data connections in 90210. I could not use the hotspot. On the Bionic, the hotspot functions really well. I've used it up north near Fresno in 3G only land, here in BH and at home where I have decent 4G coverage.
When I remove Stitcher, the reboot problem disappears. Sometimes when I 'wake' the phone, there is a dialog apologizing for Stitcher having 'force closed' even if I haven't used it for days. Market reviews indicate anecdotally that Stitcher has a problem with force closes. This behavior must also be at the root of some of the reboots.
I've also set all programs not to update automatically - this may have reduced the reboots as well. On average, I'm getting 2-3 reboots per day. More than I would like but, tolerable.
I'm running SS 3.05 and have been able to flash several roms (all GB because I need a camera) that others rave about. I have not gotten good performance out of any of them. The worst ones seem to cause almost non-stop force closes on apps while the "best" ones function but my phone runs very hot even when not being used. Just tried Steel Droid 5 over the weekend and I at least got it up and running but the phone was noticeably hot even when just sitting on the counter with the screen off.
I've uninstalled and reinstalled Safestrap a couple of times, deleted and recreated rom slots repeatedly and have just had no success. Is it possible that there is something weird about my phone? Is it just wonky? It does run normally on the stock rom, or at least as normally as any D3 can run but I'd love to run a meaner, leaner rom on my phone.
If anyone has any ideas I'd love to hear them.
JoeHockey said:
I'm running SS 3.05 and have been able to flash several roms (all GB because I need a camera) that others rave about. I have not gotten good performance out of any of them. The worst ones seem to cause almost non-stop force closes on apps while the "best" ones function but my phone runs very hot even when not being used. Just tried Steel Droid 5 over the weekend and I at least got it up and running but the phone was noticeably hot even when just sitting on the counter with the screen off.
I've uninstalled and reinstalled Safestrap a couple of times, deleted and recreated rom slots repeatedly and have just had no success. Is it possible that there is something weird about my phone? Is it just wonky? It does run normally on the stock rom, or at least as normally as any D3 can run but I'd love to run a meaner, leaner rom on my phone.
If anyone has any ideas I'd love to hear them.
Click to expand...
Click to collapse
Weird. Minimoto ran great for me. I wonder if it's an app you install?
Maybe you just have a bad app or two. You can try loading the phone stock and install only an app or two at a time and see if the phone runs better. Maybe after loading one particular set of apps you'll notice a problem.
I run minimoto as well. I don't get the miracle battery savings that others report - mine is essentially the same as running stock for me - but it is rock-solid stable, unlike stock, which tends to go wonky on me after about 5 days or so.
1
I have noticed something like that, I´m on XT862 and I have better baterry performance on Steeldroid 5.0 and If I give a try with Minimoto I have noticed higher battery drain and hot back of my device. So I always went back to SD 5.0. Strange that people have different experiences =).
doogald said:
Maybe you just have a bad app or two. You can try loading the phone stock and install only an app or two at a time and see if the phone runs better. Maybe after loading one particular set of apps you'll notice a problem.
I run minimoto as well. I don't get the miracle battery savings that others report - mine is essentially the same as running stock for me - but it is rock-solid stable, unlike stock, which tends to go wonky on me after about 5 days or so.
Click to expand...
Click to collapse
Would a app that tracks battery usage by app possibly give me that info as well? Slowly adding apps one at a time will be a major chore...
JoeHockey said:
Would a app that tracks battery usage by app possibly give me that info as well? Slowly adding apps one at a time will be a major chore...
Click to expand...
Click to collapse
Settings-applications-battery use
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Have experienced absolutely none of the issues you refer to on my SM-T805.
Runs just fine for me.
Downgrading to KITKAT doesn't void your warranty.
ashyx said:
Have experienced absolutely none of the issues you refer to on my SM-T805.
Runs just fine for me.
Downgrading to KITKAT doesn't void your warranty.
Click to expand...
Click to collapse
I agree with ashyx , my tab s runs fine n dandy , sounds like you have a faulty unit schmintan
I don't know if your tablet has Knox, you can see status if you go under status in about device, usually, and see if it is "official" or not.
Far as what you did, before you went and loaded a ROM, I would have done a factory reset. Quite often, settings/apps brought over from a previous version cause issue. I don't care if the upgrade tells you too or not, read through the forums and you'll see it littered with people stating how they noticed a massive improvement after their upgrade once they factory reset. Yes, it does suck, but these days Android makes it very easy to do.
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
Hi, have you solved The issue downvrading? I have The same problems you described.
same issues
White lines then crashes, battery life under 4 hours,
Sounds like a case of broken hardware or one seriously misbehaving application. And in general, if nothing works, I'd recommend to do a full factory reset of the tablet after the lollipop upgrade (erasing all of your data and settings of course). The only issue that concerns me about lollipop is the increase in battery drain at idle. You need to hunt down for the apps that keep your tablet awake. But spend a full battery charge in minutes? No way. Impossible. Get the tablet replaced.
I've been having the same issues. When I did a clean install, the tablet worked fine. However, as I install various apps, the issue begins again. I haven't been able to identify a particular app.
Going to try Marshmallow and see if it's more stable
If you both post your apps list that might be interesting see if you both share an app?
bigaloz said:
I've been having the same issues. When I did a clean install, the tablet worked fine. However, as I install various apps, the issue begins again. I haven't been able to identify a particular app.
Going to try Marshmallow and see if it's more stable
Click to expand...
Click to collapse
nope. no stable mm roms yet.
Well, I've upgraded to Marshmallow and whilst it took a few goes to get it up and running properly (problems with installing gapps) it's working fine (mostly) now.
I've only had it running for a day but it is much smoother and quicker than kitkat and lollipop. So far there hasn't been any random shutdowns. It's too early to say whether battery life is better.
The only problems I've had is the camera isn't working (haven't bothered to look for a fix yet) and auto rotation doesn't work all the time.
I'll keep you up to date on how things go but so far I'm very pleased with the upgrade. I might now upgrade my 10.5
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
Hola, which procedure did you follow to downgrade OS to kitkat? I m right now on official Lollipop without root.
I had a notion that even if we downgrade to kitkat screen flicker will remain.
Awaiting your reply- thanks in advance
schmintan said:
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
If your issues are caused by Lollipop wouldn't everyone one else with Lollipop experience the same issues? I have absolutely none of the problems you mentioned and I have had Lollipop installed since it was first made available for this tab. Seems to me you more then likely have a hardware problem. You said you were going to update in a day or two but you haven't so far. I'm curious if downgrading solved your issues.
Sent from my SM-T800 using XDA-Developers mobile app
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
i have found a fix for the white lines. but you need root
share the fix
zalso said:
i have found a fix for the white lines. but you need root
Click to expand...
Click to collapse
what is the fix? please share! i have root, i have the problem, and it is super irritating!
Fix
brio09 said:
what is the fix? please share! i have root, i have the problem, and it is super irritating!
Click to expand...
Click to collapse
here buddy http://forum.xda-developers.com/gal...-flicker-screen-freezes-t3374336#post66951302
I have the 8.4 and 10.5, both are stock running lollipop and neither device has had the issues you are having!
Sent from my SM-T800 using XDA-Developers mobile app
screen freeze + screen flickers bright flash bars
random reboot, screen freeze and crazy screen flickers with bright flash bars), which occurred when it had low battery
(may be not relevant but have also just given up on firefox for chrome!)
this seems to sum up my experience in the last week or so, I thought I was heading for some hardware failure but parallels what others are reporting....
SM-T705Y running 5.0.2 (LRX22G)
looks like update from 20th May which would be around when this started