I switched my newer Dell laptop from Windows 11 to Mint 22 recently, and wanted a desktop app for ADB. I used to use adblink for Windows which worked fairly well but there was no option for Linux.
A brief search for an ADB gui for Linux revealed a program called AYA. Tried it out and was pleased with it. The program is a .Appimage which is like a Windows .exe. It's a standalone app so it works wherever you decide to put it. AYA has more features than adblink. I think it's easier to use as well.
Of course you can always use ADB from the terminal but this is easier and more fun IMO. Just thought I would share this for any Linux users out there.
Here is a screenshot of logcat with uidroid running
A week ago I upgraded from a V6.x to V7.1.260616. It was working fine for a week but now I have no guide data as of 10am this morning. I'm guessing it was running off the guide data that was downloaded prior to the upgrade and that ran out.
It appears that it just no longer updates. A manual update does nothing, and I haven't changed anything else.
It should be pulling the guide data from the HDHomeRun tuner.
EPG sources shows a "Silicon Dust EPG" and below it DVB/ATSC EPG. I can't delete the Silion Dust EPG, delete butotn does nothing.
If I look under channels I can see all channels are mapped to the DVB/ATSC EPG.
I've tried all the usual stuff, reboots, service restarts, manual EPG updates etc.
I am a long time user, current version 7.1.1.260616, about 3 days ago I noticed there was a noticeable slowdown when selecting programs to record or playback, then recordings started to fail, either they didn't finish recording or when I tried to playback they would play a portion of the recording then just close, I could replay and go to same spot (no Resume available) and play, but it would stop again. Then I started to get messages "Recording service stopped during recording" Then the App started to lock up and had to be rebooted, Then the web browser"localhost8866" would fail with "Can't find" error, I can reboot and everything works for about an hour then the failures start again.
I checked the disks, they seem to be ok, I recorded and played back using WinTV, everything OK, I tried running Setup again, don't think it did anything. If I try to playback recordings from NextPvr on another windows viewer they have the same problems.
Summary
I am running the latest ARM64 Docker image of NextPVR on a Raspberry Pi 5.
The DVB-C scan succeeds and channels are imported correctly, but Live TV and recordings always fail with:
Code:
No tuner was available for the requested channel.
The DeviceHost logs show:
Code:
Failed to get tuning params for (...) from /config/adapterX-DVB-C-channels.conf
The file is either never generated by NextPVR or the DeviceHost expects a different format than the standard DVBv5 tuning files.
Environment
Hardware
Raspberry Pi 5
8 GB RAM
Hauppauge WinTV-dualHD (dual DVB-C/T/T2)
USB 3.0 connection
OS
Code:
Linux dino-pi 6.18.33+rpt-rpi-2712
Debian 13 (Trixie)
64-bit ARM
Kernel:
Code:
Linux dino-pi 6.18.33+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.18.33-1+rpt1
works perfectly, the tuner and driver appear to be functioning correctly. The failure seems to occur only when DeviceHost attempts to resolve tuning parameters for live streaming.
Thank you for your help.
Hi, hope someone can advise me. I have the Hauppauge 3875199 wintv quad HD Pcie tuner, installed with Windows 11, with the latest drivers. This tuner is a DVB-T2 tuner, yet Nextpvr detects it as only DVB-T, why is that?
I'm trying to get ITV4 HD, but I can only get it in SD, Google AI suggests I need a DVB-T2 tuner? I can get other HD channels. So what can I do, to rectify this? I've attached the log files, hoping they'll help.
I have been running various versions of NextPVR in a Docker container for a while and yesterday added a new disk to my existing installation to give me some additional recording space . I restarted the docker container and all seemed well. Just for completeness I had a look around the various persistent storage locations to see that things were appearing where I thought they should be. My Docker Compose file looks like:
The 'recordings' is disabled by choice, all my recordings are saved to folders within the 'local' folder for later post-processing, which is working fine.
Checking the Config folder (/mnt/disk1/npvr/config) I seem to have a load (currently 24) files named core.nnnnnn where nnnnnn is variable number between 876 and 115076 all dated between 17:55 and 17:56 yesterday which is when i restarted the container.
NextPVR seems to be running correctly with no other issues I am aware of. What might be creating these files and can I get rid of them ? This might have been happening for a while, I just haven't seen these files before now.
I have been using your "New Client" for very many years as my default Nextpvr client. A few weeks ago there was an update which added a new startup screen listing "New recordings", Recordings" & "Upcoming". Unfortunately the writing a bit too small to read at my normal viewing distance. It also added a "Channels" menu option which I have no use for.
No mention of the update on the Web page to v 2.10.1. I dont think there has been an actual update for quite a few years as it just works OK!
I am trying to add channels to my HDPVR2 device. After going to Settings->Devices and clicking the HDPVR2 device, the current channels are listed. I click Import Channels and expect to see the list of channels downloaded from my SD account but the only change is a box showing "loading...". No list. I can only cancel. This happens for all my devices.
I've done this before with no problems. I can log into my SD account so I believe my credentials are OK.
