[Q] Issues with Quiet Hours and Less Frequent Notification Sounds on Beanstalk - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I've been running Beanstalk's roms over the past week or so (both 4.2.2. and 4.3) and I've noticed that the Quiet Hours and Less Frequent Notification Sounds options don't really function even when I have them enabled.
For quiet hours, I have checked the box that says 'mute notifications' but I still get them during the enabled time period.
For less frequent notifications, it just doesn't work - regardless of what time gap I select, I still get repeated notification sounds without any silence gap. I've tested this across multiple apps (kik, whatsapp, hangouts).
Both my rom installs were clean (full wipe, reset etc). Any suggestions on why this may be happening? This rom is CM-based - perhaps folks using CM have experienced this?

Bump...?
Sent from my SGH-I337 using Tapatalk 4

Related

[Q] How many Crashes/Hangs per day (Avg Est.)

I'm having many many days with this tablet that are frustrating.... Today for instance, I have had 2 re-boots and 3 hangs!!! My Xoom on a custom JB ROM didn't have these issues....!!!
I can't recall for sure, but I think I had maybe 2 total random reboots, and no app FC's (on stock ROM). I use CM 10.1's nightlies now and haven't had any crashes or hangs.
espionage724 said:
I can't recall for sure, but I think I had maybe 2 total random reboots, and no app FC's (on stock ROM). I use CM 10.1's nightlies now and haven't had any crashes or hangs.
Click to expand...
Click to collapse
is everything functional on cm10?
to the op, I have had the n10 hang while in chrome. when that happens, I have to reboot by holding down the power button until it kills power and reboots. on average probably once a few days. I am not a heavy user though. have tried dolphin browser and it too crashes although can't remember if it will hang the entire device.
Ever since I updated from stock, it runs hot and now getting reboots.
Never had an issues once and ran cool on stock rom.
Mines rebooted maybe 2 or 3 times total. Been using it about 4 hours every day for the past month. Hasn't been anything anywhere near what I'd call an issue. Running stock.
On a good day 1. On a bad day 4.
I turned off location services and stopped using chrome and have only had 1 random reboot in the last 2 weeks. Hopefully google fixes something soon.
None.
If I use chrome, its very likely that mine will crash. Using other browsers makes it less frequent. Hopefully they fix it asap.
I use my tablet for around 2-3 hours on work days and around 6 hours on days off. Today is a day off, and I've already had to force reboot it 3 times... I'm close to asking for a replacement, but I'm also going to try a few things before I do. There is no doubt about it. It should just work and it isn't. But before I send it back I will wipe and start over ( I am not doing any thing special with this device either. Everything is stock)
Most of the system hang's I get are almost always in Chrome. Sometimes Facebook or Twitter, and then when I have to force the reboot (pwr + vol up + vol down) it almost always reboots into installing a new app update... Which makes me wonder if that is the issue. I have disabled auto updating of apps, and have already had the same issue so I'm not convinced it was that after all.
So I guess I can either assume that my hardware is good and this is a software issue which I can wait for Google/Samsung to address or cut my losses and try and get a replacement device before X-mas... Right now the poll shows that more people are having a good experience than bad....
Thanks for the responses guys/gals..
Several a day with location services off.
It may hang up about 1 time per day. happened when portrate, almost.
I had a few at first i think it was due to the chrome browser on 4.2.1 but did a FDR and seems to be smooth now..
Also used the toolkit to root and works like a charm now
Haven't had any in CM10.1 but I had 1-2 a day with stock
Same here running aokp with ktoonz kernel. It's been more than a week without freeze/reboots. I don't game either tho & do use Ocean.
Sent from my Nexus 7 using Tapatalk 2
Depends on use. With heavy use every 3-4 hours? Its only rebooted once overnight. Mine seems more prone to do it while installing apps if I try to do something else while installing....although it will just as readily hang browsing with chrome. I was thinking of RMA but read some horror stories on that
Oh yea, Stock
Sent from my Nexus 4 using Tapatalk 2
dalingrin said:
Haven't had any in CM10.1 but I had 1-2 a day with stock
Click to expand...
Click to collapse
This. CM10.1 FTW. :good:
I was getting somewhere around 1-3 per day on stock. I've given up waiting for Google to fix it, so am now on cyanogenmod nightlies, and have not had one single freeze or reboot since. This tablet is now perfect.
Oops just had one more
Sent from my Nexus 10 using Tapatalk HD
My experience is virtually the same as Pihrana. I am under the impression that the hangs and reboots are a software problem that is likely caused by my particular usage patterns or an app or setting (I have location settings disabled and it still hangs). Either way I have decided not to exchange it, as the problem will very likely be addressed in a future patch, and I might end up with a device with hardware problems (light bleed, etc) in addition to the existing software issues.

