This is a Mailman mailing list bounce action notice:
List: baseband-devel
Member: vmj(a)linuxbox.fi
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman(a)lists.osmocom.org.
Hi fellows.
There's been awhile since I've attended osmocom meetings in Berlin - seems like the
idea went extinct cause people are not interested in meetings for the sake of
meetings (at least without beer :)
So how about revitalizing that? Personally I'd love to attend hackathon in Berlin to
work on some osmocom-related stuff:
- there are tons of patches pending review for months
- some branches awaits to be merged/tested/rebased
- documentation always needs more love
- that cool thing you've wanted to work on since forever
What do you think?
I mean, yepp, it's summer but come on - we're all geeks with no social life anyway
;-) And yepp, there are those customers waiting for that code to be delivered
yesterday... but it might be fun to work together on something for the sake of it :)
OsmoDevConf is cool but it's only once a year. I think we got enough density of devs
in here to make smaller-scale local event - if the devs are interested of course.
--
best regards,
Max, http://fairwaves.co
This is a Mailman mailing list bounce action notice:
List: baseband-devel
Member: luca.bongiorni1(a)studenti.unimi.it
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman(a)lists.osmocom.org.
This is a Mailman mailing list bounce action notice:
List: baseband-devel
Member: osmocom(a)ninoc.nl
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman(a)lists.osmocom.org.
Hi,
I am having trouble understanding the decoding of SI3_REST. I have
highlighted the code below
if (bitvec_get_bit_high(&bv) == H)
s->si2ter_ind = 1;
else
s->si2ter_ind = 0;
Here it says that si2ter_ind is set to 1 if its high. From this can I
conclude that System Information Type 2ter is available ?
I am asking this because the following code says that System
Information Type 2ter is present
/* all relevant system informations received */
if (s->si1 && s->si2 && s->si3
&& (!s->nb_ext_ind_si2 || s->si2bis)
&& (!s->si2ter_ind || s->si2ter)) {
LOGP(DCS, LOGL_DEBUG, "Received relevant sysinfo.\n");
/* stop timer */
stop_cs_timer(cs);
But gsmdecode output says that its not present as per the below snippet
SI 3 Restoktett
0 Selection Parameters not present
0 Power Offset not present
1 System Information 2ter Indicator not present
1 Early Classmark Sending Control present
1 Scheduling if and where not present
1 High: GPRS indicator = present
I have referred GSM 04.08. But there also I am not able to understand it.
Regards,
RM
Dear Baseband developers,
We are a very small group of XDA developers and external people trying
to realize our Android based IMSI-catcher Detector (AIMSICD) project.
http://tinyurl.com/l6whse2
However, to realize such an ambitious feat we really need better access
to the various RF variables and details of neighboring cells, among many
other things. We have had partial success in that we're able to use the
ServiceMode (SM) menu from the Samsung ServiceMode application. However,
this is just a wrapper to accessing OEM_RAW_REQUESTS presented by code
that is part of the baseband FW. Now, the tricky part for us non-GSM
experts, is understanding what these variables really mean and represent.
I have started 2 threads on XDA to:
1) completely map out the ServiceMode menu options, for an GT-I9195
(S4-mini) but should work on many similar and newer Samsung devices.
2) To map out the various MM timers and many other RF/GSM variables
shown and available in the SM menu.
http://tinyurl.com/qgcmbsv
We need help from the baseband community to understand the vocabulary
used in this information as presented in (2) above, so that we can start to
fill in the catcher-catcher detection parameters from the table here:
https://opensource.srlabs.de/projects/mobile-network-assessment-tools/wiki/…
We will be using a modified version of this to do our detection.
I'd also like to invite anyone interested to participate in this free and
open
project. Everything we have done so far is available on github. There are
also some hidden documents available to motivated developers who have
shown an honest effort to help us out.
Best Regards,
E:V:A
--
View this message in context: http://baseband-devel.722152.n3.nabble.com/Documenting-Samsung-Radio-variab…
Sent from the baseband-devel mailing list archive at Nabble.com.
Hi all
I've recently have to use libosmocore from cmake-based project.
In order to make it easier to use via simple find_package(libosmocore) I've created
attached file. It's follows the example in cmake wiki which uses pkg-config to get
proper paths and flags.
The question is - shall we try to install it into CMAKE_MODULE_PATH while installing
.deb package for example or shall I try to push it to cmake's modules repo?
Another approach would be to generate libosmocore-config.cmake directly with correct
paths and options at compile-time and supply that instead of relying on pkg-config.
--
best regards,
Max, http://fairwaves.co
Hi.
I'd like to add LTE support to GSMTAP in libosmocore. How shall I proceed?
Just add
#define GSMTAP_TYPE_LTE 0x0d
to include/osmocom/core/gsmtap.h and appropriate sub-types, than send patch?
--
best regards,
Max, http://fairwaves.co