Hello,
My music player ( pre-installed in Milestone 2 UK retail ) go freeze sometimes, especially after a song finished.
This happened randomly and not so frequently, sometime music player works perfect even I played all songs ( 80+ songs ). So I don't know whether a solution really works immediately.
After the music player freezed, I cannot operate any thing in the player interface, just force close the player in process manager, restart the player, then I can't play songs anymore ( freeze again ) .
And, I can't start any SD-related apps like video players and some games ( like Asphalt 6 ). But I can copy/cut files in the file manager.
Remount SD card or reboot the phone, everything backs to normal.
Is this the microSD's problem?
I tried different ways to format it but never solve the problem, and, Watching movies/Playing games goes well. I also try to replace the music playing libs with Droid X's (http://yuanjie.name/entry/milestone-2-mp3-crackling-playback-issue-solved), but music player freeze again last night.
I have no idea what happened.
Thanks in advance.
Try an alternative music player such as WinAmp or PowerAmp.
Check if your problem persists.
MegaBubbletea said:
Try an alternative music player such as WinAmp or PowerAmp.
Check if your problem persists.
Click to expand...
Click to collapse
Thank you very much!
I'm try PowerAMP now, I really enjoy this powerful app.
I'll give a feedback if it doesn't freeze after several days.
This looks like SD Card issue. New player won't help IMO. Try testing on another dard.
I really think it's a kernel problem, or at least a problem with the media scanner. Sadly, I think we'll have to wait for GB update =/
AragornPE said:
I really think it's a kernel problem, or at least a problem with the media scanner. Sadly, I think we'll have to wait for GB update =/
Click to expand...
Click to collapse
For GT540 or M2? I think ur i the wrong thread mate.
MegaBubbletea said:
For GT540 or M2? I think ur i the wrong thread mate.
Click to expand...
Click to collapse
I didn't say anything about GT540 =]
I'm in the same situation as he is: an issue with high capacity sd cards on milestone 2
Welcome to the club.
http://forum.xda-developers.com/showthread.php?t=929901
dymonaz said:
Welcome to the club.
http://forum.xda-developers.com/showthread.php?t=929901
Click to expand...
Click to collapse
I read the thread, it has some similarities with the problems that waigx and I are facing. Can you open any other application after PowerAMP shuts down? Does it really shuts down or crash (stays in memory but doesn't execute anything)? Can you open a file manager when this happens?
I'm using Cubed as my player - though all other players I tried (default from Motorola, Meridian, PowerAMP, WinAmp) behaved exactly the same.
Sometimes the player keeps on thinking it is still playing (i.e. track progress is moving without sound), but usually it just ends up with ANR. All other applications [that I need] seem to work fine after this. I do seem to remember Goggles and Camera not responding after a crash, but they crash on their own anyways, so can't really put blame on music player crashing.
A couple of times I did have a case where I couldn't open up SD card anymore, but I've gotten so used to this (8 hours of work+music with 2-3 crashes [or more?] every day) that I stopped trying - just reboot and continue where I left off.
The crashes happen around the same time (but not exact) - around lunch, then at around 3-4pm. Sometimes it also crashes when I'm on my way home ~6-7pm. I think it is somewhat related to power management - I notice it crashes more often as the battery is going down (although I do charge pretty much every night) and there's that "standby called" log message. I did try various battery settings with no luck - any suggestions what I could try more?
There were also a couple of times where I would just leave it at rest after a crash, then start Angry Birds (seemed to reset media/sound system or something), or just wait 15-30 minutes and the sound would come back and the player would unfreeze after a force close and everything would work fine. Until the next crash, that is.
I'll try the remount SD trick and I'll double check the file manager the next time it does this - presumably just after lunch on Monday
I freezed the media scanner with Titanium Backup and scanned music media with PowerAMP, but I had the same problem afterwards... Looks like a deeper problem or a problem with the sd card
waigx said:
Hello,
My music player ( pre-installed in Milestone 2 UK retail ) go freeze sometimes, especially after a song finished.
This happened randomly and not so frequently, sometime music player works perfect even I played all songs ( 80+ songs ). So I don't know whether a solution really works immediately.
After the music player freezed, I cannot operate any thing in the player interface, just force close the player in process manager, restart the player, then I can't play songs anymore ( freeze again ) .
And, I can't start any SD-related apps like video players and some games ( like Asphalt 6 ). But I can copy/cut files in the file manager.
Remount SD card or reboot the phone, everything backs to normal.
Is this the microSD's problem?
I tried different ways to format it but never solve the problem, and, Watching movies/Playing games goes well. I also try to replace the music playing libs with Droid X's (http://yuanjie.name/entry/milestone-2-mp3-crackling-playback-issue-solved), but music player freeze again last night.
I have no idea what happened.
Thanks in advance.
Click to expand...
Click to collapse
This thing has worked on my gf's milestone 2 ... but I am not sure if it will work for you ...
1.) Backup ur device/settings/messages etc
2.) Factory reset the device
3.) Sign in your motoblur a/c after factory reset
Immediately after that
4.) Open connected Music Player .. press menu button and find the options for tunewiki lyrics/covert art downloader ... uncheck all of those
5) Settings->DataManager-> somewhere u will find similar options as above .. disable all of those
Basic Idea is to completely diasble all sort of data that the connected Music Player will ever need ....
Sorry, I could not give you the exact Menu operations because I dont have the device with right now... But it works if u r ready to do the factory reset...
You will actually like the Connected Music Player after this because it has a nice shoutcast integration and neither does it crash so often like Winamp...
Also as far as I know the bug with the Connected Music Player is such that Music in all sort of other players including Winamp also stops working ..
Tell me if it works
dymonaz said:
I'm using Cubed as my player - though all other players I tried (default from Motorola, Meridian, PowerAMP, WinAmp) behaved exactly the same.
Sometimes the player keeps on thinking it is still playing (i.e. track progress is moving without sound), but usually it just ends up with ANR. All other applications [that I need] seem to work fine after this. I do seem to remember Goggles and Camera not responding after a crash, but they crash on their own anyways, so can't really put blame on music player crashing.
A couple of times I did have a case where I couldn't open up SD card anymore, but I've gotten so used to this (8 hours of work+music with 2-3 crashes [or more?] every day) that I stopped trying - just reboot and continue where I left off.
The crashes happen around the same time (but not exact) - around lunch, then at around 3-4pm. Sometimes it also crashes when I'm on my way home ~6-7pm. I think it is somewhat related to power management - I notice it crashes more often as the battery is going down (although I do charge pretty much every night) and there's that "standby called" log message. I did try various battery settings with no luck - any suggestions what I could try more?
There were also a couple of times where I would just leave it at rest after a crash, then start Angry Birds (seemed to reset media/sound system or something), or just wait 15-30 minutes and the sound would come back and the player would unfreeze after a force close and everything would work fine. Until the next crash, that is.
I'll try the remount SD trick and I'll double check the file manager the next time it does this - presumably just after lunch on Monday
Click to expand...
Click to collapse
My Goggles and Camera also always crashed long time ago, but your problems is really stranger than mine.
I think you should WIPE your phone ( don't forget backup data before it ).
Before I flashed the Argen2Stone ROM, I suffered from the same problem. The CMP froze spontaneously.
Now - after using A2S - I never recognized such a behavior again.
anupash said:
This thing has worked on my gf's milestone 2 ... but I am not sure if it will work for you ...
1.) Backup ur device/settings/messages etc
2.) Factory reset the device
3.) Sign in your motoblur a/c after factory reset
Immediately after that
4.) Open connected Music Player .. press menu button and find the options for tunewiki lyrics/covert art downloader ... uncheck all of those
5) Settings->DataManager-> somewhere u will find similar options as above .. disable all of those
Basic Idea is to completely diasble all sort of data that the connected Music Player will ever need ....
Sorry, I could not give you the exact Menu operations because I dont have the device with right now... But it works if u r ready to do the factory reset...
You will actually like the Connected Music Player after this because it has a nice shoutcast integration and neither does it crash so often like Winamp...
Also as far as I know the bug with the Connected Music Player is such that Music in all sort of other players including Winamp also stops working ..
Tell me if it works
Click to expand...
Click to collapse
Hey anupash,
I really appreciate for your detailed answer, I was bought PowerAMP. Even thought it cost $4.99, but I think it worth that.
I delete up CMP in the file system, my phone runs well in these days. Players like Winamp, realone are using system decode libs, so they also meet some problems I guess.
Connected Music Player have a great integration with the whole system, but I need data sync and album-arts.
Thank you again, If I meet additional problems I'll post in this thread later.
Best regards.
dymonaz said:
I'll try the remount SD trick and I'll double check the file manager the next time it does this - presumably just after lunch on Monday
Click to expand...
Click to collapse
File manager seemed to work - at least for browsing the folders.
Unmounting SD killed the player. Remounting it back and trying to play anything made the phone reboot on it's own. Go figure.
waigx said:
My Goggles and Camera also always crashed long time ago, but your problems is really stranger than mine.
I think you should WIPE your phone ( don't forget backup data before it ).
Click to expand...
Click to collapse
Thanks for the tip Sadly, I don't have time for this now - as I mentioned - I pretty much got used to it constantly crashing... But I'll probably do that if the upcoming (hopefully soon...) MotoEurope update doesn't help.
Im having this problem also. Random freezes at playback... using winamp there´s no problem...
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
Hi guys,
Has anyone noticed heavy lag and freezing when using the phone. I don't have a lot of apps installed and i have disabled most apps that i don't use and the phone is still giving me issues.
Any advice is appreciated. [emoji4]
I switched from RAZR MAXX HD and this phone is a space rocket in comparison to my old Droid. Have you tried factory restore? Then if it lags - I would try to return it to Moto.
Check CPU utilization. Maybe some app hangs on. I've noticed that noozy (music player) lags like hell when album is over and player remains in notification bar.
emineh17 said:
Hi guys,
Has anyone noticed heavy lag and freezing when using the phone. I don't have a lot of apps installed and i have disabled most apps that i don't use and the phone is still giving me issues.
Any advice is appreciated. [emoji4]
Click to expand...
Click to collapse
I have the same problem, I tried to removing as much as possible automatic start calling but often when I uncheck the receiver this puts me "failed" in Rom Toolbox, I have tried Xposed Auto Boot module, but I do not feel that it works.
But for me, I have a lot of app instaled and my UI is very modified (Nova Launcher, Gravity Box, various Widget), so I know why he lag, but I still find it overheating lot and that's what most do slow.
Hi, I am having same issue. My configs was same as you, @Trinytix, but I had uninstalled all of them because lag issues. And now I continue to have same lag issues. When I use the standard cam for five minutes it become freezy and lag and sometimes I lose some photos. All the time it is burning. Just stops to burn when I leave it without work about 30 minutes. I think the problem is the snapdragon 810 but in other foruns some say that the problems with this processor was fixed.
I've been having similar issues, I got really into theming (using nova prime) the last couple of months and at the end of January the phone started to really lag hard. A couple weeks ago I stopped being able to open any apps other than the phone and google's messenger. I tried to factory reset from settings and could not (device gets stuck un the power down sequence), so I went the recovery mode route. reinstalled a fraction of my apps, put back a much stripped down version of my theme, and things were mostly ok, if a little laggy. However, the phone insisted that there was no SD card (internal or external) despite there being a 64GB card, which would sometimes show up when viewed in settings, some apps (podcast addict) were able to access the internal memory, but others couldn't (cameras, sms, photos, music). Yesterday the keyboard ceased to launch for more than a split second at a time, and would not take any input (you would not believe how infuriating this is unless you've experienced it first hand). In an attempt to regain some functionality I started uninstalling everything that I don't consider vitally important (bus app, podcasts, messenger) couldn't get through more than 1 or 2 at a time because multiple windows would stack telling me processes like "motorola" "android" and "media" had stopped. I did succeed in stripping away all the automation apps and theming apps (tasker, nova, icon packs, etc). I can't even place a phone call on the first try.
Oh and to add insult to injury I have to darned green lines about 0.5cm wide now.
Looks like hw problem or system got corrupted. Try to re-flash whole system but if is hw...
Hello i just bought this amazing phone after coming from Note 5 with android 6.0.1, and it really bugs me that all the bugs i had in 6.0.1 are still there.
The first one is wierd performance in some 3D games, mainly talking about angry birds 2 that slows down after playing for a bit, same happens on Note 5 on 6.0.1 but NOT in lollipop.
Audio cuts in half when playing games, it seems like a new gameservice feature, so far to combat it and the weird color change when launching a game, is to disable the gameservice via package disable pro.
Some animations are not smooth and either too fast or too slow.
What bugs did u encounter?
The Play Store is super slow when I'm on wifi, but every other app functions just fine... it's driving me nuts because I can't download my apps or update anything without burning through my data.
rodnii said:
The Play Store is super slow when I'm on wifi, but every other app functions just fine... it's driving me nuts because I can't download my apps or update anything without burning through my data.
Click to expand...
Click to collapse
every Android phone have slow Play store since it`s not using cache.
I had 2 issues (well 3) but not sure its Android 6 or Samsung Phone issues:
a) I had to try 3 different microSD cards till one worked - they keep showing up as corrupted (even tho they work ok in other devices) i noticed the bigger the SD storage is the worse it performs (had to use a 16GB as the 64GB Samsung card didnt work - the phone would see it but wont let me create or move any files on it
b) probably a result of the a) issue - as my camera had settings to save pix on the SD card - my camera stopped working - everytime i opened it it would say: failed to open
tried everything but only a factory reset fix it
c) the phone got frozen on the weather page and literally nothing was working - no back buttons, up/down buttons, power off - nothing - it stayed like that 15 min until i performed a battery removal simulation (hold volume down and power button for 20 sec)
Other than that ALL ok - screen is weirdly sensitive - sometimes i touch an app and it acts like long touch?!!
A bit scared of these hiccups
I reported to USA support all those issues, as mine local support stinks bad. it seems that camera app is the major complain and have issues with that, a fix probably will be soon and hopefully will eliminate over processing with HDR.
Now i hope they will release fixes asap for all other issues as well.
tim2london said:
I had 2 issues (well 3) but not sure its Android 6 or Samsung Phone issues:
a) I had to try 3 different microSD cards till one worked - they keep showing up as corrupted (even tho they work ok in other devices) i noticed the bigger the SD storage is the worse it performs (had to use a 16GB as the 64GB Samsung card didnt work - the phone would see it but wont let me create or move any files on it
b) probably a result of the a) issue - as my camera had settings to save pix on the SD card - my camera stopped working - everytime i opened it it would say: failed to open
tried everything but only a factory reset fix it
c) the phone got frozen on the weather page and literally nothing was working - no back buttons, up/down buttons, power off - nothing - it stayed like that 15 min until i performed a battery removal simulation (hold volume down and power button for 20 sec)
Other than that ALL ok - screen is weirdly sensitive - sometimes i touch an app and it acts like long touch?!!
A bit scared of these hiccups
Click to expand...
Click to collapse
Are you sure you don't just have a bad phone? Using multiple cards and having issues with all of them seems like there might be a hardware issue with the card reader.
johanbiff said:
every Android phone have slow Play store since it`s not using cache.
Click to expand...
Click to collapse
How am I supposed to fix this? I can't set up my phone unless I can use the play store... It's not just the loading information, but also the downloading. I haven't been able to successfully update any Google Apps yet, and I left my phone running overnight
rodnii said:
How am I supposed to fix this? I can't set up my phone unless I can use the play store... It's not just the loading information, but also the downloading. I haven't been able to successfully update any Google Apps yet, and I left my phone running overnight
Click to expand...
Click to collapse
you can`t. every phone has it..it`s up tho play store to fix it.
edit* you could be having some serious WIFI problems, try to restart/reset your router
tim2london said:
I had 2 issues (well 3) but not sure its Android 6 or Samsung Phone issues:
a) I had to try 3 different microSD cards till one worked - they keep showing up as corrupted (even tho they work ok in other devices) i noticed the bigger the SD storage is the worse it performs (had to use a 16GB as the 64GB Samsung card didnt work - the phone would see it but wont let me create or move any files on it
b) probably a result of the a) issue - as my camera had settings to save pix on the SD card - my camera stopped working - everytime i opened it it would say: failed to open
tried everything but only a factory reset fix it
c) the phone got frozen on the weather page and literally nothing was working - no back buttons, up/down buttons, power off - nothing - it stayed like that 15 min until i performed a battery removal simulation (hold volume down and power button for 20 sec)
Other than that ALL ok - screen is weirdly sensitive - sometimes i touch an app and it acts like long touch?!!
A bit scared of these hiccups
Click to expand...
Click to collapse
No problem here with my 64gb sandisk microsd. Which speed class do the cards have and additionally which formatting?
But as already said, it may be that the card reader of your device is simply faulty.
rodnii said:
How am I supposed to fix this? I can't set up my phone unless I can use the play store... It's not just the loading information, but also the downloading. I haven't been able to successfully update any Google Apps yet, and I left my phone running overnight
Click to expand...
Click to collapse
No problem with the play store here :/ Have you maybe tried to clear the data of google play services and play store and checked if it's still there?
Tectas said:
No problem here with my 64gb sandisk microsd. Which speed class do the cards have and additionally which formatting?
But as already said, it may be that the card reader of your device is simply faulty.
No problem with the play store here :/ Have you maybe tried to clear the data of google play services and play store and checked if it's still there?
Click to expand...
Click to collapse
I've done everything
Cleared caches/data, cleared caches from recovery, factory reset, tested the router, everything.
The WiFi works fine when I browse the Internet or download from Galaxy Apps store.
I've solved the issue to my wifi problem after fiddling around. Turns out my router was relying on the DHCP server to assign IPv6 addresses and there was some sort of issue with that, so I switched it to auto-configuration and now the Play Store works again
Same here
rodnii said:
The Play Store is super slow when I'm on wifi, but every other app functions just fine... it's driving me nuts because I can't download my apps or update anything without burning through my data.
Click to expand...
Click to collapse
Ive got a Verizon S7 Edge, and its the same way for me too.....
StevesDesigns said:
Ive got a Verizon S7 Edge, and its the same way for me too.....
Click to expand...
Click to collapse
You should check your router settings and make sure it's assigning IPv6 addresses automatically. That was the cause of my issue. It occurred to me after I connected to my university's wifi with no problems.
Sent from my SM-G935T using Tapatalk