Apparently, the Titan is the first WP7 phone that has SIM Toolkit (STK) support. For those of us who live outside the US, SIM Toolkit is an indispensable application. It allows to use mobile banking applications (extremely popular in Indai, China and Africa).
So this begs the question, is STK natively baked into WP7 and currently disabled (via some hidden registry setting) or is just available on the Titan. I have tried to get a straight answer from Microsoft but nothing yet.
Can those lucky enough to have a Titan try to find the registry setting that enables the STK?
Related
So I was looking at the manual for HTC Hero for Sprint and they have ASR included in it. What it does is allow voice recognition for voice dialing. I was wondering if it's possible to implement this in a future ROM update?
Sprint's HTC Hero is running Android 1.6 (Donut) which has ASR. When 1.6 comes to the European Hero, I am sure it will be possible.
There's no good reason why voice dialling isn't already available on the Hero.
Voice dialling always was available on US T-Mobile G1s. As I understand it, it wasn't included in UK G1s because it had a hard time understanding the "English" english accents, but when I had my G1 (sourced in the US) the problem wasn't with my accent - it was that it was trying to "force" the number to be a US format phone number.
Regards,
Dave
Hey everyone, my name is Ian. I'm kind of new here, at least in a participatory role as wiki master of the Photon 4g's Sunfire dev team/collaboration. I have some talent in the world of web coding, but I'm useless at real programming.
I also have a rather nasty addiction to the world of flight simming, mostly as stand in for real flight time that I'm trying to orchestrate as I work towards a private pilot's license. Anyways, my program I use for flight simulation is X-plane and lacks in 3rd party applications that it can interface with, especially on the Android side. I would like to help to put together an Android app that can work with the sim and control basic functions. My current goal is to control radio systems and autopilot functions. To interface with the sim, I plan to use the Simulator Control System which is based on the CAN Aerospace protocol. This is cross sim application, so whatever works with X-plane will also work with Microsoft flight sim. I've been looking at the website, http://cross-simulator.com/, and I think that this seems like a fairly easy task. All the functions and commands are well documented and supported (there is even an example android code), I just don't know how to start. If anyone in this great community has some advice, I'd love to hear it because I really have no clue.
Thanks, and happy dev'ing
I would just download the example, import it in Eclipse and run it on the Android emulator (assuming you have downloaded and installed the Android SDK). Later, you can tweak the example code as you become more comfortable.
Hi guys,
we will have to buy a new phone for my visually impaired sister during next year (or maybe much earlier), because she is currently unable to use her simple Nokia (unable to read SMS messages on display etc.).
I tried to find any simple phone with voice output for her, but the only one possible candidate was Samsung Haven, which was only available for U.S. mobile networks and not for european GSM (and did not have Czech language support, but this was minor in this case).
She needs only a simple phone to perform standard voice calls and SMS messages. Current approach here is to use some smartphone – symbian with Mobilespeak or Android with Code Factory or some other a11y suite. OK, why not, but this aims to make a accessible smartphone, while many people need only accessible phone (which is not available).
So this také me to following idea:
if Android uses a modified linux kernel and GUI via Java virtual machine Dalvik, then it should be possible to use alternative simple menu with something like linux console voice output instead of the standard GUI and so make it much quicker.
This menu could be very easy – only to provide functions similar to „normal“ cellphones like the old good Nokia 3310 only with voice output. I know that it sounds very stupid to degrade a smartphone to a simple cellphone, but I do not know other way.
I think, that such trimmed off custom ROM with this sort of text menu and only basic functions (calls, SMS, phone book, calendar and clock with alarm) combined with a voice output could be able to run on cheap and relatively weak devices like Huawei Boulder for example so final solution could be comparable with normal cellphones. We need something with physical keyboard, so we could use HTC Cha Cha or if possible, the much cheaper Huawei which are both available from official distribution.
Are there any initiatives or attempts to create something similar?
Thanks much
PS: we are ready to sacrifice wireless internet and lack of Google services for better performance.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I did have a search on here, but didn't find anything particularly relevant so I'm hoping some people could help me out.
My situation is that I manage the deployment of Android Handsets and Tablets within my company. This process is fairly ad-hoc as in, I order a few handsets at a time, set them up with company software requirements + some desktop shortcuts, and ship them to the specific user.
My problem is that the quantity of devices I'm going to be deploying in the next 12 months will grow significantly, and this job is extremely boring, and costing me in time wasted on a repetitive task that could be much better spent on other things.
So I am looking for tools to help make this process more automated/quicker/simpler.
The crux of my requirements are:
a) install software packages (some from market, some not eg Lotus Notes Traveler)
b) Slight desktop customisations (add some app shortcuts, browser homepage etc) - realistically this is optional, but I thought I'd mention it.
Currently I take care of (a) with a homegrown python script which makes some adb calls.
(b) and (c) are entirely manual, and currently depend in part on the device going out - could be any of HTC Desire/Desire S/Sensation, Motorola Atrix/Defy+/Xoom or Samsung Galaxy Tab 10.1.
I also have to do this *after* having logged in, set up at least one google account + possibly a motoblur account, and enabled USB debugging - is it possible to get adb shell functionality without needing to get into the OS and enable USB Debugging?
Moving to higher level things, I'm open to the idea of paying for dedicated tools to manage this job - eg Google Apps Domain services, or some other Mobile Data Management service (eg silverback mdm).
However, what these tools are geared to is securing a fleet of devices, but don't seem to offer what I'm looking for, which I believe are pretty simple requirements. ie add some arbitrary apps, and make them accessible on the front screen of the device.
I can't imagine that I'm the first person to need to do this, so what are other people doing to ease the management burden?
Hi,
i was wondering if anyone could recommend a book regarding NFC HCE development with SIM based SE. I have gathered some background through online research. However it would be nice to have a single point of reference to some fundamentals.
What i am trying to do.
Well basically where i live there is a NFC Payment App that uses SIM based SE. However the developers of this app claims that the software doesn't work on Samsung Galaxy Note 4. Being a software engineer i find it very difficult to accept this claim that Galaxy Note 4 NFC has some fundamental flow.
I have look around their APP with APK tool. I noticed the AndroidManifest is missing some basic artifacts that should be part of a Payment App. Such as AID for the specific Payment Network. It also relies on a library called org.simalliance.openmobileapi for NFC and i feel this part of the code may also be broken.
for example the APP uses permission org.simalliance.openmobileapi.SMARTCARD (and i have seen all NFC related permissions are packaged in this library under this permission)
The Physical card that is being emulated is Mifare Desfire EV1. I already have the required SIM card with SE from the Mobile Provider.
So basically my idea is to follow some guidelines pointed at android dev /guide/topics/connectivity/nfc/hce.htmlnd try to mimic the functionality from the original APP without using the library they had used.
I have already collected a list APDUs from the original APP that i may need to authorize the payment once the Reader and SE has done their authentication.
My only intent is to have the reader successful communicate with a Authentic SE SIM. (and no monkey business)
So if anyone can recommend me a book that might give bit more background on the matter would be great.
Best Regards
Dev