Related
Hey guys,
Since upgrading to LP 5.1 I've been not that happy really. Some minor bugs, a lot of RAM consumed by the system and, of course, the lack of the wave to wake option.
Now, I have just discovered another "change" (a bit late, I know) in the Active display behavior. When I had KK and I had AD notifications blinking, they will blink forever (even tho, they started to blink with more gap between as time passed)... Now I noticed that AD notifications with LP 5.1 blinks for a limited period of time (don't know which one yet), and then stops doing it, leaving the screen totally black and without knowin I have a notif pending unless I take my phone.
Anyone noticed this change of behavior too ?
34 views and no one could notice this behavior ? I must assume you guys don't stay more than 5/10 minutes without receiving a new notification.
I think it has to do with what version of Android you were running prior to upgrading to LP. I say this because I flashed to an AOSP 5.1.1 ROM and not only is my wave to wake still working, wrist twists launches the camera app. The OS before was 4.4.4 SU4.21. But the ambient display would flash on and off for a long time when I receive a notification, don't know about forever since I would check the notification with the hand wave gesture oh and I get the green LED after a while also.... Perhaps after it gets sick of flashing the AD notification?
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
I think it has to do with what version of Android you were running prior to upgrading to LP. I say this because I flashed to an AOSP 5.1.1 ROM and not only is my wave to wake still working, wrist twists launches the camera app. The OS before was 4.4.4 SU4.21. But the ambient display would flash on and off for a long time when I receive a notification, don't know about forever since I would check the notification with the hand wave gesture oh and I get the green LED after a while also.... Perhaps after it gets sick of flashing the AD notification?
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
You flashed a 5.1.1 LP to your X 2013 ? How did you do that ? The latest (and only) LP for our X is 5.1
Emiliano55 said:
You flashed a 5.1.1 LP to your X 2013 ? How did you do that ? The latest (and only) LP for our X is 5.1
Click to expand...
Click to collapse
I have a XT1060 DE and got sick of waiting for Verizon so I flashed one of the ROMs in the forum. http://forum.xda-developers.com/showthread.php?t=3116436
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
I think it has to do with what version of Android you were running prior to upgrading to LP. I say this because I flashed to an AOSP 5.1.1 ROM and not only is my wave to wake still working, wrist twists launches the camera app. The OS before was 4.4.4 SU4.21. But the ambient display would flash on and off for a long time when I receive a notification, don't know about forever since I would check the notification with the hand wave gesture oh and I get the green LED after a while also.... Perhaps after it gets sick of flashing the AD notification?
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Doesn't have anything to do with what version of Android you were running prior to upgrading. Your wave to wake, wrist twist to launch camera, and ambient display (plus the green LED notification) are part of the AOSP rom you installed. Those features work pretty great on the moto x. But he's on stock, which is quite different (ambient display vs active display)
I've tried AOSP roms and now running a stock 5.1 rom. Active display does behave differently than it did on 4.4.4. The notifications stop flashing after a while and the wave to wake doesn't work. But the wave to wake was actually a bug, not an advertised feature, hence why it was removed.
oeusr said:
Doesn't have anything to do with what version of Android you were running prior to upgrading. Your wave to wake, wrist twist to launch camera, and ambient display (plus the green LED notification) are part of the AOSP rom you installed. Those features work pretty great on the moto x. But he's on stock, which is quite different (ambient display vs active display)
I've tried AOSP roms and now running a stock 5.1 rom. Active display does behave differently than it did on 4.4.4. The notifications stop flashing after a while and the wave to wake doesn't work. But the wave to wake was actually a bug, not an advertised feature, hence why it was removed.
Click to expand...
Click to collapse
Understood, however, I was wondering why so many people are having issues with 5.1 and I'm not. So I went outside the box and came up with that theory.
Since you are on stock 5.1, have you tried installing Moto app? https://m.reddit.com/r/MotoX/comments/3anh0n/2013_so_i_figured_out_how_to_get_the_chop_chop/ You'll get hand wave as well as the new chop gesture for flashlight.
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
Understood, however, I was wondering why so many people are having issues with 5.1 and I'm not. So I went outside the box and came up with that theory.
Since you are on stock 5.1, have you tried installing Moto app? https://m.reddit.com/r/MotoX/comments/3anh0n/2013_so_i_figured_out_how_to_get_the_chop_chop/ You'll get hand wave as well as the new chop gesture for flashlight.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
I have that feature already in the stock rom I use (the only stock 5.1 in the development forum) and it works really well!
Sent from my XT1053 using XDA Free mobile app
oeusr said:
Doesn't have anything to do with what version of Android you were running prior to upgrading. Your wave to wake, wrist twist to launch camera, and ambient display (plus the green LED notification) are part of the AOSP rom you installed. Those features work pretty great on the moto x. But he's on stock, which is quite different (ambient display vs active display)
I've tried AOSP roms and now running a stock 5.1 rom. Active display does behave differently than it did on 4.4.4. The notifications stop flashing after a while and the wave to wake doesn't work. But the wave to wake was actually a bug, not an advertised feature, hence why it was removed.
Click to expand...
Click to collapse
I'm glad someone finally answer my question. So I'm not the only one that noticed this about AD notifications. On 4.4 they blinked forever, now they blink for a short period of time (unless, of course, you get ANOTHER notification and the timer will reset).
It's a shame how Active display behavior has suffered with the Lolli update. First the wave to wake, now this. I'm surprised so few people noticed this also, maybe people get notifications every time, lol
Emiliano55 said:
I'm glad someone finally answer my question. So I'm not the only one that noticed this about AD notifications. On 4.4 they blinked forever, now they blink for a short period of time (unless, of course, you get ANOTHER notification and the timer will reset).
It's a shame how Active display behavior has suffered with the Lolli update. First the wave to wake, now this. I'm surprised so few people noticed this also, maybe people get notifications every time, lol
Click to expand...
Click to collapse
Did you consider that most ppl don't rely on AD and just pick up their phones, unlock them and see all their notifications?
Just imagine
liveroy said:
Did you consider that most ppl don't rely on AD and just pick up their phones, unlock them and see all their notifications?
Just imagine
Click to expand...
Click to collapse
Yeah, I tend to think people really rely on AD, and they use it. Truth is people doesn't notice this features, they just grab their phones and use it, without noticing a lot of things/features/bugs.
Emiliano55 said:
Yeah, I tend to think people really rely on AD, and they use it. Truth is people doesn't notice this features, they just grab their phones and use it, without noticing a lot of things/features/bugs.
Click to expand...
Click to collapse
Yep, exactly.By the way I also didnt notice that bug or if its feature (dunno).Just didn't have notifications that I didn't see for long enough I guess
Hey guys, so I've had a bit of an weird issue recently, it started up randomly, I hadn't installed any new apps or anything.
I had rooted my phone and gotten TWRP stuck on it so used Wugfresh to flash it out. During this I fully reset the phone to the stock ROM. Even after this I had this issue. Check attached files for an example of what it looked like.
I thought, maybe it was an app that I had installed previously? So I booted to safe mode and waited a while, and sure enough, the issue persisted.
Today, the Stock 6.0 ROMs were released. So I thought, might as well flash it, my device is being RMA'd for another issue (top speaker loudly crackling when audio isn't being played). So I flashed the 6.0 Stock and left it lying on my laptop for a few minutes as I chatted with a friend on facebook. And sure enough, what's floating there at the bottom of the screen? An empty toast notification.
This is a completely fresh flash. This was on the first screen before I'd logged in or set it to restore my apps or anything. This is the screen where you hit the arrow before adding Wi-Fi and such.
What could this be?
TL;DR: I have constant toast notifications and they're there regardless of safe mode or clean flash. They even exist between major updates (5.1.1 > 6.0)
I have the same issue on my stock ubrooted nexus 5 running 5.1.1
It's driving me crazy! My nexus 6p can't come in the mail any faster!
Egkphoto said:
I have the same issue on my stock ubrooted nexus 5 running 5.1.1
It's driving me crazy! My nexus 6p can't come in the mail any faster!
Click to expand...
Click to collapse
I've sent in an RMA for my Nexus 6, hopefully I get it replaced. I'm going to use my brother's old iPhone in the meantime while I wait for a response from them, and then leave my replacement unopened and resell it on kijiji. I can't trust my N6 to last when after only around 8 months it's crapping out like this.
Having the same issues on my Nexus 5. Anybody found out?
UPDATE: I installed an Xposed module called Enhanced Toasts, it logs all the toast shown in the device. In my case the Sim Toolkit app showed these blank toasts, i recently changed my SIM.
This issue of incoming call screen not opening just started a few days ago. I get a ringtone and vibration, but whatever screen I happen to be on stays the same. As a workaround, I enabled a notification in the notification shade from which I can answer or decline. I've tried every possible fix I can think of, even doing a factory reset as a last resort, but the problem persists. Neither Motorola nor Google has a clue. Any help would be greatly appreciated!
I should note that I am running stock Android 7.0.
i installed gapps and it worked for me(but with twrp - unclocked bootloader)
Bsherb said:
This issue of incoming call screen not opening just started a few days ago. I get a ringtone and vibration, but whatever screen I happen to be on stays the same. As a workaround, I enabled a notification in the notification shade from which I can answer or decline. I've tried every possible fix I can think of, even doing a factory reset as a last resort, but the problem persists. Neither Motorola nor Google has a clue. Any help would be greatly appreciated!
I should note that I am running stock Android 7.0.
Click to expand...
Click to collapse
I haven't ran 7.x for about six months so I don't remember if this is an option but try going to Settings --> Apps --> Phone and see if Phone is set as the Phone app. Also,is there a reason why you haven't updated to 7.1.1? There were a lot of bug fixes and improvements from 7.0 to 7.1.1.
This topic is obsolete (for me anyway) since I have a new phone. But to answer your question about version number, official support for the Nexus 6 ended shortly after Nougat arrived. Thanks!
Google updated the N6 to 7.1.1 before ending support [emoji39]
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Hi, today I was asked for MIUI update, which I updated, and regretted for that after.
My WhatsApp notifications gone wrong: sound doesn't work (I checked everything many times),and also floating notifications (which I hate and always turn them off) started annoying me. They are off on settings.
Does anyone have this issue after today's update?
Was shocked to see the notification this morning, jumped in with the update before leaving for work and seems fine so far. Navigation Bar customization lost for now, Nav Star under Good Lock says they're working on an update so hopefully that takes care of things. Haven't had much time to explore yet but initially phone is much snappier, even after considering it restarts automatically once a week.
JLFitzpatrick said:
Was shocked to see the notification this morning, jumped in with the update before leaving for work and seems fine so far. Navigation Bar customization lost for now, Nav Star under Good Lock says they're working on an update so hopefully that takes care of things. Haven't had much time to explore yet but initially phone is much snappier, even after considering it restarts automatically once a week.
Click to expand...
Click to collapse
What version software were you on before?
Good question, don't really see an update Log. Last update was November so I assume it was SJ1. Updates have been running around 45 to 60 days on this phone.
I will say, and unfortunately not sure this option was around on Pie, but looked up Android 10 tips and enabled Adaptive Power Saving under Device Care / Battery / Power Mode and at least for the first day it seems battery draw has improved. Time will tell.
JLFitzpatrick said:
I will say, and unfortunately not sure this option was around on Pie, but looked up Android 10 tips and enabled Adaptive Power Saving under Device Care / Battery / Power Mode and at least for the first day it seems battery draw has improved. Time will tell.
Click to expand...
Click to collapse
Can you pull the update zip and post it?
JLFitzpatrick said:
Was shocked to see the notification this morning, jumped in with the update before leaving for work and seems fine so far. Navigation Bar customization lost for now, Nav Star under Good Lock says they're working on an update so hopefully that takes care of things. Haven't had much time to explore yet but initially phone is much snappier, even after considering it restarts automatically once a week.
Click to expand...
Click to collapse
Were you on a US or EU firmware?
Should be on US Firmware. Not sure what you mean by update ZIP, but see attached.
JLFitzpatrick said:
Should be on US Firmware. Not sure what you mean by update ZIP, but see attached.
Click to expand...
Click to collapse
You're using an N960U1 or an N960U but it has Unlocked US firmware on it, which just makes it an N960U1. Did you register for the beta on the Samsung Members app? Or can you tell us what your previous firmware was before you got Android 10?
Jammol said:
You're using an N960U1 or an N960U but it has Unlocked US firmware on it, which just makes it an N960U1. Did you register for the beta on the Samsung Members app? Or can you tell us what your previous firmware was before you got Android 10?
Click to expand...
Click to collapse
I see in all these post about the beta, you seem to never get a straight answer for that :fingers-crossed: maybe someone will actually respond instead of just asking questions
Dr.Lost said:
I see in all these post about the beta, you seem to never get a straight answer for that :fingers-crossed: maybe someone will actually respond instead of just asking questions
Click to expand...
Click to collapse
Yeah it's kind of.....odd.??* I don't even want the beta. I just want to know what the banking schemes are for the firmware itself. It'll give us a hint IF Samsung is leaving towards a bootloader update. Which will help tell us they fixed something nasty from the current bootloader. ?
I think I did register for the Beta so that makes sense, went to the Members Center looking for something else and tapped the icon for it, never got confirmation of anything though. The upgrade notification didn't state it was Beta either. Based on dates per Samsung Phone was probably on SJ1 Pie prior to this. I assumed this was the December 1 patch when it first popped up.
Notification popped up today when opening Settings that this is the Beta, a fact not communicated by Samsung during the update. Went into Settings upon noticing the Phone which was good all weekend today at work without using it started getting hot and draining the battery. Shut it down wiped partition cache a during startup then went into Battery / App Usage and found Camera, which had not been open since last night had used 62.7% of Battery over the past 6:43 hours. Toggled on 'Put App to sleep when not in use' for Camera App and will keep an eye on this along with everything else. All other App Usage seems to be normal. Charging phone now and it has cooled down.
Realize this was the Google Camera acting up that was installed from a link on this forum and mapped to activate by double tapping the Bixby button through BxActions (Samsung Camera activates by double tapping Power Button). Explains why it was acting up after the update. I like the G-Cam night mode and have been comparing the results to the S-Cam night mode including a few shots of Christmas decorations last night.
Updated this Thread Title to reflect what this upgrade actually is. Very happy with this upgrade so far, even though it wasn't labeled as the Beta version in the notification when it first popped up. Only real glitch I've noticed besides the G-Cam battery drain episode which is no fault of Samsung being a sideloaded App, is the settings security page. Phone is setup to require security log on when Settings is opened, currently the security pattern screen flashes then goes to Settings menu without requiring login fingerprint or pattern. Lost Navigation Bar customization I assume will be recovered when NavStar is updated, there is a notification in LockStar that let's you know they're working on an update.
Received another Beta update today.
Another Beta is pending, brings Security Patch up to January 1st, will install tonight.