Audio playback stopped on 8.1 - Nokia 8 Questions & Answers

I am having an issue where audio stops after about 30 minutes of playback, the only way to get it going again is to unlock the device and go into the app. This happens with audio books on Audible and podcasts through Podcast Addict with wired and Bluetooth headphones. The issue only starred after the full 8.1 update. I had no issues with 7.1, 8.0 beta, 8.0 full release or 8.1 beta. I tried a full wipe and it still happens. Is anyone else seeing this? Any ideas on a fix? It's as if Android is killing the app.
I tried tweaking a couple of things in developer settings but nothing worked. So I tried playing Audible and Podcast Addict using Android Auto and both played for well over 30 minutes without stopping. This was with the screen off and over bt. But having to fire up AA to play something isn't ideal.
Sent from my TA-1012 using Tapatalk

I have had Poweramp stop just like that as well using 8.1 stable and Bluetooth headphones

Same for me with any audio apps.
Could be a background killing service after 30 min of srenn off.

Mastamike said:
Same for me with any audio apps.
Could be a background killing service after 30 min of srenn off.
Click to expand...
Click to collapse
Good to see I am not alone. Let's hope HMD are on this and we see a fix next update.
Sent from my TA-1012 using Tapatalk

Its just happened to me twice while i was walking somewhere, not ideal having to get your phone out to get the music going again when it is banging it down with snow.

Same here

me too, it happened twice using "music folder" app.
it happened since I've oreo 8.1 stable version.

I have tweeted Nokia Mobile and i have seen people have posted about it on the official community forums (probably us lot lol) so lets hope they hear this, clearly it isn't a one off and i haven't stumbled across a simple fix.

MrBelter said:
I have tweeted Nokia Mobile and i have seen people have posted about it on the official community forums (probably us lot lol) so lets hope they hear this, clearly it isn't a one off and i haven't stumbled across a simple fix.
Click to expand...
Click to collapse
Yeah, I created the thread on Nokia Care. The issue is pissing me off so I want HMD to address it.
I will have a better test of using Android Auto to initiate audio playback when I go for a run tomorrow. Having to stop every 30 minutes to restart a podcast isn't good.
Sent from my TA-1012 using Tapatalk

Well it stopped twice for me in a 4 mile walk, it's a bit of a pain in the arse to be honest.

Press and hold battery, go to background activity manager, find your app, grey out slider switch.
This will allow any app to work forever and a bit longer.

TeddyBeers said:
Press and hold battery, go to background activity manager, find your app, grey out slider switch.
This will allow any app to work forever and a bit longer.
Click to expand...
Click to collapse
Cheers, trying now will report back. I was looking for a setting like this but what I found in developer settings didn't work.
Sent from my TA-1012 using Tapatalk

Been playing audio for 45 minutes now with no issues. Thanks Teddybears.
Just hope that it doesn't rape the battery and Nokia fix it properly.
Sent from my TA-1012 using Tapatalk

I'm blind. Teddybeers. Doh.
Sent from my TA-1012 using Tapatalk

TeddyBeers said:
Press and hold battery, go to background activity manager, find your app, grey out slider switch.
This will allow any app to work forever and a bit longer.
Click to expand...
Click to collapse
Maybe i have the wrong end of the stick here but I don't have the background activity cleaner enabled and all of my apps are on the whitelist and shouldn't be restricted anyway, i also have Poweramp set to have no battery optimisation since google fannyed around with how Bluetooth works and the audio still stops at around 30 minutes.

MrBelter said:
Maybe i have the wrong end of the stick here but I don't have the background activity cleaner enabled and all of my apps are on the whitelist and shouldn't be restricted anyway, i also have Poweramp set to have no battery optimisation since google fannyed around with how Bluetooth works and the audio still stops at around 30 minutes.
Click to expand...
Click to collapse
It needs to be greyed out, not blue. Imo this is a bug. After changing it to grey solved the problem
Sent from my TA-1012 using XDA Labs

Toedwarrior said:
It needs to be greyed out, not blue. Imo this is a bug. After changing it to grey solved the problem
Sent from my TA-1012 using XDA Labs
Click to expand...
Click to collapse
So you have to remove it from the whitelist essentially blacklisting it even if the actual background activity cleaner is turned off which is the exact opposite of what it was in 8.0?
That's just bonkers.

