Hi Tarmo,
Once a proper database is used, this mostly goes away as an issue. We
did add the SPN field to MBPI schema in the olden days. The problem
is that nobody actually updated the MBPI database to take advantage of
this.
Hmm, maybe my memory is faulty (it has been ~9 years now), but I
Hi Denis,
On 12.03.20 16:49, Denis Kenzior wrote:
Hi Tarmo,
I don't see how am I going to solve this. The end user cannot
configure the device (there's no user interaction whatsoever). I could
not find the mythical Android database at the time (I do now - it's at
Hi Cristophe,
On 12.03.20 17:51, Christophe Ronco wrote:
In my case automatic provisioning always fails:
- the database has multiple entries for basically every
operator/country
mbpi is just not a very good database. It provides lots of
duplicates and doesn't distinguish by spn last I
Hi Tarmo,
On 3/12/20 2:22 PM, Tarmo Kuuse wrote:
> Hi Denis,
>
> On 04.03.20 20:49, Denis Kenzior wrote:
>>> In my case automatic provisioning always fails:
>>> - the database has multiple entries for basically every
>>> operator/country
>>
>> mbpi is just not a very good database. It provides
Hi Tarmo,
I don't see how am I going to solve this. The end user cannot configure
the device (there's no user interaction whatsoever). I could not find
the mythical Android database at the time (I do now - it's at
Hi Denis,
On 04.03.20 20:49, Denis Kenzior wrote:
In my case automatic provisioning always fails:
- the database has multiple entries for basically every operator/country
mbpi is just not a very good database. It provides lots of duplicates
and doesn't distinguish by spn last I checked.
