We shared a Brother QL-700 over Google cloud print.
We print from a desktop the print went through without an issue.
But, when we print from an android no matter which page size we pick it gets to the printer as 3.5' which doesn't fit the printer.
We tried from different apps (google docs, word..) and nothing helped same issue everywhere.
After long debugging and many support calls with Brother we found the issue as a driver bug (Brother released a fix), which caused GPC to wrongly read the printer configuration.
Related
I have a weird problem with viewing PDF files.
I have a menu button on a windows forms application that opens up a form with a PDF viewer. This works absolutely perfectly in the majority of cases, however I have one user who is experiencing problems.
It seems to work but them it will suddenly refuse to load the document and just shows a grey screen. She also has problems when printing from this form.
I have investigated this issue and I cant reproduce this is the dev environment.
The only possible reason I can see is that she is using something called "Nitro reader" rather than the standard Adobe viewers which we tested on.
Could this be the cause of this intermittent error or are there other known issues with the PDF viewer in C#?
I know this question is a long shot but I am hoping someone else will have come across a similar issue.
I am using .net 4 with VS2010 and I am using PDF sharp to generate the document.
Thanks
I still cannot get my chromecast into developer mode. I tried compiling the sample android app and my chromecast doesn't appear in the list of devices. I have indeed checked "Send this Chromecast's serial number when checking for updates" and rebooted my device. I even let it sit overnight to give it time to contact Google. When i got to http://[my chromecast ip]:9222 I get connection refused. I can ping it though. And http://[my chromecast ip]:8008/apps/ returns an XML response.
When I first sent the request to Google, they said the whitelist was backlogged but shortly thereafter they said the backlog was cleared.
Any ideas besides the fact that maybe whitelisting didn't work on Google's backend?
Even I had same problem earlier
In earlier version of chrome-cast app (for android) there was an issue Send this Chromecast's serial number when checking for updates is uncheking always, So I removed that app and again installed new version. That bug was removed now. OPtion is by default Checked.
If it doesn't work then try to use other device. Surely that will solve your problem
I'm working on a Spotify App, but the Spotify application keeps crashing on me. I have been trying to debug my own Javascript code, to see where it goes wrong, but it seems a bit random. It almost always happens when my app loses focus (i.e. switch to another app). Is there a compatibility issue with jQuery perhaps?
Unfortunately I can't find any crash-logs or anything, for Spotify. Are there any?
I hope someone can help me along here, because this problem makes developing cool Spotify Apps as good as impossible.
Edit: To clarify, I'm using Spotify 0.8.8.450.gd9413514, on Windows 8 64-bit, but I've also experienced the same on Windows 7 and Mac OS X 10.6.
Using Windows 7, you can create a crash log by accessing the Task Manager, right clicking the Spotify process and selecting "Create dump file". If you're on Mac OS X, you can get a crash dump by opening the Activity Monitor, selecting the Spotify process and clicking 'Sample Process'.
I was having the same problems, It seems related to ads banner on the top. Run the ad video and pause it, that solved the problem for me.
I use the webbrowser control to display a webpage from an application, but it just displayed a white screen. I tried Internet Explorer and it did not display anything either.
Any ideas how to fix this problem.
Thanks a lot in advance.
Windows Phone Emulator requires a DirectX 10 or above capable graphics card with a WDDM 1.1 driver. I assume that you got an error message on first start of the emulator that your graphic adapter isn't capable for all functions the emulator is using and that this may impact XNA games and sometimes silverlight like this one:
If your graphic adapter does not fully support DirectX 10 or doesn't has a WDDM 1.1 driver you will only see a white screen instead of the rendered webpage. This also affects all controls using MultiScaleImage, including the webbrowser control. As far as I know there is no solution for this at the moment.
To check if the emulator is running the required GPU emulation take a look at the arrow to open the application list and if it points to the right or left. If it points to the left, NO GPU is available - if it points to the right (as on the hardware phone itself) the GPU is available and rendering should work as expected.
See also this page in the msdn.
You haven't said if you're testing a local/private page or one on the web.
Also test other pages on the web. Can you view anything or just your own page.
If you can't see pages on the public web then you have a networking issue
If you can see public pages but not locally hosted ones then you probably have a different networking issue. If you're on an actual device or the emulator will likely greatly affect this.
The other things it may are:
you're trying to view a page that is to compilcated to be displayed (if there is such a thing - test with a very simple static page first)
the page uses useragent detecction and doesn't recognise the user agent and so is serving nothing
the page has complex javascript which runs before the page is rendered and the javascript is failing and so the page is never displayed.
I have an app on the android market, which uses the mapview to display some locations. This works fine on all the devices i have tested it on. After having it on the market for a while, i see several people reporting a problem.
The mapview does not seam to display/load the tiles on the map, and only displays the gray grid. All the people reporting this, are using a HTC Desire/Desire Z/Desire HD.
I have searched for this problem, and seen many having problems with their mapview, and they often have a HTC desire, but i have not found any mention of it being caused by the Desire phone.
Does anyone have a clue to why people with Desire phones are having problems with the mapview, when it works fine for others?
I've downloaded your application and tested it on my HTC Desire with MIUI, and as you said the mapview is not loading the tiles on the map.
FYI the application gives the following error:
IOException processing: 26
java.io.IOException: Server returned: 3
at android_maps_conflict_avoidance.com.google.googlenav.map.BaseTileRequest.readResponseData(BaseTileRequest.java:115)
at android_maps_conflict_avoidance.com.google.googlenav.map.MapService$MapTileRequest.readResponseData(MapService.java:1473)
at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher.processDataRequest(DataRequestDispatcher.java:1117)
at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher.serviceRequests(DataRequestDispatcher.java:994)
at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher$DispatcherServer.run(DataRequestDispatcher.java:1702)
at java.lang.Thread.run(Thread.java:1019)
Here you can find a question with the same problem, which seems related to the maps key.
As I said my Desire uses MIUI v1.10.28, with gingerbread, so the problem shouldn't be related to HTC's sense ROM... as it has been some time since you posted your question, do you have more information of the devices in which your application doesn't work?
I have made an update to the application, where i created a new maps api key, and it is working now.
I am not sure what caused the problem before, but i think they may have changed the type of key you have to submit for the maps key.
I have an old file where i had written a SHA1 Certificate fingerprint of the application and i am quite sure that it is the one i used to get the old maps api key. Maybe they changed something along the way, that caused it to fail on most phones?
Anyway, creating a new maps key from an MD5 Certificate fingerprint fixed it on every phone i have tested with.