So I got this update today and of course the "learn more" link just pointed to the 4BQA2 update, which was just the first Nougat release, which I already had.
Anyone know anything about this one? It still says Android version 7.0, and the security patch level is 2/1/17. The kernel is 3.18.31 and is dated March 13th. The full build number is NRD90M.G930VVRU4BQA4
doncaruana said:
So I got this update today and of course the "learn more" link just pointed to the 4BQA2 update, which was just the first Nougat release, which I already had.
Anyone know anything about this one? It still says Android version 7.0, and the security patch level is 2/1/17. The kernel is 3.18.31 and is dated March 13th.
Click to expand...
Click to collapse
I just got it also, claims to improve wifi. My wife and I were just discussing that the GPS has been a bit laggy lately, maybe this will help that, too.
Yep just Wi-Fi fixes. Nothing to improve battery. Fail. still 7.0.0
Sent from my SM-G935V using Tapatalk
Checked SamMobile & Update.com & still no download link. Anyone know when or if they've released one yet?
Got it the other day as well
So far, no issues with the latest update. Still wish they'd fix the "switch keyboards" issue. Really annoying to go into the manage keyboards section and turn off all the other keyboards and leave the one on that you want to switch to. Otherwise, really happy with this. I got 20 hours on one charge and had about 27% left in battery. This was after playing games, reading email, reading news, surfing the web, texting and phone calls. I do have it on the mid-power saving mode, and I use the App Power Monitor that currently has about 89 apps flagged to be put to sleep when they're in the background. That really helps and is a built-in Greenify in Nougat. Really nice.
I wrote in another thread.
Can someone help? I just got the update to QA4,decided to go thru with the verizon wireless assistance programme via usb cable,now phone stuck on verizon screen bootloop. Any suggestions to save the day?
Update : safe mode doesnt boot up,either.
Can anyone confirm if this update fixes the Samsung calendar app from keeping the screen on when a reminder or calendar event pops up while the screen is off? This was introduced for me with the original nougat update.
cowman4000 said:
Can anyone confirm if this update fixes the Samsung calendar app from keeping the screen on when a reminder or calendar event pops up while the screen is off? This was introduced for me with the original nougat update.
Click to expand...
Click to collapse
Is the behavior you see?
Set screen timeout for 15 seconds. Set up a meeting in google calendar with starting in 7 minutes and reminder 5 minutes before meeting. Then wait for reminder on lock screen to pop up, don't touch anything and let screen timeout. See if screen will get activated again and go off after 2nd screen timeout.
If you get the same behavior, please report. I think there is something wrong with this as if you had a meeting reminder and the phone in you pocket, the phone battery will drain fast and phone gets hot of course.
Thanks
The behavior you described is similar except that the screen turns on for the initial reminder, then it times out and comes on again, times out and then turns on again and this is an endless cycle until I dismiss the reminder. I thought factory reset would fix it... But nope.
cowman4000 said:
The behavior you described is similar except that the screen turns on for the initial reminder, then it times out and comes on again, times out and then turns on again and this is an endless cycle until I dismiss the reminder. I thought factory reset would fix it... But nope.
Click to expand...
Click to collapse
That is exactly what I get. Is there a ticket opened with Samsung?
This seems to be the issue with Samsung pay https://forums.androidcentral.com/s...ar-notifications-keep-screen-post-nougat.html
What does BQC5 do? Has anybody recently received this update?
Tech180 said:
What does BQC5 do? Has anybody recently received this update?
Click to expand...
Click to collapse
Was it really that difficult to look just a few threads below this one to get your answer?
https://forum.xda-developers.com/verizon-galaxy-s7/how-to/security-bulletin-ota-update-s7-t3600060
Oh Woops! Thanks!
Related
Happy New Year everyone!
I'm a complete noob to root/flashing my samsung captivate glide so please forgive me if these questions seems stupid. I searched on google and in this forum but can't seem to find answers.
I just recently rooted + flash to CM10.1 (android 4.2.1 beta) on my phone and I have been playing around with the software for the past 2 days. I'm pretty happy with it so far; patiently waiting for some fixes like Bluetooth and keyboard back light (like everyone else). I would also like to take this opportunity to say thanks to everyone involved in these kinds of projects. You guys fill the need left in the gap between the manufacturers and the service providers that decide that our phones are obsolete and shouldn't get updates even if the phone can actually benefit from said update.
Today I just tried something: I pushed the power button and on the screen there was a menu to reboot or shutdown: I selected reboot, and then had other choices on screen, and I selected "download" thinking it would go into update mode?... so the device rebooted into download mode and I see the green android logo with the words "Downloading..." in white and "Do not turn off target!!" in green. It's been like that for 30 minutes now and I was just wondering if it truly is downloading something and/or if I can just pull the battery out right now to turn the phone back on normally. If it really is downloading, I find it funny that it's taking so long since I have a 20 MB connection speed...
The reason I went into download mode is because I saw the options inside android 4.2.1 to update CM10.1 automatically (I chose "nightlies" and "check twice a day"...) and I have yet to see any updates being done. Will there be a pop-up of some kind if there are any nightlies available for download? Will I have to go into download mode to apply the updates? Do they auto-download when the phone is on and they update at next reboot? Please explain the update process...
Also. I don't know if this is a problem or not, but I noticed in JB that my battery seems to drain faster than with GB installed... nothing drastic, but noticeable. For example, if I turn everything off except cell antenna overnight, 10 hours later I have 10% less battery. It used to be around 5% less battery. Can anyone confirm that JB uses more battery than other android versions?
Thanks for taking the time to answer all my questions, I appreciate it and hopefully it will answer other noob questions in the future.
Download mode is used for downloading an operating system via Odin and USB connection. Rather curious how you would not have used that to get to where you are now, unless you obtained your phone with a CWM recovery already on it?
As for battery life, in my time lurking here, I haven't seen many posts about it, but can weigh in with my thoughts. I noticed a significant power drain when I had enabled Google Now. Once I had turned it off, my battery life improved drastically. Still does seem to drain a bit more than stock, but I suspect that is due to optimizations that need to happen for our devices and/or bugs in cm10 itself, as I have seen some things suggesting issues with the screen auto brightness in someone's ROM notes...
Hope this helps and welcome to the world of Android modding!
Artemis-kun said:
Download mode is used for downloading an operating system via Odin and USB connection. Rather curious how you would not have used that to get to where you are now, unless you obtained your phone with a CWM recovery already on it?
As for battery life, in my time lurking here, I haven't seen many posts about it, but can weigh in with my thoughts. I noticed a significant power drain when I had enabled Google Now. Once I had turned it off, my battery life improved drastically. Still does seem to drain a bit more than stock, but I suspect that is due to optimizations that need to happen for our devices and/or bugs in cm10 itself, as I have seen some things suggesting issues with the screen auto brightness in someone's ROM notes...
Hope this helps and welcome to the world of Android modding!
Click to expand...
Click to collapse
Thanks for your quick reply,
Yes I used the Download mode with odin to root my device, but I wasn't sure why it was written "Downloading...." like it was actually downloading something (like a CM10.1 update or something). Anyway, thanks for confirming that this is the same download mode as for odin.
Do you know how the CM10.1 updates work? will it post a message on the phone when an update is available?
I am already using auto-brightness so that's not the issue and all other antennas are off, except for cellphone antenna to receive calls.
anyway, it's not a big problem for now, there are still tweaks and updates to come so we will see how battery use develops in the coming weeks/months.
Thanks for your answers.
bombermanCC said:
Thanks for your quick reply,
Yes I used the Download mode with odin to root my device, but I wasn't sure why it was written "Downloading...." like it was actually downloading something (like a CM10.1 update or something). Anyway, thanks for confirming that this is the same download mode as for odin.
Do you know how the CM10.1 updates work? will it post a message on the phone when an update is available?
I am already using auto-brightness so that's not the issue and all other antennas are off, except for cellphone antenna to receive calls.
anyway, it's not a big problem for now, there are still tweaks and updates to come so we will see how battery use develops in the coming weeks/months.
Thanks for your answers.
Click to expand...
Click to collapse
Purely guessing, but seeing as how the OTA updates work from carriers, you get notified in the notification bar and downloads the ROM while the phone is still up and running, I would assume CM would work the same way. But, I don't think it's actually enabled as of yet, since the ROM is still in development. Feel free to anyone to correct me on this, but I feel I am more or less correct on this.
bombermanCC said:
Today I just tried something: I pushed the power button and on the screen there was a menu to reboot or shutdown: I selected reboot, and then had other choices on screen, and I selected "download" thinking it would go into update mode?... so the device rebooted into download mode and I see the green android logo with the words "Downloading..." in white and "Do not turn off target!!" in green. It's been like that for 30 minutes now and I was just wondering if it truly is downloading something and/or if I can just pull the battery out right now to turn the phone back on normally. If it really is downloading, I find it funny that it's taking so long since I have a 20 MB connection speed...
Click to expand...
Click to collapse
It's waiting for Odin to connect to it via USB. Just hold the power button until it shuts off.
The reason I went into download mode is because I saw the options inside android 4.2.1 to update CM10.1 automatically (I chose "nightlies" and "check twice a day"...) and I have yet to see any updates being done. Will there be a pop-up of some kind if there are any nightlies available for download? Will I have to go into download mode to apply the updates? Do they auto-download when the phone is on and they update at next reboot? Please explain the update process...
Click to expand...
Click to collapse
That only works for official CM releases. You'll have to check the thread periodically and manually update by downloading the zip and flashing it with CWM.
Also. I don't know if this is a problem or not, but I noticed in JB that my battery seems to drain faster than with GB installed... nothing drastic, but noticeable. For example, if I turn everything off except cell antenna overnight, 10 hours later I have 10% less battery. It used to be around 5% less battery. Can anyone confirm that JB uses more battery than other android versions?
Click to expand...
Click to collapse
JB battery has been better for me than the official ICS was. There's so many variables there though, you're probably doing something different or have some app installed that you didn't before.
So here's a weird one: I'm running stock 4.1.2, and after the update I noticed the alarm going off when I set it... but only for about a second before turning itself off. It doesn't happen consistently - it only seems to happen when I leave the phone charging overnight. If I set the alarm for a minute from now, it goes off as it should. Anyone experience this? Any ideas?
I've tried setting the alarm to repeat weekly, clearing the clock app's data, and, yes, doing a full factory reset. The issue returned. Sometimes I think it might have to do with whether Google Now or Aurora (alpha Firefox) have recently added something to the notification bar, but that's pure speculation.
Don't want to install an app to rectify this, but I suppose I will if I must.
Thanks
P.S. - This thread appears to be nearly identical regarding a GSIII, but even if disabling the lock screen is a work-around, I can't do it.
P.P.S. - Any chance Samsung will be issuing any further updates (bug fixes), or can we expect this most recent update to JB to be the last?
Bump
Nobody else has this issue!?
Nrbelex said:
Bump
Nobody else has this issue!?
Click to expand...
Click to collapse
I have had it from time to time. Haven't found a fix for it.
Sent from my SPH-D710 using xda premium
graydiggy said:
I have had it from time to time. Haven't found a fix for it.
Click to expand...
Click to collapse
Well at least I'm not going crazy. I encourage you and anyone else having this issue to star it on the Android bug tracker: http://code.google.com/p/android/issues/detail?id=43430
Solved: See post #7
I used to be able to Ok, Google and say "set countdown timer 2 minutes and 30 seconds" and it did it. Now when I do it, it brings up a screen to choose between either 2 minutes or 3 minutes. Did this start with the last update, or is there a setting I'm missing?
Edit: I contacted Moto 360 chat support and their response was to take it back to place of purchase!!
I was just about to complain about this, it was so handy to set count down timer without the need to touch the watch. Now it will just show the blue bullet menu and you have to confirm by touching the watch.... stupid....
Many complaints about it on google product forum
https://productforums.google.com/forum/#!category-topic/android-wear/9fcM_13j6so
lifeisfun said:
I was just about to complain about this, it was so handy to set count down timer without the need to touch the watch. Now it will just show the blue bullet menu and you have to confirm by touching the watch.... stupid....
Many complaints about it on google product forum
https://productforums.google.com/forum/#!category-topic/android-wear/9fcM_13j6so
Click to expand...
Click to collapse
Yes, I found that too. Hopefully it'll be back again.
Same issue with Lg g watch and google now on 5 different phones...
It seems like it broke on the last Wear update on the phone for me.
Jawbox said:
It seems like it broke on the last Wear update on the phone for me.
Click to expand...
Click to collapse
The issue has been posted in a few forums. I went ahead and did a review of Android Wear in the Playstore to report it. It probably won't hurt to have a lot of users report it via a review in the Playstore.
I think I found a fix for the countdown timer. On your phone, say OK Goggle, set countdown timer to 2 minutes and 45 seconds. (Any off the wall time will work). After it's done on your phone, try your Moto 360 now. It's working for me. If someone would confirm that it works, I'll rename to title of the thread to help others.
Problem is fixed now
They pushed update this morning.
lifeisfun said:
Problem is fixed now
They pushed update this morning.
Click to expand...
Click to collapse
Which update? I haven't gotten any update.
Edit: I just got the update, curious to know if the update fixes the timer issue. At the time I posted my fix, I had not gotten the update.
Idk if i got the update but i sure dont remember updating the Wear app. Although the fix you posted worked like a charm
April was Autism Awareness Month Sent from my SM-G900P using Tapatalk
Have had the Huawei Watch for a few days and it seems to have a deal-breaking bug. Frequently, after the watch has been in ambient mode for a while, it won't come out of it. If I touch the screen, the ambient display gets brighter, but that's all. No response from swiping or button presses. Sometimes, after a very long pause (a minute or so) it'll come back to life, but usually I have to hold the button until it restarts. Anyone run into this before? Ideas? Any help is greatly appreciated.
Using it with a Nexus 6. Android wear version 1.3.0.2176821.
Thanks!!!
Sent from my Nexus 6 using XDA Free mobile app
Forgot to mention that the time sticks at whatever time it freezes and so it doesn't even tell the correct time. Sigh.
Have tried a factory reset. Didn't fix it.
Sounds like it's maybe in need of replacing. Like any new product release, there's bound to be a certain percentage of failures. Depending on how you look at it, you're either really lucky, or really unlucky
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
gyromiterob said:
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
Click to expand...
Click to collapse
I have absolutely same issue. In ambient mode it freezes from the first day I bought this watch. Thank you for investigation and info.
got my hwatch and experienced the ambient mode freeze. to unfreeze, i enter and exit theater mode. it works. but now i'm never sure if the ambient time i'm glancing at is accurate or not...
Similar problem with an HTC M8. I'll try the theater mode to see if that helps. I still can't trust the time any more.
+1 on the Huawei Watch freeze. Sometimes after 15 minutes, sometimes after several hours. It has frozen with ambient mode disabled and with wrist gestures disabled as well.
Sent from my LG-V500 using Tapatalk
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
brizey said:
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
Click to expand...
Click to collapse
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
lukhof said:
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
Click to expand...
Click to collapse
Good to hear you got it fixed!
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
maximus96 said:
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
Click to expand...
Click to collapse
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
lukhof said:
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
Click to expand...
Click to collapse
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
maximus96 said:
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
Click to expand...
Click to collapse
None of them had red-tint issue. It seems this is not related with the freezing ambient mode.
Thanks, that solve my problem as well.
Happening to me too. Was using 3rd party skymaster watch face.
Got a replacement from amazon and it hasn't froze yet in the past two days of using it. The last one froze several times a day
I've been having issues with touch responsiveness off and on for the last two weeks or so, and I'm wondering if somehow the last security patch could have caused it. Like, I will be typing with the swipe and it will stop halfway through a word and spit out random stuff, or sometimes I have to pull a few times to bring down my notification bar
Everything's ok for me. Are you using a glass protector?
No such issue here either, I don't use a screen protection.
Phazonclash said:
Everything's ok for me. Are you using a glass protector?
Click to expand...
Click to collapse
I am using a glass screen protector, but I've had it since I had the phone
I'm having the same issue. And of course, it's not doing it now as i swipe. Happens more when i type.
CrimsonToker said:
I've been having issues with touch responsiveness off and on for the last two weeks or so, and I'm wondering if somehow the last security patch could have caused it. Like, I will be typing with the swipe and it will stop halfway through a word and spit out random stuff, or sometimes I have to pull a few times to bring down my notification bar
Click to expand...
Click to collapse
Larzzzz82 said:
I'm having the same issue. And of course, it's not doing it now as i swipe. Happens more when i type.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I have noticed something similar. My issues has been like this since I got the phone and upgraded to 8.1. I heard of others also making this complaint after the fist update to 8.1.
For me... When I try to silence a call it will not let me swipe down on the end button. Unlocking can also be a challenge.
Scott said:
For me... When I try to silence a call it will not let me swipe down on the end button. Unlocking can also be a challenge.
Click to expand...
Click to collapse
I use a pattern and sometimes getting to that can be an issue.
The only problem I've noticed, and I'm not positive this is from the OTA, my Gear S3 stopped vibrating and showing notifications from Android Messages. It was literally the day or the day after I took the OTA. But, who knows. All other SMS apps seem to work fine though.
I still haven't unlocked and rooted mine yet, so I'm hoping by doing so maybe this issue will disappear. Lol at least it doesn't seem to be just me. Though I'm glad to have this issue and not one of the other, worse issues I've heard of people having ?
I'm unlocked with root...
I have screen touch issues. Answering or declining a call is frustrating.
I get it still when I try to swipe away a notification or if i'm pulling down the Notification shade to access the quick toggles, it goes up and i gotta pull it down like 4 times to get it to stay
Yeah I've noticed this as well, have issues answering and rejecting calls and typing on the phone the touch screen responsiveness is off. Hopefully they fix this and the battery drain issue in the March update, because you know we wont get an update before March 5th lol. Also noticed my Gear S3 doesn't receive notifications properly anymore, tried factory resetting the watch and the phone and no resolution unfortunately.
I noticed this both on factory 8.1 image AND on DU RC22 Rom.
Once in a great while, usually when playing a game, I have to tap twice to get a recognized touch, especially near the edges.