[Q] Note 3 - Alarm / Music issues?

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

What are your impressions of 5.1?

It took my a while, but thanks to Wugfresh I was finally able to instal 5.1 on my N6. Curious to know what the general consensus is. I've only had it up and running for 6 hours, but has anyone noticed improvement in battery life or memory management?
Thanks.
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
AstroDigital said:
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
Click to expand...
Click to collapse
Franco's kernel has given my battery some extra life, I hope this update does the same.
I have yet to get the two bugs that were really getting on my nerves previously in 5.0 and 5.0.1
1- Random restarts. They could happen at any time, but it seemed like they would happen when I was trying to text. I'd try to keep closing my text messenger application (happened with both Google Messenger and Hangouts), but it didn't always help. I'd send a text message, put my phone down and then a few seconds later, notice the Google logo because it was restarting.
2- Sometimes when the screen powers up, all I see on my lock screen is a blank black background, the on-screen back button and the usual clock and what not at the top of the phone. Otherwise, the screen itself is black and I'm basically locked out of my phone until I restarted it. If I was lucky and I was using my Bluetooth headset, if I received a phone call, that would sometimes get the phone to snap out of it and allow me to answer the phone call and then when the call was done I'd get the normal lock screen again.
So far so good with 5.1 *knocks on wood*
I just flash it this morning and I feel like im still on 5.0.1. I only use 1 wifi connection and 1 bluetooth connection, so a drop down menu doesn't really effect my daily usage since I don't switch them. Whatever they did behind the hood to improve performance/battery will be nice, but haven't had it installed long enough yet to notice anything different really.
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
5.1 is what Lollipop should have been from launch. It's equivalent to Windows 7 replacing Vista. It's that much better.
Sideloaded with adb on my stock att N6. Seems real quick so far. Don't notice any additional drain on battery.
So far it seems about the same as before to me. However, I am on Sprint and the new radio that prevents duplicate texts is awesome so that part of it makes it seem like a new device.
I play Hearthstone, Kingdom Rush and Clash of Clans on My nexus 6 and they all run fine so far.
I did un-encrypt like before. I cannot comment on battery life yet since it hasn't even been 24 hours for me since I updated.
So far so good. Battery life has certainly improved, it was pretty abysmal for me before. I only experienced one bug that I know of on 5.0.1 where occasionally my status bar and nav bar would disappear and the phone was in a partially locked state. Trying to slide down the notification drawer would show the lockscreen. Hopefully that's fixed.
is double tap to wake.. enable in 5.1??
I'm not on a N6 yet, but my GNex is on 5.1, and to compare (because I've only got 1Gb of RAM here, it's a good test because the margins are so small compared to having 3Gb) the 5.1 update is by far the most stable yet for my device. 5.0 was baaad, but consider how many commits corrected memory leaks and you can tell this is the one. I'm looking forward to getting my N6 with 5.1 on it.
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
I am noticing a huge performance improvement from 5.0.1 already. Battery life is also better. I am not having the dialer issue like some, but have seen 3 instances of people saying the same thing.
Was on stock, now on Vanillipop 1.6 with Franco Kernel r20.
Much smoother and the battery seems improved. Still testing out.
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
got a tempered glass protector on it?
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do you use a screen protector that covers the sensor? I know there is a thread somewhere around here with a lot of people that have that issue and it's because of their screen protector in 5.1 for some reason.
jakebites said:
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
Click to expand...
Click to collapse
Greatly, its butter all the time.
I haven't noticed a whole lot yet, some games seem to be playing a lot better, the graphical glitch I was seeing on xcom seems to have disappeared so its actually playable now
I've been experiencing an increase in fluidness (is that a word) throughout the UI as a whole, the phone moves from task to task without any stutter and the animations seem to have a bit more polish to them. Checking on the battery now, but I was never a power user to begin with. Overall it may not look like much but you can tell there are some big time enhancements coming from 5.0.1

Official 5.1 Feedback [Moto G 4G]

