Related
I'm working on a project for work, and I'm not sure if the product I'm looking exists, at least yet anyways. I'll tell you what I'm looking to do, and hopefully the community can let me know if this kind of device is out yet, or if it will be released soon.
I work at a hospital and I primarily provide training and support to Physicians for our Electronic Medical Record. One of our challenges has been getting physicians engaged and interested in learning about upgrades/changes/optimization and such pertaining to our medical record. We may fix a problem that they've been complaining about for a year...but then it's very difficult to let them all know that it's been fixed without tracking each of them down to tell them. We're not talking about a dozen physicians either, it's probably closer to 400 or so.
I spoke with a few other people and we came up with the idea of basically creating an electronic bulletin board that can be wall mounted in the doctors lounge, and they can use it to look at recent tip sheets, patch notes, lesson plans, etc, that we post about our EMR. I'd also like to add some links to the more reputable medical journals, so they can use it for something more than just reading our tip sheets.
I feel that Android would be the best platform for what we're trying to do, especially since it makes it easy to share and email items to accounts, that way if a Doc doesn't have time to review it in the lounge, they can at least email the document to themselves for later review.
I'm looking for an All-in-one device, a flat panel touchscreen display running android, and the display needs to be between 32 and 50 inches.
If I could get it done for 1500 or less, that would be great, although I pretty much have the approval to use up to 5000 in capital. I know there are several devices coming out that are integrated with Google TV, but few if any of the ones I've seen have a capacitive touch screen.
Does anyone know of a current or upcoming device that could meet my needs?
Bump
**********************************************************
Being a big fan of Android, I really do hate to say this, but I don't know you're going to find what you're looking for. From what I've seen lately, there have been fairly successful pilot deployments of iPads + AppleTV touchscreen bulletin boards in the medical sector, but without some serious serious hacking, I don't think you're going to see this in the Android arena. I don't think I've even seen any android device larger than 11" screens... On the plus side, that does sound like a new break-in type of market if any of the major product ODMs are paying attention
L4T
What about this!? asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101
This is just a poll thread to gather some statistics about the HTC One S body issue.
Please, vote only if you are using the device for some days (3 and more) and do not vote if you have a brand new phone out from the box.
And, if you would have this issue after your "Not issued" vote, please, leave a comment.
Thank you.
Discussion thread is here: http://forum.xda-developers.com/showthread.php?t=1589364
P.S Moderators, please, merge this thread with the disscusion one.
SH23, 5 days, no issue YET
Hi,
I've been using my black One S during 5 days.
SH23 with no real issue yet, except that the USB port edges have some "micro" clear spots
I still voted "no issue" because its much smaller than what is shown on the pictures.
Hopefully this pole will be merged with the other thread
We've started a poll yesterday in a german thread. Results are:
Black issued: 40
Black not issued: 27
Silver issues: 2
Silver not issued: 10
Total number: 79
The two cases with "silver issued" hab no problem with the unibody, but the plastic sim-cover. As far as I know all devices have HT23 or SH23 SN.
http://www.android-hilfe.de/htc-one-s-forum/poll-956-hat-lackschaeden-am-htc-one-s-nicht.html
Good initiative. Hope it gets merged
I do not want to piss in the pool here, but over in the MAO failure discussion thread it was recently mentioned that the first 4 digits do not tell us anything but year and month of manufacture. It takes the first 5 to really peg it down to the exactly to the day of manufacturing.
Also I am not sure if it makes sense to throw both of the sites of manufacture into one put. HT stands for a Taiwan factory and SH for... I forgot - Shenzhen or Shanghai I think.
I think for this to be useful it should take into account the first 5 digits AND separate the locations. My reasoning: the SH facility might have had a "good" (non issued batch) during three days of March, while the HT facility produced issued phones on those dates. Then, later on, the HT facility may have had a few good days, while the SH facility put out crap. With the current setup this is meddled up and there is not really much info to be gathered, except the overall percentage of ppl who have issues with the devices made in March in both locations. It does not indicate whether SH or HT is better or worse.
Of course this would make for a complete overkill of poll options. (Assuming the first were made on the first of March it would take 30 options for each facility).
Suggestion: Change or close this thread and create a new one with the poll options "No issues (yet)" - "Major issues" - "Minor issues" and maybe a second poll asking when the first issues were noticed ("First day", "within 3 days", "within 5 days" etc.)
And then request users the users to post a picture or at least a description of the issues (at top edge, around all edges, around sim cover, around USB Port) and the first 5 digits. Then the entire thing would be much easier to follow and notice trends.
Of course that would require moderator or someone with permanent editing rights to take in all the new posts and add them to some sort of list / table in the First Post for easy reference.
But if done this way it would probably make for a useful source of info even for HTC engineers, becaue from what I gather a lot of ppl who have this problem and post in the debate thread are not ready or willing or able to send in their phones just yet for inspection by HTC.
Just my 2 cents
Just my two cents.
I'm quite short on time but wanted to quickly provide the recent numbers:
Black issued: 46
Black not issued: 32
Silver issues: 2
Silver not issued: 10
Total number: 90
But: I agree absolutely on the fact that SNs are not helping much right here!
psych0t1c, I think you are right about the S/N. It`s just the first batches. But the poll options with "days used" is not so good, cause some users are more careful than others
All we can do, is just collect the stats "Issued / Not issued". And ofcourse it`ll be very good if people post the photos and comment on if these scratches appeared after they had already voted.
psych0t1c said:
I do not want to piss in the pool here, but over in the MAO failure discussion thread it was recently mentioned that the first 4 digits do not tell us anything but year and month of manufacture. It takes the first 5 to really peg it down to the exactly to the day of manufacturing.
Also I am not sure if it makes sense to throw both of the sites of manufacture into one put. HT stands for a Taiwan factory and SH for... I forgot - Shenzhen or Shanghai I think.
I think for this to be useful it should take into account the first 5 digits AND separate the locations. My reasoning: the SH facility might have had a "good" (non issued batch) during three days of March, while the HT facility produced issued phones on those dates. Then, later on, the HT facility may have had a few good days, while the SH facility put out crap. With the current setup this is meddled up and there is not really much info to be gathered, except the overall percentage of ppl who have issues with the devices made in March in both locations. It does not indicate whether SH or HT is better or worse.
Of course this would make for a complete overkill of poll options. (Assuming the first were made on the first of March it would take 30 options for each facility).
Suggestion: Change or close this thread and create a new one with the poll options "No issues (yet)" - "Major issues" - "Minor issues" and maybe a second poll asking when the first issues were noticed ("First day", "within 3 days", "within 5 days" etc.)
And then request users the users to post a picture or at least a description of the issues (at top edge, around all edges, around sim cover, around USB Port) and the first 5 digits. Then the entire thing would be much easier to follow and notice trends.
Of course that would require moderator or someone with permanent editing rights to take in all the new posts and add them to some sort of list / table in the First Post for easy reference.
But if done this way it would probably make for a useful source of info even for HTC engineers, becaue from what I gather a lot of ppl who have this problem and post in the debate thread are not ready or willing or able to send in their phones just yet for inspection by HTC.
Just my 2 cents
Just my two cents.
Click to expand...
Click to collapse
You make a very valid point, but it could very well be for nothing as well. For example the phones prone to this error could be within each batch much like processors, where the ones of lesser quality are sold as lower-end models.
My point being, we could put a lot of effort in this but the best thing is to just make a huge deal out of it so HTC will solve it for us. Of course feel free to go along, the data should be interesting anyhow
OldЕr said:
This is just a poll thread to gather some statistics about the HTC One S body issue.
Please, vote only if you are using the device for some days (3 and more) and do not vote if you have a brand new phone out from the box.
And, if you would have this issue after your "Not issued" vote, please, leave a comment.
Thank you.
Discussion thread is here: http://forum.xda-developers.com/showthread.php?t=1589364
P.S Moderators, please, merge this thread with the disscusion one.
Click to expand...
Click to collapse
Decided not to merge. I see you have already provided a link to the other thread and this one is closed. That should suffice
Rick
Samsung has released a new flagship smartphone, the Galaxy S3, including voice control, wireless beaming of content and exclusive apps, as it aims to consolidate its position at the top of the mobile sector.
The S3 has a super AMOLED 4.8in screen, larger than its predecessor the S2, with an 8 megapixel rear camera and 1.9MP front camera which offers "intelligent camera features" that the company says will adapt to what it sees you doing.
The phone runs on Google's Android 4.0 (Ice Cream Sandwich) software, but has a number of Samsung additions – including voice recognition and eye tracking.
The phone will go on sale on 30 May in the UK, with Orange and Phones4U already lined up to sell it. No price has yet been given. It will go on sale in the US this summer. Samsung said it will go on sale with 296 carriers in 145 countries. It can connect at "4G" speeds in compatible countries.
"S Voice" can respond to spoken orders such as "wake up" when its screen is off, "snooze" for an alarm, or to play a particular song, change volume settings, and take pictures. It also responds to gestures, so that lifting the phone to the face while sending a text message will dial the recipient's number instead.
Samsung has also souped up Google's Android Beam (which can pass data such as business card details) so it is capable of sending a 1GB file between two S3 phones in three minutes, or a 10MB file in two seconds by touching them together.
It comes in a 15GB or 32GB version, though the company said a 64GB model would come soon. Buyers can get an optional wireless charging pad, similar to that offered with the now-defunct HP TouchPad last year.
At 4.8in, the screen size is only just below the minimum 5in that most analysts class as a tablet – indicating Samsung's confidence that top-end users will want larger screens. The first-generation Galaxy S in 2010 had a 4in screen; the S2, a 4.3in screen.
The company sold an estimated 44m smartphones across its entire portfolio in the first quarter of 2012, more than any other company. It dominates the Android sector too, selling around 50% of phones on a platform which itself makes up 50% of smartphone sales.
Jason Jenkins, editor of CNET UK, said: "The Samsung Galaxy S3 is a cracker of a smartphone that makes the iPhone look a little like yesterday's model. It cements Samsung's place as one of the leading phone manufacturers and really puts the pressure on Apple to come up with something different for its next iPhone later in the year.
"It's also starting to look like this will be a two-horse race – Samsung and Apple fighting it out for the number one spot with everyone else left to pick up the crumbs. HTC, Sony, BlackBerry and Nokia are the ones with the real work to do."
Ian Fogg, an analyst at IHS Suppli, said: "What's striking is that Samsung is focusing on software and the experiences, more than the hardware (although that is excellent too). Features like Pop over, social tag, and S Voice all aspire to differentiate from the opposition through the user experience that Samsung's software customisation delivers.
"Samsung have been leading up to this for a while, but this is the first time they've led their product positioning on user experience and software."
Francisco Jeronimo, IDC's smartphones analyst, was downbeat, saying: "It is not an eye-catching device that will overwhelm consumers."
He noted that analysts had not been given the chance to try out the voice control in pre-release demonstrations of the phone. Of a brief test, he said: "Overall, [it] seems very similar to Siri, but my first impression was that is not as well integrated with the phone as Siri is with the iPhone."
Carolina Milanesi, smartphones analyst at the research group Gartner, said that Samsung was looking for ways to remain ahead of rivals in the Android space, as well as Apple.
"They need to push the boundaries in order to remain ahead," she said. "It will be interesting to see how many of these new features [in the S3] will be open to developers so that they can take advantage of them in their apps."
However, if developers start to target Samsung APIs for apps, that could potentially split the Android platform still further beyond the individual versions produced by Google – and would also tend to increase Samsung's control of Android.
Such an "embrace and extend" manoeuvre would build its control of the platform, where it already presently has half of worldwide sales and is the biggest profit-maker.
Jeronimo observed: "Samsung definitely embraced Android, and is extending it. We shouldn't also forget that Samsung has a quite opportunistic approach to market trends.
"If Android is now the new kid on the block that can best contribute to its success, they will invest and nurture it to maximise the opportunity. But if the trend changes (and they are very good at anticipating that), they will also change the platform they embrace in the future."
But, he added: "It is clear that Samsung has no other strong options at the moment."
No price was announced, though Milanesi suggested that it would be priced similarly to the Google-branded (but Samsung-made) Galaxy Nexus, released last October, and that prices of the year-old Galaxy S2 would be cut to boost Samsung's already dominant share.
Milanesi was generally impressed with the device, though with some reservations. "The design is much improved, and despite the fact that it is still plastic it feels much less cheap than the Galaxy S2 and the Nexus," she said.
But she thought the S Voice control was less convincing: "It came across as a little gimmicky when I played with it. But to me the main issue is that these features are quite buried in the device, so might not be that obvious to consumers. S Voice is not as complex as Siri – more like voice activation for simple commands."
Overall, she suggested: "I think Samsung has similar challenges to Apple but with a less convincing overall package and a weaker brand."
But Fogg suggested that the real problem would be for other companies. "For Nokia, this must be deeply concerning," he said. "One of Nokia's stated reasons they opted for Windows Phone was because they believed that it would be impossible to differentiate using Android.
"Samsung is showing with the the Galaxy S3 that it's perfectly possible to innovate with Android software. In fact, Android is enabling faster innovation than any handset maker has managed with Windows Phone."
But the new Galaxy S3 could also pose problems for the smaller players in the Android space, Fogg suggested. "Samsung's marketing spend and brand awareness are second to none. This combination of marketing spend and channels will cause serious problems for smaller handset makers such as HTC, LG and Motorola."
Jeronimo warned that Samsung needs to consolidate its position: "Samsung needs to come up with unique features and not to catch-up once again with other vendors. What is there that's completely unique on the S3 that we haven't seen on other devices? Maybe slight differences on the features, but nothing disruptive.
"They entered a new era. The only way to succeed is to set the pace of innovation. I believe that's exactly what they want to do, but they still suffering from the 'follower-syndrome': to improve what others created. That's why consumers will compare the S Voice to Siri and not the other way around."
If you're going to copy/paste an article that someone else wrote, I believe common courtesy would be to cite the source. Also, what is the point of starting a thread like this? There are already a ton of other GS3 threads, why not post your OWN opinions in one of those threads instead of starting a new thread with someone else's words?
All that said, I don't think Sammy is going to dominate anything with this phone, it is downright hideous. I really hope the US variants look a lot nicer.
On July 21st, Zimperium Mobile Security group dropped word of the most pervasive and threatening Android vulnerability discovered to date: Stagefright. With the ability to remotely execute commands on an Android phone just by sending an MMS media message to an unprotected phone number, Stagefright is a rare exploit offering the entire keys to a user's castle. The fallout over the past few weeks has been swift, with Google moving rapidly to patch the underlying Android system vulnerability and push updates to manufacturers. Problem solved.
Except for the multi-millions of Android owners still using older phones which are no longer supported with regular system updates from their carrier. Currently, there is no plan from major cellphone manufacturers nor the telecom carriers to protect Android owners who still operate older model phones. This protection gap also extends into no-contract cellphone resellers who cannot pass through regular system updates. As such, there are currently a substantial number of Android owners who are not protected from Stagefright and the potential for having personal data monitored and stolen.
Given the severe implications of identity theft, financial loss, or personal embarrassment and endangerment due to the exposure of private information, have we arrived at a point when digital data security must be considered a matter of consumer safety? It is well established that car manufacturers must recall certain models due to defective parts or systems which endangered lives. Therefore, should phone carriers then also be expected to issue phone recalls when a serious security exploit is identified?
There are some past examples of phone carriers issuing recalls for defective batteries or total system faults that render phones inoperable, but no significant instance of a recall for a security related vulnerability. At best, carriers could take the initiative to implement low-cost phone exchange programs with no additional service obligation for users with outdated phones. Meanwhile, phones with current Android versions can largely be patched through ongoing updates. At worst, carriers can continue to place the greater burden of data security onto individuals and abuse emerging security vulnerabilities as a marketing device to drive more purchases of their newer devices. Regardless of how much or little of the cost carriers will assume, the stakes for personal data security will only continue to grow.
Greetings all,
I have been unable to find any sort of best practices for this, on this or any other site, so I hope you can provide some insights.
My company has just started to deploy Android tablets to users in the field and I am looking for guidance on the recommended replacement/retirement interval for standard consumer-level Android tablets. For standard desktops and laptops this interval would typically be 3 or 4 years, but given how quickly the Android OS changes and how quickly a device may be obsoleted by virtue of end-of-life or lack or ongoing OS upgrades I would assume that the effective lifespan of a tablet would be shorter than that, not to mention that these are going to be used by non-technical people who may not be treating them as electronic devices but more like paperbacks that run on batteries.
Already we are seeing devices coming back in for repair due to forced charging cable insertions and/or bent micro-USB connectors, as well as the standard cracked screens and such, so these may end up being destroyed before their expected usefulness has been achieved, and as much as we have made the case to management that we ought to be deploying ruggedized devices supported by enterprise-level MDM, they insisted on launching with Samsung Tab S2's and SOTI Mobicontrol for MDM.
So, choice of device and MDM aside, when would you,if you were administering this deployment, plan on refreshing the devices in the field? That is, taking the old ones back in and providing all-new ones before they begin to show age (not wear) related problems? Accounting can write them off over any interval but we want to replace them before the support becomes too burdensome and the devices too unreliable (affecting productivity).
2 years? 3? Something else?
Many thanks,
Matt