-Hi
I'm using the Zebra Link-OS SDK to play around with a QLn-320 mobile printer. I have not altered any of the code. The printer is able to communicate through a network but not via USB. It is using the ZDesigner QLn320 driver on a USB port. I know the problem isn't the USB because I am able to perform SGD commands via Zebra Toolbox as well as print documents through notepad. The sample code should print out a 60 byte sample logo, instead the application returns "Communications error" in the form of a red label. It doesn't even seem to read anything from the printer as I don't get anything returned by doing a SGD command. It seems to work about 1% of the time and other times it shows the blinking folder icon but nothing happens. I've tried all the firmwares for the printer listed on Zebra's website including the latest one. I've tried deleting the project, re-importing it, cleaning it, and even using NetBeans, but nothing seems to work. The bug seems to be in the SDK.
Any ideas?
Thanks!
Verify that you are running JRE v1.6 or above.
Try doing a factory default on the printer.
You can do this by sending to the printer the following SGD command:
! U1 do "device.restore_defaults" "all"
Then try printing from the app via USB.
Related
I have the following problem:
I have a MZ320 printer Zebra works by bluetooth, but application is under develop phonegap.
I found this plugin (https://github.com/EionRobb/phonegap-print-plugins), but do not know how to implement it (and install).
I am a neophyte at this, please help.
My English sucks, sorry
I pushed on Github a simple cordova/phonegap plugin to send ZPL data to printer. Use it is very simple. Visit project page for more infos.
I am not familiar with the plugin you referenced. I can suggest two ways: (1) Embed Zebra SDK in your app and use it to implement printer discovery, connection and printing to MZ320. (2) Use centvia app to handle printer discovery, connection, and communications and invoke it from your app to send your print data to the MZ320.
I am new to java and android and wanted to see how developing for android works
I started by downloading the SDK FROM HERE
However after I finish making the Hello World project sample given in the website HERE, if I try to run it on the emulator as explained HERE, the emulator screen appears, but nothing seems to happen. I can see the word android on the middle of the screen with some animation happening, but that's it. The website says something about unlocking the emulator, but I have no idea what that means. What I have gathered from reading other posts is that the emulator is supposed to have some kind of slider switch as in real smart phones which should be dragged to unlock it, but I can't see it in my case. Now I have no idea why this is happening or what I should check out in order to fix this. Are there any installation logs or something else that I can check to see what the settings are?
What I have tried till now:
I downloaded the SDK ADT bundle from HERE and just unzipped it. Then looked for eclipse.exe and ran it directly. Is there anything else I should have done prior to this?
When I did it for the first time, I had only JRE installed and not JDK, which I realized after reading THIS POST. So I downloaded JDK from HERE, updated the required environment variables and restarted eclipse, but still it's the same thing.
I looked at the Eclipse isn't talking to the emulator section GIVEN HERE, but all it says is to restart eclipse and the emulator, and it doesn't do anything at all.
Rant:
I can understand if the program had failed to compile when I didn't have JDK , or if the IDE gave any indication at all of a faulty program install, but that isn't the case. Everything seems ok, there are no errors, but it just doesn't do anything. This is the type of thing that makes people pull their hair out, and personally, I think the With a single download, the ADT Bundle includes everything you need to begin developing apps: in the android website is very misleading, especially for complete beginners
Anyway, what should I do to make the tutorial program run on my computer? My computer is a bit old and slow so could that be an issue? My computer is Windows XP SP3 on Intel(R) Pentium(4) 4 CPU 3.20 GHz 3.19GHz 2.50GB RAM, but if that was the case I assume the emulator shouldn't even start up
You just have to wait a bit longer. Android loads pretty long on emulator.
Tutorial says about unlocking, because when Android is loaded, your screen on emulator will be locked.
If you find emulator too slow for you, you may want to check this topic out: Why is the Android emulator so slow? How can we speed up the Android emulator?
I had the exact same problem as you when I first got into Android development a week ago. The two things I did are simply
1) Set the usable RAM on your AVD to 768MB
2) When you run your Hello World program in your emulator, give it about 5-10 minutes. Don't touch or click the window at all, just let it load up. Later you can make it persist
3) If your home screen comes up, click and hold the mouse button in the center of the screen, then drag towards the sides and release, this should unlock the device.
Try these steps first, if they don't work then there is likely a problem with your AVD configuration.
If you are launching your app first time with emulator, it will take appropriate time.After that, on Lock icon click and slide to the right. then you can view you application. If not check for your app(icon) installed.
By seeing your configuration of PC I think it will take some time to load emulator. After emulator is load (see below image)
then and then run your code and also check in eclise-device that whether emulator is online or not.
For checking emulator in eclispe :
In second image just above windows logo you can see small rectangular button with plus sign click on that you will get list from which you can select devices. You can find similar button in you eclipse at the bottom.
I had the exact same problem and followed the exact same steps, but was also unsuccessful. I ended up creating a new AVD with a Nexus 4 instead of the latest Nexus 6. The resolution of the 4 is much lower, which I think is what solved my problem. It loaded much more quickly using the 4.
Also, When I was using the 6, I could only see "ndroi" because the size of the screen was much larger than the size of the phone. Now I can see the full device.
vs.
You may just need to relaunch the Android studio 3.6.3.
I got a similar problem. The hello world app does not install on the emulator.
Problem solved after relaunch.
I hope my question is suitable here. I recently started learning android - making buttons, using google maps and other basic stuff. I saw a thread recently (can't find it) about this and I got interested in it: https://github.com/jackpal/Android-Terminal-Emulator/wiki
This is an open source android terminal emulator. It also seems to have a library called EmulatorView with which people can call methods etc. What I would like to do is use this app inside my own app. Instead of just looking at the file system on the android phone etc. my app would connect to the console of a serial device like a router, usb to serial. Something I usually use minicom for on my pc. As in there could be a button in my app and if I press it it opens the console of the attached router and I could issue administrative commands.
I was wondering what the easiest way to do this would be? Would it be to try and use this library and make my own terminal, seems quite hard, or would it be to copy their source into a project and try to edit it? Seems messy to organize everything, and could be hard too? Then use some library like this to connect to the serial device? http://slickdevlabs.com/slick-usb-2-serial-library/
What would the first steps be, make a terminal like the open source app has, use their library or paste in their code? Then try and edit it to do something over serial?
I have tried to use their example for using their library (jackpal.androidterm.sample.telnet), but it crashes when I click open shell, I was wondering if this open shell button in their example was what I needed?
I decided I would learn more by writing the app myself using the library.
i have created a successfully hello world program with an image in it. and here is how it looks on windows 7
I have now connected to my DELL XCD to the computer, ensured that "USB Debugging" is ticked and also made sure that "Settings > Applications and enable Unknown sources" is ticked
I have followed all the steps given here - in android documentation
But the following steps fail:
You can verify that your device is connected by executing adb devices
from your SDK platform-tools/ directory. If connected, you'll see the
device name listed as a "device."
Here no device is displayed in command prompt.
If using Eclipse, run or debug your application as usual. You will be
presented with a Device Chooser dialog that lists the available
emulator(s) and connected device(s). Select the device upon which you
want to install and run the application.
And this doesn't happen
I have the following packages installed currently
So how to deploy my simple hello world program on my phone now?
After exhaustive search i found out that the USB driver required for
my DELL XCD35 was available in the form of a .exe file on my mobile's
original Micro SD memory card. The shocker was that there was no
direct download available from DELL's website for the same. So if you
loose this file, or have exchanged the Micro SD card for a better
version then you are in trouble as you wont get it from DELL also.
So folks, i have uploaded the same file for those who want it. - Dell Phone Android USB Connector Device Driver
PS: I spent so much time on this silly matter that i had to let others know of this and wrote an article for the same, so that others don't make the same mistake lol.
I have seen this problem off and on while running the Eclipse (Galileo) under Fedora 11-13, whether the target is my device or an emulator. But now with my new device, the HTC T-Mobile G2 (Android 2.2), I see it much more frequently: I successfully download the app (complete with lots of Log.d() calls), the system successfully launches it, but the LogCat pane in the DDMS perspective is completely blank.
Sometimes, only sometimes, I seem to be able to kick it into action by clicking on the tool for Debug (the little bug one). But that doesn't even work all the time. Worse yet, it forces me to restart the whole program, which is very cumbersome.
And yes, I did remember to connect the device and make sure the device shows up under "adb devices", AND make sure that is the device the ADT downloaded to. I can even hit breakpoints in the code.
I suppose I could try relying only on the debugger, but I put a lot of work into writing those Log.d statements in the right place, it would be a giant leap backwards to do without them now. So any suggestions concerning what the problem might be, workarounds, or how to find relevant bugs logged against either ADT, SDK or the G2, would be welcome.
TIA
PS: Google searches such as "android ddms logcat" have not helped so far.
PS: I have also considered running ddms from the commandline, but the instructions on how to do this wtihout conflicting with the port already chosen by ADT for running DDMS are not clear enough to inspire confidence: so I always quit Eclipse before running the command line version of ddms. But then I lose the handy ability (provided by Eclipse) of navigating my source code while reading the log, so this too, is an inferior solution. Perhaps if someone can connect a few more of the dots in Google's instructions on this by explaining how to get the device and command-line DDMS to agree on a port while still running Eclipse, that would be a good solution.
Just to suggest the basics, when you click on the DDMS tab, is the device listed on the devices tab? (If devices isn't there, click Window->Show View->Devices) If it is listed, have you clicked on the device (on the name column). Sometimes if the device isn't clicked on it will not show the logcat.
If it is and you have selected the device - try clearing the log (the icon of a page with a red cross at the bottom right corener of it - located at the top right of the logcat panel) I find if I have had it running for a long time it sometimes fills up and stops displaying the log, although normally one line is shown.
It seems that ADT looses the connection with the device or is not re-connected when you reboot the device or emulator.
I've found that if you have more than one device or emulator you can click on the other one, click on the empty log window and the logs for this other device appear, then click the device that lost connection and will be re-connected.
Yes, sounds like black magic, but it's all we have...
It worked for me when I did following.
Remove the connection to the device (i.e. unplug the USB cable), then restart Eclipse. Next time it starts, you can see the LogCat is back on action writing logs.
Hope this helps.
I have experienced the same problem on and off.
Basically the logs were coming on console using "adb logcat" but not in the logcat view of eclipse. I've noticed that restarting the emulator , then restarting the eclipse and then relaunching the emulator from eclipse gets rid of this problem.