Open any app eg. dialer.
Press home button. There is a slight delay (the amount of delay seems to vary at random) and then it closes. Sometimes it's not noticeable, sometimes there's a half a second delay.
When it does happen, you can see the home button light up animation stuttering too.
Compare this with the back button.
Open app again
Press back button. It closes instantly every time.
This is repeatable, and happens with every app.
Edit:
There also seems to be added delay to the multitasking button.
When pressed at the home screen, it's there's a small amount of delay. When pressed inside an app, there's a one second delay.
Using ART runtime seems to fix the lag in home and app switcher buttons, though 4.3 did not have the lag and it was dalvik, so not sure what that means.
Pulling down the notification on lockscreen also lags. But I do have the transparent system bars mod so it could be that.
doesnt happen on my phone
hmm.. happens with me too. stock 4.4 with TWRP
You overreacting.
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
I see what he means.. I wouldn't call it lag, just delayed.
I did a screen record of it. It's so minimal I would never have noticed it until my attention was called to it
I have animations disabled
Not to sound rude but... this is a complaint? I get that the transition animation might look like crap and a tad choppy. In that demo at least, it does. But come on, just turn the animations off if they bother you. I've got an iPhone 5S, which is by most accounts the smoothest mobile experience, and clicking the home button takes the same amount of time (probably longer) because of the stupid fade in/out stuff.
If your complaint is a freeze up, then that's valid. But as an aside, I'm with you in that these animations are getting borderline cumbersome and stupid. The "lag" you see is Google's need to utilize these things.They used to be cool, like the first 1,000 times I saw them. Now they're just a lame hindrance to opening an app.
Sent from my Nexus 4 using xda app-developers app
Actually has nothing to do with transition animations.
It is the delay with the home button press being registered, before the animation even starts.
And actually in the video recording above, animations are off.
This is a regression. In 4.3 the home button was much more responsive, so yes it's a complaint. Actually, not really. I'm just putting the information out, and also want to see if others are experiencing the same.
I'd love it I'd you could stop watch these findings to display this massive regression.
Sent from my Nexus 4 using xda app-developers app
monkor said:
I'd love it I'd you could stop watch these findings to display this massive regression.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you can't notice the difference then more power to you. Stop posting in here.
Not to sound rude but... you're complaining about a complaint?
Out.
I was actually just hoping you would get out a stopwatch and show the difference with some stats...I mean maybe it is an issue.
Sent from my Nexus 4 using xda app-developers app
I am using factory stock with AOSP launcher (launcher3.apk from CM11) and ART enabled, don't have that problem, its very responsive.
Don't watch this if you suffer from epilepsy.
I guess sometimes there are 100ms delay, but its not abnormal. Delays tend to be because its trying to launch a new app.
I just tried Google Launcher and its not an issue either.
This should go without saying but... I'll throw it out there anyway. Because... Yeah...
For anyone watching the screen record I made.. You have to remember the overhead encoding video and writing to the Sdcard will have on the end result. ie: Performance in video may not be a complete accurate representation of real world use.
/I just wanted to use screen record and this looked like a opportune time.
I've noticed the same thing on both 4.3 and 4.4. Captured a video of mine and streamed it to Twitch since it's one of the few places that accepts and plays back at 60 FPS: twitch.tv/caiman86/b/479853664 (won't let me linkify it since I have too few posts)
Sometimes the home button is perfectly responsive and sometimes there's that strange hitch and delay when going home. The video showcases this fairly well.
morgante said:
I've noticed the same thing on both 4.3 and 4.4. Captured a video of mine and streamed it to Twitch since it's one of the few places that accepts and plays back at 60 FPS: twitch.tv/caiman86/b/479853664 (won't let me linkify it since I have too few posts)
Sometimes the home button is perfectly responsive and sometimes there's that strange hitch and delay when going home. The video showcases this fairly well.
Click to expand...
Click to collapse
That video shows the issue pretty clearly. Link (since you can't post a direct link)
Though I can't say I remember having this issue on 4.3. I could be wrong. My girlfriend has a Nexus 4 still on 4.3, so when I can get my hands on it (probably tomorrow), I'll confirm.
But even if it was in 4.3 and not just a new 4.4 issue, I still think it's worth reporting.
Also I don't actually know if this is specific to the Nexus 4. If anyone has a Nexus 7 or 10, could you please test if it happens.
Thanks.
Have you ever had a go on an s3? I had a go on my dad's and there's a huge wait after pressing home and anything happening, although admittedly this is because you can double tap home to open something (s-voice I think it was)
Sent from my Nexus 4 using Tapatalk
On S3 you must disable option (double home button klick action) in Accessibility.
On the iPhone it's almost instant whereas on Kitkat it's quite laggy.
Sent from my Nexus 4 using xda app-developers app
wilsonlam97 said:
On the iPhone it's almost instant whereas on Kitkat it's quite laggy.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Switch to ART and see the lag gone.
Tom540 said:
Have you ever had a go on an s3? I had a go on my dad's and there's a huge wait after pressing home and anything happening, although admittedly this is because you can double tap home to open something (s-voice I think it was)
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yep, it's because of the double tap command, not the same issue as this.
You are right. The delay is quite noticeable.
Related
Ok so i am trying to determine what my problem is.. here are the symptoms. When i try and end a call i sometimes have to press multiple times or deliberately press and hold the end button and sometimes it doesn't respond pretty much at all. Also i am using go launcher and when i press icons that are in the dock bar they have the same issues. I also have similar issues when i text it's really annoying so is anyone else have similar issues?
Sent from my VS910 4G using XDA App
Same here. I've noticed that to hang up it takes a deliberate double tap. Also, the screen will sometimes become inoperable requiring a reboot. This has happened three times since first getting it. One note if that out happened twice stock, and once with decrapped 1.1
Any body else seen this?
Sent from my VS910 4G using XDA Premium App
I haven't seen it anywhere else, but I have seen the double tap on the end button to end a call. Seems to happen frequently. A "feature?"
Either way, it's annoying.
Running Go Launcher as well.
To me, it seems like it takes the screen a really long time to wake up from being off, in all cases - for example, dial voicemail and put the phone to your ear. When you get the prompt to put in your PIN, take it away and the screen comes on, try to punch the dialpad button immediately and it just won't work. I tried it as I was writing this and had to triple tap the button.
Same thing with the lockscreen (still on the stock lockscreen for now). The screen will wake up and it takes a second or two to even start to register finger swipes. It's really annoying...
Speaking of phone lockup, I received a call a few days ago and the phone froze - I couldn't answer the call, or do anything, all the while the phone just kept ringing. Had to pull the battery. I'm still on the stock ROM.
Me too! I had a call and it froze. Battery pull as well. Also, forgot to mention I am using open home launcher.
Sent from my VS910 4G using XDA Premium App
Yep it's a bug either in LG's function to turn on and off the screen in Android, or the kernel drivers that enable/disable the touchscreen. There is about a 1 second delay to it.
I discovered this lovely bug while porting the AOSP lockscreen mod.
I'll run some more tests to see whether it's an android bug or a kernel bug. I'm betting it's android (something like the screen being turned on before the touch controller has had time to reinitialize itself, or something more complicated like a race condition of some kind...)
Either way, with cm7 around the corner, I don't think it's that big of a bug
thecubed said:
Either way, with cm7 around the corner, I don't think it's that big of a bug
Click to expand...
Click to collapse
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
AndroidCraig said:
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
Click to expand...
Click to collapse
Since he is the one working on getting it ported over, I think he has the best idea, and the only rule of cm is no asking for etas ;-)
Sent from my VS910 4G using XDA Premium App
My S5 seems to be possessed. Its not rooted (cant anyway) no rom, have done absolutely nothing out of the ordinary to the phone other then install my normal apps from the play store.
Yet the phone is constantly, about 20x a day just going to the 'call logs' screen. I've rebooted the phone, logged in and with nothing open poof call logs. It seems to happen more when my fingers are hovering near but not touching the screen, is there some sort of air gesture for call logs that I dont know about ? Its never any other screen, its not like its accidentally hitting the 'back' button. It is starting to get a bit annoying ..
I notice mine opens apps "on its own". Not sure if its a gestures or hover thing or what. Usually gallery or phone, which are right next to each other on my home screen (all the way left). Must have something to do with it.
trichert said:
My S5 seems to be possessed. Its not rooted (cant anyway) no rom, have done absolutely nothing out of the ordinary to the phone other then install my normal apps from the play store.
Yet the phone is constantly, about 20x a day just going to the 'call logs' screen. I've rebooted the phone, logged in and with nothing open poof call logs. It seems to happen more when my fingers are hovering near but not touching the screen, is there some sort of air gesture for call logs that I dont know about ? Its never any other screen, its not like its accidentally hitting the 'back' button. It is starting to get a bit annoying ..
Click to expand...
Click to collapse
YES!!! My Rogers (SM-G900W8) does it too! I thought it was probably because I installed something, but, now that I see you have the issue !!
I posted this same question in the Q&A section regarding the call logs. Ultimately , I factory reset my phone. That fixed whatever the problem was. It was annoying the crap out of me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
peaster3 said:
I posted this same question in the Q&A section regarding the call logs. Ultimately , I factory reset my phone. That fixed whatever the problem was. It was annoying the crap out of me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found the problem, it was my galaxy gear 2, every time it 'checked' my phone for new messages it would leave the phone on the call log. I turned off the option to open content on my phone from my gear and all is well now !
I have been experiencing this issue since upgrading to Lollipop on my S5. I too have a Galaxy Gear 2. I have just disabled 'Smart Relay' in the Gear App (which is what I presume you were referring to) and so far all seems good Thanks.
okay, this is going to be a long post.
I will recomplie all the known bugs in this thread until now.
Known Bugs:
-Galaxy Player bugs up after playing music constantly for 30 -60 minutes.
(ALL system begins to slow down, creating an unusable device, restart fixes this bug.)
-Camera takes pictures, some of them after being taken, are corrupted files.
Not sure why this happens but it happens.(Some users report this is due to the Music Player bug)
-Phone Lags on Wake-Up after using a 64gb Micro-SD. Not tested on 16 or 32gb ( using 32gb, no wake up lags )
Rare Bugs:
-Unresponsive power button, does not work anyhow, long pressing for 10 seconds = one long press.
Rebooting several times solves this. (HAPPENED ONLY ONCE) (The chances of getting this bug is the same as catching a shiny pokémon)(Some users report this is due to the Music Player bug)
- Headphonejack Bug: Contacts detect headphone still inside after submerged in water, to solve this issue: "There are 4 contacts in the jack hole. You have to touch and slightly straighten out them by needle. But first let the water to dry in the hole".
Well, Ultimately, this is to see if samsung can create the next update, fixing these issues...
Sent from my SM-G900H using XDA Free mobile app
fenchai said:
okay, this is going to be a long post.
I will recomplie all the known bugs in this thread until now.
Known Bugs:
-Galaxy Player bugs up after playing music constantly for 30 -60 minutes.
(ALL system begins to slow down, creating an unusable device, restart fixes this bug.)
-Camera takes pictures, some of them after being taken, are corrupted files.
Not sure why this happens but it happens. (the chances of this happening is like catching a Pikachu in the beginning of the game)
Not Sure if a Bug or not(Rare Bug)
-Unresponsive power button, does not work anyhow, long pressing for 10 seconds = one long press.
Rebooting 1X times solves this
HAPPENED ONLY ONCE.
(The chances of getting this bug is the same as catching a shiny pokémon)
I shall update this if any more bugs are known.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
maybe you have some issue..
i have the mobile from 16 April and i dont have any issue with my SM-G900H
neither camera neither power button..
P.S. i dont have galaxy players (deleted by root )
fenchai said:
okay, this is going to be a long post.
I will recomplie all the known bugs in this thread until now.
Known Bugs:
-Galaxy Player bugs up after playing music constantly for 30 -60 minutes.
(ALL system begins to slow down, creating an unusable device, restart fixes this bug.)
Not Sure if a Bug or not(Rare Bug)
-Unresponsive power button, does not work anyhow, long pressing for 10 seconds = one long press.
Rebooting 1X times solves this
HAPPENED ONLY ONCE.
(The chances of getting this bug is the same as catching a shiny pokémon)
I shall update this if any more bugs are known.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
These two are caused by the Music app having a memory leak...
Didn't had any issues taking pictures yet, overall I'm a happy camper.
drakester09 said:
These two are caused by the Music app having a memory leak...
Didn't had any issues taking pictures yet, overall I'm a happy camper.
Click to expand...
Click to collapse
not sure if I want to root it yet, i hate knox so much T.T want warranty but freeedom too.
well for now, there is no rom for g900h anyways, I will wait.
S5 music player is the only one that has built in streaming, so its a nice feature..
Sent from my SM-G900H using XDA Free mobile app
Tried it on two different devices and other users have had same results. Having a 64GB memory card causes the phone to take longer/lag to "wake up".
I have not tried a 128GB, but my 32GB is not as laggy. Best results is no memory card at all.
keysoh2 said:
Tried it on two different devices and other users have had same results. Having a 64GB memory card causes the phone to take longer/lag to "wake up".
I have not tried a 128GB, but my 32GB is not as laggy. Best results is no memory card at all.
Click to expand...
Click to collapse
Ok, will update post. Thanks for reporting
Hadphone jack lies that headphone is connected after 5 min. underwater trip. Repaired by needle after drying. Happend second time.
alexmeo said:
Hadphone jack lies that headphone is connected after 5 min. underwater trip. Repaired by needle after drying. Happend second time.
Click to expand...
Click to collapse
Can you tell me with details your solution?
Sent from my SM-G900H using XDA Free mobile app
fenchai said:
Can you tell me with details your solution?
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
There are 4 contacts in the jack hole. You have to touch and slightly straighten out them by needle. But first let the water to dry in the hole.
alexmeo said:
There are 4 contacts in the jack hole. You have to touch and slightly straighten out them by needle. But first let the water to dry in the hole.
Click to expand...
Click to collapse
Thanks for reporting
Sent from my SM-G900H using XDA Free mobile app
"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk
enop4 said:
"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
How often does this happen?
Did you listen to music via Sammy's music player before this happened?
How much battery did you have when it happened?
Sent from my SM-G900H using XDA Free mobile app
enop4 said:
"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Did you switch to ART?
Sent from my SM-G900F using XDA Free mobile app
Ave666 said:
Did you switch to ART?
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
No.
fenchai said:
How often does this happen?
Did you listen to music via Sammy's music player before this happened?
How much battery did you have when it happened?
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
On one day it happens like 4 times.
Sometimes this happens and I haven't been using the music player.
Sometimes 20% or even 85% always different.
When this happens there were some times the phone rebooted.
when I get free time I will reset to default and see if it gets fixed.
Sent from my SM-N900 using Tapatalk
well this is a strange bug, make sure to check if any app is interfering. wipe and try again if possible.
Sent from my SM-G900H using Tapatalk
I had all this problem too, after using music player , some of my lictures in gallery broken.
Sent from my SM-G900H using Tapatalk 2
all bugs are cleared after a small update via ota from samsung. otherwise download and install new custom rom or official
Sent from my SM-G900H
I've got some kind of unresponsive buttons bug. Btw my version is G900F.
So, when i tried to woke it up, it worked, fingerprint unlock too but then, screen nor capacitive buttons were responding. All another buttons was and screen not. After 30 seconds it's fixed itself.
Only bug I have is that the fingerprint scanner occasionally stops working completely on the lockscreen (the animation will stop and all I can do is turn screen on/off with lock button until I can restart).
This occured on multiple firmwares, although perhaps xposed might be the culprit.
enop4 said:
"Unresponsive power button, does not work anyhow, long press...."
For me when screen goes black and I want to wake up again with the power button doesn't do anything and home button doesn't work too. After a couple minutes it wakes up. Anyone with a fix?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
I can confirm this as well. It is quite frequent and very annoying. Whenever I receive any notification, I see the led blinking. I look to turn the phone on by the power button or home button, but only the capacitive LEDs light up and screen goes blank. At times I have had to wait for more than 30 seconds to get it back working or worst case I had to pull the battery and restart.
Very annoying bug since Kitkat. I now have the lollipop version installed (XXU1BOAD) in the hope that this dreadful issue is fixed.
Unfortunately it didn't. Samdung made this phone ****ty with the in house exynos processor. Please suggest some fix for this if anyone finds it.
Hey guys,
I am using my Moto X (XT1052) for almost 2 years now. It is/was the best android phone I've had so far. It was smooth, had no hangs and just did what it was supposed to do. Since I received the Update to 5.1 I keep on having real strange issues and it really bothers me because it really renders the phone useless at times. And since I couldnt find another thread with all bugs collected in one place, I am going to start my own thread.
So which bugs did I find so far?
1.Youtube and other video services don't work all the time
(They work sometimes, but the the video stops, tries to resume and ends up in a loop trying to load the video. Often only a reboot helps.)
2. Battery consumption in general has become way worse (cell-standby)
3. Random "Optimizing apps" after a reboot
4. No Active Display with handsover (I know this isn't a feature anymore, but to me this is a bug as well)
5. Missing energy widget
6. Wifi range has reduced significantly and seems to be buggy at times (can't always tell if it's my router or the phone, but mostly it's the phone)
7. Sometimes the phone uses mobile data instead of wifi, even if connected
8. Vibration mode (important notifications only) doesnt always end properly and the phone doesn't start vibrating again after the set time or alarm
I think that's it for now. But this clearly is enough for me.
So please Moto guys do something! If you need logcats or anything else, let me know and I ll help out as good as I can. I was one of those who patiently waited for an update instead of crying for one, because I wanted a stable one rather than a fast and unstable one. So either fix it, or I ll have to return my Moto X. The phone in its' current state is useless for me. Especially as I can't even downgrade without having to risk a full brick. So please do something and push an update to either allow downgrading, or fix the existing bugs!
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
Hey guys,
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I miss this very badly
"No Active Display with handsover"
Now I have to tap or take my phone to see notifications... :crying:
I switched over to CM and all is going great of course at a small cost of losing Moto voice feature but I can most certainly live without it. I've got very decent battery life of 5-6hours of screen time over a span of 13hours. No over heating issues and usually cell standby sits at 2% usage which is absolutely fine for me.. Even the hand wave gesture works with active display. I'm so happy with how stable it is with CM. Living with a bug free phone for now.
Sent from my Moto X
Random Crashes followed by optimization boot
I have been getting random crashes that lead to the phone shutting off. When I turn it back on, it takes FOREVER to optimize 92 apps. I don't have even 30 apps on the phone!
I did a factory reset and still have this problem. It's happening every couple of days. It's making my experience with this phone very frustrating!
Some more issues I've found:
Soundproblem, sometimes when I switch e.g. from twitch to spotify and then try to increase or decrease the volume, I get a crackling sound every time I push the button. Sometimes it disappears after a certain time of not playing anything, but mostly again only a reboot helps.
The phone unlocks itself more often in my pockets for no obvious reason.
The unlock on the ActiveDisplay unlockscreen often only leads to the normal unlocking screen instead of the homescreen. Same thing when I try to open notifications. Mostly those apps run, but I get to see the normal lockscreen, instead of the app with the notification.
Sent from my XT1052 using XDA Free mobile app
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
adity said:
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
Click to expand...
Click to collapse
Well that's not exactly what I would call a fix it appears to work sometimes though. I also noticed that simply changing the video quality from let's say 720p to 480p often resolves the issues. I mostly get the video bug, when I am trying to watch things in 720p or above. Maybe it is a codec problem? A broken lib?
Sent from my XT1052 using XDA Free mobile app
For YouTube, you could get another app. I stopped the cell standby issue by turning off carrier internet when not needed. Install greenify, servicely, battery saver, and power nap. 1 I too have random optimizing of apps. 2 pocket dials have increased, 3 if I tap on the phone icon from messaging app to make call to that person, I have to exit out of the SMS app before I see the call screen. 4 sometimes when I'm multi tasking I go back to another app but the app reloads and doesn't take me to where I was. 5 Google now voice only responds 30% of the time when i say hello google. Some other problems I have noticed but can't think of right now
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
Good thing I waited for a version that I could go back to kit kat because it didn't update the bootloader to lollipop. This is the thread if anyone is interested. I flashed this rom for xt1053 on my Rogers xt 1058, with only speaker phone not working away from WiFi for some reason, but that's if you flash on another moto x besides xt1053. http://forum.xda-developers.com/showthread.php?t=3155843
1. Battery drain (cell standby) makes the phone unusable.
2. WiFi does not connect or only works rarely now.
- download two times on whatsapp
- dialler doesnt dial a call
Sent from my XT1052
Cell Standby Battery drain is the worst..
Randomly restarting and optimizing apps has been a huge problem as well.
I miss the wave to wake for active notifications...
But what I really hate about 5.1, is that when using wifi my mobile radio keeps active all the time...
This drains the battery while being on wifi...
Funny enough, when I'm on mobile data, everything is ok and mobile radio is active only when needed by the apps...
On wifi on the other hand, oh man... it's active all the time...
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.