Posts by cayoenrique

@jenseneverest

Any little help is really appreciated. Just pointing me to a direction is of big help.

I know, sadly we are all feed always with complete solutions, never teach how to create, adapt or build.

Now I am no expert neither, my knowledge goes as far as running full Linux Debian inside Android. Now long time ago I did some help my self in Android phone theater. So I am custom on bricking thing and repairing them back. ;)

In general I have hard time buying from common stores. They do not seems to want to ship to my area. For example world-of-Satellite.co.uk do not want to ship to my area, others as well. That leave me with Chinese models at alliexpr3s. I plan to play myself with GTMedia GTCOMBO. Best reason it is been said it has sensitive tuner. There other hidden advantages.

Now Been Chinese manufactured device, I expect no help from neither manufacturer nor any mayor enigma team. They seems to exclude each other. So it is more or less to see how far I can get. And sure learn at the process.

From your post.

1) You seems to suggest me to start with OpenATV.

2) You seems to suggest Kernel/drivers are going to be use at OE alliance .

OE alliance!!! Very interesting I did not expect that. It is NICE to know. I do not have to start with Eningma 2. But instead, with OE alliance. IIt is a very nice hint you have gave me. It should simplify my test process as to just running to a Linux kernel prompt.

After that I guess I will see if I can tune to a signal. Something like installing Debian dvb-utils package and tuning using


scan/dvbscan: scanning tool used to generate channel lists

szap: tuning utilities DVB-S

dvbsnoop: To record some signal

And I am very happy for it. See I got some directions. Lets see how far I get.

So @jenseneverest or to all others. If you guys have more good hint PLEASE let me know. I am very open to suggestions. Will keep looking at this thread for more help.

1) I do not know where should I place this thread. This was best of I can figure out. Please move to proper section if this is out of place. Thanks.

I want to know if we have users of Enigma 2 that can help me porting any Enigma2 to a new Android device. What is needed?

For example, If I build for Linux PC,

1) I go to github,

2) clone a repo,

3) make install

4) at the end enigma2 run on top of Linux kernel, just as any other Dvb application.

So if I try to imagine what is needed, then I guess I need kernel sources with drivers for the device.

I know, Normally on Linux/Android we do not get open sources for drivers. Instead drivers are binary blobs with extra firmware that need to be compiled for a specific kernel.

I suspect an Enigma 2 will require similar approach.

2) In general I plan to test by booting from external SDcard. Leaving original Android firmware as it is.

Boot any useful information on multiboot it is appreciated. For now I am studding using Tasssadar's multirom approach.

Any help Thanks in advance.

@rush1

I mention 4.2.2, just to show there are hobbyist that will love that. Yes a powerful CPU. GTCombo has an average CPU. New GTXCOMBO has a better CPU/Memory capabilities.

Just to be clear.

In my case

I like current CTCOMBO as it is: AU BISS, MARS and LACAM capabilities. Like I said I do not have one but plan to have one for near future. About ALL I like the fact that have a sensitive tuner. And that has an affordable price. For the future, I will like to have this unit running multi-boot bootloader. So that I can run ALSO Enigma E2 on it. So I can have the BEST of BOTH Worlds. A close firmware with all its features, PLUSS an open source E2 for all my regular needs.

Other previous post

Clearly MOST if not all that posted earlier where Interested in just running E2 to make this receiver respond Faster. Some are even tire of having to constantly reset / power up the unit. It is known that Android receivers get in trouble because they allow a bunch of none essential programs to run ALL at same time, witch finally result in running out of memory or even CPU capacities. You may ask then: Why Android? Because there are more Android users that love the easy to use and how easy to add new applications. Yes, for those users E2 is a complicated thing!!

So hopefully we can convince GTMedia to allow us to get kernel and drivers as this should not be hard for them. Hopefully in the following weeks I will receive my unit. And if others agree we could find a way to multiboot to the external SDCARD. And from there we can try to develop E2 or even convince some of the current firmware developers to include this unit in their builds.

