Related
Recently I noticed my Fascinate would skip constantly while playing music - like every 30 seconds maybe even more often. For me, the mp3 player is one of the most used things for me on my phone. I don't want to double fist a phone and an ipod or something if I don't need to!
After looking back I realized that although the problem was recent I had been having minor skipping for quite a while - but not often enough to really take notice. Anyway, when it finally started skipping all the time I couldn't stand it anymore.
I've done a lot of searching and testing with this issue and have resolved my problem.... sort of. Lot's of people seem to have this problem and others don't...
So, it seems a lot of times widgets can be the problem. So after uninstalling "battstat" the skipping went down to 1-2 times a song... Hooray? Still less then ideal - I shouldn't have any skipping! Then I got rid of "beautiful widgets" and that minimalized the skipping even more. I finally got rid of "widget locker" while I was at my widget uninstalling spree. So far NO MORE SKIPPING!!! Hooray! ... ...
BUT
This is less then ideal. Many people have perfectly working music playback AND have all their widgets. I on the other hand, it would seem, can only have widgets OR flawless playback - not both. Say it ain't so Joe! Is my phone just one of the flawed, I should return this because all hope is lost, phones? Or is there still a chance to get this phone working like a charm?
Seems like a software thing to me though which should suggest that my phone itself is ok... otherwise playback would be constantly bad... But I'm no IT person so I can only make educated guesses based on limited research really.
Anywho, I guess I'm just reaching out to the community to see if anyone has any idea on if I'm screwed and can no longer have my widgets. Or if there is something else that can be. Hotfixes? 2.2 fix?
I've very sad about my very plain looking phone right now. =( To a point that I have actually stopped stalking the forums and finally posted something...
EDIT: Not sure if it really matters but I should just note. My phone is rooted, de-bing'ed, de-bloated and of course has clockwork recovery. NOT de-odexed, NO voodoo or lagfixes, and NOT running any roms (just used Titanium Backup to freeze all the bloated stuff) - waiting for 2.2 before I start getting really deep into phone fiddling.
Thanks,
-Andrea
Yea same for me. I deleted Battstat because Winamp was skipping. Sad to remove such an awesome widget.
I too have had this problem but haven't been able to figure out what is causing it. I noticed that if I load a rom and wipe first it starts doing it, but if I start with my stock backup and load the rom without wiping, it doesn't do it. I actually returned one to the store for this issue. Do you happen to have anything on your sd card that you had on another phone? I have a theory that had something to do with it, but I have nothing to back that up with.
Sent from my SCH-I500 using XDA App
No, my SD is clean from any old phone's data. I was having playback problems on Pandora as well. =/ Also tried all sorts of different music players but they all skipped just the same.
Been playing around with different widgets... Beautiful widgets was causing problems but I put it back on for the 3rd time and my phone is happy... for now at least (knock on wood ). The two main culprits are Battstatt (MAJOR ISSUES) and very sadly TypoClock was causing problems too (not nearly as bad as battstatt but problems none the less). With these two widgets removed I've had almost no skipping. Think I heard 1 during my 30 minute drive home (yay traffic!) - which could have just been the phone lagging b/c of an update or sync or whatever.
But this still leaves me with the same issue. Basically there is just a band-aid over the problem. But why are only certain phones doing this... and more importantly can anything be done to have a happy phone - widgets, music, and all?
At the very least, I hope this thread has helped or can help others who have been having problems with their music playback.
I've noticed this when frequently flashing ROMS. I have concluded that following these steps fixes the problem. Disable voodoo(if applicable) restore original mbr. Odin all the was back to stock after backing up everything wipe data/cache and load the ROM of your choice on a clean slate and then restore all and problem should be fixed. Worked for me. Music playing skip free.
Sent from my SCH-I500 using XDA App
It seems to do this when there is an app poling for data.
Sent from my SCH-I500 using XDA App
Talek said:
No, my SD is clean from any old phone's data. I was having playback problems on Pandora as well. =/ Also tried all sorts of different music players but they all skipped just the same.
Been playing around with different widgets... Beautiful widgets was causing problems but I put it back on for the 3rd time and my phone is happy... for now at least (knock on wood ). The two main culprits are Battstatt (MAJOR ISSUES) and very sadly TypoClock was causing problems too (not nearly as bad as battstatt but problems none the less). With these two widgets removed I've had almost no skipping. Think I heard 1 during my 30 minute drive home (yay traffic!) - which could have just been the phone lagging b/c of an update or sync or whatever.
But this still leaves me with the same issue. Basically there is just a band-aid over the problem. But why are only certain phones doing this... and more importantly can anything be done to have a happy phone - widgets, music, and all?
At the very least, I hope this thread has helped or can help others who have been having problems with their music playback.
Click to expand...
Click to collapse
Same thing here. Removed TypoClock and it went away. It still concerns me though.
That's weird. I have both Typoclock and Battstatt on my Eris and music plays awesome. Lag can't be a problem with this issue. Just my 2 cents.
Sent from Eris with Froyo
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
Problem 1:
I've just rooted my nexus-s and I'm not sure whether it's due to rooting or a software conflict with apps installed on the device that's not compatible with android 2.3, but I'm experiencing quite a frequent phone reboot while I am in the middle of an active call.
Is there a way to capture the log of the phone's function and see what's causing the reboot?
Are anyone experiencing this problem as well?
Problem 2:
I probably have only used 240 Mb of the USB storage, and it shows that I have 13Gb free. However, when I put the check boxes beside the applications that can be moved to the USB storage (i.e. native apps2sd), I seem to have surpassed the limit allowed for moving the app for USB storage. I've got 21 apps that can be moved, but it won't allow me to move the 21st app. Error message says "[! Move Application] Failed to move application. There is not enough storage left." I've tried checking and unchecking boxes of different applications, and it has nothing to do with the 20 apps limit, but rather it's the amount of memory being moved to the USB storage
********************* updated 01-12-2011 **********************
Please report to Issue 13674 on google's bug reporting page.
hXXp://code.google.com/p/android/issues/detail?id=13674
Sorry, I'm a newbie, so I can't post outside link. Please change the XX to tt in the link above.
************************************************************
Well I have 23 apps on my USB storage, and I have the Voodoo Root kernel as well. It shows 2.1gb used, 11gb free.
I did notice a 'soft reboot' earlier today but it wasn't during a call, don't know what caused it but yeah. Honestly if I were you and the problem persists just reformat and start over.
Im having the same phone reboot problem as you during phone calls. I thought it was due to an app called Screebl being incompatible, but i just made a test call and it rebooted after about 18 minutes. Im going through my apps to see what else effects the phone state during phone call.
Ive heard of some people having problems with google maps causing problems during phone calls, or sprint nav (but we dont have sprint nav) So im going to try shutting down maps, and uninstalling my task killer, which i also heard can cause problems.
Have you been able to figure anything out? I really dont want to have to reset my phone and lose all my save data information from my games. My phone is not rooted, and i dont plan on rooting yet, so i cant use titanium backup for my data.
Phone only Reboots during active phone call, i can play games or surf the web on it all day long with no reboots.
So software issue in android 2.3, or some kind of app incompatibility im thinking
you can capture the log with adb logcat command, or download a logcat app from the Market http://www.appbrain.com/search?q=logcat
Why are you bothering with apps2sd? The Nexus S shares the Galaxy S line's hugh, I mean HUGE, 1GB of "disk" space for apps. I've got almost 100 apps on my phone and not a hint of low space. See the screen capture I've attached: 284mb used for apps, 724mb still free!
oh crap! please let it not be the same problem as in the SGS i9000m
that's one of the sign before the internal SD goes belly up
AllGamer said:
oh crap! please let it not be the same problem as in the SGS i9000m
that's one of the sign before the internal SD goes belly up
Click to expand...
Click to collapse
Didn't they switch the type of flash memory used from earlier Galaxy S phones? I saw some discussion about it not being movinand any longer, or at least some sort of physical difference between what the NS has vs the SGS line.
distortedloop said:
Why are you bothering with apps2sd? The Nexus S shares the Galaxy S line's hugh, I mean HUGE, 1GB of "disk" space for apps. I've got almost 100 apps on my phone and not a hint of low space. See the screen capture I've attached: 284mb used for apps, 724mb still free!
Click to expand...
Click to collapse
Haha this may be the case, but I've inherited the habit of obsessively moving apps to sd/usb from using my Nexus One. Combined, I am using about 450MB of space for my apps at the moment. But this is a huge improvement from the Nexus One.
DumbUglyDragon said:
Haha this may be the case, but I've inherited the habit of obsessively moving apps to sd/usb from using my Nexus One. Combined, I am using about 450MB of space for my apps at the moment. But this is a huge improvement from the Nexus One.
Click to expand...
Click to collapse
Oh yes, I was the same on my N1 and even EVO 4G, but once I got a Galaxy S, never even considered it.
I'll wager the nand used for the "rom" space is faster than the nand for the "sdcard", another thing to consider. You're not even half-way used up with that 450...
americancrew said:
Problem 1:
I've just rooted my nexus-s and I'm not sure whether it's due to rooting or a software conflict with apps installed on the device that's not compatible with android 2.3, but I'm experiencing quite a frequent phone reboot while I am in the middle of an active call.
Is there a way to capture the log of the phone's function and see what's causing the reboot?
Are anyone experiencing this problem as well?
Click to expand...
Click to collapse
I haven't rooted my Nexus S,but i've experience the same soft reboot during call.
I have the "End call using power button" option enabled. Im not sure if i was leaning on the button when it happened, but stock doesn't have a reboot option, so its unlikely. I suspect its a OS bug, rather than a rooting issue.
Let me know if you make any progress, i've since made calls with no problems.
Psosmith82 said:
Im having the same phone reboot problem as you during phone calls. I thought it was due to an app called Screebl being incompatible, but i just made a test call and it rebooted after about 18 minutes. Im going through my apps to see what else effects the phone state during phone call.
Ive heard of some people having problems with google maps causing problems during phone calls, or sprint nav (but we dont have sprint nav) So im going to try shutting down maps, and uninstalling my task killer, which i also heard can cause problems.
Have you been able to figure anything out? I really dont want to have to reset my phone and lose all my save data information from my games. My phone is not rooted, and i dont plan on rooting yet, so i cant use titanium backup for my data.
Phone only Reboots during active phone call, i can play games or surf the web on it all day long with no reboots.
So software issue in android 2.3, or some kind of app incompatibility im thinking
Click to expand...
Click to collapse
You know, I thought there were software incompatibilities too at the first place. I did not use "End call using power button". But after running the same stock rom with rooting and apps for a week, I didn't see the soft reset during the phone call. I have just installed a new rom on my nexus s, the R2 version of MoDaCo Custom ROM for the Samsung Nexus S. Running great so far. No soft resets.
** Edit **
Actually, after posting this post yesterday, I did experience another soft reset whilst talking on my phone. I have the same apps that I have been running in the background, mainly: google pinyin, paypal, k-9 mail, ebay, rhapsody, google voice, bluetooth share, and swype. I am not experience the soft reset in all calls, after I have installed the R2 version of MoDaCo Custom Rom. I will post any problems again if I do see this happening again.
I did a factory reboot/restore and that seemed to take care of the soft reset during call problem.
Have made several calls without issue
Its doing it again, this phone is going back. The screen coating is already wearing off as well. Hopefully number 2 will be better.
I have yet to get one android phone that hasnt had to be exchanged once. Android phones really need to have better QC before leaving the factory.
Droid 1: 3 times (keyboard, GPS problems)
Evo: 4 times (terrible screens)
epic: 1 time (Keyboard)
Nexus: 1 time (so far) Screen Coating, Constant Reboots
Phone reboots itself during an active call.
I have been experiencing this problem and it seems to escalate in frequency. I got this Nexus S on day one when it came out. However, I have not experienced soft reboot issue until last week, after the OTA update. Since then, it keeps doing it more and more and now it's like almost every active call I make. First, I thought it's software conflict. Now, having read this whole thread, I think it's an OS issue.
I also sometimes encounter with completely losing signal. The phone can not register to any network, and I have to reboot.
One more issue is the voice search apk sometimes activates itself when I shake or move the phone.
My phone is stock, and I do not have any issue with USB storage.
I like the phone for its speed, and the contour screen. It handles most tasks very quickly, even it's still a stock phone, unrooted.
I still have it until Jan 14 to decide whether I will keep it or not. Hopefully, there are some ways to fix these issues.
Mine is restarting during calls and also when not in use. It restarted 3 times during calls within 10 days, and I witnessed it restarting by itself at least once when the phone was locked and not in use.
I have an unrooted Nexus S, which I started using yesterday. The OTA came almost immediately after setting up, so I installed that. It appeared to be working flawlessly until this evening when I made the first call on it. It rebooted a few minutes into the call. After redialing it did it again, the third call I ended without problem, but was shorter than the previous two. A few mins later I made some test calls and it rebooted during both of them.
I did a factory reset and wipe of USB storage - I didn't bother adding my Google account and just made a test call which lasted 13 mins before I hung up.
I'll have to make some more calls tomorrow and if they work, I'll try adding my Google account and restoring stuff.
I had this same thing happen to me quite a few times reboot during a call or locking up after a call. I work to a company and we purchased three phones. So I switched with another one and guess what? Same problem definitely looking like a software problem.
This just happened to me for the 1st time a little bit ago. About 35 mins into the call/conversation, phone rebooted itself. Non-rooted here, I hope it's a software issue, that can be corrected within the next OTA update.
Are the spontaneously rebooting phones possibly overheating? Do they feel warmer to the touch than normal when it happens?
distortedloop said:
Are the spontaneously rebooting phones possibly overheating? Do they feel warmer to the touch than normal when it happens?
Click to expand...
Click to collapse
While I cannot speak for anyone else having this issue, in my case - no. The phone didn't get warmer, or seem to overheat. Odd issue to say the least.
Stock ROM (2.3.1) here as well. Just had it reboot 10 minutes into a call, then one minute into the following call to apologise for the first dropped call!
Ever since the Gingerbread update (and subsequent 2 patches) I’ve noticed that my DX will occasionally shut down(?) while listening to audio, it doesn’t matter if it’s streaming or a local file, podcast or music, at some random moment everything stops on my phone and the only way to get it restarted is by pulling/reinserting the battery.
So far it has happened while using Google Listen, Pocket Casts, Pandora, and Winamp
Other audio players where it hasn’t happened it is Google Music (both stock and beta), TuneinPro, SoundCloud, and Scanner Radio, though I don’t know if it hasn’t happened on these by design or it’s just that I haven’t used them as much as the ones were the freeze/crash happens.
The reason why I’m not sure if it’s a freeze or a crash is that it seems like theirs is still power, it’s just that nothing is responding, the screen is black, nothing lights up, and pressing and holding the power button does nothing so I get the impression it’s stuck in some strange loop that clears once I pull the battery.
This is my second DX this is happening to, my 1st DX was replaced by Verizon for dead pixels so this doesn't seem to be related to just a bad phone.
Is anyone else having this problem? Any suggestions of a resolution?
I have had similar issues a well, maybe happens once a week though. Mainly when I have my cassette adapter running and doing other things at the same time. Haven't gotten too bad to try repairing it yet though.
Sent from my DROIDX using XDA App
MrWall said:
Ever since the Gingerbread update (and subsequent 2 patches) I’ve noticed that my DX will occasionally shut down(?) while listening to audio, it doesn’t matter if it’s streaming or a local file, podcast or music, at some random moment everything stops on my phone and the only way to get it restarted is by pulling/reinserting the battery.
So far it has happened while using Google Listen, Pocket Casts, Pandora, and Winamp
Other audio players where it hasn’t happened it is Google Music (both stock and beta), TuneinPro, SoundCloud, and Scanner Radio, though I don’t know if it hasn’t happened on these by design or it’s just that I haven’t used them as much as the ones were the freeze/crash happens.
The reason why I’m not sure if it’s a freeze or a crash is that it seems like theirs is still power, it’s just that nothing is responding, the screen is black, nothing lights up, and pressing and holding the power button does nothing so I get the impression it’s stuck in some strange loop that clears once I pull the battery.
This is my second DX this is happening to, my 1st DX was replaced by Verizon for dead pixels so this doesn't seem to be related to just a bad phone.
Is anyone else having this problem? Any suggestions of a resolution?
Click to expand...
Click to collapse
Only time I ever had an issue like this was one of 2 things happened... either the phone overheated, or I ran the memory out... do you use a task killer? I personally like using a task killer, even though they say GB automatically shuts down background apps when needed, I always found my phone faster and more responsive using a task killer. Just a preference but TaskXP for multitasking works very well for me and it is free on the market. If you have any questions about setting it up you can pm me.
On another note... if you are using so many apps to listen to audio, I'm assuming you probably have it hooked up in your car, maybe on a dash mount... check and see how warm your phone gets, as my DX runs pretty warm too, I had to modify my mount to allow for heat dissipation and I never had a problem after that.
SGT+CM7=:-D
I don't use a task killer mostly as you stated because gb is supposed to manage it well enough but also because it doesn't suppress apps so I kept noticing things restarting right after the app killer did it's thing.
actually I mostly get around on motorcycle and I'm not a fan of using headphones while riding. for the most part, when I'm listening to my dx that's all I'm doing with it because I'm usually preoccupied with something else at the same time.
So in short, when it crashes it's when it's only playing audio
Good suggestions though since I didn't cover what I was doing when it crashes
Sent from my DROIDX using XDA App
A factory reset will cure this.
rocko73 said:
A factory reset will cure this.
Click to expand...
Click to collapse
one would think but I've tried that a few times with the first DX and it didn't resolve the situation.
rocko73 said:
A factory reset will cure this.
Click to expand...
Click to collapse
I'm sure there is more than one issue that could lead to the unexpected reboots, so I doubt there is any easy and universal panacea, much as I wish there were. Factory resets haven't worked for me on either of my 2 DX's, and I can guarantee that overheating is not relevant on mine. It comes and goes, and I thought that perhaps I had it beat, but it's still there.
I've been through a number of SBF's, cache clearing, data clearing, factory data resets, etc., app removals with no resolution. It's most prone to spontaneous reboots while running audio apps, or navigating with Google Maps.
I am not too familiar with some of the acronyms used here but I am having the same problem. The reboots started to happen after I downloaded the latet OS update code. So far Verizon has been unable to help me fix the problem,. I will be going back to Verizon today and will update you with the outcome. So far Verizon has not been all that helpful.
Verizon reloaded the OS yesterday. I will know if that cured the problem after I do an hour on the bike this morning in the gym.
Same issue
I'm having the same issue; it happens when using Google Listen or Audible, more frequently with the latter. I've noticed the problem happens most frequently when I hit the power button to turn off the screen; about a half-second after the screen turns off, the phone crashes. Sometimes it reboots itself, but most of the time I have to remove the battery and then turn it back on. This happens only when listening to audio, and it doesn't matter whether it's through the audio jack, Bluetooth or the speaker. I've formatted the SD card and done multiple hard resets, but the problem continues.
I noticed that my DroidX only seems to do it when the screen is off. As far as I can tell if you keep the screen on it should not crash.
Nobody seems to know what to do about it. Verizon knows about it but Motorola seems to be clueless. Their crappy tech support only said it was a problem with the phone, but didn't know if it was a hardware or software bug. I have has the issue across 2 Droid X devices so I figure it is more likely just Motorolas crappy software.
I have installed the latest revnumbers daily build and it hasn't conked out yet.
Verizon is of course happy to keep swapping them out under extended warranty coverage at no cost. Not that it actually helps much.
I've had my Verizon Galaxy Note 3 since 10/13-10/14, pretty close to when it was released at Verizon. I've loved it, loved its tons of features, since I got it, and have had many people jealous. (I upgraded from a Galaxy Nexus, a heck of a reliable phone, when I realized that the Nexus 5 would also not go to Verizon.) In the past 6 weeks, i've encountered some curious behavior that i'm stumped and frustrated by. Overall, I love the phone.
Notes: I have searched and searched and searched for help, via Google and via XDA / AndroidCentral / other sites. My phone is un-rooted (never rooted), and has not been factory reset, dropped, submerged in liquids, or in any way mishandled. My phone uses the stock launcher and aside from some games, does not have a ton of apps installed.
However (Stated verbosely but with detail):
1) On two separate occasions, my Alarm has crashed. I used my Galaxy Nexus for nearly 2 years without ever having it fail to wake me (with many roms in between); I used my Droid X for nearly a year prior without ever having it fail to wake me, and before that my Blackberry Storm 2 for nearly a year without it failing. I'm not used to my phone failing me as an alarm.
In both cases, last Thursday (11/21) and today (11/25), I woke up to my phone acting as though the Alarm was still going off. (The notification bar indicated I should either Snooze / Dismiss the Alarm). I woke up about an hour after it should have went off, and there is absolutely zero possibility that I slept through the alarm going off that long. When I unlocked my phone, in both cases, it indicated the Alarm app had crashed.
I was using Timely on my Galaxy Nexus for the last few months of it as my daily driver, and then for the first few weeks on this phone. I immediately assumed it was the culprit, and went back to Alarm Clock Plus (the app I had used for nearly the entire time on my Nexus). This morning, Alarm Clock Plus crashed (with the 'Wait / Report / Close' options), and i'm now more confident that Timely was not the culprit.
In both cases, with both apps and on both days, after I clear the error, I had a similar experience.
- On Thursday, I pressed the power button to turn off the screen, and when I pulled the phone out of my pocket about 20 minutes later, it was completely powered off. However, I could not power it back on by pressing the button, and had to perform a battery pull to turn it back on.
- Today, I had pressed the button to perform a restart, and only tapped it instead of pressing + hold. Same thing happened: it turned off the screen but also somehow powered it entirely down, and required a battery pull to start it again.
- After Thursday's debacle, I have rebooted my phone multiple times, so it's definitely not because of an uptime related issue.
The only thing I can think of for the above scenario, is that I did have it work (the alarm) without any issues for a few weeks, and both issues (and some other random crashing of Google Plus, etc) have been following the update that was released by Verizon.
2) This is an issue i've experienced for the entire life of the phone, and is flummoxing me and extremely frustrating. I loved using the Droid X and then Nexus as my music player (both via headphones and definitely in the car via the Aux on my older stereo). On my Nexus I experimented with different Equalizers, including ones from Google Play (I liked 'Equalizer' quite a bit actually), and then I tried out and enjoyed Beats (or whatever it is now called, NexusLouder or whatever), to great enjoyment. Music sounded awesome.
On my Note, I expected at least a marginally similar level of audio (to that of the Nexus without Equalizer), until I rooted (which I have not done yet). I am facing (like others have sporadically reported) and issue where it appears that my Audio or Equalizer or something is turning off or turning on between songs. I'll plug it in to my car stereo, slap it in the window mount thing, and let it ride. It plays one track (sometimes two) without issue. Then, it will play a song either really quietly or really loudly. (I don't mean the volume has changed; it has not and I have verified this). The solution i've found is to go back (or forth) a track and then return to the same track, which has resolved this 100% of the time .... until a few tracks later. /rinserepeatrage
- I have tried this with the same Equalizer app, a few other Equalizer apps, and even without a Google Play Equalizer app (using only the built in one).
- On my Nexus and now my Note, i'm using Google Music, and use the pre-downloaded/cached songs.
- I have tried clearing the data / cache for Google Music and uninstalling / reinstalling it, to no effect.
- The only interesting thing i've noticed is that after the Verizon Note update (I believe), the audio appears to only get softer, rather than getting ear splittingly louder.
- Additionally, this seems to occur much more frequently when the screen is off.
Today I am going to the Verizon store and they will likely tell me they have to perform a Factory Reset (which is why I haven't already done one) before they'll give me another one, in the case that it is a hardware issue. I will very carefully be monitoring and see if this corrects / resolves either issue. I also intend to NOT install the update if I have any say (I don't know how not-rooted phones work with updates, i.e. if it is required or prompts for update, etc) If any of you have any ideas, solutions or suggestions, i'd be very open to them. I love this phone, but I absolutely hate that these two very important functions are not working consistently.
Well, i've been to Verizon and as expected, they heard my issue and thought that a factory reset might be the solution.
Their logic, which is not terribly shaky, was: the recent update (or even the factory pre-load of the OS) could have config or factory fragments / blahblahblah that a clear of the data / cache / etc could resolve. This made sense to me.
After the reset, we tried to recreate the Google Music bug in the office, no such luck, all looked good on the home front. I tried a few more songs on the way home, still not able to recreate the issue. I got home, all my stock apps updated, then I went through and installed apps, blah blah blah. I also cached the songs for an album so I could continue to confirm my confidence in this as being resolved.
I then went for a drive not too long ago, and the issue occurred again. I also noticed (though it may have existed prior to the factory reset) a new issue / symptom. When I scrub, like clockwork, the issue shows up. Song plays perfectly, I scrub (even only a few seconds forward), equalizer is gone and the music is much quieter. I have no clue what to think now. I will be hesitantly trying to recreate the alarm clock bug over the next few days. I also may try the old 'uninstall apps until I can't recreate' method too, for at least the Music bug.
If any of you all have thoughts, that would be extremely appreciated. Else, i'll keep reporting info as I get it, maybe this will help someone else.
Mine crashed Saturday. Woke up to the force close message.
Sent from my SM-N900V using xda app-developers app
kickenwing13 said:
Mine crashed Saturday. Woke up to the force close message.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Sorry to hear that! I know i've seen other reports on the interwebs saying similar things, but did not see any threads with discussions about theories or investigation, beyond the 'me too' I see often (which is entirely fine, and unfortunate for those who also have this issue!). Having the volume helps a ton, but i'm surprised I didn't see more analytical or critical thinking / discussion happening in the many threads, and figured i'd just get the ball rolling and hope this helps others (even if it's just mostly me putting findings down).
That said, I have more information to offer.
1) Alarm - Day 1, following the Factory Reset yesterday, it started without issue (not unexpected). I expect that the issue (if it does) will re-appear sometime around Friday - Saturday.
- Other than installing some apps (as mentioned previously) mostly things like Netflix and some games, I have not installed anything that (from what I can see) should interfere with an Alarm app
- I am presently using Alarm Clock Plus (the second of two apps I encountered the issue in); this is for consistency, and also because the app worked without issue for over a year prior to this
- I have not 'Turned off' any apps, though previously (prior to the Factory Reset) I had turned off some apps mentioned in other XDA threads as not required by the system to run (mostly Verizon and Samsung apps)
- I am not and have not rooted this phone at any time; this is 100% stock Android at this point (well, as Stock as a Samsung phone gets)
- After speaking with a few friends, they have confirmed that: this issue has occurred with the stock Alarm Clock app and another 3rd party app (one I have not tried yet) as well; but one friend has not experienced any Alarm issues at all (though he may just not be aware of them, so i'm taking his account with a grain of salt)
2) Music - To add to my previous notes about the issue around the equalizer ..
- I am able to (as indicated previously) re-create the issue on-demand by scrubbing
- I can re-create the issue relatively reliably by hitting 'Pause / Play', and I didn't see a difference (in ability to reproduce) whether it was from the lock screen or in the app that I hit 'Pause / Play'
- It does appear that (with inconsistent results) I experience the Equalizer turning off / on by itself, if I keep listening to songs the issue seems to reverse. (i.e. Song 1 is fine, Song 2 - Equalizer turns off, Song 3 or Song 4 - Equalizer turns back on) I encountered this just a bit before this post, and sure enough, after hitting 'Pause / Play' I was able to verify that the Equalizer had turned back on.
- I am now 100% positive it is the Equalizer being horked by the phone / OS / something. This is based on replication of the issue (where it sounds like it gets soft) being the exact same sound as when the Equalizer is just turned entirely off.
A few things to test today / next few days:
Alarm issue:
-None at this time; keep observing
Music issue:
- Google Play Equalizer app (see if issue occurs still outside of the stock Equalizer)
- Try non-Cached music to see if this is a factor (including 'Pause / Play'; song scrubbing; etc)
- Try an alternative to Google Music (this is not a practical solution to me, but would provide comparison data)
Last note:
- After completing the Factory Reset and hearing my story yesterday, the Verizon rep did inform me that I could bring the phone back, if the issue keeps happening, and exchange it for a refurb. I'd rather avoid this if possible, as I feel like i'm not as confident it is a hardware issue as before, but this is an option (and may be an option for others wishing to try this path). Obviously, I hadn't rooted, so the Manufacturer's Warranty was available, so YMMV.
verziehenone said:
Sorry to hear that! I know i've seen other reports on the interwebs saying similar things, but did not see any threads with discussions about theories or investigation, beyond the 'me too' I see often (which is entirely fine, and unfortunate for those who also have this issue!). Having the volume helps a ton, but i'm surprised I didn't see more analytical or critical thinking / discussion happening in the many threads, and figured i'd just get the ball rolling and hope this helps others (even if it's just mostly me putting findings down).
That said, I have more information to offer.
1) Alarm - Day 1, following the Factory Reset yesterday, it started without issue (not unexpected). I expect that the issue (if it does) will re-appear sometime around Friday - Saturday.
- Other than installing some apps (as mentioned previously) mostly things like Netflix and some games, I have not installed anything that (from what I can see) should interfere with an Alarm app
- I am presently using Alarm Clock Plus (the second of two apps I encountered the issue in); this is for consistency, and also because the app worked without issue for over a year prior to this
- I have not 'Turned off' any apps, though previously (prior to the Factory Reset) I had turned off some apps mentioned in other XDA threads as not required by the system to run (mostly Verizon and Samsung apps)
- I am not and have not rooted this phone at any time; this is 100% stock Android at this point (well, as Stock as a Samsung phone gets)
- After speaking with a few friends, they have confirmed that: this issue has occurred with the stock Alarm Clock app and another 3rd party app (one I have not tried yet) as well; but one friend has not experienced any Alarm issues at all (though he may just not be aware of them, so i'm taking his account with a grain of salt)
2) Music - To add to my previous notes about the issue around the equalizer ..
- I am able to (as indicated previously) re-create the issue on-demand by scrubbing
- I can re-create the issue relatively reliably by hitting 'Pause / Play', and I didn't see a difference (in ability to reproduce) whether it was from the lock screen or in the app that I hit 'Pause / Play'
- It does appear that (with inconsistent results) I experience the Equalizer turning off / on by itself, if I keep listening to songs the issue seems to reverse. (i.e. Song 1 is fine, Song 2 - Equalizer turns off, Song 3 or Song 4 - Equalizer turns back on) I encountered this just a bit before this post, and sure enough, after hitting 'Pause / Play' I was able to verify that the Equalizer had turned back on.
- I am now 100% positive it is the Equalizer being horked by the phone / OS / something. This is based on replication of the issue (where it sounds like it gets soft) being the exact same sound as when the Equalizer is just turned entirely off.
A few things to test today / next few days:
Alarm issue:
-None at this time; keep observing
Music issue:
- Google Play Equalizer app (see if issue occurs still outside of the stock Equalizer)
- Try non-Cached music to see if this is a factor (including 'Pause / Play'; song scrubbing; etc)
- Try an alternative to Google Music (this is not a practical solution to me, but would provide comparison data)
Last note:
- After completing the Factory Reset and hearing my story yesterday, the Verizon rep did inform me that I could bring the phone back, if the issue keeps happening, and exchange it for a refurb. I'd rather avoid this if possible, as I feel like i'm not as confident it is a hardware issue as before, but this is an option (and may be an option for others wishing to try this path). Obviously, I hadn't rooted, so the Manufacturer's Warranty was available, so YMMV.
Click to expand...
Click to collapse
My stock alarm crashed yesterday. Woke up to a completely black phone. Only the pulldown would get out of the crashed alarm app. Quite unfortunate. 100% stock, unrooted.
Botond said:
My stock alarm crashed yesterday. Woke up to a completely black phone. Only the pulldown would get out of the crashed alarm app. Quite unfortunate. 100% stock, unrooted.
Click to expand...
Click to collapse
Sorry to hear that
On a similar note, if anyone can re-produce the Music issue i've mentioned, that would help me confirm i'm not crazy or alone in my issue.
Of note:
Music:
- I have attempted to recreate the issue in Pandora, but was unsuccessful. The audio remained unchanged when I did a Pause / Play (I was unable to scrub, unsure if that's a Premium feature or just not a thing with Pandora). I will not be able to try a local song with another music app until I am home this evening.
- I was able to recreate the issues (scrubbing, between track loss of equalizer, pause/play) with the Google Play equalizer app 'Equalizer' reliably.
- I was able to recreate the issues (scrubbing, between track loss of equalizer, pause/play) using both Cached music and Streaming, with stock and 3rd party equalizer
After searching for awhile for an already open bug report, I have opened up a bug report on the AOSP site, in case you are interested, for the Music issue: 62864 is the defect number; I am unable to link it since i'm still not yet a real boy.
I will hold off on creating one for the Alarm issue until I am able to recreate it post-Factory Reset.
This will likely be the last update until post-Thanksgiving, and will hopefully bring a measure of consistency (if the Alarm error returns) or confidence (if it doesn't) to the information I have.
Music:
- I was able to recreate the issue with scrubbing and 'pause/play' with a song located directly on the phone (not downloaded/cached via Google Music)
Other notes:
- I've seen other sites with similar sounding issues for different phones, such as the Galaxy S4, well before the Note 3 came out
- This is noted as being a bug with the equalizer, but not specific to the .api or .dll or whatever Android calls reusable things (as this is an issue with not just the stock equalizer, which points to some system dealie rather than the specific equalizer)
- I have not yet tested another app such as PowerAmp or similar, but suggested workarounds on the GS4 issue thread (on AndroidCentral) indicate disabling the equalizer altogether (not a great workaround) or using another app (not confirmed as a workaround; by me or the thread)
- One other forum suggests it is due to a bug in the OS with the equalizer not having a persistent icon in the notification bar, and suggests using another app (the 'Equalizer' app from Google Play is suggested) to resolve; this thread was started in May of 2013, but does point to it turning off during playback, not in between songs
- Still another person does report the issue I have experienced, with the issue displaying when the screen is off during the change from one track to another; this person also indicates WinAmp did not resolve this issue (implying that: A) local tracks are not the fix, and B) that another player is not)
Alarm:
- Day 2 after Factory Reset, the alarm went off again without issue
- I have had difficulty with finding many other threads or information; if you are reading this and have experienced this, it would be helpful for information to note that you have had it, and if you have the MJ7 update (or whatever) that too would help
- I might end up doing a bit of 'set an alarm for 5 minutes' testing and see if I can recreate the issue with any reliability
Learning is fun! Happy Thanksgiving and/or Hanukkah everyone!
verziehenone said:
Alarm:
- Day 2 after Factory Reset, the alarm went off again without issue
- I have had difficulty with finding many other threads or information; if you are reading this and have experienced this, it would be helpful for information to note that you have had it, and if you have the MJ7 update (or whatever) that too would help
- I might end up doing a bit of 'set an alarm for 5 minutes' testing and see if I can recreate the issue with any reliability
Learning is fun! Happy Thanksgiving and/or Hanukkah everyone!
Click to expand...
Click to collapse
My alarm crashed a couple times with my unrooted Note 3. After I rooted, no more problems with Alarm or anything else crashing.
My advice??
Root & load SafeStrap 3.65 HAppY Thanks Giving
Are you using any battery-saving apps? That could create issues like this, especially if the app messes with wakelocks.
I am rooted with the stock MI9, and alarm crashed one morning. Apparently there is a bug, root or no root. All I had to was restarting the phone and it worked after that, but it may crash anytime, I'm afraid.
Sent from my SM-N900V using xda app-developers app
Update (12/2):
So, after a Thanksgiving break and more time for more research...
Alarm:
- Since the Factory Reset, I have not had the alarm fail
- From Thursday Morning to Sunday Morning, I did manually / individually set an alarm for each day; unknown if this is a factor
- I do not use any power saving anythings (I don't even use the built in Note power saving mode)
Music:
- Audible (the Amazon Audiobook App) did not display this behavior
- I have not had a chance to try to uninstall until I cannot recreate this
Related to above?
- Once more I set the phone down (this time after using it very liberally for the past few days, and then on an 8 hour drive home yesterday) on a coffee table, not hard or anything, and it would not turn on
- Weirdly enough, although the power button, home key (or whatever the physical key in the middle of the phone is called) would not turn the screen on, but when I pulled the stylus out (on a whim), the screen turned on but was not responsive
- Battery pull resolved this, but I never saw any errors / errored apps / etc
- I am more firmly believing that at least this part is related to a hardware issue and will be going to Verizon tonight for my Manufacturer's Refurb or whatever
Notes:
- I am not using any crazy apps, mostly games and such, all straight from Google Play and none are those obviously suspect apps (like the many strip poker, etc, that are very shady)
- Although I have a decent volume of apps (probably about 40 or so from Google Play, not including the Verizon pre-loaded), I have fantastic battery life still
- I do not have any power saving anything turned on, on the phone, and do not use auto-dim, or anything like that
- Since the factory reset, I have not 'turned off' any apps
- I do have a Sandisk Ultra 32GB microSD card, this could be a factor
- I have a Model: SM-N900V UD (in case the Refurb is a different model)
That's all for this update, will keep updating as I have more information to share. (Still assuming that at least someone is finding this helpful, if not, i'll keep playing quietly in the corner)
More updates -
Alarm:
- The Alarm functioned without issue once more this morning (this time the result of a recurrent alarm, and not a manually set alarm)
- I am beginning to suspect that after the latest OTA, it gummed up something and just required a Factory Reset to un-gum
- The alternative is that the issue with the unresponsive screen is related, but the times I experienced the Alarm issues were accompanied with an error indicating the Alarm app had crashed
Music:
I played around with a few settings and did some app-investigation and learned stuff.
- I DO have 'All Access', though i'm unsure how that would impact the equalizer
- Surround vs. Stereo does not make a difference, issue is still present
- Adapt Sound On does not make a difference
- Adapt Sound 'Turned Off' does not make a difference
- Having the S Pen out does not make a difference
- I went through and wrote out every single app installed on my phone, Google, Samsung, Verizon, Play, etc ... and found a total of 356 apps. The breakdown was: 326 Pre-Loaded/Verizon, and 30 that I installed. I have uninstalled all but about 5 apps (Alarm Clock Pro, Business Calendar, Facebook, Outlook.com, A Better Camera, and Safe In Cloud) and the issue is still present
- I cleared the Cache / Data and 'reverted' Google Music to the pre-installed/factory installed version: v5.1.1107K.753159 and after this was completed, the issue was NOT re-creatable (at least the 'scrubbing' part)
- I re-installed the most current Play version: v5.2.1301L.891271 and the issue was NOT re-creatable (at least the 'scrubbing' part)
- My working theory is ... well, no, I don't really have any idea now; I thought the version could be an issue, but that doesn't appear true. After the Factory Reset, the version would have been reset as well, but the issue returned, so maybe it takes time?
Note:
Due to the other mentioned issue (where I set my phone down and it randomly is unresponsive) I will be receiving my Manufacturer's Refurb on Wednesday-ish (depending on whether or not FedEx tries to deliver when i'm at work or not). The hope is threefold: 1) that this resolves the issue with the random unresponsiveness, 2) this resolves the issue with Google Music, and 3) this resolves the issue with Alarms. This would confirm a hardware related issue as being the source of all three, but if either of the other issues return, this means one of two things: 1) the issues are software related, or 2) the statistically unlikely but possible situation where I received two bad units.
To any readers: I've asked before, but figure i'll ask again.
1) Have any of you experienced the issue with Google Music's equalizer shutting off when scrubbing, in between tracks, or similar?
2) Have any of you experienced the issue with the Alarm not going off, AFTER receiving the latest OTA?
3) If you have experienced either of the above issues, have you performed a Factory Reset after the OTA?
Update: 12/5
Alarm:
- No issues since the Factory Reset still
- Really starting to think the Factory Reset was the key
Music:
- Still all kinds of things going on; tried another reset to 'stock' Google Music but issue came back
- More research seems to find this issue with other 4.3 phones like the Galaxy S4, etc
Notes:
I have now received my Manufacturer's Refurb. I'm about to go through the process of the switchover, but I wanted to note something I found interesting. On the sticker behind the battery, (where the IMEI and all that business is), I noticed one difference between the one I bought in the store and the refurb.
Model is unchanged, so is SKU and FCC ID. Right below 'Made in China' and above 'IMEI' I see a number. On the one I bought was '13.09', but the refurb is '13.10'.
Does anyone else have any other numbers? Is that a revision or something like that? Just wondering if that could mean another run of the hardware or something. Or if it's nothing of course, whatever.
I'll update again once I have more info from the refurb. /crossingfingers
I have the same problem. I have had my Note 3 for a week, and yesterday a third party alarm crashed (Sundroid). Then today, the stock alarm app crashed. Do you use a widget for your alarm? I do. This is stock, unrooted, very few apps. Is there more information I can give to you?
Alexander_Q said:
I have the same problem. I have had my Note 3 for a week, and yesterday a third party alarm crashed (Sundroid). Then today, the stock alarm app crashed. Do you use a widget for your alarm? I do. This is stock, unrooted, very few apps. Is there more information I can give to you?
Click to expand...
Click to collapse
Good questions I do not use a widget, and with regard to the Alarm, I think the one big question is: Have you received the MJ7 OTA? (If you go into About Phone and look at Build Number, the last 3 characters tell you if you have the latest OTA). If you do, I would suggest a Factory Reset, which is painful but appeared to resolve the issue for me.
Updates: (12/6)
I have received my Manufacturer's Refurb and have completed the process of switching over (including a Factory Reset after the OTA update). I am still curious what the 13.10 means on the sticker with the IMEI (since my previous phone at 13.09).
Alarm:
- The alarm worked without issue on Day 1 with new device
- All signs right now point to: If you have Alarm issues, and have received the MJ7 OTA, perform a Factory Reset; seems to resolve it
Music:
- On the Manufacturer's Refurb I was able to quickly confirm the presence of the bug
- This is looking more and more like an issue with either 4.3 or some Samsung software issue
- I would suggest submitting a bug report to Google and also posting a review on the Google Music software, see if we can get Google to look into it
Thoughts:
- Is there a Google Music .apk for 4.4? Does it require Root to side-load if so?
- I wonder if anyone with a Nexus 5 (or other device with 4.4) can recreate the issue
I didn't read thru everything here, but I use Alarm Clock Plus (the paid version) and it has never crashed once on me.
I bought my N3 the day they where released and used it everyday on first the stock ROM & now Beans ROM..
I am on the updated mj7 firmware etc.etc.
jmorton10 said:
I didn't read thru everything here, but I use Alarm Clock Plus (the paid version) and it has never crashed once on me.
I bought my N3 the day they where released and used it everyday on first the stock ROM & now Beans ROM..
I am on the updated mj7 firmware etc.etc.
Click to expand...
Click to collapse
How long ago did you root it? I'm assuming you performed a factory reset or a cache/data clear (or similar) as part of the rooting process, so i'm leaning towards that being the reason it has been stable. That said, if my theory holds that it is related to the MJ7 firmware and needing to be cleared out or whatever, that also means that it likely wouldn't be affecting everyone.
Are you able to replicate the issue with equalizer? I hadn't thought to ask if Rooted users experience it too.
verziehenone said:
How long ago did you root it? I'm assuming you performed a factory reset or a cache/data clear (or similar) as part of the rooting process, so i'm leaning towards that being the reason it has been stable. That said, if my theory holds that it is related to the MJ7 firmware and needing to be cleared out or whatever, that also means that it likely wouldn't be affecting everyone.
Are you able to replicate the issue with equalizer? I hadn't thought to ask if Rooted users experience it too.
Click to expand...
Click to collapse
When the mj7 tar was released, I did an odin flash of that to reset everything in my stock ROM slot.
I still had beans ROM in slot one with safestrap and it didn't affect that.
I have had no music problems whatever, but I use WinAMP with the viper sound mods. I have 800 gigs of music on my 64 gig card that I play thru headphones or hdmi out in my truck.
jmorton10 said:
When the mj7 tar was released, I did an odin flash of that to reset everything in my stock ROM slot.
I still had beans ROM in slot one with safestrap and it didn't affect that.
I have had no music problems whatever, but I use WinAMP with the viper sound mods. I have 800 gigs of music on my 64 gig card that I play thru headphones or hdmi out in my truck.
Click to expand...
Click to collapse
That helps
Unfortunately, i've already heard that a good way to resolve this issue is to install the Viper sound mods, but was hoping to prove whether or not Rooting / Rom-ing it (without Viper) made a difference.
Of note -
Music:
- I turned off the equalizer entirely, figuring i'd just deal with it with a more flat sound, and after playing 2-3 songs, the music got really loud; after doing a pause/play, it went back to normal. I verified (before pause/play) that the equalizer was still off
- I am still unsure why my friend couldn't recreate this, as if it is a software issue, any Note 3 should be able to recreate it