Hi guys,
Now that some 5.1 ROMs have started to roll out in a few countries, could anyone who has tried it give us a little detailed review of lollipop?
I'm especially interested in the following points (in comparison to KitKat):
-Memory management
-Battery life
-Any bugs (real bugs, not things you just don't like)
Just a reminder: I'm asking for info on official android 5.1, NOT 5.0.X
Cheers to anyone for taking part! :beer::beer::beer:
Sent from my XT1039 using XDA Free mobile app
Anyone?
C'mon guys, a few European countries have rolled out now, I'm sure someone could give us a review
Sent from my XT1039 using XDA Free mobile app
I updated mine last night from 4.4.4-5.1
Don't know what I can say to be honest though it's nice and smooth so far
steve.loveday said:
I updated mine last night from 4.4.4-5.1
Don't know what I can say to be honest though it's nice and smooth so far
Click to expand...
Click to collapse
Cheers :beer: If you notice anything worth mentioning please let us know
Sent from my XT1039 using XDA Free mobile app
I don't have a 4G but I'd be interested if anyone with battery drain AFTER using GPS still has it after the update, or is it fixed...
Hi, i updated it yesterday and my mobile is a lot more smooth!
With KitKat I was having huge memory problems, I couldn't use Spotify and chrome at the same time cause the music on the background was killed and the launcher redrawn. But now I can open apps with music on the background, multitask changing between apps without a redraw. It seems like it's fixed, I hope it doesn't get bad with time.
Battery seems better but can't say nothing that soon.
Also I've noticed something: there is no quicksettings bar widget (at least I can't find it) and screen cast included in 5.1 doesn't work, it says no device found, and doesn't let you add or search for devices.
Update was a little bit over 400 mb big. It took a while to download. The device didn't get warm during the update procedure. Pulling down notification bar twice shows the toggles (brightness slider, screencast and flash light included). Settings got a separate icon. There's a guest mode. If you touch the battery symbol, you'll be directed directly to the according settings menu. Virtual buttons and icon of the messages app changed also. Background color of the settings and notifications is white. You can delete all of the notifications at once. The notifications are prominently shown on the lock screen. Multitasking got a new look either (Material design).
how to root 5.1?
I've found it's still possible to crash Google Play Music or Poweramp from within Chrome. Do too much and one's music stops. I had the same issue on KitKat - normal apps are generally okay but things that are slightly heavier on the CPU make the sound jump or cut out (the player restarts about a minute later paused). Not too bothered, I just avoid surfing if I'm listening to music. Using Bluetooth audio if that makes a difference.
I had to factory reset initially - update was a bit sluggish (marginal) and battery wasn't great. Encountered a few oddities.
Luckily all my apps reinstalled and none of my data was lost except SMS messages and e-mail account logins (odd); everything else either synced or was on the SD card. Didn't take long; 5 minutes doing the welcome setup, outside that 30 mins either side where I just left the phone to do things.
No other bugs here. Yet. Though the performance isn't on-par with KitKat (I think). It's marginal though; Google Now might not pop up as quickly or the animation might lag if something else is going on. But all in all it's a trade-off for the material design which is oh-so nice.
Thank you very much
Sent from my XT1039 using XDA Free mobile app
Ok, my Moto G is running Lollipop now for 24 h. It does look defintely nice, there is no mistake about it. And it's quite responsive, but the WLAN connection is the opposite of it...
XShocker22
XShocker22 said:
Ok, my Moto G is running Lollipop now for 24 h. It does look defintely nice, there is no mistake about it. And it's quite responsive, but the WLAN connection is the opposite of it...
XShocker22
Click to expand...
Click to collapse
What do you mean?
First time I read about WiFi problems, even on the CM threads... Connectivity drops?
Sent from my XT1039 using XDA Free mobile app
crakeron said:
What do you mean?
First time I read about WiFi problems, even on the CM threads... Connectivity drops?
Sent from my XT1039 using XDA Free mobile app
Click to expand...
Click to collapse
No, I can not check for sure, but the latancy must be abnormously high, because the reaction in Browser and Apps over the Internet is hilarious...
Gesendet von meinem XT1039 mit Tapatalk
Have been running it for roughly 48h... processor has minimum state of 787 MHz (instead of 300 something MHz), and every second reboot Android seems to reset the Dalvik (loading apps at startup). Otherwise pretty impressed. I did a full reset after the installation btw... Here with retail German XT1039 5.1
I've rooted now. I was having issues with the memory filling up. Google App seems to be the worst offender but I use it a lot so I've left it alone.
Installed AdAway, removed Motorola Alert/Assist, some Google Apps and a few other things and unsurprisingly, things have massively sped up. Tempted to remove the random services which are probably orphaned ie. com.motorola.bug2go, com.motorola.emarphoneextns, com.motorola.motgeofencesvc, Invisible Net 1.0, etc. etc. but no idea what they do.
I thought there was no method yet to root Peregrine with 5.1 . Could you tell us how did you do it?
Using this method worked fine for me
http://forum.xda-developers.com/showthread.php?p=56800467
Gesendet von meinem XT1039 mit Tapatalk
Yeah I used the chainfire method, pushed a new logo via adb to get rid of the bootloader unlocked warning.
For some speed you can install AdAway, use Greenify with root and uninstall some system apps. That said it's probably worth steering clear of Xposed and GravityBox since its early days (former is super alpha).
I am eagerly awaiting a way to cleanly strip out all of the Motorola components without leaving any hooks, oddities or references in the Settings Menu or elsewhere. Just for a bit more free RAM. New phone so still enjoying Stock. Tried playing with MyAndroidToolkit(?) to kill wakelocks but didn't know what I was doing so hit the reset button when location services started acting dodgy. Seems 1GB RAM is not enough for me
Do you recommend wiping cache after update?
Thanks!
Hello,
I have had boootloader-unlocked stockrom 4.4.4 and made the ota 5.1 update and i got a message (status 7) while updating and it aborted. Black screen and nothing else. I tried many things - 15 hours long. Phone did not been recognized by PC (unknown device). Now, I tried to charge the phone and it works like nothing happened.
What did i made wrong? Do I have to lock bootloader before updating? How? What is "Status 7"? Is there another method to get lollipop to the phone (with unlocked bootloader)?