MrBelter said:
So you have to remove it from the whitelist essentially blacklisting it even if the actual background activity cleaner is turned off which is the exact opposite of what it was in 8.0?
That's just bonkers.
Click to expand...
Click to collapse
This is dumb but yeah it fixed the problem
Sent from my TA-1012 using XDA Labs

Bizarre and a bug that needs correcting sharpish really, when you turn it off (or make it grey which ever term you prefer to use) you can even see the number of allowed apps that can run in the background decrease so android is even telling you you have just restricted its ability to run in the background lol

Seems there is some aggressive background app optimisation. Better if hmd unlock the bootloader so that devs can utilise the full potential of the device.

Related

[Q] any kind of notifications, without turning on the screen?

As most of us know our beloved Note (1) doesn't have the "notifications LED" present in so many dumber and older phones.
After completely breaking the power button from just checking if there's any notification I've got a new phone and I'm on a quest for finding some alternative notification.
So, it seems that in order to actually GET that there's some notification you need to have talkback enabled and that's buggy (you get this spooky voice when doing certain tasks). FINE, I disabled (freeze) both samsung and google TTS (although I didn't really wanted, but OK). Then I get a hand icon in the notification area with "talkback activated". Ok, FINE. I'm using Flashlight Notifier (which flashes the camera LED) and it seems to be somehow working, except that it leaves the (camera) LED turned on continuously!!!
I seems that there's some other option to flash the soft buttons backlight but it needs some very old (I think GB) ROM and I'm not going there. For what is worth I'm on a stock new JB with speedmod kernel.
In short, any solution that "just works", getting extremely frustrated with all the stupid problems I run into? I need notification for gmail, hangouts, sms, missed calls, nothing fancy.
Whats wrong with vibrate and message/ring tone?
This is question. So should be in Q and A thread
a. vibrate/ring disturbs people around (especially when there are at least 10-20+ notifications coming every day)
b. you might step out briefly and you might not take the phone (all the time...) with you to WC and such. Yes, some applications allow for repeat rings (like the default SMS app) but that only makes (a.) worse
I think it is good to be able to just look at the phone and see that you don't want to turn the screen on as opposed to turning the screen on, see you don't need anything from there, turn it off.
If a mod wants to move the thread please and thank you.
https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoff
Thanks, interesting but not at all what I want. Just want something to blink reliably ...
There's a whole cohort of software that does that but is usually geared towards making the "real" notification LED blink in various colours and also it usually shares the talkback (samsung) bug (but I'm willing to work around it).
d210 said:
Thanks, interesting but not at all what I want. Just want something to blink reliably ...
There's a whole cohort of software that does that but is usually geared towards making the "real" notification LED blink in various colours and also it usually shares the talkback (samsung) bug (but I'm willing to work around it).
Click to expand...
Click to collapse
try NoLed from play store, there is a thread for the same in XDA too.
d210 said:
Just want something to blink reliably ...
Click to expand...
Click to collapse
Fork this, modify it any way you like, compile and bob's your uncle.
treacherous_hawk said:
try NoLed from play store, there is a thread for the same in XDA too.
Click to expand...
Click to collapse
Thanks. Is it a warlock...
Sent from my GT-N7000 using xda premium
dsmas said:
Thanks. Is it a warlock...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
did not get you. warlock (literal meaning?, some user?).
none that dont cause severe wakelock lol
Sent from my GT-N7000 using Tapatalk 2
Typo error. Sorry.
Sent from my GT-N7000 using xda premium
NoLED seems to be fine (I was thinking for a long time that on OLED it might be a good idea to have some "few pixel" notifications, although I understand there is still significant power consumption even with OLED and few pixels on).
The device still deep sleeps (at least without notification) but of course this is the type of thing liable to kill the battery overnight.
Still, it works great and for most notifications I need it doesn't even need talkback (that's a big plus because I don't have to freeze TTS). And it looks great! Will report later or tomorrow how things go, with my luck I'll run into some issues in no time.
wow
treacherous_hawk said:
try NoLed from play store, there is a thread for the same in XDA too.
Click to expand...
Click to collapse
I was looking something like this. (It has many options / choices).
Thanks.
baz77 said:
none that dont cause severe wakelock lol
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
The battery drain was extra 2-3% while me and the phone were sleep from 10pm to 6am. Acceptable. Good. With setting - noled always on and battery % while charging on.
Thanks.
Sent from my GT-N7000 using xda premium
lol, maybe they obtimized it, that is good news if true. The wakelock occurs when not charging btw.
Thank you everyone!
NoLED is great for now, battery life is good, it catching all I want (maybe except hangouts) without enabling accessibility and is better than I dreamt.
Maybe, maybe a little concerned with display life now (it looks like there is still some kind of backlight, not only the small icons) but overall it looks good!
Maybe some option to blink the camera LED would still be good but you can't have everything.

