2015-11-09, 09:39
Welcome guys, I signed up here as well.
I can confirm that the problem that uboot was corrupting hdcp keys has been fixed (koying I've just mailed you a zip file with a rom without hdcp, you can flash it copying the recovery.img from that zip and the zip itself to a microsd card and booting pressing the pinhole, then choosing apply update from -> sd -> zip and doing a factory reset before rebooting).
The newer builds should also include all the apps I did for WeTek, like the new launcher, the new WeUpdate that is not slow as **** like the stock Amlogic upgrader app (I had put that app there temporary because I knew was crappy but I also knew I was going to code a brand new one), the selector for which app enabling the 24p video mode.
The new setup wizard is already included if I'm not wrong (I saw the welcome screen on cnx's review).
Yesterday I completed a Tvheadend helper app that needs to be coupled with a flashable zip file that includes the drivers built from linux-media git few weeks ago and it requires root permissions because it has to load the required drivers for the plugged in tuner, you can flash supersu zip using cwm for the Core.
Android has nothing like udev to try to automatically load the required driver when you plug in something so I had to rely on parsing "modules.alias" to read the vip/pid and busybox's modprobe to load the driver.
That modprobe, though, fails to attach the frontend so it requires some user interaction to add the frontend kernel module to the app's settings (no manual insmodding though, once added the app will load it), it supports passing options by adding them to /system/etc/modprobe.conf (i had to add "options dvb_usb_dib0700 force_lna_activation=1" to that file for the Nova-T Stick).
It's not rocket science and if you search on LinuxTV wiki (or just pay attention to the dump of dmesg.txt that I create on the sdcard when a frontend is not found you can see a "cannot find XXX_attach" and most of the time the driver is just "XXX").
You can enable automatic start at boot, enable oscam, enable acl or anonymous access... and there's an option that will hold a wakelock (preventing the device from going into standby) when tvh is running.
As stated in that option I strongly recommend keeping it turned on because the kernel doesn't take nicely that.
It also doesn't like the unplugging of some devices, even with the server turned off (that will also unload the loaded modules), it panics randomly. It happens with the dvb-usb-dib0700 based but not with the dvb-usb-af9015 one (I have these two dvb-t usb sticks at home and both work).
My suggestion is, anyway, to not unplug it from Android if the kernel driver had been previously loaded (like if tvheadend was running). Just reboot to recovery and unplug it from there
Here you can see some screenshot of this new app: http://imgur.com/a/d7HOu
I work on Android roms since few years but I just recently started studying app development and those apps are my first creations so if there are any bugs or suggestions I will try to make things working right.
I can confirm that the problem that uboot was corrupting hdcp keys has been fixed (koying I've just mailed you a zip file with a rom without hdcp, you can flash it copying the recovery.img from that zip and the zip itself to a microsd card and booting pressing the pinhole, then choosing apply update from -> sd -> zip and doing a factory reset before rebooting).
The newer builds should also include all the apps I did for WeTek, like the new launcher, the new WeUpdate that is not slow as **** like the stock Amlogic upgrader app (I had put that app there temporary because I knew was crappy but I also knew I was going to code a brand new one), the selector for which app enabling the 24p video mode.
The new setup wizard is already included if I'm not wrong (I saw the welcome screen on cnx's review).
Yesterday I completed a Tvheadend helper app that needs to be coupled with a flashable zip file that includes the drivers built from linux-media git few weeks ago and it requires root permissions because it has to load the required drivers for the plugged in tuner, you can flash supersu zip using cwm for the Core.
Android has nothing like udev to try to automatically load the required driver when you plug in something so I had to rely on parsing "modules.alias" to read the vip/pid and busybox's modprobe to load the driver.
That modprobe, though, fails to attach the frontend so it requires some user interaction to add the frontend kernel module to the app's settings (no manual insmodding though, once added the app will load it), it supports passing options by adding them to /system/etc/modprobe.conf (i had to add "options dvb_usb_dib0700 force_lna_activation=1" to that file for the Nova-T Stick).
It's not rocket science and if you search on LinuxTV wiki (or just pay attention to the dump of dmesg.txt that I create on the sdcard when a frontend is not found you can see a "cannot find XXX_attach" and most of the time the driver is just "XXX").
You can enable automatic start at boot, enable oscam, enable acl or anonymous access... and there's an option that will hold a wakelock (preventing the device from going into standby) when tvh is running.
As stated in that option I strongly recommend keeping it turned on because the kernel doesn't take nicely that.
It also doesn't like the unplugging of some devices, even with the server turned off (that will also unload the loaded modules), it panics randomly. It happens with the dvb-usb-dib0700 based but not with the dvb-usb-af9015 one (I have these two dvb-t usb sticks at home and both work).
My suggestion is, anyway, to not unplug it from Android if the kernel driver had been previously loaded (like if tvheadend was running). Just reboot to recovery and unplug it from there
Here you can see some screenshot of this new app: http://imgur.com/a/d7HOu
I work on Android roms since few years but I just recently started studying app development and those apps are my first creations so if there are any bugs or suggestions I will try to make things working right.
