Hi Dominik

Can you explain how what did you use to access Secure element?
Which methods , which file?

Because permission may depend on how you are accessing it.

Regards,
Ajith

On Thu, Jan 20, 2011 at 2:21 AM, Gruntz Dominik <[email protected]>wrote:

>  in the mean time I received my nexus-s. I tried to access the secure
> elements, but android returns an error message
>     java.lang.SecurityException: WRITE_SECURE_SETTINGS permission
> required:
>     Neither user 10058 nor current process has
> android.permission.WRITE_SECURE_SETTINGS.
> Giving this permission to my app did not help. Probably only system
> processes are allowed to accesss this functionality.
> Dominik
>
>
>  ------------------------------
> *From:* Ajith Kamath [mailto:[email protected]]
> *Sent:* Dienstag, 18. Januar 2011 04:12
> *To:* Gruntz Dominik
> *Cc:* Android Developers
> *Subject:* Re: NFC Secure Element
>
>   I still dont have nexus s but there is a high probability that its
> Embedded
>
> Yes Keys are private and most likely needs to be provided by Service
> Provider. The same thing has been mentioned in nokia forum
> But I am not sure  how this will be done for nexus S.(may be there are ties
> with Service Provider)
>
> If anyone can explain OTA agent and its communication with TSM, it would be
> very helpful. Since this too is not clear (w.r.t android)
>
> Regards,
> Ajith
>
>
>
> On Tue, Jan 18, 2011 at 5:41 AM, Dominik <[email protected]> wrote:
>
>> According to the NXP documentation of PN544, three SE variants are
>> supported:
>> - SIM Card (via UICC)
>> - Embedded (SmartMX security chip)
>> - SD Card
>>
>> Do you know which version is intended to be used by the Nexus S
>> device?
>>
>> The above messages describe attempts to enable SmartMX. As soon as
>> access to this SE is possible:
>> Which keys do you use to access the SE? Such keys should be private
>> and not generally be known.
>>
>> I am at a loss.
>>
>> - Dominik
>>
>
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to