Smart Reader

[Guest the-jackal]

Anyone tried this yet? It works quite well and picks up the name and number from the business card but mine freezes straight after it asks me if I want to save it.

[Guest efjay]

Works fine for me on G4 firmware, what is your firmware version?

[Guest the-jackal]

Works fine for me on G4 firmware, what is your firmware version?

PDA: i900XXHG5/MSHG1

PHONE: I900XXHG5

Some thing strange is going on too. I have not had the sim update but I can make calls with new and old phone. i cant send texts with new phone but cant with new and I am not getting any texts through at all on either.

[Guest efjay]

Since you've just got it maybe a hard reset might be an idea? Seems to clear a few problems for others I've seen.

[Guest the-jackal]

Since you've just got it maybe a hard reset might be an idea? Seems to clear a few problems for others I've seen.

Well the phone is sorted now, new phone can now send and receive. Funny thing is, I can still make calls on my old phone with the old sim card. Calls and texts don't come through but outgoing works fine.

BOT It all seems to work fine now. Must of just been me. :D

[Guest javman]

hello i have PDA i900SAHH6/CXHH6, Telephone i900XXHH4

it's polish rom and in this rom have not install smart reader, but i find an italian website some files whose been copied on news rom and this files is ok but when i take the photo text eg. book program started creating note but it's not finish him.. i have only photo but i have a note.

this files is :

DioOCR.exe

DioOCR.exe.0410.mui

DioHook.dll

DioOCREngine.dll

FREmbed.dll

maybe i need something else file ?

Edited October 13, 2008 by javman

[Guest Octopus1968]