GTMedia

PLEASE give us a chance by providing kernel + driver sources. Thanks in advance.

Quote from jenseneverest

Indeed the tuner is sensitive on weak signals, 4.2.2 is useless unless a very low bitrate feed.

If the manufacture could provide :

an e2 boot partition, dvb drivers, a patch for icam.... and access to its biss server....it could be a great little box (i wont hold my breath lol )

Please focus, Lets do it step by step. Easy part first. And in any case what Linux Kernel licensee require: Kernel sources and drivers

Preferable posted at github so any one can start from there.

Quote from GTMedia

....we don't have the resources to start over with Linux...

Just in case you have not realize. Android runs on top of Linux Kernel. So you do have the kernel sources on your hand right now. I guess there will be also a need for any special command we may be required to address for you particular Tuner/demodulator/frontend model or any other vendor specific device.

Listen, most likely GTMedia may not need to even get involve, The kernel sources and its drivers can come from the manufacturer that provides your boards or even the manufacturer of the tuner and any other special/specific device that is not part of mainland Linux.

I do not own a GTMEDIA GT COMBO jet. And there is little found on the net. But I had run across some good thread, like one in UK where a bunch of guys report that the COMBO have a pretty sensitive tuner, one that picks transponders and opens channels where other best sold receiver fail to pick! Plus they seems to like 4.2.2 limited capabilities, one that no other ARM device is capable.

I also found Russians forums where they seems pretty interested as with US/EU do not let them buy from America or Europe.

Finally is an affordable device to purchase.

What is missing is that is close source. If we could at least get the basics Kernel/device drivers/vendor blobs then this can easily become a very popular device.

Here my grain of salt for E2 development.

Linux license require all manufactures to Post Open Sources for their Linux kernels. Sure many manufactures opt to not provide opens sources for private drivers, but instead they do supply private closed source binary blobs. And most manufactures opt to post WORKING kernel sources on github together with vendor specific extra requirements.

Once the sources are in github the Satellite community pick ups the work of developing none official firmware like E2.

There is no rocket science on this. Only willingness for a specific manufacturer to join what the rest of the satellite community does.

We will assume you are still a newbie to forums. Most forums have rules against asking same thing in different threads, I know an innocent error. You start introduction with a question instead of presenting your self. So be careful not to go against forum rules.

I already say I am no expert in Card Sharing. But we all know that now this days Cards are Pair or we said they are married. What this means is that before the card even try to work it first check if it is inside the Box was sold with!!! This means that in general Card Sharing should never happen.... Well people went to the difficulty to find how is the pairing process so that the card can finally be fool to play out of the box.

Ok so why I am yelling you all this? Because you keep asking:

Quote

when i insert in the conax card into slot the channels remain blank screen .

You can not expect a CARD to work in any unknown box just because you insert the card in it.

Lets take the simplest of all pairing. A pairing done in another Vendor Official authorize receiver, Yes lets saying switching from same model box. Lets use SKY sample( NOT conax) , we where given this tutorial

How to pair your viewing card online

See even to use a Card in another same model box requires you to pair the card. That is the process you need to find out how is done for conax.

Another hint, II guess djalanga ask that question in june.... Best you can do is sent him a PM see if he found the answer. Good luck.

I see you initiate a conversation.

Quote

hello mate,what should i do after introductions ?

But I do not have experience in that area. Sorry.

Most important thing to do is to read Forum Rules. You do not want to ask wrong question.

Well best you can do after you start your request for help in a thread is... Yes wait some time for an answer.

Now you can still do your assignment! How? You use the Search button.

Search "conax"

Conax pairing-card

Now to be honest I have seen very litle in pairing cards. I guess the rules of forum prevent it. see admin master G responce in

Conax pairing-card

Quote