Notification shade lag/stutter

I have a pretty minimal bunch of apps installed, and yet when I pull the notification shade down, there is lots of stutter, and seconds-long delay when I try and swipe a notification away. As I use the shade to manage my incoming notifications all day long, this is extremely frustrating on such a new phone.
Anyone else finding this? Any ideas?
Yes me too and it's typical Samsung. Going back to pixel.
I have weird lag on notification and facebook until I take out the accessibility service like enpass autofill. once i have done that, everything runs smoothly.
Same here - I did uninstall a bunch of game and other apps, and since then the problem has gone. Phew. Kinda annoying it's really difficult to pinpoint what app is causing the issue...
alexkaye said:
I have a pretty minimal bunch of apps installed, and yet when I pull the notification shade down, there is lots of stutter, and seconds-long delay when I try and swipe a notification away. As I use the shade to manage my incoming notifications all day long, this is extremely frustrating on such a new phone.
Anyone else finding this? Any ideas?
Click to expand...
Click to collapse
YES! Having the same issue with notification shade and also the multitasking view when flipping through apps. I can't figure out what's causing it. For me changing screen resolution fixes it every time until it starts happening again.
I don't have any accessibility services running so not sure that's it. Anybody have any ideas of culprits? I have quite a few apps installed but not sure what could be causing this issue
Same here.
No lag at all.
I wonder how many people experience these things have rooted or something?
I've not had any issues with my S8 since I've had it.
Very strange.
Everyone has different apps, data and usage. You could give me your phone and I would wipe and use it and it would lag. That's the reality
Same problem and same resolution : switching performance profile via edge pan
I just got an update on Verizon S8 - the red tint fix or whatever but so far this has fixed my stutter problem. I'm hoping it lasts but by now I would have seen stutter and it's still very smooth. Crossing my fingers
Bittersweetly glad to see others are having the same issue. I first noticed it when I upped the screen res from FHD to QWHD, so I switched back and that seemed to help for a few days. But, it did creep back. I performed a factory reset, but I don't think that's a permanent fix, either. Occasional reboots seem to stave it off, too. I would really like to get to the heart of the problem. FWIW, I'm on a Snapdragon S8+ on T-Mobile, unrooted. Outside this hiccup, really enjoying the phone.
anyone noticed that when you swipe up to the app drawer, there is a hint of stutter/lag? Thats the only annoying thing for me at the moment.. Everything else seems to be ok!!
If your phone is rooted and you have a custom kernel running, you can see why this happens. Install kernel auditor and drag down the status bar, you can see that the cpu goes up a bit. If you increase the minimum cpu (both big and little) to 1 value higher than what you saw when you dragged it down before then this should fix the issue however I assume it will affect battery life but not sure to how much, you'll have to do some testing.

Categories

Resources