List of bugs on Note 3

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

[APP] S2W Phone Call Disabler

S2W Phone Call Disabler
If you have sweep2wake enabled, you may notice the touchscreen is active while the screen is blanked during phone calls. This app will disable sweep2wake and doubletap2wake during phone calls and re-enable them with your previous settings after the call is finished. I couldn't find a way to do it reliably in the kernel, so I made this companion app. It will work with any Nexus 6 kernel that has sweep2wake.
It requires no configuration, just install it, and run it once. After that, it will automatically work, even after rebooting.
There is one option in the app. Since this app only needs to be opened once, you can click a check box that will remove this app from your app drawer. If you change your mind and want it back in the app drawer, you will have to uninstall and reinstall the app.
This app shouldn't use many resources. It runs an intent service when the phone state changes. That means the app wakes up, does its thing, and then stops itself. In other words, it is not always running in the background.
This app requires root!
Download:
S2WPhoneCallDisabler.apk
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Thanks wanted to run your kernel but kept having issues in call.
My so glad to be able to run your kernel been with Vzw m8 for last year... an this app has worked great for me all day. An also I just wanted to throw out I'm on .24 an having zero call issues
3rd!
Works great thanks man
This issue bugs the crap out of me. I'm testing now. Thanks flar.
Nexus 6
I assume it's working good for everyone?
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Ngo93 said:
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Click to expand...
Click to collapse
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Will do!
flar2 said:
I assume it's working good for everyone?
Click to expand...
Click to collapse
You have no idea. This app is pure genius.
Nexus 6
Not sure why but my copy doesn't have the option yo hide from the app drawer.
Great idea for this app, I'm surprised that there isn't greater call for it, or maybe I'm alone in having major screen issues when in a call with 2t2w enabled.
My issue is that it never turns double tap back on after a call. I'm using LK with it set up through lkconfig. Anyone know a solution to this? Thanks
Sent from my Nexus 6 using XDA Premium HD app
In fact I've experienced the same once or twice with ElementalX Kernel. I'm going to observe if it is happening again on my next call.
Edit: Tried it twice, no problems, so false Alarm. Everything working as it should be!
Thanks for the app, Flar2! I wrote a guide for this on my website (here), and also made a video tutorial:
https://www.youtube.com/watch?v=bHjN6jUdgzs
Feel free to use either, and thanks again for the great work!
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
datajosh said:
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah it's been happening a few times over the last couple days, but nothing major.
Nexus 6
Great!
Works perfectly, and removed from the app drawer. Screen is completely unresponsive (as it should be) when on a call with the prox sensor covered.
Thanks for this!
Hey @flar2 ... I think I may have found a sequence that keeps disabling dt2w and s2w. It seems if I get a call and swipe to ignore the call within a second or two that it's disabling those two features, they only come back on after I re-enable them in your ElementalX app.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
I've been getting this behavior lately where it would disable itself but it seems completely random to me.

My phone vibrates for no 'reason'

