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?
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
For as cool as the Sense UI is, I don't think it was quite ready for the Hero.
Plus there are bugs that have been talked about quite a bit in the official 2.1 update for the Hero.
Hero + Sense = Dialer lag. Even after rooting and running a (mostly) much cleaner flavor of version 2.1, any rom I installed still had lag in the dialer app.
I finally scrapped Sense altogether and went with a vanilla aosp rom (darchdroid) and the whole device, including the dialer, runs smooth as butter. No lag at all.
Thank you!! I did try and run Drachroid 2.8 but it just kept looping on me so I do have another rom installed at the moment and will wait for a fix for 2.8. Any other Vanilla roms you would recommend?
brookegray said:
Thank you!! I did try and run Drachroid 2.8 but it just kept looping on me so I do have another rom installed at the moment and will wait for a fix for 2.8. Any other Vanilla roms you would recommend?
Click to expand...
Click to collapse
It's possible that the bootloops happened to you because of the overclocked (OC) kernel in DarchDroid. Some phones cannot boot at overclocked speeds and will just bootloop while trying to load up.
The latest DD 2.8 already comes with an undervolted (UV) kernel, which some phones can boot better than the regular OC kernel, so it may just be that your phone doesn't like OC at all. Lots of phones here are like that.
Try flashing and booting DD2.8 on a FULL battery. You'll have a much better chance booting an OC kernel on a full battery, and while it's plugged into the charger still.
Another good Vanilla ROM I really liked was Ic3Rom, but it is no longer kept up so it's not as current as DD or the 2.2 Cyanogen Froyo ROM.
Good luck!
Try turning off the dialer sound in settings. That fixed the lag for me.
If you try the latest froyo nightly, it should boot, it's capped at 691- which is still overclocked but seems like everyone can boot.
Sent from my HERO200 using XDA App
Help: Sprint tech Actually Sent Me Here to Root my Phone!
mkhopper said:
I finally scrapped Sense altogether and went with a vanilla aosp rom (darchdroid) and the whole device, including the dialer, runs smooth as butter. No lag at all.
Click to expand...
Click to collapse
I've been complaining to Sprint about the lag since before 2.1. Last night a Sprint tech said to come here for an "unofficial" way to get my phone running smooth, including rooting it to make it do things that aren't "supported." So after searching around here I see posts about Nandroid, rooting, backing up, restoring, and flashing roms. I've rooting iPod Touches but never a phone. I want to try this while I have hours to kill at work. Forgive the shortcutting but can you:
1. Point me to an updated step by step guide.
2. Point me to an updated recovery image.
3. Point me to an updated ROM that you PRAISE.
4. Pray for me.
Thanks,
Ken
kenwhittaker said:
Forgive the shortcutting...
Click to expand...
Click to collapse
Welcome to XDA! Just as an FYI, many of us here don't take too kindly to this. We have had to put in our time searching and reading -- it's only fair that you should too.
That being said, this thread will tell you how to root and will include a recovery image: http://forum.xda-developers.com/showthread.php?t=694572
That's all you get from me Now it's up to you to browse around and find a ROM that you like best. No one here can tell you which one the "best" one is....it's all about personal preferences and tastes. Browse the Development forum and try several ROMs. Also check the Themes and Apps forum for cool extras. You'll soon find what you like.
Good luck, and make sure you do PLENTY of reading here before doing anything to your phone.
chromiumleaf said:
Welcome to XDA!
Click to expand...
Click to collapse
Thank you. I'm well on my way. Rooting as I type. I'll check out the Dev threads.
I am running a non OC version of aloyuisus and i am loving it nothing ever lags i don't run task killers. I get great battery life, last me all day with moderate use, if i tether i always make sure its plugged in otherwise its never plugged in until late night. I listen to Audible and mp3s and probably make about 1 - 1.5 hrs worth of calls a day.
no random reboots either,
Nannuq said:
I am running a non OC version of aloyuisus
Click to expand...
Click to collapse
Thanks buddy. I'll look for a download link for that one. I just dropped to RUU 2.27.651.5 so I can root.
brookegray said:
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
Click to expand...
Click to collapse
I had this same problem. Even after rooting and installing fresh 2.3.3 it wasn't much better. I was almost to the point of taking the phone back to sprint when i found Cyanogenmod 6. I started with test 4 which was still pretty buggy but the current nightly that is out is awesome. FroYo is the best thing that has ever happened to my phone. No Lag, EVER.
RocStar629 said:
i found Cyanogenmod 6.
Click to expand...
Click to collapse
The 5MP Cam, preview, and video camera? No video playback problems? I need to find that one!
brookegray said:
Ok I am having some serious dialer lag. I am talking up to a minute to actually dialer a number that I have put in or chosen a contact before it actually dials. I am running the 2.1 update and don't know if this was an issue before this update as I just got the phone wihin the last month and downloaded the update right away.
I do use Advanced Task Killer and have killed everything before attempting to make a call but it is still just a laggy. I have also gone in and killed processes that are running like Sprint TV. Still have major lag issues.
Is there a way to fix this? I am getting so frustrated and am about to return the phone to Sprint!
Click to expand...
Click to collapse
this is a bug that was never fixed by htc when 2.1 was released and finalized. do a google search, lots of people are having this issue. no fixes for it either as the hero was left behind by htc.
Actually darch fixed the lock screen lag in his latest kernels. It's amazing
Sent from my HERO200 using XDA App
danaff37 said:
Actually darch fixed the lock screen lag in his latest kernels. It's amazing
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
hes talking about the dialer lag.
chromiumleaf said:
Good luck, and make sure you do PLENTY of reading here before doing anything to your phone.
Click to expand...
Click to collapse
That one statement can't be said enough.
Read, attempt to comprehend, read some more and then do the work.
There are some apps and / or scripts nowadays that will give you "1-click root", but I frown on these to be honest. There's too much "magic stuff" going on behind the scenes that you're not aware of and if an issue pops up, it's harder to backtrack to figure out what went wrong.
1-click root apps are fine, later on down the road when you're comfortable with the process and just want to get it done, but manually running through the steps to root, backup and finally flash a new rom is the best way to go.
Hello Community!!
I am seeing a problem with my Revo, and I'm putting it out here because you guys are good at finding answers.
I am running Gingervolt 1.3 with the blitzkreig kernel installed. I have previously tried Hicks' little ICS responsiveness script.
Here is my problem. Most days after little to moderate use, Phone/text, I have to reboot my phone by either soft reboot (power button) or a hard reboot (battery pull) because nothing at all is responding. By nothing I mean, touch the screen..nothing, open a program...nothing...etc.
It is a slow degrade sometimes where (and my wife has mentioned it using my phone) that the touch screen is really really laggy and non responsive, especially when using a keyboard or even trying to play angry birds.
I have done a full wipe including data, cache, dalvik. I have formatted my internal and removable SD card, I have not used previous backups, instead resorted to downloading programs and installing from scratch.
This is a very frustrating issue. If it was a computer I'd say either the processor was overworking, or the ram was used up. But since we don't use program killers in GB I'm kind of at a loss. And I'm tired of having to wipe my phone every few days just so I have meh performance (and no, I'm not hating on the phone, or the rom or any of the developers, nor do I have any interest in changing phones,etc)
I'm just looking for suggestions/solutions etc. I'm sure I missed something in my troubleshooting steps.
Thanks in advance for those who read through this and try to give a hand. I appreciate it.
Wow. Since you've already gone to extreme measures, I'm at a loss. My suggestion would be to freeze the apps you do install to look for a culprit there. Or, don't install any and see how the phone performs.
I restored a nandroid prior to Google's 10¢ apps promo and my phone is back in fine form. It was lagging badly before that. I was rebooting daily. Now I go for days and the phone's solid.
Sent from my VS910 4G using Tapatalk
I was experiencing similar issues about a week after updating to blitzkrieg 1.0. I restored from backup and it's been stable since. I just installed 2.0 today, so I'm curious to see if it'll have the same effect.
Sent from my VS910 4G using xda premium
I can't say yet whether or not 2.0 has added to or taken away from the response type issues. I did have to do a couple of battery pulls yesterday just to get firefox to do anything. I'm going to uninstall that one. I may, just for S&G's do one more factory wipe and put all the tweaks and mods in place before downloading anything but the most essential programs. I did this phone, but the unresponsiveness sometimes can be a real pain.
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
revo_65 said:
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Currently I have it at 1.7, before when it was really bad, the oc wasn't sticking and I was at 1024, so not overclocked much. I am sure its an app that is causing the problem, but I'm not sure what.
I've never had this type of issue using Blietzkreig or any of the other tweaks so I'd guess you're right in thinking it's an app. Since you've pretty much tried everything else I would say maybe try going back to complete stock then rooting again? That just seems like what I would try if I had tried everything else and nothing worked.
And yeah you definitely don't want to overclock too much because it could definitely damage the hardware of your phone since it's not meant to run at that level. But you said you had it at 1.0ghz so it doesn't seem like that is the problem unless the damage was cause when running at 1.7ghz. I had mine at 1.9 and didn't see any issues except my phone randomly started to vibrate for a while then just restart. It did that twice when i first flashed everything but it seems fine now. I brought it down to 1.0ghz just cuz i'm not really using it now and I don't want it causing any problems with the hardware.
Thanks for the Feedback everyone. I am not sure what the issue is/was/going to be. I think Firefox was a big part of it and I have since removed it. But I am still getting random freezes, almost like the deep sleep while the screen is on. Oh well, maybe I do need to go back to complete stock.
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
I'd recommend flashing a rom like pure nexus, super stable that should fix your problem, otherwise you've done all you can and is the easiest fix
Sent from my Nexus 6 using Tapatalk
lchiu7 said:
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
Click to expand...
Click to collapse
Hello,
It seems like some apps are really slowing down your phone. I use my N6 at home for web browsing mostly as I have a Pixel XL now. Just like you I love the screen size.
The camera has always been slow fore, because of the time it takes to focus...
Did you try using your phone a few days without Snapchat installed? Maybe you also have other misbehaving apps installed.
Uninstall Snapchat and other apps and start from here. Reinstall one per one with a few days interval. See if the issue still occurs.
Installing a custom ROM + kernel will likely speed up things a little bit. I second @Dugaldrob with Pure Nexus and I'd suggest ElementalX kernel on top. Running this combo on N6, N6P and Pixel XL and they work flawlessly.
I don't believe installing a custom ROM alone will fix your issue though. Stock ROM shouldn't cause the phone to slow down to the point you need to reboot to use it.
Finding the culprit will...
Good luck...
5.1 said:
Hello,
It seems like some apps are really slowing down your phone. I use my N6 at home for web browsing mostly as I have a Pixel XL now. Just like you I love the screen size.
The camera has always been slow fore, because of the time it takes to focus...
Did you try using your phone a few days without Snapchat installed? Maybe you also have other misbehaving apps installed.
Uninstall Snapchat and other apps and start from here. Reinstall one per one with a few days interval. See if the issue still occurs.
Installing a custom ROM + kernel will likely speed up things a little bit. I second @Dugaldrob with Pure Nexus and I'd suggest ElementalX kernel on top. Running this combo on N6, N6P and Pixel XL and they work flawlessly.
I don't believe installing a custom ROM alone will fix your issue though. Stock ROM shouldn't cause the phone to slow down to the point you need to reboot to use it.
Finding the culprit will...
Good luck...
Click to expand...
Click to collapse
Thanks
First step is to remove Snapchat. I rarely use the app and only because my daughter sends stuff on it. I am going to tell her to send me stuff via another method
If that doesn't work then it's a new ROM. I have performed ROM installs before but have never flashed a new kernel on a phone before so that will be a new experience. Hopefully I won't brick the phone
lchiu7 said:
Thanks
First step is to remove Snapchat. I rarely use the app and only because my daughter sends stuff on it. I am going to tell her to send me stuff via another method
If that doesn't work then it's a new ROM. I have performed ROM installs before but have never flashed a new kernel on a phone before so that will be a new experience. Hopefully I won't brick the phone
Click to expand...
Click to collapse
Hello,
Don't worry, it's really easy. Also, if you are lost, there must be a ton of tutorials in general section. If you are lost yet, just ask and someone will point you in the right direction...
Good luck...
lchiu7 said:
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
Click to expand...
Click to collapse
I've been running Pure Nexus and wanted to let peeps know I put Nitrogen on and man it's so smooth, my wifi tether is back and I went to sleep last night with 50% battery still. When I installed it I opted for the nano gapps I think so like 175mb for minimal apps and maybe that's why it's running so efficient. Maybe I could have re-installed Pure Nexus with a clean install and it would have gotten better but it was a good time to try something else. Also when Nitrogen got an update I was notified just like stock and it downloaded. I didn't even know these could do that. Anyways give it a try and you might just switch back. I was looking into new phones but if it keeps working so smooth with battery longer than a day then I'm fine for now.
Snap chat is not that big of an issue. What I have found to cause the device to slow down is normally almost full device storage and a crappy cache release code in apps. Some apps don't release their cache properly. So it causes lag. This is why a reboot seems to fix it.
While a custom rom may fix this issue it is not the solution. The proper solution is to find what is causing it and fix/repair/ditch it.
Worst offenders for crappy code in my thoughts. Other will disagree with one on this list I am sure. So don't bother. I know people swear by it. It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
Mind you this is just a list on my usage. It may very per user and even device (considering different hardware)
zelendel said:
... It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
...
Click to expand...
Click to collapse
I can confirm this, because I've removed these apps (-whatsapp) and also decrypted the data partition...
My N6 is fast.
Maybe a lite stock ROM and an other kernel is a good start.
NLBeev said:
I can confirm this, because I've removed these apps (-whatsapp) and also decrypted the data partition...
My N6 is fast.
Maybe a lite stock ROM and an other kernel is a good start.
Click to expand...
Click to collapse
Currently I have FB, FB messenger, and Chrome but when I installed gapps I chose a super lite install so tons of bloat and google apps were not installed and my battery has gone way up and it's so smooth. I'm sure even when we don't use apps they're always doing something in the background. I bet you're right and a stock lite ROM would be good too with the minimal bs apps.
zelendel said:
Snap chat is not that big of an issue. What I have found to cause the device to slow down is normally almost full device storage and a crappy cache release code in apps. Some apps don't release their cache properly. So it causes lag. This is why a reboot seems to fix it.
While a custom rom may fix this issue it is not the solution. The proper solution is to find what is causing it and fix/repair/ditch it.
Worst offenders for crappy code in my thoughts. Other will disagree with one on this list I am sure. So don't bother. I know people swear by it. It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
Mind you this is just a list on my usage. It may very per user and even device (considering different hardware)
Click to expand...
Click to collapse
Thanks for the advice. Of the list of apps above I have only Chrome and Hangouts. I really can't see replacing either of them.
I also should have pointed out that the phone locks up randomly requiring a hard reset. I wonder if an errant app could cause that or I have some RAM problem. Certainly on a PC bad RAM can use in Windows a blue screen or something but perhaps Android isn't so forgiving?
lchiu7 said:
Thanks for the advice. Of the list of apps above I have only Chrome and Hangouts. I really can't see replacing either of them.
I also should have pointed out that the phone locks up randomly requiring a hard reset. I wonder if an errant app could cause that or I have some RAM problem. Certainly on a PC bad RAM can use in Windows a blue screen or something but perhaps Android isn't so forgiving?
Click to expand...
Click to collapse
I would flash TWRP, flash supersu in TWRP to root, make a complete backup in twrp, then remove whatever Google apps you're not using with a system app removal app. Getting some of that bloat off the device should help. If it's still laggy, then look into a custom ROM. I run Tesla on my Nexus 6 with none of the issues you're having. I don't decrypt it either
Running abdroid 7.1 here. I dont get any slowdowns, at leas until the battery doesnt drop below 50 and 25 percent.
Im running a custom kernel and my phone is rooted. Everything else is stock.
Can you flash a custom kernel and presumably TWRP without wiping the phone? If so then might try that before a custom ROM
lchiu7 said:
Can you flash a custom kernel and presumably TWRP without wiping the phone? If so then might try that before a custom ROM
Click to expand...
Click to collapse
Hello,
Since your bootloader is unlocked, flash TWRP and install the kernel, no problem.
Might give you a slight boost at first sight, but your device will likely slow down over time anyway...
Cheers...
I'm on 7.0 with the April SP. I have dozens of apps installed, including Hangouts. I use Firefox for browsing, I like it better than chrome (and you can install an ad blocker).
My camera slows down when the battery is under 40%, and the whole device slows dramatically, though not unusable, at or below 5%. But otherwise, no issues what so ever.
One solution that I have not seen suggested here is resetting the device and NOT taking the Google account backup of all your apps. I would suggest making a completely clean install of the factory rom you have and installing one or two apps at a time, most important to you first. And do this for a few days/weeks until you find the app that's misbehaving.
Although there are general bad players out there, this bad app could be unique to your device. Just because all devices of the same model have the same specs and components, doesn't mean that there isn't variability in parts quality.
I would do this before trying any new roms or kernels. Find the true problem first.
Good luck!
edit:
I had another idea: Go into your battery stats and network stats and storage stats and see if any app seems to be using too much of any, or all of the 3. This may get you the answer more quickly.