I've been trying hard to figure out what may be causing this anomaly. When I play a file, the file plays fine but if I stop the video, the file won't resume. It will start from beginning. In Video Settings, there is a default select action. I've tried toggling from play to choose to resume but that too does not help. Any insights please. The kodi version I'm on is:
kodi-20141213-88f9fb0-master-armeabi-v7a.apk
you using a nightly build. its going to have bugs, even says so on the site "Nightly Builds are made on a daily basis and contain the most recent changes. These should be considered unstable for daily usage and should only be used for to help us find possible issues to provide more stable monthly builds and in the end a stable final release." try the release candidate ver http://mirrors.kodi.tv/releases/android/arm/kodi-14.0-Helix_rc3-armeabi-v7a.apk
pbanj said:
you using a nightly build. its going to have bugs, even says so on the site "Nightly Builds are made on a daily basis and contain the most recent changes. These should be considered unstable for daily usage and should only be used for to help us find possible issues to provide more stable monthly builds and in the end a stable final release." try the release candidate ver http://mirrors.kodi.tv/releases/android/arm/kodi-14.0-Helix_rc3-armeabi-v7a.apk
Click to expand...
Click to collapse
Agreed. I was hoping there is a selection somewhere that could help me fix that. The release candidate has issues with the .ts file playback and I was impressed that they fixed that with the Nightlies.
pbanj said:
you using a nightly build. its going to have bugs, even says so on the site "Nightly Builds are made on a daily basis and contain the most recent changes. These should be considered unstable for daily usage and should only be used for to help us find possible issues to provide more stable monthly builds and in the end a stable final release." try the release candidate ver http://mirrors.kodi.tv/releases/android/arm/kodi-14.0-Helix_rc3-armeabi-v7a.apk
Click to expand...
Click to collapse
Even with the RC3, I cannot get it to resume. Is there a setting somewhere for this?
i dotn remember having to set that in settings maybe do a full reset on kodi and see if that fixes it, maybe some data got messed up. im using rc3 and its fine
pbanj said:
i dotn remember having to set that in settings maybe do a full reset on kodi and see if that fixes it, maybe some data got messed up. im using rc3 and its fine
Click to expand...
Click to collapse
I finally redid the whole thing with the version you suggested and it works with the file list and the movies but I cannot get it to resume now on the Recent Movies Added. Those too used to work with Gotham. Any suggestions? appreciate your help.
Does your kodi resume from recently played?
well i just tested it and on the stick it resumes from the library list but not from recently added, on the box it wont resume at all
side note: im pretty sure my install on the box is screwed up as when it goes to the next video instead of having loading in the bottom corner its tiled across the screen
pbanj said:
well i just tested it and on the stick it resumes from the library list but not from recently added, on the box it wont resume at all
side note: im pretty sure my install on the box is screwed up as when it goes to the next video instead of having loading in the bottom corner its tiled across the screen
Click to expand...
Click to collapse
Interesting at least I'm not the only one. Do you know if there is a db or a cache I can clean up and try it out. Here are my findings.
1. If I started the movie playback prior to changing the settings to resume from xbmc/settings, that movie will always restart and won't show up the resume button no matter what setting I change.
2. If I play the movie for the first time from the library after the setting has been changed, the resume button pops up just fine. but the earlier movie will start from beginning.
3. The recent resume works fine with xbmc gotham.
Was hoping to know if there is a db or some config I could change or clear to test out this theory. I've already cleared my whole library and restarted it but the problem still persists.
navigates said:
Interesting at least I'm not the only one. Do you know if there is a db or a cache I can clean up and try it out. Here are my findings.
1. If I started the movie playback prior to changing the settings to resume from xbmc/settings, that movie will always restart and won't show up the resume button no matter what setting I change.
2. If I play the movie for the first time from the library after the setting has been changed, the resume button pops up just fine. but the earlier movie will start from beginning.
3. The recent resume works fine with xbmc gotham.
Was hoping to know if there is a db or some config I could change or clear to test out this theory. I've already cleared my whole library and restarted it but the problem still persists.
Click to expand...
Click to collapse
Its a known issue:
http://forum.kodi.tv/showthread.php?tid=210480
navigates said:
Its a known issue:
http://forum.kodi.tv/showthread.php?tid=210480
Click to expand...
Click to collapse
I've gone back to the nightlies for 11/28 and the resume with .ts files works perfectly fine. I'll stick to this version. Hope this helps someone.
kodi-20141128-44c2e69-master-armeabi-v7a.apk
Thanks for the 28/11 nightly tip, I was on RC3 too and this was driving me mad on AFTV
Tried various skins and couldn't figure out why it wasn't saving resume sometimes
Related
Sometimes when I launch Super Hexagon, the game runs terribly slow. It feels like it's running at 15-20 FPS instead of 60 FPS. The weird part is that this lag persists after I exit the game. The whole system becomes super slow with choppy animations.
I've tried killing the app and even clearing the data, but the only thing that seems to fix this is a reboot. I can reproduce this behavior after rebooting again. It usually happens on the 2nd or 3rd time I launch the app, but sometimes it can take up to 10 times of closing and launching. Holding the tablet vertically seems to trigger it faster (although I'm not completely sure if it's related yet).
I'm running completely stock KOT49H and version 1.0.5 of Super Hexagon.
I haven't been able to reproduce this on my Nexus 4 or my old Nexus 7 (2012).
Can anyone else confirm that this happens on their Nexus 7 (2013)? I'm just wondering if it's a bug/compatibility issue or if it's a problem with my device
Just a quick update: Tried changing to ART with and flashing the latest franco kernel (just to experiment), and it still happens in the exact same way
Eregoth said:
Just a quick update: Tried changing to ART with and flashing the latest franco kernel (just to experiment), and it still happens in the exact same way
Click to expand...
Click to collapse
I know this is a late response but I had the same thing happen to me twice tonight and I found your thread while googling for the issue myself.
Force closing the app doesn't help. It seems I have to reboot to fix it.
Have you by any chance figured out a fix? I'm running a 2013 n7 completely stock
chiefz0r said:
I know this is a late response but I had the same thing happen to me twice tonight and I found your thread while googling for the issue myself.
Force closing the app doesn't help. It seems I have to reboot to fix it.
Have you by any chance figured out a fix? I'm running a 2013 n7 completely stock
Click to expand...
Click to collapse
Haven't found a fix yet
It's clearly a software issue though, either with the game or the latest N7 2013 build. Maybe someone who's more skilled could check the debug log (or something) to figure out the cause.
Hey
EDIT:
to fix this problem, open your favorite file explorer..
navigate through android/data/(superhexagon package file name)
go to settings.dat
change vsync from 1 to 0
NsZebra said:
EDIT:
to fix this problem, open your favorite file explorer..
navigate through android/data/(superhexagon package file name)
go to settings.dat
change vsync from 1 to 0
Click to expand...
Click to collapse
Just tried this and it happend again (on the first try). Rebooted and triggered it again after launching the app 3 times.
Eregoth said:
Sometimes when I launch Super Hexagon, the game runs terribly slow. It feels like it's running at 15-20 FPS instead of 60 FPS. The weird part is that this lag persists after I exit the game. The whole system becomes super slow with choppy animations.
I've tried killing the app and even clearing the data, but the only thing that seems to fix this is a reboot. I can reproduce this behavior after rebooting again. It usually happens on the 2nd or 3rd time I launch the app, but sometimes it can take up to 10 times of closing and launching. Holding the tablet vertically seems to trigger it faster (although I'm not completely sure if it's related yet).
I'm running completely stock KOT49H and version 1.0.5 of Super Hexagon.
I haven't been able to reproduce this on my Nexus 4 or my old Nexus 7 (2012).
Can anyone else confirm that this happens on their Nexus 7 (2013)? I'm just wondering if it's a bug/compatibility issue or if it's a problem with my device
Click to expand...
Click to collapse
I confirm, the only solution is to reboot... Very annoying if it happens while you break a record
Wow, I am astonished by Google. It has been over a year now and this problem STILL exists, I am having the exact same problem as described in the OP with several apps. How come this problem gets so little attention? Should be well known by now.
All those fancy design changes but who cares about actual system stability.
^What apps? I've never had this problem and this is my first time reading about it.
It's up to the app developer to keep their **** updated to work well with new versions of android. Nothing to do with google.
yosmokinman said:
^What apps? I've never had this problem and this is my first time reading about it.
It's up to the app developer to keep their **** updated to work well with new versions of android. Nothing to do with google.
Click to expand...
Click to collapse
No way apps are supposed or even able to mess with the whole system like that and this bug doesn't happen on other devices like nexus 5 with the same apps so it's obviously just the device. I mean did you even read the thread you ignorant prick? The thread creator said too that he can't reproduce it with other devices such as Nexus 4 or Nexus 7 2012.
Hello,
Just a couple of quick questions regarding Netflix, maybe it only involves a simple fix. Went through and got cm11 running very smooth on the ouya. No hiccups, bugs, or major setbacks with anything. Everything that I use seems to be working fine, except for Netflix.
It loads properly and seems to work, but ever since I hit the "expand" button in the lower right corner, it won't back out of full screen. It would pull any controls whether I click on screen or press any buttons on my keyboard. The only way to back out is by pressing ESC on my keyboard.
I've tried uninstalling/reinstalling the app, rebooting after logging in, deleting the data/cache from the app, also tried installing a couple of older apk's(3.0 & 2.4?) And the problem is still there. Granted its such a minor setback in a huge breakthrough overall, but I was just wondering how to fix that.
Factory reset? Maybe just a bug with Netflix for android? I don't have any other means of trying this out. Regardless, cm11 has brought new life into this console, thanks !!
Sent from my XT907 using Tapatalk
Yeah, apparently that's normal behavior for us CM11 folks.. (Actually not sure if it's the same in stock ROM because I didn't try it on stock)
I get the same thing no matter what controller or remote I try. It seems like Netflix doesn't recognize or acknowledge player control / commands on the device or ROM. It does respond to 'left' and 'right' arrow commands for rewind a scene/chapter and skip, respectively, however... But to pause you have to hit 'Back' or 'Esc' and hope it actually picks up in the same spot you exited out of the video stream... I don't seem to mind it so much compared to the other issue I'm seeing: Sometimes the video gets stuck or freezes on a frame, but the audio will continue. The video will eventually catch up, but apparently it occurs most often when another device is using just a bit of Internet bandwidth... However, my WDTV box seems to handle that much better. I'm assuming because I never see Netflix do any buffering on the Ouya, and I don't see any setting that helps with that.
I managed to get netflix on a stockplus ROM. I honest don't remember how the controls were, didn't use it much. I also don't remember which apk it was, other than it had a black loading screen.
Overall, its not a deal breaker, since I mainly use xbmc, but having netflix would be a plus. Are all netflix apk's responding that way? On the cm11, I mean.
Sent from my XT907 using Tapatalk
You can just go to the Play Store and install the "regular" Netflix app on CM11. Works like any tablet version would with a controller.
brandogg said:
You can just go to the Play Store and install the "regular" Netflix app on CM11. Works like any tablet version would with a controller.
Click to expand...
Click to collapse
I've tried that and it seems to retain the full screen setting, which is the problem in question. Even after uninstalling it & reinstalling it, from the play store.
Plus, how do you sync an ouya controller to cm11? That's not that important since I've been using the k400, but to play gta it would be nice to know.
Thanks dude
If you've flashed the zip with all the button layouts, pairing the controller is as simple accessing the Input and Controllers menu, and holding down the U on the Ouya controller until it enters pairing mode. I know I'm missing a step in the menu, but its there, you'll see it. Promise
Sent from my K00C using XDA Free mobile app
Hey, when the Youtube app update that enabled 1440p quality playback came out i had the same problem, when you select a resolution it doesnt apply it, its like the app is always in auto quality mode. I read that you should uninstall updates and then install the newest version and that solved the issue for some time but now i have the same issue again. Does anyone know how to solve this?
Same issue here. I hate that I can't use 1440p. I've tried to uninstall updates but that didn't work. Anyone out there who knows how to fix this???
BentCleanson said:
Same issue here. I hate that I can't use 1440p. I've tried to uninstall updates but that didn't work. Anyone out there who knows how to fix this???
Click to expand...
Click to collapse
The app itself updated today but the issue is still there.
Hey guys, I found a solution for my tablet at least. The problem for me was Viper4android, I had changed the driver from power saving to high quality, reverting to the power saving driver seems to have solved the issue for me.
try to clear the apps data in setting application youtube and see if it stick.
Clearing those didn´t help.
Last time's solution (Clear Data and cache, Uninstall Updates, turn off and then turn on and Install updates from Play Store) is not working this time, very frustrating.
My solution didn't seem to stick and now I have the same issue again.
Mine suddenly began working, at third attempt. I cleared cache and data, Uninstalled updates, force stop, then I went to the play store and download the new updates, when I tried the first video it didn't seem to have worked, but I exit YouTube and the next time I tried it worked.
Only thing I think I did different is that I didn't disable the app before download the updates.
erasat said:
Mine suddenly began working, at third attempt. I cleared cache and data, Uninstalled updates, force stop, then I went to the play store and download the new updates, when I tried the first video it didn't think to have worked, but I exited YouTube and the next time I tried it worked.
Only thing I think I did different is that I didn't disable the app before download the updates.
Click to expand...
Click to collapse
I found that it didn't stick when I selected it but after a few seconds of the video playing it changed to the new setting.
Here's a quick fix: after you tap the 1440 display button drag the time bar back to the beginning of the video and it will begin playing in the higher resolution.
Reckoning said:
Here's a quick fix: after you tap the 1440 display button drag the time bar back to the beginning of the video and it will begin playing in the higher resolution.
Click to expand...
Click to collapse
That doesn't seem to work for me every time.
Crypticpest said:
That doesn't seem to work for me every time.
Click to expand...
Click to collapse
Sorry, best I could do.
I'm trying the newest YouTube version, 5.10.3.4 (not yet in the playstore) and the issue is still there.
My Netflix sucks big time on my rooted fire TV. Stutters quite a bit. No combination of the video frame rate helps in the settings. What more can I do? I shouldn't have to wipe cache and restart every hour to get smooth playback. Thanks
supremekizzle said:
My Netflix sucks big time on my rooted fire TV. Stutters quite a bit. No combination of the video frame rate helps in the settings. What more can I do? I shouldn't have to wipe cache and restart every hour to get smooth playback. Thanks
Click to expand...
Click to collapse
Netflix has been terrible on aftv. Between the loading to 99%, and "unable to play this title right now" not to mention that atv2 has a much better resolution (for me anyway).
I was experiencing a stutter and I think I switched to WiFi to fix it. Not 100% on that but its working better now.
KLit75 said:
Netflix has been terrible on aftv. Between the loading to 99%, and "unable to play this title right now" not to mention that atv2 has a much better resolution (for me anyway).
I was experiencing a stutter and I think I switched to WiFi to fix it. Not 100% on that but its working better now.
Click to expand...
Click to collapse
How'd you fix the two issues you mentioned? Netflix just started doing the same, for no apparent reason about a week ago on my FTV. I found one that here that was said to have the fix, but I've performed each of the steps listed there with no luck. Right now, I'm on 51.1.6.0... I tried the latest, but am affected by the HDCP issue, so had to roll back.
JediSooner said:
How'd you fix the two issues you mentioned? Netflix just started doing the same, for no apparent reason about a week ago on my FTV. I found one that here that was said to have the fix, but I've performed each of the steps listed there with no luck. Right now, I'm on 51.1.6.0... I tried the latest, but am affected by the HDCP issue, so had to roll back.
Click to expand...
Click to collapse
Not sure I did fix it. It may have got better on its own. You could try uninstalling Netflix, clear data 3 times in Amazon video, unplug for 10 seconds. Then it may be beneficial to boot recovery and wipe dalvik and cache partitions. Finally reinstall Netflix.
Mine occasionally doesn't load all the way but restarting the video fixes it.
KLit75 said:
Not sure I did fix it. It may have got better on its own. You could try uninstalling Netflix, clear data 3 times in Amazon video, unplug for 10 seconds. Then it may be beneficial to boot recovery and wipe dalvik and cache partitions. Finally reinstall Netflix.
Mine occasionally doesn't load all the way but restarting the video fixes it.
Click to expand...
Click to collapse
I don't know what the deal is, but I've tried all of the suggested fixes, but continue to get the same error message. I'll wait for pre-rooted 51.1.6.3 and see if that fixes it.
JediSooner said:
I don't know what the deal is, but I've tried all of the suggested fixes, but continue to get the same error message. I'll wait for pre-rooted 51.1.6.3 and see if that fixes it.
Click to expand...
Click to collapse
Sorry. Overall Netflix on Amazon has been terrible for a lot of users while others seem to have no problems at all. They're not likely to provide a fix but it doesn't hurt to contact Amazon. At the very least you'll join a growing list of dissatisfied customers. Problem is Amazon points the finger a Netflix and vice versa. But like I've said before, Netflix has always been fine on my other devices going back almost a decade.
KLit75 said:
Sorry. Overall Netflix on Amazon has been terrible for a lot of users while others seem to have no problems at all. They're not likely to provide a fix but it doesn't hurt to contact Amazon. At the very least you'll join a growing list of dissatisfied customers. Problem is Amazon points the finger a Netflix and vice versa. But like I've said before, Netflix has always been fine on my other devices going back almost a decade.
Click to expand...
Click to collapse
Yeah, the part I don't get is that it just stopped working for no apparent reason. It'd been working fine for months, then all of a sudden I start getting the "can't play video at this time" error (something to that effect). Anyway, thanks for the suggestions and feedback.
JediSooner said:
Yeah, the part I don't get is that it just stopped working for no apparent reason. It'd been working fine for months, then all of a sudden I start getting the "can't play video at this time" error (something to that effect). Anyway, thanks for the suggestions and feedback.
Click to expand...
Click to collapse
If it's any consolation... on 51.1.x.x versions of Fire TV, I never had issues where it wouldn't play video, but I did have studdering and slow/fast issues. On the 51.5.3.0 Fire OS 5 preview, all that has gone away and aside from an issue with 5.1 sound which is solved by putting it on stereo, netflix is working great.
KLit75 said:
Netflix has been terrible on aftv. Between the loading to 99%, and "unable to play this title right now" not to mention that atv2 has a much better resolution (for me anyway).
I was experiencing a stutter and I think I switched to WiFi to fix it. Not 100% on that but its working better now.
Click to expand...
Click to collapse
I agree. Netflix performance actually gotten worse on the Fire TV since the latest official stable update. For months I been using it and it was fine but now once again I have issues where the video would freeze up for about 5 to 10 seconds then speed up right away everyone is super fast while the audio continues. Very annoying as I thought they finally fixed it but it came back again. Now I also been getting the "unable to play title" error again too.
I actually started to use my Apple TV 3rd Generation which is connected to Wifi 5ghz channel 36. Loads programs quickly, no stuttering, no unable to, no credit shrinking.
I've learned that having another video app open while trying to access Netflix is what causes the problem. The reason rebooting fixes it is because you essentially flush the FireTV's memory when you do the reboot. If you exit out of other apps fully, you shouldn't have anymore problems. I miss being able to click the Home button when switching between video apps but ever since I started doing a proper shutdown for video apps before switching to the next one, I no longer need to reboot to get the different video apps work.
JediSooner said:
Yeah, the part I don't get is that it just stopped working for no apparent reason. It'd been working fine for months, then all of a sudden I start getting the "can't play video at this time" error (something to that effect). Anyway, thanks for the suggestions and feedback.
Click to expand...
Click to collapse
That message occurs when you have another background application tying up the video process.
Try rebooting. And never use the home button to exit Kodi or any other video application. Quit it properly. And watch out for SPMC, the way it's been implemented to minimize to the home screen with the back button is really unhelpful on the AFTV.
Same goes for using Kodi as a launcher. Don't expect it to be reliable.
Claude Koch said:
That message occurs when you have another background application tying up the video process.
Try rebooting. And never use the home button to exit Kodi or any other video application. Quit it properly. And watch out for SPMC, the way it's been implemented to minimize to the home screen with the back button is really unhelpful on the AFTV.
Same goes for using Kodi as a launcher. Don't expect it to be reliable.
Click to expand...
Click to collapse
Hadn't considered that possibility; however, I don't use an alternate launcher and I always shutdown Kodi properly. Maybe there's something else tying up the video process? I've gone through the 'clear data' process on Amazon Video multiple times, but that didn't fix Netflix. I'll try to go straight into Netflix after a fresh reboot and see what I get.
I've been using Ghostrace with a Polar H7 and Jaybird Bluebud X headphones. While running and listening to offline Google Play music, about 30-40 minutes into my run, the songs start to get cut short and a new one starts, then, eventually, everything freezes and I have to reset by holding the button. My ghostrace logs are recovered and I am able to get all my stats, but they are broken and not very useful. Also, doing this 3-4 times during a long run is REALLY counter productive. My songs, even from the beginning of a run, seem to not finish completely before it moves on to the next one. It is rather annoying when you are expecting your song to continue and it just stops mid way and a new one starts.
I've done a factory reset and re-downloaded all my music and it still seems to be happening. A
Any suggestions?
Getting worse now. Can only run about 10-15 minutes and it starts to happen and then freezes. Factory reset watch. Cleared cache on phone and redownloaded and installed everything. Still happening.
Hi, just trying to figure out whats causing this bug, though yours sounds different in that you have to reset. I've seen other reports of it just resetting on its own.
Anyway, what version of Ghostracer do you have? You can see on the watch, on the 3rd page down. Just wanting to find out if its a new problem I've created or if its something to do with the google play update the last month.
Cheers
Craig
cjkiller said:
Hi, just trying to figure out whats causing this bug, though yours sounds different in that you have to reset. I've seen other reports of it just resetting on its own.
Anyway, what version of Ghostracer do you have? You can see on the watch, on the 3rd page down. Just wanting to find out if its a new problem I've created or if its something to do with the google play update the last month.
Cheers
Craig
Click to expand...
Click to collapse
0.9.2
Don't really have a problem with Ghostracer. It seems to work fine. It appears to be a bluetooth issue (leaning this way since I started experiencing issues transferring files from my phone occasionally) or google play music issue since many times I haven't been using Ghostracer when the issue occurs.
Is it possible that sweat is the culprit? I have heard of people having problems with sweat during their runs messing up their SW3 - that's because although the SW3 is water-resistant, that applies to fresh water only, not salt-water like sweat. Try running with a sweat band under your watch and see if that solves the problem.
Colinmb said:
0.9.2
Don't really have a problem with Ghostracer. It seems to work fine. It appears to be a bluetooth issue (leaning this way since I started experiencing issues transferring files from my phone occasionally) or google play music issue since many times I haven't been using Ghostracer when the issue occurs.
Click to expand...
Click to collapse
Thanks for your info Colinmb, I was going crazy thinking I had broken something in the latest beta. So it looks like its a bluetooth problem created in the last update of the wear app/google play update, which came out around the 7th of November I think. Might make a post on the Sony site, see if anyone cares.
Problem solved with latest Google Play Services update.