Without the RSA key and Box key you won`t be able to view a conax card with oscam in the dreambox.

There is no forum support for rsa key extraction. If someone wants to PM you the information they are free to do so.

I hope you get the answer you are looking for. I do not have expertise in this area.

Normally your 1rst post should be an introduction, create a post in this area => Introductions

Regards you request to be a friend. You are an exact example of why I do not believe in "Likes" or "Friends" or joining any type of group. This Web culture have it ALL WRONG. Se you have not even presented and you already wanted have many friends. HEHEHEHE. Listen do not get me wrong. I even will accept that as courtesy. But this takes away or make useless the idea behind it. And I even will say welcome and I hope you become my best friend in reality in the future.

But regards this Web Culture this is wrong people. See Thank Button for the most part is not used. And That my friend reflects appreciation of the help you received. See the difference, one reflects what happens after a positive action. The other is like joining a gang on a bad neighborhood. People join because are force..

Advertise as E2, but can it run Android?

Where its official support forum? If private please send by PM.

Where can I locate the Source Code?

Since a few days has pass and you had posted very little, lets resume where we are.

You all ready have the oscam build solution you had ask. A specially build with patch for your box. Because our friend fegol posted that solution on #97. I assume that as always you tested. It is just you forgot to tell us.

SOOOooooo, at this moment we are only having fun...

Empty? That's weird. You must have a dvb device.

Again. As last script, this is to be run inside your Android TV Box.

#!/system/bin/sh
su
ls /dev -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/ /' -e 's/-/|/'

This will print the full tree.

I just came to check and saw I wrote bash, wicth is good for Ubuntu, or even Android with busybox. Problem is that I am not usure /system/xbin/bash will be see as /bin/bash

so just change script to

#!/system/bin/sh
ls /dev -R | grep "dvb"
ls /dev/dvb/adapter0

Sorry for the confusion.

Upsss!!!

I guess I was wrong....

See

_https://www.linuxtv.org/docs/dvbapi/dvbapi.html

DVB Frontend API

DVB Demux Device

DVB Video Device

etc

are part of dvbapi.

But still, I will expect that a well design driver should account for the standard. I guess we need to go deep in the patch to see what part it modify in order to know better.

1) Do not forget to test my file again, but when you test my file, you need to edit

"/storage/sdcard/OSEbuildOSCam/conf/oscam.server"

and comment or deleted the part for the slot card reader Like i posted? To commerny you place a "#" at the first line.

#[reader]
#label                         = myslot
#enable                        = 0
#protocol                      = internal
#device                        = /dev/hi_sci
#boxid                         = *
#detect                        = *
#mhz                           = *
#cardmhz                       = *
#aeskeys                       = *
#group                         = *

2) I see your analogy but that is not how I believe all works.

See you should have a physical dvb device hook to I guess PCI. A "Linux driver" will make that device to show as

/dev/dvb0.frontend0 or /dev/dvb/adapter0.

Then TVHeadend will control the dvb device using /dev/dvb0.frontend0 or /dev/dvb/adapter0/frontend0

And TVHeadend will pickup ts Video at /dev/dvb0.dvr0 or /dev/dvb/adapter0/dvr0.

At this level I do not believe dvbapi is used.

I believe dvbapi will be use(see <==>) if needed between TVHeadEnd and oscam. Like in;

Video Payer <-- TVHeadend <==> oscam_emu or the other way

Video Payer <-- oscam_emu <==>TVHeadend

I think oscam may also used it for the readers. Like if you use your internal slot or a cccam/newcamd server.

So if you had both the latest svn oscam and TVHeadend then no trouble should be shown with dvbapi.

3) sh is simple

#!/bin/bash
ls /dev -R | grep "dvb"
ls /dev/dvb/adapter0

Also can you show us what is the dev been used for dvb on your box. Can you do

ls /dev -R | grep "dvb"

As example in ubuntu a USB PCSAT will show like this

$ ls /dev -R | grep "dvb"
dvb
/dev/dvb:
/dev/dvb/adapter0:

and inside adaoter 0 we have

$ ls /dev/dvb/adapter0
demux0  dvr0  frontend0  net0

Be aware that it is know that in Android many dvb devices show like

/dev/dvb0.frontend0
/dev/dvb0.demux0
/dev/dvb0.dvr0
/dev/dvb0.dvr0
/dev/dvb0/ca0

what your box show?

We seen the patch. We know it is making changes to oscam dvbapi files. What I am saying is, if you leave all config as is I bet you may need that.

But I still wonder why do you need that?

What part of the program needs "(dvbapi) ... Hisilicon{1}."

I am no expert on oscam nor you had said what/how you use it for. My best guess is the Internal Slot Card Reader. Well the question is still up.

When you test my file, did you went to "/storage/sdcard/OSEbuildOSCam/conf/oscam.server" and comment or deleted the part for the slot card reader Like i posted?

#[reader]
#label                         = myslot
#enable                        = 0
#protocol                      = internal
#device                        = /dev/hi_sci
#boxid                         = *
#detect                        = *
#mhz                           = *
#cardmhz                       = *
#aeskeys                       = *
#group                         = *

I bet you if you do you will not have any trouble.

Now the other area is TVHeadEnd. If TVHeadEnd may have an old protocol and maybe that is the reason for the patch.

In any case, I bet you that patch if not needed if you have an update TVHeadend and so not use the Internal Slot Card Reader.

I know you say "Bear with me a bit" I will be arround. Just keep testing and send me a PM in case you need extra help. But our buddy fegol has been given time after time good orientation and in this time even patched files. He is the champion here.

As I said I been doing mechanics work on my truck, witch took much of my time. I am trying to say that I had little time lately. And in general have no time to look at the hilsilicon file mismatch from oscam svn files.

Now that a patch has been provided. We all can see if the dog is male or not.

Now looking at the patch I see it is making changes to oscam dvbapi files. This seems to agree with DANNYPS4 constant request of a patch needed. See the way I seen is that many pcsat devices handle most of the requirements with internal hardware and the drivers takes care of the rest. Yes just plug & play. Similar to hooking a mouse to your PC. the driver takes care of the issues. No need for special patches. So I was under the assumption we should try oscan from svn first to see what was needed. But real explicit feedback from DANNYPS4 was limited.

Now after seen this patch, I started to wonder on previous reading on mothern Arm CPU / GPUs capabilities and licenses. The original comments where that even when modern GPU did in fact had new Ultra HD capabilities, the fact was that at request of the authorities their decryption capabilities where crippled. I wonder if this patch requirement have something to do with that. That will also explained why the manufacturer did not wanted to post new oscam patch. Just to avoid any legal license bridge with ARM/GPU. In general as my oscam knowledge is very limited I guess I will need help on that.

Boy I had learn a lot in last month. PC Emulation of ARM/MPS, oscam, Andoid issues on Version 5 or greater and a lot of more stuff. It is strange how in this forum most people interest is just dedicate to offering binaries or requesting them. Little to do with teaching & learning. I do appreciate the help of fegol, nozorrog and many others that makes the difference.

fegol

Waooo! Impressive. You seems to had done the whole solution; patches, scrips, lib & include. I can not test as I do not have that box. But I have no doubts it should work. Lets see what DANNYPS4 reports. From my part a Big Thanks.

@nozorrog

I did try your suggestion using adb via TCP. Works very nice in Android 5.

As I said I stop using it long time ago because at the time I thought It was a security risk leaving adb/tcp always on.

In android 5 there is no default . Instead we have to manually open it by doing in Android Terminal. I did create a sh for easy access.

su
setprop service.adb.tcp.port <port>
stop adbd
start adbd

where <port> is the assigned new port number.

So as I said it can be DEACTIVATE is simply by doing .

su
setprop service.adb.tcp.port -1
stop adbd
start adbd

Thanks again for this useful tip as my drobear is giving me some issues.