It works for me on my iPhone 4.that pages has a count-down timer which shows how long the session will last. Somehow, this page never worked in my previous iPhone.
It works for me on my iPhone 4.that pages has a count-down timer which shows how long the session will last. Somehow, this page never worked in my previous iPhone.
JPBarringer said:The problem is that China's mobile regulator has mandated the use of WAPI (Wikipedia link) which is incompatible with a lot of hardware out there. Even foreign places like Starbucks use the standard at their locations in China, and mobile devices need compatible firmware to get on the network. There are also security concerns with WAPI as it the authentication server is centralized and (I believe) run by the Chinese Government.
radioman said:I thought the government backed off off of that WiFi position. China Mobile has infiltrated Starbucks for sure, and its annoying, with a new login scheme where they need to SMS passcodes for you to input. But with that said, my iPad and iPhone 3GS have no problem connecting through the WiFi networks there.
ryanwhalen said:Is there any sort of mailing list I can get onto that will update me when there's an impending Pleco Android release? I loved and used the WM version for years, but switched to Android last September. I'd love to have Pleco on my phone again, and I'll certainly send more money pleco's way as soon as the app is available...
Android 3.0 brings a new UI designed for tablets and other larger screen devices, but it also is fully compatible with applications developed for earlier versions of the platform, or for smaller screen sizes. Existing applications can seamlessly participate in the new holographic UI theme without code changes, by adding a single attribute in their manifest files. The platform emulates the Menu key, which is replaced by the overflow menu in the Action Bar in the new UI. Developers wanting to take fuller advantage of larger screen sizes can also create dedicated layouts and assets for larger screens and add them to their existing applications.
mikelove said:The Android version certainly doesn't need to be a finished product in its first release, but I do think we want to at least have fullscreen handwriting and OCR working from day one, particularly as they're both mostly working already - handwriting seems to be very solid on pretty much any device not made by HTC, and OCR's only major failing so far relative to iOS is that it has to be done in landscape orientation - the engine at least is actually about 20% faster on the Galaxy S than the iPhone 4 owing to the higher-clocked processor on the former (though I'd gladly give up that performance if the Galaxy could match the iPhone's battery life). And stroke order and audio involve lots of data but very little code so it's logical to make those available from the get-go on Android as well.
What we're aiming for is still much less than what we launched with on iOS, both because it doesn't need to be as thoroughly debugged and because there are a lot of things that people can do for themselves in the short term - no need for us to include our own built-in file manager or a system for automatically downloading database files in the first public Android release, we can use manually-installed databases and license "keyfiles" just like we did on Palm/WM and tell anyone who's uncomfortable with those to wait for the finished version. But it has to be more than a quick-and-dirty thrown-together-in-2-weeks type thing or it won't be worth all the hubbub.
nomadism said:Hi Mike, I can't express my excitement that you will be supporting android.
nomadism said:As a previous Nexus One user, I wouldn't be surprised the the N1 failed your expectation (it's a known fact that the N1 touch screen was very poor), but do the later HTC devices (like the more recent G2 / Desire Z or Desire HD) also fail your expectations?
mikelove said:Perfect timing, too - next week we begin a period of about 2 months of pretty much 100% Android coding, so it'll be nice to have this to play around with / test on / etc.
mandu said:Now, I'm not sure if I followed the preceding discussion correctly, do you know which is the lowest version of Android you'll end up supporting? I can tell that 3.0 brings developer-support much closer to where you'd like it, but have you decided which version will be required for basic dictionary functions?
mikelove said:I've got a pretty good idea, but I don't think I should say anything specific here yet... there's the possibility our plans might change, plus I'm really really worried that I might post something here that might motivate somebody to choose a particular Android phone only to discover that that phone doesn't actually work with Pleco; better to just say nothing. Sorry...
westmeadboy said:
Apps developed by Google's new lab are expected to be free and might have ads that would generate revenue, the people familiar with the matter said.
They've also said that Android is not the market for paid apps:westmeadboy said:I read somewhere that Angry Birds makes more than a million dollars a month from advertising on the Android app. If true, then I think that's pretty good for them right!? Still, like you say, the advertising model on works for certain types of apps. Probably those that appeal to a wide audience rather than niche products like Pleco.