Related
I love this device but it has a couple of issues. I thought it would be helpful to list bugs in this first release of the software. I'm not rooted. These are mine:
Haptic feedback on menu keys sometimes stops
Air Command has stopped working. Its intermittent.
Sound controls sometimes don't allow me to make changes (right now I can't change notification sound level)
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Another annoying bug is that AVRCP 1.3 does not seem to be implemented properly.
Song/Media metadata does not get properly sent via bluetooth to receiving devices. This has been seen as not working at all to song information getting stuck on display and not changing when tracks change.
I'm definitely looking forward to a big fix for this one.
This has been seen on ATT, Tmobile, and Sprint variants.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Gary02468 said:
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Click to expand...
Click to collapse
You have to edit some code to allow video call on LTE. changing a 0 to a 1. Google to learn how. Can be fixed
wdkingery said:
You have to edit some code to allow video call on LTE. changing a 0 to a 1. Google to learn how. Can be fixed
Click to expand...
Click to collapse
But the workaround requires rooting, doesn't it? (For me, the disadvantages of rooting at this point outweigh the benefit of Hangouts via LTE.)
Gary02468 said:
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Click to expand...
Click to collapse
Edit. Just saw you dont wanna root
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Gary02468 said:
But the workaround requires rooting, doesn't it? (For me, the disadvantages of rooting at this point outweigh the benefit of Hangouts via LTE.)
Click to expand...
Click to collapse
Whats the disadvantages to rooting?
The only bug that I have noticed is sometimes when I get an email notification from the stock email app, it appears in the status bar and then disappears within a couple of seconds. I've seen this a couple of times.
I guess we have to expect some issues since this is the first device out of the box with 4.3.
I really wish they would allow the widgets on the lock screen while having a pin for security. At least read only.
Unhived__Mind said:
What['re] the disadvantages to rooting?
Click to expand...
Click to collapse
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
screen and sound
has anyone noticed occasional brightness flickering? I thought it might be adaptive display or something like that, and i disabled it all, but I still see it.
also, I'm not sure what in the world happened, but my phone started randomly playing music. the music player didn't open, I had air gestures, off, and it wasn't ringing. I turned off wifi and the music stopped. In fact, i don't even think I have the song that was playing saved to my phone.
nespid said:
has anyone noticed occasional brightness flickering? I thought it might be adaptive display or something like that, and i disabled it all, but I still see it.
also, I'm not sure what in the world happened, but my phone started randomly playing music. the music player didn't open, I had air gestures, off, and it wasn't ringing. I turned off wifi and the music stopped. In fact, i don't even think I have the song that was playing saved to my phone.
Click to expand...
Click to collapse
Ghost in the machine....
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Gary02468 said:
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
Click to expand...
Click to collapse
Rooting any device voids warranty. It does not trip the flash counter or Knox. Just flash back to stock or supersu unroot.
As for the other stuff, no issues here. Phone is as stable as it was on stock. Runs even better because debloated it myself.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Gary02468 said:
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
Click to expand...
Click to collapse
Good summary!
Sent from my SAMSUNG-SGH-I317
Using Google Music over headphone aux cable, setup eq the way you want, listen for a sec and slide the track knob to another part of the song. The eq turns off. If you go in to the eq settings, it is showing on. Toggle off and on and you will hear the difference.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I don't have any of the bugs being list here. However, when I have S Voice on for wake up when the screen is off, it will sometimes turn on randomly even when nothing is said. Happened in a movie theater for me and it was embarrasing. That feature is now off.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Anyone else having problems using whatsapp with pen window?
It seems that when I minimise it from a conversation I then can't open it again or move the icon around on the screen.
Works normally if I press back to the conversation window first though
S voice gets weird with me too. Had it in hands free mode and it kept telling me something about my safety while it simultaneously read my text out loud. it kept getting stuck in that loop for any new messages.
lax_22 said:
Anyone else having problems using whatsapp with pen window?
It seems that when I minimise it from a conversation I then can't open it again or move the icon around on the screen.
Works normally if I press back to the conversation window first though
Click to expand...
Click to collapse
Same here
Screen brightness and
Screen brightness issue: occasionally, when brightness is set low (not auto), when phone is turned on, screen turns on at full brightness for a split second then go to low setting level. Happens about 25% times.
Haptic feed back when screen off: after I turn screen off, if I move phone, I get a haptic feed back once. Doesn't repeat until I turn screen on and off again.
Edit: this is caused by 'smart alert'. Under Controls -> Motions. It vibrates when you pick up the phone and you have a notification and the screen is off to let you know there is something you missed.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Anyone having internet problems? When I'm on wife or 4G lte, the stock browser will get halfway through loading a Web page, then it will just hang there for a little.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Ever since upgrading to Lollipop 5.1 on my Moto X (2013), I get the message: "vnd.android.nfc://ext/motorola.com:xring", every time that the screen unlocks with the Motorola NFC Skip. Is there a way to prevent the message from showing?
Thanks
Pat
I get that message as well, the Skip doesn't really work consistently for me anymore though. Maybe the first day I set it up it kind of worked, now it doesn't do a damn thing. Anyone on 5.1 with 2013 able to get it to work reliably? I may do a factory reset if so.
If i remember correctly, Motorola posted that skip wont work anymore with 5.1
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
ohmimpotence said:
Called them up to get suggestions.
I uninstalled and reinstalled the Skip app on the play store. Then I re-added the Skip to NFC security settings. Seems to be working reliably now.
Click to expand...
Click to collapse
Does it still give the message or is it gone now?
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
ohmimpotence said:
Still gives the message if I do it with the screen on. From the lock screen it doesn't seem to. I haven't tested if it's still working today because I'd have to remove like the 4 trusted locations I have for my home but even with trusted location on, my phone will lock itself after not using it for a certain amount of time and I'm not using on body detection. When it did that this morning, I was not able to unlock it using the Skip.
Click to expand...
Click to collapse
I think that it has to do with SmartLock locks up the phone after 4 hours of inactivity.
The weird thing is it doesn't unlock with the Skip if it's locked due to inactivity.
Anyone ever get any satisfaction here? I just got the 5.1 update for me Verizon moto x, it's made my NFC ring practically unbearable. It unlocks the phone fine, but then it continually scans my ring and pops up every time the ring moves out of range and back in range of the NFC reader.
Sent from my XT1060 using XDA Free mobile app
Well the update finally hit and now I'm looking for anybody who is using it to share their experience(s). I'm scarred by the G3 update to Lollipop which basically broke the phone but that's another story. Does anybody know of a known bug list or anything like that which is being compiled?
Cheers
I like it. Haven't ran into any problems yet. I didn't OTA. I downloaded the firmware, factory reset my phone, then flashed via Odin.
Im running it for 2 days now, rooted and viper4android working. I love it. Battery life is good, Deep sleeps like it should. Very snappy and they made some minor changes to the UI. Just waiting on a fully compatible kernel now
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
troby86 said:
I like it. Haven't ran into any problems yet. I didn't OTA. I downloaded the firmware, factory reset my phone, then flashed via Odin.
Click to expand...
Click to collapse
I did the same, some say dont but i like change and this one is a good change
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
I updated about two days ago, so far I like it a lot. My device seems to be running a lot smoother than before. Feels much better to me.
Sent from my SM-G925T using XDA-Developers mobile app
HKSpeed said:
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
Click to expand...
Click to collapse
Wait till you use fingerprints to unlock the device, they have updated some security policy so they need secondary unlock method along with fingerprint to unlock the phone, that's very very annoying.. thinking of replacing fingerprint lock all together
soumik shah said:
Wait till you use fingerprints to unlock the device, they have updated some security policy so they need secondary unlock method along with fingerprint to unlock the phone, that's very very annoying.. thinking of replacing fingerprint lock all together
Click to expand...
Click to collapse
Ummm...no. The secondary unlock is a backup for the fingerprints. You don't have to do both to unlock the phone. Just verified, turned the screen on, and held my finger in place...boom, unlocked.
Just when you restart the phone you need to put the secondary unlock method.
Phone is very fluid and I love it, best update i had in a phone in a long time.
Just 1 thing and I bet you'll like it.
No more laggy.
Sent from my SM-G920T using XDA-Developers mobile app
Wow first time I've seen a SW push on a phone that everybody seems to be pretty satisfied with lol. I took the plunge this morning and noticed the secondary password for fingerprints as well. However I know that's always been there as a back up and for whatever reason it had to be reset on the first boot but it's gone away now and is only a back up when it doesn't recognize my fingerprint more than three times. So far so good, I'm curious to see if there is any improvement on the battery life or not.
Thanks for the info everybody!
After I updated my phone to 6.0.1, I did a factory reset. I couldn't be happier. I use fingerprint unlock and have my phone encrypted. Since the release (4/11), I haven't had any issues with battery or performance. I did notice that the auto-brightness seems to be more aggressive than Lollipop. One issue I didn't like was that when I used All-In-One-Gesture to enable double-tap to sleep, I had to manually type my password every time to unlock the phone. I think because of my security settings (allowing an app to have permission to lock the screen), I wasn't able to fingerprint unlock unless I manually turned off the screen using the power button. Otherwise, I don't mind entering a long password every time I turn on the phone.
In standby, my phone would drain 15%-20% over 8 hours each night while I slept. With MM, my phone drains less than 5% each night now.
Anyone having problems with LED notifcations not working? It works when I'm charging, but not any other time. It is turned on in settings>display. I also made sure notifications settings for my apps were not blocked. Weird. So far I'm unimpressed by MM. Alot of things don't work right, like LED notifications The battery improvement is negligible. I was getting 5% battery loss overnight anyway. I didn't do a factory reset before/after upgrading. Maybe that will fix my problems.
Update: I fixed the LED notification by doing a factory reset in recovery. Now I have to reinstall everything . My phone is stock by the way.
it works pretty good all around ui is smooth it has a refined feel compared to the older updates
Sent from my SM-G920T using XDA-Developers mobile app
Battery life has been MUCH better for me.
Rooted+ Xposed. I even disabled the location wakelock module I HAD to use in LP, and it's still much better. SOT isn't really effected much, but screen off + listening to streaming music has more than halves battery usage for me, along with idle time.
Tthe phone is much smoother, and I have not experienced any lagging (have animations turned off, though). Plus, finger print unlock is tons faster. LP always lagged hard for me there, now it's almost as fast as the wife's 6s+.
I got a small issue with unlock function.
If I made screen of my hard button, I could use fingerprint to unlock the screen, but if I used 3rd-app to make screen off, I need to use back up method - PIN to unlock the screen.
Does anyone face the same issue?
Received the OTA update. I'm on stock.
Battery life is *slightly* better, but it's nothing to write home about.
The auto-brightness has been updated, and I feel it's not for the better. It seems to dim/brighten aggressively, and/or not work at all. It's been irritating.
trungctu said:
I got a small issue with unlock function.
If I made screen of my hard button, I could use fingerprint to unlock the screen, but if I used 3rd-app to make screen off, I need to use back up method - PIN to unlock the screen.
Does anyone face the same issue?
Click to expand...
Click to collapse
I have that problem too. I forget which security setting it is, but basically it requires you to enter your password whenever an app locks the screen. I don't think there is any way around it. I uninstalled all my apps that lock the screen, except greenify, for that reason.
drbongles44 said:
I have that problem too. I forget which security setting it is, but basically it requires you to enter your password whenever an app locks the screen. I don't think there is any way around it. I uninstalled all my apps that lock the screen, except greenify, for that reason.
Click to expand...
Click to collapse
Me too... back to stock "easy touch" and wait for next update...
Sent from my SM-G920T using Tapatalk
Great update
If you stick with the stock marshmallow update I think you will be happy. You are able to root it also without a problem.
If you make sure NFC and WiFi are turned off (When you're not using them) I personally have seen better battery usage than Lollipop.
I'm running the stock rooted marshmallow and it really is a beautiful update with a bunch of enhanced features. I would recommend.
As a bonus, it also gives your phone a radio update (which allows it to better contact T-mobile's towers).
If you really want a boost in speed, you should lookup changing your APN settings to force your phone into IPv4, because currently your phone will default to IPv6 which (at least for me) is a tad slower than IPv4.
Good luck and have fun messing around with the new update
HKSpeed said:
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
Click to expand...
Click to collapse
yeah I'm with you on that.
Another thing that is annoying me, and maybe there is a setting to turn this off (if so please tell me as I've not yet found or really looked into it yet)...
It used to be that when I opened a link it would prompt me which browser or or program I wanted it to open with. I actually like being prompted each time because sometimes I want this a bit more secure and so would open with Orweb vs. Google.
Now it seems that once I select and option it becomes the default option until I go in and change it.
Otherwise, I'm enjoying it. I'm rooted running xposed and viper etc.
I really do want my gradient status bar back though...
Ever since the update to Oreo I've been constantly having this issue and it's extremely irritating and can't figure out how to stop it from happening. Basically at least once a day now, sometimes more than once it refuses to use the fingerprint scanner and wants me to enter my password or now my PIN since I switched to the less secure pin just to make it less of a pain everytime this happens and I just want it to go back to working properly so I can have the password again, does anyone know how to fix this issue? It's an unlocked note 8 and it's not rooted or anything, just a stock phone.
It's probably because you're phone has restarted and requires a pin after a restart before it'll use biometrics - It's a problem on Oreo, it's basically just a completely cr*p update that's broken so many things.
Samsung as usual, don't seem to give a stuff!
Nope, it's not a restart that's causing it, that's an entirely different message, especially since the phone's encrypted so the phone won't even start up on a reboot till the encryption password is entered. This is just a it randomly won't accept the fingerprint to unlock, I've turned the phone off then turned it right back on to unlock it and this has happened, 100% certain it had nothing to do with rebooting.
I've read some people saying they had an app that force locked the phone and that causes this and removing it fixed the problem, but I don't have any app that does that.
I have an unlocked note 8 too, I only use iris validation (finger print does not reliably work for me because of my eczema), the only time i have ever encountered this was when the phone went to lock screen while trying to access bio-metric validation (banking app, only ever happened once, i disabled fingerprint after due to unreliability relating to eczema as previously mentioned)
Maybe not the same issue but fingerprint unlock never works for me reliably. I get that message when my fingerprint can't be recognized. I have working hands so often my fingers get knicked, scratched, etc or even just wet causing my fingerprint not register. If I reregister fingerprint with out a perfect fingerprint, after my fingers heal, can't be recognized again. Happened on my Note 5 as well so I stopped using fingerprint to unlock.
Don't think that's the issue for me, I never have any issues with the fingerprint reader normally, it always works great when it actually lets me use it.
I use a fingerprint lock and after the last update I get this message quite a bit, perhaps hourly. It used to occur about every two days, which probably wasn't enough, but now having to type my rather complex password a dozen times per day is annoying. It's not like I even sat the phone down -- it stays in my pocket and sometimes does this despite never leaving my hand. I even use "SmartLock" with my bluetooth watch, which hasn't helped. Any idea short of a firmware downgrade to improve this?
izomiac said:
I use a fingerprint lock and after the last update I get this message quite a bit, perhaps hourly. It used to occur about every two days, which probably wasn't enough, but now having to type my rather complex password a dozen times per day is annoying. It's not like I even sat the phone down -- it stays in my pocket and sometimes does this despite never leaving my hand. I even use "SmartLock" with my bluetooth watch, which hasn't helped. Any idea short of a firmware downgrade to improve this?
Click to expand...
Click to collapse
I never have to use a password except just after a reboot, so having to do it once every two days is already abnormal to me
And I use smartlock with a bluetooth watch as well, that smart lock will ask me to use fingerprint after some idle time though
I searched for this issue for close to a month will no resolve.
Today I finally read what I've been experiencing!
My phone would jump to lock screen asking for pin while it was in in use with google apps and 3rd party apps.
I also had smartlock active @ home, my vehicle and BT devices.
In my vehicle while navigating with maps and on my bike using a trail map app it would go black screen/pin. It would also happen with spotify the screen would go black but ask for pin when screen was touched.
At home it would be in the news feed, messenger, FB, etc.....black screen/lock screen.
Numerous factory wipes and 3rd party apps deletions didn't resolve.
I started the warranty process with google. I wasted time with their CSR trying to T/S online. , I went to ubreakifix 3 times at google's insistence to get it rechecked, ubreakifix duplicated the issue and couldn't do anything for me.
They recommended replacement.
Google was hesitant because ubreakifix couldn't confirm a hardware issue. Ubreakifix wouldn't and couldn't diagnose hardware because they have no replacement parts for the Pixel 5.
Google agreed but would not send a device until my was sent back. They suggested going through my wireless provider for a loaner. My provider did but then they sent it off to their repair center instead of Google and found nothing abnormal and sent it back to me.
I just got it back yesterday after 2 weeks, I had one lock up yesterday.
I read that last night's security update resolved a "sensor" issue and I'm hoping that was the original issue.
This device is not on my recommended list.
I miss my 3XL, the size, the haptics, the squeeze are things I miss from that phone.
My kid reminded me everyday for the 10 days I was without mine.
izomiac said:
I use a fingerprint lock and after the last update I get this message quite a bit, perhaps hourly. It used to occur about every two days, which probably wasn't enough, but now having to type my rather complex password a dozen times per day is annoying. It's not like I even sat the phone down -- it stays in my pocket and sometimes does this despite never leaving my hand. I even use "SmartLock" with my bluetooth watch, which hasn't helped. Any idea short of a firmware downgrade to improve this?
Click to expand...
Click to collapse
This happened to me just once last night. Not sure why/what triggered it but fortunately it only has happened the one time.