Hey, I'm a developer who already has this program that does complex data entry, designed for field service reporting. The problem is it was written for Windows Mobile 5 (which is no longer supported) and runs on old HP iPAQ's (hardware that is no longer being manufactured or sold). There are only about 30 units on the field and I have enough backup units to keep the company running for a little while, but a more long term solution is in order.
I've been looking around for a new device that does what I need.
Really all that's needed is Wi-Fi capability (which applies for most everything out there anyways), built-in database (which I thought was widespread but apparently isn't included in Windows Phone 7), and a touchscreen (for signature capturing purposes). It could be a phone, tablet, pda, eda, or really anything.
Now,this seems like a forum with a bunch of veteran developers for a wide range of mobile computing products. Do you guys have any good recommendations for what device would be good/cost effective? It doesn't have to be the same programming language and porting it is no problem, I just need ideas on what devices would be good for the job.
Related
Large post: full letter can be found: http://austechreview.zoomshare.com/files/Open_Letter/An_Open_Letter_WM.htm
AN OPEN LETTER:
TO the individuals working in the Microsoft Windows Mobile division, to the hardware vendors for the platform, to the many Windows Mobile communities, to the avid enthusiasts of the technology, to the new-comers, to the onlookers and especially to those frustrated users of old and new alike.
I address this discussion to you all, as diverse and wide ranging audience for we all share a common trend in our lives, which, regardless of the corner we examine, be it: our work environments; our social interactions; or simply our personal lives, we find ourselves using (or looking to use) what perhaps best represents the apex in the convergent technologies trend - the Windows Mobile device.
We are speaking of a device whose form today can take on the properties of a phone, a portable music player, a mobile media centre, a camera, a camcorder, a webcam, a high speed modem, a GPS navigation unit, a portable gaming device, a radio, a mobile CRM, web-browser, email client, information management center and as a mobile office. I don’t doubt more could probably be added to that list, but those are just some of the features these devices are largely capable of and all of this functionality rests right there populating our pockets, belts or briefcases.
Despite this unprecedented functionality in convergence and the leaps ahead these devices have made in quite recent times, the changes have been largely hardware driven and when they have been software driven it has largely been by third parties or by hardware manufactures doing the platform vendors job. It seems these changes have not gone unnoticed, consciousness in the community, due to years of the same pattern - in contrast with the events of this year - have finally began to demand answers to the why’s and where’s of the Windows Mobile platform. It is time for a discussion on the issues with this platform and where it’s heading [CSM forum discussion]. With that in mind let’s ask ourselves some whys:
Why is it 2007 and only now with the consumer rollout of Windows Mobile 6 this year (the later part for most of it) are we only now - after all these years - finally seeing support for VGA resolutions in Windows Mobile? It’s not like the technology to support it hasn’t existed, 3rd party workarounds are a plenty, but they are often tedious and have results which require the user to make compromises often combined with GUI deficiencies.Why is it that this is now supported in WM6, yet my HTC advantage with WM6 still requires me to load this 3rd party software? Is Microsoft not giving you the code to activate the resolution options HTC? Or Microsoft do you not feel it prudent to work with HTC to encourage them to adopt such a simple capacity as letting us use VGA on our VGA devices?
Why has it taken so many years to do something with the X button, despite an array of 3rd party applications demonstrating the productivity and ease of use gains from enabling options with this part of the software?Why have manufactuers like HTC had to release their own X button software? Why, have roll-out and constant updates been such a prevalent facet of Windows for PCs, yet you feel no need to roll-out updates for your WM line, contrary to the capacity of the platform to support it?
Why after all these years of Windows Mobile, are syncing issues still so prevalent?
Why, despite the obvious adoption of WiFi technology and its virtual inclusion in all WM devices can we still not Sync over WiFi? Did HTC not inform Microsoft that they had put WiFi onto virtually all of their Windows Mobile devices these days? I ask because from the hoops you often have to jump through to get wireless networking connection in WM one might wonder.Why, has it taken HTC and O2 to give limited users a Media Centre application despite the popularity of Media Centre software on PCs and in the home, and despite the capacity of these devices being capable of viewing, pictures, video, music, radio and more recently TV?
Why have hardware vendors had to produce this software?
Call it a crazy division of labour thing, but shouldn’t hardware vendors in this case be sticking to well, hardware?Why has Microsoft not worked with them then to release better versions of the software or encourage them to release such software to the wider community? Media integration of this kind has been such a Grand strategy across the rest of the Microsoft divisions, did the WM division not get invited to the meetings for this strategy?
Just because these devices are largely aimed at professionals doesn’t mean this functionality cannot be built on. Yes I largely use this device, like most, for its superior information management and touch screen functionalities. But that doesn’t mean I don’t want to enjoy or use its other capabilities. Why after so many years of this platform being around, after so many operators adopting its hardware and after the recent popular release of devices like the Touch or last year the HTC TyTN series, why after all this do so few people still know about the capabilities of Windows Mobile devices?
Is this a problem limited to Australia? Apparently, it might be. You’re advertising on behalf of the hardware vendors in India, which makes sense having the second largest market, but while your off advertising in India, the IPhone is advertising (if it even has to) across the rest of the Western World!
It never ceases to amaze me how few people know about these devices, even people in IT, if they do know about them they are largely unaware of there capacities, and secondarily associate them with all the bugs and problems of Windows.
This lack of awareness is largely a marketing and promotions issue, but heres the kicker it’s a two party problem. If the hardware vendors and Microsoft haven’t noticed you’re futures are tied together. It’s in both of your interests to promote these devices. Microsoft you especially, because there are multiple hardware vendors but only one software vendor in this game, and the devices are by name Windows Mobile devices, which people will aptly associate with……Microsoft.People have a million and one choices of mobile devices in the market, and more contemporarily a wider choice of touch based technology devices. People aren’t going to magically seek out the Windows Mobile products, especially with their price tag, if they aren’t aware of it, and further aren’t educated on its features.
Why Why, did you allow the iPhone to gain such a hype and pre-eminent status? Hardware vendors and Microsoft, your devices have been largely capable of everything the iPhone can do, sans multi-touch, and much much more as we have discussed. They have had this capacity for years, why did you allow the IPhone to capture the mass market like this?
The answer most likely lies in the marketing as we have already discussed, but surely by now you’re picking up on my pattern here. That being, both the hardware and software vendors need to work with each other to promote these devices, enhance its functionality and use of the convergent technology.
It’s a two way street too hardware vendors you need to encourage Microsoft, you both should be listening to users; hardware vendors chances are your hearing the gripes with WM more than Microsoft, are you communicating it back to them and encouraging these changes?Why after so many years of Windows Mobile do I still have to install or buy 3rd party software to get half-descent time-management functionality out of these devices? Why are the tasks and calendar options barely more customisable or expanded then they were in Windows 2002 or earlier?
Why after so many years of Windows Mobile do I still virtually have the same basic interface? Why despite all this hardware power and the fact that we are using touch-screens do I have an interface that has remained virtually unchanged for all these years?
I know these are aimed at enterprise users (hi) but do we not deserve a nicer interface? The interface isn’t even all about aesthetics; it’s also about productivity, look at how much more the devices can be enhanced through 3rd party software like Wisbar desktop etc.
Are there plans to change this? Or will I have to buy a “Zune phone” to get some nicer interfaces? Why did it magically take for the iPhone to come out before we finally got some hardware (and software from the hardware vendor no less) that actually takes advantage of the fact that we are using touch-screen devices – referring to the HTC Touch of course.
Why isn’t there more collaboration between Microsoft and even 3rd party software vendors?
One of the greatest benefits this platform has over the iPhone and over symbion is the range of software. Why isn’t this more widely, promoted and encouraged? This isn’t perhaps so much a serious question that needs answering, since there are many community based sites that review and promote WM software but it’s a key and crucial benefit of the Windows Mobile platform and one that needs to be more readily promoted, advertised and enhanced.I, like most fellow Windows Mobile users, have either enjoyed using my Windows Mobile device or had to use it because there was no alternative – most likely a mix. And the Why’s I have asked today are not likely to dissuade me or anyone else from buying a Windows Mobile device and I have no illusions that there are many more whys people would like answered.
The point has been to briefly illustrate the mediocrity and failings both Microsoft and its hardware vendors have settled for with this platform combined with a reiteration of the many benefits and possibilities of the platform as one of the pinnacles of convergent technology.
Furthermore as should be apparent now, encourage a closer and more importantly, public, strategic collaboration between the hardware vendors and Microsoft. Both of your futures are tied to this platform, it’s a robust hardware device with many software features and a tonne of uses, but these must be enhanced, visually and functionally.
Secondly the platform must be promoted. You have a technologically advanced and highly convergent device rivalled by no other platform. The devices despite being geared for enterprise have many features consumer users could gain from them, particularly since the cost of many of the devices has become comparably affordable (aka HTC Touch). Its time consumers were made aware from joint marketing between the hardware and software vendor.
The IPhone has done a good job (as was expected from the hype and the eye candy interface) of capturing the consumer market. Now despite a consensus that the IPhone isn’t ready for business use, don’t be naïve enough to think this will always be the case. I don’t want to give Apple any ideas, but it strikes me if they were to buy up Pocket Breeze or Agenda Fusion etc and adapt it to the IPhone platform, maybe add some functional word, excel and pdf viewing capabilities, and correct some limited (and quite fixable issues) with the interface, you would surely have a sleek stylish well known business rival to the Windows Mobile platform.
Apple has the easy job here, it’s the only face behind the iPhone, its not HTC producing a device and then powered by Windows, its just apple and its iPhone; it doesn’t have to worry about collaborating with a partner, only telecommunication carriers that are dying to supply the device to consumers.
It stands to reason that if Windows Mobile can do this and more, and without the restrictions of the iphone, it should be the HTC Touch et al, that carriers are dying to sell to consumers, yet its not is it?
More dangerously, as mentioned, the transformation to a business capable device is a lot easier than the task of making a business device (despite its many consumer features) appeal to the mass market, especially after Apple has stolen the thunder to appear like the pre-eminent technological device.
I hope this generates some discussion amidst the Windows Mobile users and perhaps even between the hardware vendors and Microsoft, who should together be hatching out a strategic direction for these devices and who perhaps would see fit to work more closely with the communities who use their devices, so that some of the basic issues mentioned at the start, aren’t taking years to respond to.
Regards,
Osiris.
Hi,
We've all seen the Windows Phone presentations where the presenter streams the content of the phone on the projector or monitor using some sort of an internal Microsoft tool (as I've come to learn).
Any idea what the tool is? Where one can find it or what would it take to write one?
any answer to this? I need this info as well
Yes I can tell you why its not present on the consumer phones.
This is what I got as an answer to a related question:
The technology used to make this happen is patented and Microsoft is not allowed to distribute it into consumer devices. There are certain devices that are fully open (the devices they use to do the presentations with the TV-out) everything can be taken off those devices and can be added. The consumer devices have some remains of these things (for example in the registry). Only a couple of people own these devices and this technology may not leak for the above mentioned reason, that's why these devices are not widespread amongst developers outside of MS.
Correct me if I'm wrong, this is kind of what I've been told.
Hey mates.
Im looking for a wm 7 alternative to the quite nice app protector android app called Smart App Protector.
What i need is the functionality to restrict my wm7 devices so the users cant enter IE, Settings and other functions than those i want them to.
When a user tries to open the browser on a android device with the smart app protector installed, they get prompted for a password, which is exactly what im looking for.
If there isnt an app that does what im looking for, does anyone know a way to restrict at least internet trafic in IE, i still need data connections, but the users wont be allowed to use data except for 1 app.
My first impression of the wm7 - 7.5 is that its very restricted compared to Android devices :S
Thanks a lot for your help.
A quick for-the-record: No such thing as WM7. Windows Mobile is dead. Although some of the underlying code got re-used in WP7, the upper part of the Windows Phone stack is completely new, and the low-level stuff has changed considerably as well. What you're asking for would probably have been quite easy on WinMo.
On WP7, it's a lot harder. There are three ways I can think of. The first and simplest would be a well-modified custom ROM. Another is to modify the policy system to prevent launching iexplore, settings3, and similar programs, but have an app that (once the password is provided) allows changing those policies. Note that we don't yet have full control over the policy system (as a community; Heathcliff74 knows quite a bit but is busy with his Root Tools project). The third would be to try modifying the registry entries for certain operations. The effectiveness of this depends on whether apps are launched directly (by executable) or indirectly (by GUIDs in the registry). If it's the latter, the launch request could be routed through an authorization app first.
Bear in mind, the only one of these changes that is permanent is a custom ROM. Otherwise, the user could hard-reset the phone (losing all data on it but bringing it back to factory default configuration). It's possible to hard-reset just using the buttons; you don't even need to use the touchscreen.
Thanks for the correction, WP7 ofc
Im rather impressed by the performance of the OS so far, but it has many unforseen restrictions for my needs.
Since i only had the windows phone 7 for 1 day so far, i dont have much knowledge about changing what you are suggesting.
I know what you mean, but no idea how to do on WP7.
A custom ROM would be great indeed, but i dont have any experience in that field. Would be great to get a nice configuration tool with a gui to make the needed changes and then a tool to upload the new ROM to the phone...in that simple order
Im also looking for a solution to install software that was supported by windows mobile. Im checking out cheronwp7 at the moment to see if that can do the trick.
It seems a lot like WP7 is 99% consumer minded than business minded compared to old WM, a bit shame imo.
Hi,
is there a displayLink Software for the RT?? I have an Dockingstation with an extern SCreen and i really would like to use it, but this will only work with DisplayLink Software. So is there a solution for the RT??
Thanks a lot
HandyBesitzer said:
Hi,
is there a displayLink Software for the RT?? I have an Dockingstation with an extern SCreen and i really would like to use it, but this will only work with DisplayLink Software. So is there a solution for the RT??
Thanks a lot
Click to expand...
Click to collapse
Nope- no DDK for WinRT, so no one can make third-party hardware that doesn't fit the preloaded driver set:
http://www.displaylink.com/support/ticket.php?id=335
Well, no public DDK. There's (quite obviously) an internal one, and it has apparently been shared with certain partners, and a copy of it has leaked onto the Internet and been found (and occasionally used) in various places. That said, even if a commercial outfit were willing to entertain the use of such a thing, they would need to get the resulting driver signed by Microsoft for it to be installable on non-"jailbroken" RT devices.
this signing thing is really terrible. is there a chace to get such a driver in future??
GoodDayToDie said:
Well, no public DDK. There's (quite obviously) an internal one, and it has apparently been shared with certain partners, and a copy of it has leaked onto the Internet and been found (and occasionally used) in various places. That said, even if a commercial outfit were willing to entertain the use of such a thing, they would need to get the resulting driver signed by Microsoft for it to be installable on non-"jailbroken" RT devices.
Click to expand...
Click to collapse
Right, so effectively no DDK for general peripheral manufacturers to use unless MS decides otherwise for that device-- hence the situation with USB Ethernet adapters (and the driver that Plugable released then had to pull).
I'm a bit puzzled by the situation-- if MS' concern is that poor drivers would affect the WinRT user experience, then presumably they could enforce a testing process (as they already have w/ WHQL) and only allow driver delivery through Windows Update.
As it stands, WinRT devices, running full-blown Windows, are ironically far less useful in custom applications than iPads, which have all sorts of accessories available. Why wouldn't MS want WinRT to be usable in, say, medical settings? (even iPhones, let alone iPads, can connect to hardware accessories like medical sensors).
Android's also catching up quickly in the accessories space, and it's only a matter of time before iOS/Android destroy any advantage MS had w/ hardware manufacturers, as happened so dramatically in the software space (there are now so many more devs who've worked with iOS and Android than have with modern MS platforms).
Well, for accessories that just need "traditional" data I/O - things like what you might have done over a serial port in days of yore - you can easily use either BlueTooth or the audio jack (although the latter is a real hack, usually used only for very small dongles powered by the audio signal). The iPad is definitely less extensible with third-party hardware (note, accessorizable != extensible) than RT, but I fully agree with you that Microsoft's stance on RT drivers is just plain weird. Keep the pool smallish and/or WHQL-test the crap out of them, but make them available! Those USB ports can and should be a killer feature.
The audio channels available on many consumer devices are often perfect for bit banging various communications protocols. UART "emulation" has often been done on the headset jack with a level shifter and some trickery, often on android devices much less powerful than the surface RT (seen a demo on an 800MHz single core ARMv6 handset). If your willing to sacrifice audio output from your application on the RT (as it is being used for bit banging the UART) then you essentially have a plug and play serial port without any special drivers needed, your application just needs to be able to generate an audio signal and analyse an input. the peripheral will need an external power supply but this is common on many legacy RS232 applications too.
There is the bluetooth serial port profile. Thats often used as a replacement for RS232 or UART. I dont know if windows RT supports it though (someone would have to check).
Another trick I have seen involves a microcontroller with USB capabilities. I have seen examples of people setting a microcontroller to appear as USB mass storage and having a small file system with 1 plain text file. Writing into this text file from windows or linux etc would then cause the microcontroller to perform a particular operation in response. Sensors can also be read by the microcontroller causing it to update the text file too. You essentially have file based GPIO without.
Its all rather hacky but it works technically.
There is also an i2c bus on the RT keyboard connector.
I would like to create an IoT device by buying new, cheap android phones, strip them down and remove the screen, rebox into my own physical box, install a custom ROM without any bloatware (and that will boot without a screen!), and install my android app on the device to do stuff.
An example of a purpose for this could be a GPS tracker for a car. The box would be placed in the car, and record GPS and accelerometer readings, posting these readings back to a central server via the cellular network. (This is just a random example, so don't focus too much on the detail of this, but there are thousands of uses for a IoT board with the sensor, CPU, RAM, storage, and connectivity capabilities of a budget android smartphone)
The reason I want to use existing phones is that they are wonderful, mass produced, cheap devices with a variety of sensors I can use.
The reason I want to use Android is because it is because of the customization ability, and the mature development ecosystem.
To me, it seems an obvious thing to do, but I don't seem to be getting much joy trying to search for examples of this sort of thing (either here, or on the internet in general).
So some questions:
1. General thoughts? (Good idea? Am I missing some fundamental problem?)
2. What are the challenges of running Android without a screen connected?
3. Are there any custom ROMs you know of that specialize in this sort of thing?
(I've seen Google Brilo, but it still seems a bit early yet, and I really like the idea of just using the standard Android SDK to develop the app - and the abundance of help and information that comes with it)
Thanks!