Greetings all,
I have a new Note5 and overall I like it.
As you might expect I have been working feverishly to find up to date app solutions for my usage model and that will work on an unrooted device. I despise all that conspire to force this upon us! Anyway I have been testing loads of apps and somewhere along the way something has been set to vibrate to indicate something. It is happening at fairly random intervals and nothing shows on screen or in the pull down that accounts for it.
I have looked for events that are pending, past due, etc. I don't get many texts. So, it isn't that. I have even turned on airplane mode which should prevent any kind of updaes or pushes that might trigger an notice.I have checked all of the apps I am using and none are set to vibrate only. From the initial turn on of this phone I have run package disabler pro for Samsung. Using a basic list from this xda thread: http://forum.xda-developers.com/note5/general/guide-bloating-touchwizzing-note-5-t3184563. I have restarted the phone several times as well
Can anyone suggest some kind of system monitor/logging app that I can load that will allow me to find out which application is triggering this? Is there some other way I can find out what is triggering this event? I expect that a logging app will eat battery more but on a temp basis that would be ok.
Thanks all and here's to someone finding a way for us to root our notes without messing up our warranty and secure payment...
p
If you are talking about how it vibrates when you first pick it up for seemingly no reason, then that's a feature. It's to let you know you have notifications. It's called smart alert, you can disable it in the gestures menu.
vibrate (and sound) for 'no reason'
Thanks _MetalHead_
But no. This happens when it is sitting undisturbed. I will check and turn off that feature if it isnt already so it isnt adding to the confusion.
If I didnt say, I find no idication of active alarms or notifications.
P
Do you have any Bluetooth devices connected? I had a smart watch with my S5. Every time it connected or disconnected, the phone would vibrate. This was especially annoying when I left the watch in the bedroom while sitting in the living room with my phone. Every few minutes it would connect/disconnect and the phone would vibrate.
STM8
Not clear if this is contributing. Will turn BT off to be certain.
Actually, I think I can say for certain no. This has happened in airplane mode.
That is why I am looking for a system logging application or some equivalent method.
P
Sent from my SM-N920V using XDA Free mobile app
pwhalley said:
STM8
Not clear if this is contributing. Will turn BT off to be certain.
Actually, I think I can say for certain no. This has happened in airplane mode.
That is why I am looking for a system logging application or some equivalent method.
P
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
Hi, Go to settings and go to S Pen Option, and turn off all S Pen alerts, including power saver one.
pwhalley said:
STM8
Not clear if this is contributing. Will turn BT off to be certain.
Actually, I think I can say for certain no. This has happened in airplane mode.
That is why I am looking for a system logging application or some equivalent method.
P
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I re-read your OP, and noticed you said it was happening in airplane mode.
The S-Pen suggestion above seems worth pursuing.
Good luck!
I have the same problem. It would just randomly vibrate. I think is something to do with Google notifications.
Sent from my SM-N920I using Tapatalk

Pie/One UI Impressions?