I've got a different problem with SmartReader: it started once and then never again. When I click on the icon, i can see the rotating wait cursor, then it disapears and SmartReader doesn't start. This happend in all ROMs I tested (the original german rom, then DXHI1, now I'm on DXHI3)

Am I the only one?

[Guest Flash_Gordon]

I've got a different problem with SmartReader: it started once and then never again. When I click on the icon, i can see the rotating wait cursor, then it disapears and SmartReader doesn't start. This happend in all ROMs I tested (the original german rom, then DXHI1, now I'm on DXHI3)

Am I the only one?

Hi,

I am on DXHI1 and my Smart Reader also does not start.

I never tried it on earlier versions so it has never worked.

Anybody any ideas?

FG

[Guest javman]

unpack this archive and copy dll files to /windows on i900 pda and copy files dio ocr.exe to your memory on storage memory and start it.. in my omnia smart reader is started but dont work properly :/ chek this...

archive file :

http://www.sendspace.pl/file/pVNBREN9/ if you want to download files please press "pobierz plik" button :lol:

Edited October 14, 2008 by javman

[Guest metalman705]

unpack this archive and copy dll files to /windows on i900 pda and copy files dio ocr.exe to your memory on storage memory and start it.. in my omnia smart reader is started but dont work properly :/ chek this...

archive file :

http://www.sendspace.pl/file/pVNBREN9/ if you want to download files please press "pobierz plik" button :lol:

eey i have tried it it worked for a little.

i could take a picture but than i get a message that something was wrong with the .exe

end than i cant do anything... everything works slow and cant turn my phone so (power buton didn't work anymore)

so i had to reset it and everything came back to normale XD...

i use version =

XKHH1

Edited October 14, 2008 by metalman705

[Guest pedramgm]

hey guys,

i dont have a smart reader on my omnia, does anybody know where to download this??

[Guest pedramgm]

hey guys,

i dont have a smart reader on my omnia, does anybody know where to download this??

[Guest Octopus1968]

hey guys,

i dont have a smart reader on my omnia, does anybody know where to download this??

The link is in the post abbove yours.

I tried this, doesn't work for me, SR does not start.

[Guest javman]

eey i have tried it it worked for a little.

i could take a picture but than i get a message that something was wrong with the .exe

end than i cant do anything... everything works slow and cant turn my phone so (power buton didn't work anymore)

so i had to reset it and everything came back to normale XD...

i use version =

XKHH1

on my omnia it's that same... :/ but when i take the photo he's start converting photo to text but he's dont finish and he's view me folder with image i press back button and omnia works good

my rom is : SAHJ1

[Guest ilkkes]

i notice that S2U2 with volume control broke the smart reader. So if you have S2U2, this might be the solution..

edit. with HJ1 and S2U2 v1.30 this doesn't occure anymore

Edited October 17, 2008 by ilkkes

[Guest jeffrey2000]

i notice that S2U2 with volume control broke the smart reader. So if you have S2U2, this might be the solution..

edit. with HJ1 and S2U2 v1.30 this doesn't occure anymore

Yeh I noticed the same, after installing S2U2 (and some configuring the app itself and a reboot) the smart reader just wouldn't start anymore.

Now I have the DTHJ5 rom and S2U2 v1.32 and the problem seems to be gone.

Edited October 21, 2008 by jeffrey2000

[Guest sebolex]

This one is working http://org.downloadcenter.samsung.com/down...CR_Eng.WM60.CAB

Thx to luuuki from pdaclub.pl

Edited December 17, 2008 by sebolex

[Guest ow1]

This one is working http://org.downloadcenter.samsung.com/down...CR_Eng.WM60.CAB

Thx to luuuki from pdaclub.pl

Thank you. It works well.

[Guest PetiaDCh]

Hi, everyone! My question is: can I change the language in Smart Reader? Only text that can recognise is English.... please, help!!

[Guest Prufrock Ellington]

I may have a hint of an idea what the problem is with SmartReader. First off, I should say that I noticed that this thread is over a year old, so things may have changed somewhat since then. However, I recently ran across a problem with SmartReader and Wisbar. In an effort to debug the problem and to provide Wisbar developers with as much information as possible, I got some information that strengthened my conjecture.

In Wisbar, one can place a "Button" on the screen (I have an Omnia SCH-i910). A Button is an object managed by the Wisbar screen management software and has various attributes associated with it. Basically, it's a way to put an icon on your screen and have something happen when you click it. The "something happen[ing]" is the execution of a Wisbar "Script." A Script is a linear list (i.e., no loops, conditionals, anything) of commands that are chosen from a pre-defined set of actions. Examples are "launch a program," "delay <M> milliseconds," and "vibrate <M> milliseconds." There are about 30 such baked-in commands.

I configured my Button to have a one line Script, "launch a program," the program being /Windows/Start Menu/Programs/SmartReader.lnk (a link to /Windows/DioOCR.exe). When I click the "Button," it launches the card reader like a champ, but, when I terminate SmartReader (pressing the [X]), something undesirable occurred - rather than return to the screen Page I was on where the Button was, Wisbar was taking me back to the "First Page." Wisbar allows you to have multiple "Page"s and one of them can be designated as the "First" Page.

Why was it taking me back to the First Page? Well, I thought that if I added another command in the script, namely, "return to last page," it should do the right thing and get me back to the page with the Button.

However, this didn't work. I saw a brief flash on the screen, just before the launch of SmartReader that looked like it might have been the right page, but then SmartReader came up and [X] got me back to the First Page. Being a unix guy, I thought the behavior had the feel of SmartReader being executed asynchronously. When using a unix command line interpreter ("shell"), if one runs "sleep 3600," then you don't get your prompt back for 3600 seconds, but if instead you enter the command "sleep 3600&" then you get a process ID printed out, and you get your command prompt. The "&" tells the shell to start the "sleep" application but, to not "wait" for it to finish up and exit. The "sleep" command will "sit" there for an hour, but you won't notice it at the shell level because the process is running "in the background." For convenience, the shell prints the process ID of the "sleep 3600" command so you can, for example, kill it. If you're familiar with background processes, fork()/exec(), etc., skip to the Conclusions and Discussion below.

Now, if the Wisbar Button Script interpreter works like this pseudo code:

while moreCommandsInScript

do

getNextCommandInScript

executeCommand

done

then everything will be great as long as each of the individual commands completes its work before yielding control back to the Script interpreter. Using the "sleep 3600" example, and adding a "echo hiya, guys!" command after it, then this interpreter loop would execute the sleep and, one hour later, the sleep would finish, and the interpreter would go to the top of the loop, get the "echo hiya, guys!" command and print "hiya, guys!"

On the other hand, if the first command was "sleep 3600&", the interpreter would start up the "sleep 3600" - but not wait for it to finish - and it would immediately get the next command and print "hiya, guys!"

Wow. Loooong way to get to my point. What SmartReader feels like its doing is acting like there's a "&" after its name, like "SmartReader&"

If this were to be true, it would explain why I was seemingly unable to get a "return to last page" command to get me back to the Page that had the launching Button. Why? Because the interpreter would read the "launch SmartReader" command and execute it. With what I'm saying, SmartReader would return control to the interpreter immediately as if it was a unix shell command with a "&" at the end. The interpreter would go back to the top of the loop and get the "return to last page" command, which it would faithfully execute. But, SmartReader would be in the process of initializing while the interpreter uselessly switched back to "the last page." When SmartReader got running, it would clear the screen, etc. and if I were to press the [X], the fact that the "last page" had been displayed would be irrelevant -- SmartReader would have "stepped on" the screen display of the "last page."

I further tested this using a different second command, "vibrate <M> milliseconds." I added a "vibrate 500ms" command after "launch SmartReader." Sure enough, when I click on the Button, I feel the vibration before SmartReader even clears the screen! So, at the least, the Wisbar interpreter doesn't seem to be waiting for SmartReader to finish. Of course, that could just be a Wisbar bug, but stay with me. If it's SmartReader's problem, then it could explain some of the things you guys are seeing...

Conclusions and Discussion

If I may use the unix vernacular, SmartReader must do a fork() without doing a wait() in the parent branch of the fork. That is how "command&" is implemented by the shell. Usually the shell does a fork() and then in the child part of the fork, it exec()s (overlays itself with) the desired program ("/bin/sleep", for example), whereas, in the parent, it executes the wait() system call passing it the process ID of the child process. When the child process calls exit(), the wait() in the parent part of the fork returns, and the shell gives you another prompt. When the shell parses a "&" after the command, it does not do the wait() in the parent. Instead, it just prints the process ID out on the terminal and goes back to the top of its loop, giving you another prompt.

Note that a process could do this all on its own. That is, if you write a program, you can choose to make it run as if it was started by a shell with a "&" at the end of the command. This is what "daemon" processes do on unix systems. They fork(), which creates a copy of the process. In one of the processes (the "parent"), fork() returns the process ID of the child. In the other process (the "child"), fork() returns zero. Testing that return value lets you know if you're the parent or child. If the parent merely exits, then the child process goes on its own. That is, no application code will be "wait()"ing on it to terminate. If SmartReader is doing this, it may be a bug, or there may be a good reason for doing so, but it would cause Wisbar problems and might very well explain the behavior several of you have seen: that you can launch it, but then you can't launch it again, or if it fails to run, the rest of your Windows process environment gets flakey (slow down, etc.) How?

If SmartReader is launched "in the background," then whatever software you're using to launch it will be under the impression at a way too early stage that SmartReader is "done." This could cause all sorts of problems depending on how you launch it and how the launcher is written. In my case, the launcher is Wisbar, and the trouble it gets into is that it runs through the rest of its Script before SmartReader terminates. But regardless of how it gets launched, once you launch it, there would be a SmartReader process running. Unless SmartReader encounters an error and terminates itself, the only way it will exit is by your pressing the [X]. Trying to launch it again could understandably fail, especially if SmartReader tries to do things like open the camera device up for exclusive use. That could cause the first, second, or both instances to fail. If SmartReader is having a hard time initializing (if, say the camera device driver takes time to get going), then the program you used to launch the app might go back to the top of its "loop," looking for another "command." If SmartReader now spooges all over the screen, you may never see that the "launcher" is looking for more work. This could make the launcher itself get screwy.

For example, suppose SmartReader is getting hung up in initialization, before it clears the screen and takes over. If you launched SmartReader from Windows Explorer, what you'd experience is that a) You clicked SmartReader, ;) Explorer seemed to do something, but c) Nothing ever "happened," that is, you never saw the SmartReader GUI. The truth could very well be that Explorer did launch SmartReader, but that SmartReader, acting like a daemon process, began running independently "in the background." Explorer would sit there, in control of the screen, waiting for you to do something. If SmartReader was taking a long time to initialize (maybe forEVER), the SmartReader process would be running even though you never got any visible feedback. Launching it again is not going to do any good and may mess everything up.

One more quick observation: suppose SmartReader launched ("in the background") and drew its GUI on your screen. You take a picture of a business card, save the information, etc. Now, before you get a chance to [X] the program, you get a call. Your screen becomes the phone, you talk to mom, and hang up. The phone GUI stays up since it's what you last executed...but SmartReader is still "out there" running. Who knows how a second (or more) instance of SmartReader will behave?

I put way more in here than I should have, but I'm hoping this is something like the truth and that the SmartReader coders may need to take a look at how they are managing themselves as a process. I've sent a question in to the Wisbar people to see what they think, too. Hopefully, I'll get a firm answer and post it here then.

[Guest Priceless07]

I've got a different problem with SmartReader: it started once and then never again. When I click on the icon, i can see the rotating wait cursor, then it disapears and SmartReader doesn't start. This happend in all ROMs I tested (the original german rom, then DXHI1, now I'm on DXHI3)

Am I the only one?

I had a similar problem earlier...I think u need to uninstall some prog which i cant remember...its either s2u2 or s2p...try and see.

[Guest ivanxxx]

Is it possible to add other languages to smart reader or does anyone know a good OCR prog which includes other languages or customizable?

Help? ;)