Pik TV is a big disappointment and nightmare
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
This thread's discussion is locked. If it doesn't give you the information you need, head to its forum board for active discussions or to start a new discussion.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
1 Year
4 different Pik TV boxes
4 all never worked for me and all Telus did was keep sending me new boxes.
Issues - to get is to work I have to unplug every night and reboot every day to access shows. 2-3 times per week I have to factory reset because Pik TV can’t be accessed. This is the biggest kicker. Telus forces you to access Netflix only using their technology but every time I use Netflix I am forced to factory reset after EVERY use. Needless to say I will be leaving Telus and returning to Shaw
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Find a post useful, please click on "Like" to give the author recognition or mark as an accepted solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
This looks like a defective box. I would recommend to contact support and get it replaced.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
no, this is not hw related. it's a common problem and it occurs on both of my boxes.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello
Same problem here. Newest software version. Since almost two years Pik TV is available on the media box. Actually not really because it's still not working the way I expect it to work. Needs some user action like reset or unplugging at least every second day, goes back into sleep mode after about 90 minutes into a new movie when watching Life TV, etc . Unfortunately I do not know where the real problem is. Being it providing inferior hardware as some people state or being it developers just simply unable to get a software package running without the most basic errors.
I'm using the box connected through cable, wireless off, static IP and I have no other apps loaded. The pre-installed YouTube app works flawless and so does my ROKU on the same subnet, so I'm leaning towards software that is not capable to handle the task. A company like TELUS should have access to people who can handle a job like error free streaming on an Android TV box.
Clint
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Just to be sure, by "shutdown and reboots", you mean the full box reboot including seeing the 2 red LEDs at the front of the box and the "android" boot animation, right? Not just the Pik TV app restarting (the animation looks like the boot animation, so it may look like a reboot).
Full reboots are usually caused by hw things like power supply and overheating. Android usually takes care of killing misbehaving applications so they don't take down the system. I have been using the box for 2+ years and seen many issues, but sudden full reboot is not on my list, but my usage patterns may be different than yours. If you find any sequence that helps reproducing, I can give it a try on my box.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hi dominiol
No, it's not a full hardware reboot/restart. Since YouTube works fine I tend to blame the Pik TV software or the feeding channel. 95% of the time I'm watching Knowledge so I don't have to mute the annoying ads others are trying to feed me with.
Error 1: When I start watching Live TV at 7:00PM and not changing channels, then at 10:20PM more or less the screen goes black. Without interaction it changes to the Android background. If I press Ok on the remote Live TV continues. This error appears regularly if one sequence is longer than an hour, saying it starts at 8:00PM and is supposed to run till 10:45PM or so (Fridays, Saturdays and Sundays on K). It also happens randomly.
Error 2: I'm watching Live TV and suddenly an error message appears in the middle of the screen saying something like the application has to restart, reload or whatever. Sorry can't remember precisely. I get a choice of Ok or Cancel. Hitting either or not doing anything brings the app back on track after a while. From the looks I would say it is from the system. This happens on different Live TV channels.
Error 3: Channel surfing - After some channel changes, carefully letting the system settle each time after the change, the app locks up. When I'm lucky I can go Home. Settings, About, Restart and the app restarts. If I'm not so lucky and the system is completely frozen then the only option is a power cycle.
I'm on PureFibre 25 with 30 Mbs download, wireless completely off, static IP and no others using the connection. The box is fully updated to the newest version.
Marcel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
WORKAROUND FOUND.
The solution to the netflix red/gray static issue with freeze/audio and then reboot is to roll back to the last version of Netflix build 2424. The latest build 2440 is causing this issue. As to whether this is Telus or Netflix as the root cause, it's up to them to figure it out.
If you don't want to install from an unknown source like apkmirror.com, then just uninstall the update and it will revert back to the embedded ROM version build 1965.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Sorry, jumped the gun, build 2424 also crashes. Will try an even earlier build later.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
@clint17 wrote:No, it's not a full hardware reboot/restart.
Good, that means the Android logs could potentially provide useful info about the crash and the events leading to it. Do you know how to extract Android logs? It can be a bit tricky, but I can help you do it if you are interested.
Like Android phones and tablets, the Pik TV box allows app developers to run and debug their own apps, but also to look at the system logs. To do that, you need to enable developer mode by clicking 7 times on the line that says "Build" in the Settings > "About" menu. (This is not specific to Pik TV, it's the standard Android way of enabling developer mode.) This will add the "Developer options" submenu to the Settings. In the "Developer options", enable the "USB debugging" to allow remote access. Then go back to "About" > "Restart".
Although the settings called it "USB debugging", it's actually going to be network debugging, because the Pik TV doesn't have the USB debug port that are usually on Android phones. Note your Pik TV's IP address, you'll use that to access it.
On your computer, you'll need the "adb" executable from the Android platform tools to connect to the device. (https://developer.android.com/studio/releases/platform-tools.html)
They are also included in the Android Studio installation if you feel like trying app development 😉
Once you get adb, all you need to do is "adb connect <ip>" where <ip> is your Pik TV's IP address. Then you'll see a popup on the TV asking if you authorize access. After that, "adb logcat" will show you what is happening on the box. You can scroll back and see what happened.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello dominiol
First thank you so much for this excellent tutorial. I will try it out and see if I can get results, and I will stay in touch with you.
Have a good day
Marcel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Managed to capture the crash, thanks for the instructions.
Excerpt:
01-18 22:42:37.012 2969 3193 V Avrcp : MediaController playback changed: PlaybackState {state=3, position=2022576, buffered position=0, speed=1.0, updated=91277524, actions=570, custom actions=[], active item id=-1, error=null} 01-18 22:42:37.368 6062 6062 I chromium: [6062:6062:INFO:CONSOLE(94)] App ID: CC32E753 " [ 0.017s] [cast.receiver.CastReceiverManager] Version: 2.0.0.0078", source: https://www.gstatic.com/cast/sdk/libs/receiver/2.0.0/cast_receiver.js?google_cast_bg=true (94) 01-18 22:42:37.371 6480 6496 I chromium: [6480:6496:INFO:media_capabilities_bindings.cc(323)] CanDisplayType type=video/mp4; codecs=hev1.2.4.L153.B0; eotf=smpte2084 (unsupported eotf: smpte2084) -> false 01-18 22:42:37.371 6480 6496 I chromium: [6480:6496:INFO:media_capabilities_bindings.cc(237)] CanDisplayType type=video/mp4; codecs=dvhe.04.06 (unsupported media format) -> false 01-18 22:42:37.380 6062 6062 I chromium: [6062:6062:INFO:CONSOLE(301)] App ID: CC32E753 "document.registerElement is deprecated and will be removed in M73, around March 2019. Please use window.customElements.define instead. See https://www.chromestatus.com/features/4642138092470272 for more details.", source: https://www.gstatic.com/cast/sdk/libs/receiver/2.0.0/cast_receiver.js?google_cast_bg=true (301) 01-18 22:42:37.527 6480 6496 I v8 : [6480:0xace03b80] 796 ms: Scavenge 1.7 (3.3) -> 1.5 (3.8) MB, 5.2 / 0.1 ms (average mu = 1.000, current mu = 1.000) allocation failure 01-18 22:42:37.599 6480 6496 I chromium: [6480:6496:INFO:html_media_element.cc(514)] HTMLMediaElement(0x2ac03210) 01-18 22:42:37.622 6062 6062 I chromium: [6062:6062:INFO:CONSOLE(1)] App ID: CC32E753 "[eme_polyfills.tester]", source: https://cast.scdn.co/castless/867e539/main.js?google_cast_bg=true (1) 01-18 22:42:37.682 2476 4507 V PlayReadyDrmFactory: createDrmFactory >> 01-18 22:42:37.682 2476 4507 V PlayReadyDrmFactory: isCryptoSchemeSupported >> 01-18 22:42:37.694 2476 4356 V PlayReadyDrmFactory: createDrmFactory >> 01-18 22:42:37.694 2476 4356 V PlayReadyDrmFactory: isCryptoSchemeSupported >> 01-18 22:42:37.694 2476 4356 I PlayReadyDrmFactory: isContentTypeSupported >> mimeType = video/webm 01-18 22:42:37.694 2476 4356 I PlayReadyDrmFactory: isContentTypeSupported >> mimeType = video/webm Supported 01-18 22:42:37.709 2478 16009 I MediaPlayerService: MediaPlayerService::getOMX 01-18 22:42:37.711 6062 6511 I OMXClient: MuxOMX ctor 01-18 22:42:37.713 2478 3089 I OMXMaster: makeComponentInstance(OMX.broadcom.video_decoder) in mediaserver process 01-18 22:42:37.713 2478 3089 V bomx_android_plugin: OMX_GetHandle(OMX.broadcom.video_decoder) 01-18 22:42:37.716 2478 3089 I bomx_video_decoder: NEXUS_Platform_SetHeapRuntimeSettings(3:0xce07e900, open) on decoder open -> success 01-18 22:42:37.818 2478 3560 W bomx_video_decoder: BinderNotifyDisplay: New frame (22088) arrived but previous frame (22087) hasn't been displayed yet! 01-18 22:42:38.081 2478 3089 I bomx_video_decoder: NEXUS_Platform_SetHeapRuntimeSettings(12:0xceb64000, open) on decoder open -> success 01-18 22:42:38.083 2507 2507 W NEXUS : nexus_statistics_module: platform[Default] nexus/base/src/nexus_base_scheduler.c:949 251 msec 01-18 22:42:38.083 2507 2507 W NEXUS : nexus_statistics_module: sage[Default] include/linuxkernel/driver/nexus_driver_body.h:155 354 msec 01-18 22:42:38.088 2507 2507 E NEXUS : Error at nexus/modules/security/src/nexus_security.c:249 01-18 22:42:38.090 2507 2507 I NEXUS : nexus_platform_core: Detected SECURE MEMC ARCH violation. Terminating.... 01-18 22:42:38.408 2470 2801 I AudioFlinger: BUFFER TIMEOUT: remove(4100) from active list on thread 0xa5283680 01-18 22:42:43.421 2440 2814 E bcm-hwc : [chpt]: time out waiting for 5000 ms 01-18 22:42:43.421 2440 2814 E bcm-hwc : [chpt]: checkpoint error: 10 01-18 22:42:43.421 2440 2814 E bcm-hwc : [ext]:[blit]:18446744072333991520:213703:213702: failure to blit. 01-18 22:42:43.421 2440 2814 E bcm-hwc : [chpt]: checkpoint error: 10 01-18 22:42:43.422 2507 2507 E NEXUS : Error (0xa) at nexus/modules/graphics2d/src/nexus_graphics2d.c:1329 01-18 22:42:43.422 2507 2507 E NEXUS : Error (0xa) at nexus/modules/graphics2d/src/nexus_graphics2d.c:1329 01-18 22:42:43.622 2440 2814 E bcm-hwc : [ext]:[frame]:213704:213703:grabbing framebuffer FAILED!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello dominiol
Error #1 happened at 22:05PM. I have logs from 20:00PM till 22:40PM (3 files) which might be of interest for you. Please let me know where to send them.
Marcel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Find a post useful, please click on "Like" to give the author recognition or mark as an accepted solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Without checking specs, I am going to assume Apple TV has more RAM, which probably improves the menu interface for PikTV, which is always clunky.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Thanks for the crash log @DanielK. The log excerpt you posted will likely reboot the whole system (after ~30 seconds). I would like to reproduce this on my box. Can you describe the sequence leading to this?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello @clint17, please check in your logs at the time of the error if you see a line with the "F" (fatal) prefix, followed by a few lines that all start with "at ". The "at " lines are the stack trace (the details of which function called which function to trigger the crash)
For example: https://developer.android.com/topic/performance/vitals/crash#reading_a_stack_trace
Try to narrow-down to a section around the crash and post that section here. Note: usually one crash will trigger other crashes afterwards (dependencies), so please try to focus on the first crash around that time.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello dominicl
Thank you for your response. I did search for Fs (3rd column after the time) but there are none. Instead there are lots of Es. What baffles me is that the system starts "dropping outstanding frames" long before it finally stops and goes to dream background. Somehow it gets out of sync in a long program sequence (Netflix error after 90 mins comes to mind). These long sequences are mostly between 21:00PM and 23:00PM on K. Therefore the error happens usually around 22:30PM.
I have a full 1Gb connection from the ONT to the box. YouTube on the box and other streaming services on the Roku work without errors.
I have a good file (0.5 MB) from yesterday with 10 mins before and 10 mins after the error which happened at 22:33PM. I would like to make it available to you to see because I have no idea how PikTV is supposed to work and I have no idea how to get parts of the file on the forum screen.
Marcel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello dominicl
You can see the file from yesterday here:
https://drive.google.com/file/d/1B_Hcfb9-DlsMSwqEY19Xy18Co_9lP6wN/view?usp=sharing
There are two big error sequences at 22:27PM and 22:32PM, but only the second one ended in the system going to sleep. Pressing ok 5sec later got it back to work.
Marcel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hi @clint17,
There is an idle timeout in Android for going to sleep. I don't have my box with me, but it's in the screensaver settings (aka daydream). Is it set to 5 minutes by any chance? That would explain the delay between 22:27 errors and the 22:32 sleep. Usually, playback applications will hold a "wake lock", which prevents it from sleeping even when the timer expires. However, it looks like the Pik TV app may have lost its wakelock along the way. The log doesn't give any hint (to many silenced lines due to "chatty" app). You can see around 22:32 Android goes to sleep intentionally:
01-19 22:32:23.698 2811 2913 I PowerManagerService: Nap time (uid 1000)... 01-19 22:32:23.710 2811 2885 I DreamManagerService: Entering dreamland. 01-19 22:32:23.712 2811 2885 I PowerManagerService: Dreaming...
A quick-and-dirty hack is to enable the "stay awake" option (Developer option). This will hold a separate "wake lock" independently of the Pik TV app, and will prevent your box to sleep, unless you actively press the power button.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello dominicl
My settings:
Screen Saver: 30mins (default, max 1 hour)
Put Device to sleep: Never (default, equals max)
I'm gonna try Stay awake and will report back in about a week. Thanks for looking into the problem. I'm concerned by the frame mix up and if there
might be a flooding of the box.
Marcel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
By the way, does anyone know what happened to this thread? It used to be called « Box randomly rebooting (not just on Netflix) » and turned into something rather depressing.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
@dominicl wrote:
By the way, does anyone know what happened to this thread? It used to be called « Box randomly rebooting (not just on Netflix) » and turned into something rather depressing.
Either a moderator changed the title, or the original poster did.
Possibly it can be corrected......
If you find a post useful, please give the author a "Like"
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
Hello dominicl
For me it did not happen Sun and yesterday. It always happened on uninterrupted sequences longer than 90min and between 22:00 and 22:45. The next window to watch will be next Fri and Sat. Then I will watch the program on my phone too to see if they die together, or if its only the box. Later on I will also replace all my equipment (2 ER-X with 2 subnets each) with the Telus supplied 3200 and only attach the box to it.
Does anybody know more about Sasktel who use the same box for their 'cheap' IPTV?
A moderator named DRU moved 2 of my posts into the 'depressing' one. Why?
Marcel
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
yes thats correct, the box then reboots to the pik loading screen.
After booting up, i start netflix, and sign in as necessary. Then i watch a video from anywhere of 1m to 1hr and it will reboot in between. Netflix just launched a new build 2 days ago and I'm testing it now.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content
update: crash hasn't occurred since the new build.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Link to Post
- Email to a Friend
- Report Inappropriate Content