I'm trying to see if I have a bad Iconia. I've only read great things regarding the quality of the device. For the most part I agree.
Problem:
So I just I just bought an Acer Iconia on 6 days ago.
Just a couple days ago while listening to some music, I noticed clicking and popping during playback. Its not quiet either, the offending sound is louder than the music that is playing.
Workaround:
I have found if I want to stop the offending sound. If I play music in a different app, then the switch back to the first music app, the offending sound is gone. However, only a short time passes before I have to perform this task again.
Solution:
I'm considering exchanging the tablet for a new one.
Has anybody else experienced something like this?
Just after I first bought mine, my speakers would occasionally make a crackling sound, sometimes even when no audio was being played, it went away after a bout a week though, and hasn't happened again.
I exchanged the problematic with a new one. I've been listening to music all day without any issues. It appears I got a bad apple the first time. It happens.
UPDATE!!!
So here we are, 3 days worth of regular music playback and I just experienced the problem again. Just as the previous poster mentioned, I will wait until Wednesday next week to see if the problem clears up on its own.
Odd, perhaps this is a software issue?
So here we are, 3 days worth of regular music playback and I just experienced the problem again. Just as the previous poster mentioned, I will wait until Wednesday next week to see if the problem clears up on its own.
Odd, this is starting to sound like a software issue. I will report back soon.
I can pretty much guarantee that this is a software problem, as I didn't have any issues to this effect for months, but now have it happen all the time after either the most recent update or possibly the one immediately prior. I'm having all kinds of problems after this last update, including music playback stopping after the current track when the screen is turned off, the popping and clicking, slow to come back after sleeping, crashing of the browser and of the overall system... Hopefully we'll see another update that will get things back to normal very soon, because this is nuts.
I agree its a software issue. Here is what I've found:
1) I am unable to replicate this problem using other media players. One of the ROMS i was trying out had the toshiba media player, and i played hours of local music with no issues. The new android music player periodically pops and cracks regardless of whether i am playing local or streamed music via gmusic.
2) By simply pausing the current track, and resuming shortly after eliminates the sound issues. You may even need to unplug your headphones / line out if you are using that.
3) I subscribe to Rhapsody and have yet to experience the popping issue, even after continuous hours of streaming playback.
This is very likely a software issue, much like the random issue some HC users were experiencing with the browser spontaneously closing. Hard to track down, and hopefully fixed in some update that may or may not come
To me this sounds like...
I think more troubleshooting may be in order - have you been able to reproduce the problem with *any* mp3 file you use, or only from one specific set of mp3?
Default music player works great for me for any files I decide to throw at it. Sure, I still have to wake up the screen between tracks sometimes, but that is a known issue with the a500 - never get any strange popping - and my a500 literally plays tracks 4+ hours a day (I do a long commute to get to work lol)
Try reproducing the problem using a known good set of mp3 files - the fact that you have returned one unit and are still having the same problem means that chances are:
1) you have a bad set of audio files - other systems, especially desktop and laptop systems - may be able to decode the corrupted or unstandard file without issue - this does not mean the Iconia can do the same.
2) you installed a application that is causing issues - can you reproduce this problem after a full factory reset? Just reset, load your music, and try to reproduce the problem.
If you could attach a copy of the audio file that is causing this issue - perhaps people can take a look at it and see if you have a format issue.
orbix said:
I can pretty much guarantee that this is a software problem, as I didn't have any issues to this effect for months, but now have it happen all the time after either the most recent update or possibly the one immediately prior. I'm having all kinds of problems after this last update, including music playback stopping after the current track when the screen is turned off, the popping and clicking, slow to come back after sleeping, crashing of the browser and of the overall system... Hopefully we'll see another update that will get things back to normal very soon, because this is nuts.
Click to expand...
Click to collapse
Music stopping between tracks while screen is asleep is a known issue - it's nothing unique to your experience.
Work around - use an alternative media player (in my experience winamp does not have this issue) or simply hit the power button between tracks to continue playback in the default media player. It's a pain in the ass, but it works.
Unfortunately, I've been using Google Music to deal with having a music library I want to access on my Galaxy S phone, Iconia, and work laptop, so unless I just download everything I want to listen to using the 'make available offline' feature and then listen to it in another app (which is a PITA), I guess I'm stuck with this. The 'pause and it goes away' bit hasn't worked for me, either.
As for the music stopping when the screen is off, I'm just frustrated by this since it was working fine for me before, and then Acer broke this with the update (at least for me- no guarantees it's specifically that update, but something about that update made this start happening for me).
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.
Hi guys. I got myself a 32gb, wifi only version of N7. Upgraded it instantly to 4.2.2 . Nothing to complain about in the first 2 days.
After that, I noticed that, when I play music (stream through upnp on local network or play mp3 / flac files on local storage - tested several players, bsplayer, google player, poweramp...), and do some other stuff on the tablet at the same time - surf, or just 'click around', or swipe through my documents - occassionally I experience short sound dropouts, like the I/O-load would be too high or something. Please note this isn't bluetooth thing some people experienced, I use regular phones. It happens sometimes when I do some trivial stuff...noticed it all over the place, while starting an app, surfing, writing something in the Google search window, searching people on FB, opening a browser (empty) tab, even clicking on application button to see the list. It can be really anything, it doesn't happen a lot but it's there.
I googled the problem but couldn't find anyone with similar issues. Read on the other hand a lot about general performance issues of the Nexus 7 after 4.2.2 upgrade, about (visual) lag, so I figured, even though my eye didn't catch that on my device (this is my first experience with 4.x.x so it looked fast and smooth enough to me), I decided to revert to 4.1.2 and see whether there would be any difference. I can't say I could see/hear improvement, maybe a slight one, but I still get to experience occassional chops in my music, which is very annoying, this should be ridiculously easy for a 4-core processor to accomplish. It's unacceptable. I even checked that CPU wasnt overloaded when these chops occured (in fact, it was only around 25%-30% when the chops occured, perhaps the peaks were too short for program to register them - I dunno)...
I also tried everything people suggested here regarding general performance issues, disabling this and that, Currents, factory resets, cleaning cache partition...you name it. Nada.
Anybody experienced similar thing? Don't know if I have faulty unit or if this is bug in software (Samsung Galaxy S3 had a similar thing when it got out, even though the sound pops were of different nature and occured under different circumstances - took several software upgrades until it got fixed)...I'm thinking of returning it and go for iPad mini or something.
Thanks in advance for any feedback.
The results of this have varied but there are some who attest that this works.
Have you disabled auto-sync in Google Currents (Blue Circle Icon)?
If not, try that; this has worked for me.
Open up "Google Currents" Hit the 3 dots on the top right -> Settings -> Scroll down and UNCHECK "Enable background sync"
Remember these results have varied, but it fixed the issue with my tablet. Also I heard there were some issues (although if someone can confirm them further for us--that'd be appreciated!) with the RAM in many Nexus 7s so stressing out the ram and filling up your SDcard to the max will cause it to have stutter issues too.
Hi and thanks for the suggestion,
Disabling the background sync in Google Currents was actually the first thing I did. I believe I tried out everything that was suggested so far on the net regarding the general performance issues. I used Forever Gone app to fill up all space and then delete it, I wiped the cache partition in bootloader mode, I even did a factory reset, and eventually I re-flashed it back to 4.1.2 (it did improve then but the music lag / pops were still not entirely gone). SD-card space-thing cannot be the issue either as I have like 23gigs free.
Now I even noticed that video playback is effected by occasional sound pops. When I play video in full screen, not doing anything else, it still happens. Rarely but it does happen.
TheAltruistic said:
The results of this have varied but there are some who attest that this works.
Have you disabled auto-sync in Google Currents (Blue Circle Icon)?
If not, try that; this has worked for me.
Open up "Google Currents" Hit the 3 dots on the top right -> Settings -> Scroll down and UNCHECK "Enable background sync"
Remember these results have varied, but it fixed the issue with my tablet. Also I heard there were some issues (although if someone can confirm them further for us--that'd be appreciated!) with the RAM in many Nexus 7s so stressing out the ram and filling up your SDcard to the max will cause it to have stutter issues too.
Click to expand...
Click to collapse
Returned it and took money back. Will look for other options soon. This thing was too 'beta' for me.
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