Using the US unlocked variant, I haven't yet received the pie update. However, just reading around, I get the general impression that the update isn't that good (buggy, lost features).
What are people's thoughts on it? Right now, I'm kinda glad I haven't gotten the update yet.
Looks like unlocked goes last for updates. I guess the carrier versions beta test for us.
Sent from my Samsung SM-N960U1 using XDA Labs
Works fine for me. Prefer it to Oreo.
djbutter said:
Using the US unlocked variant, I haven't yet received the pie update. However, just reading around, I get the general impression that the update isn't that good (buggy, lost features).
What are people's thoughts on it? Right now, I'm kinda glad I haven't gotten the update yet.
Click to expand...
Click to collapse
I decided not to wait for Verizon Wireless to update my phone, and I saw a way to get it now on reddit so I pulled the trigger (go to https://firmware.science/ for instructions). It was brain dead simple.
Not sure what's supposed to be "buggy", because I have found zero issues - but then I've only had it a day now. Lost features? Not sure. Well, you can't set Performance mode any more in Device Maintenance (now called Device care), but I never changed it. And the Device Maintenance edge panel is gone, too. You can still get Battery, Memory, and Storage in settings. Also, you can schedule the phone run this automatically, now.
Night mode works (long as you're not using any theme). Battery life is impressive (lost less than 2% overnight). Edge panel icons are huge, now. Not a fan of that. At least Android Auto fully works... no more lost icon dock. That's the main reason I upgraded.
I mean, if you have examples of specifics where it's buggy or other lost functions, I'd be interested in what, but i can't complain so far.
Main issues for me
1. Multi window features are completely stripped down. No drag to popup, cant switch window positions without redoing the actions from scratch, etc.
2. Samsung Good lock customizations and routines are broken.
3. The interface is very erratic. Even Samsung apps with the interactive areas at the bottom still have the 3 dot menu at the top. Non Samsung apps anyway follow the old ui, so overall, its not that much of a benefit.
These were an integral part of my usage, so Pie is a disappointment for me at least.
Sent from my SM-N960F using Tapatalk
The only issue for me (and its major) is that I can no longer use Bluetooth in the car for phone calls. Connection always drops. I started another thread on this issue.
Not that impressed so far; cannot add items to quick settings menu - you can only move around the existing icons.
Lots of things now require more tapping to get there, ie simple thing like checking batter usage now needs five steps: pull down on quick start menu>press settings>press device care>press battery>press battery usage.
Would be so much easier if you could just create a shortcut to this screen??
PIE/One UI just seems change for the sake of change. I've not seen any benefits yet.
Lesthehammer said:
Not that impressed so far; cannot add items to quick settings menu - you can only move around the existing icons.
Lots of things now require more tapping to get there, ie simple thing like checking batter usage now needs five steps: pull down on quick start menu>press settings>press device care>press battery>press battery usage.
Would be so much easier if you could just create a shortcut to this screen??
PIE/One UI just seems change for the sake of change. I've not seen any benefits yet.
Click to expand...
Click to collapse
Put device care as an icon on home screen.
Sent from my SM-N960U1 using Tapatalk
Already have setting icon on home screen, just a pain that you cant add items to quick settings anymore...
I got Pie last week (AT&T - US) and so far I don't have any complaints. A few cosmetic things to get used to, head-up notifications are a bit different looking, but battery life is actually noticeably better.
I like it. Was apprehensive about this at first as was concerned at ruining decent battery life but this is darn good!
Sent from my SM-N960F using Tapatalk
RGardner said:
I decided not to wait for Verizon Wireless to update my phone, and I saw a way to get it now on reddit so I pulled the trigger (go to https://firmware.science/ for instructions). It was brain dead simple.
Not sure what's supposed to be "buggy", because I have found zero issues - but then I've only had it a day now. Lost features? Not sure. Well, you can't set Performance mode any more in Device Maintenance (now called Device care), but I never changed it. And the Device Maintenance edge panel is gone, too. You can still get Battery, Memory, and Storage in settings. Also, you can schedule the phone run this automatically, now.
Night mode works (long as you're not using any theme). Battery life is impressive (lost less than 2% overnight). Edge panel icons are huge, now. Not a fan of that. At least Android Auto fully works... no more lost icon dock. That's the main reason I upgraded.
I mean, if you have examples of specifics where it's buggy or other lost functions, I'd be interested in what, but i can't complain so far.
Click to expand...
Click to collapse
If you go in Settings > Device Care > Battery, the first option is Power Mode. You can choose High Performance from there.
Sent from my SM-N960F using Tapatalk
My only issue so far is that Pie seems to be forcing people to create duplicate threads here on XDA asking for people's opinions on Pie, even though there's already several Pie threads here. I hope Samsung squashes this bug soon.
kta said:
If you go in Settings > Device Care > Battery, the first option is Power Mode. You can choose High Performance from there.
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
Ah!! Didn't see that. THanks.
Pie is downgrade from Oreo. No real benefits. Just questionable cosmetics.
-multiwindow management is a joke
-cannot have recent apps list view
-no call recordings
Sent from my SM-N960F using Tapatalk
EzEddie said:
The only issue for me (and its major) is that I can no longer use Bluetooth in the car for phone calls. Connection always drops. I started another thread on this issue.
Click to expand...
Click to collapse
I have tried it several times and keep going back to Oreo. I got the official OTA (At&t) thinking the minor issue I had with bluetooth would be fixed. If I'm connected to bluetooth in car there is no alert if I get a text. This doesn't exist on Oreo. I know its minor but bugs me.
Sent from my SM-N960U using Tapatalk
main issue here
can't use multiwindowed
video recording is laggy, compared to oreo, it's not 4k and 60fps i think
lagging using spen to write your massage
Mr. Orange 645 said:
My only issue so far is that Pie seems to be forcing people to create duplicate threads here on XDA asking for people's opinions on Pie, even though there's already several Pie threads here. I hope Samsung squashes this bug soon.
Click to expand...
Click to collapse
Ha! I personally haven't seen them; they're usually beta impressions or threads for specific issues.
butchieboy said:
I have tried it several times and keep going back to Oreo. I got the official OTA (At&t) thinking the minor issue I had with bluetooth would be fixed. If I'm connected to bluetooth in car there is no alert if I get a text. This doesn't exist on Oreo. I know its minor but bugs me.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
If you go in the Bluetooth Devices list, find the car Bluetooth, hit settings and make sure that both Call Audio and Media Audio are set to ON. You may have had Call Audio off if you experienced that behaviour.
Sent from my SM-N960F using Tapatalk
kta said:
If you go in the Bluetooth Devices list, find the car Bluetooth, hit settings and make sure that both Call Audio and Media Audio are set to ON. You may have had Call Audio off if you experienced that behaviour.
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
Nope thats not the issue, thanks.
Sent from my SM-N960U using Tapatalk

Categories

Resources