When I run my app full screen mode (Game Canvas, setFullScreenMode(true)) in Nokia Symbian3 emulator a on-screen keypad appears that covers half of the screen.
How do I get rid of it to implement my own menu/touch screen events?
Can I make sure it won't appear on users' screens when they install this app?
I've read I need to put MIDlet-Touch-Support: TRUE in JAD file but I don't see any JAD file yet :S
Using Eclipse, Nokia Symbian3 SDK v0.9 SDK emulator.
Eclipse supports adding properties to your JAD file, it may be listed as descriptor. That's where you state which midlets are included in your suite, so if you don't have a JAD file you can't run your midlet.
There is a JAD property for setting the type of on-screen keyboard, but I cannot remember what it is at the moment. Probably "Nokia-On-Screen-Keyboard-type: none" or somthing similar.
Related
After migrate Xamarin iOS project to Unified API, the app shows black screen only.
Apparently all resources are not loaded at all.
Not only all images including icon, splash are not loaded, but also all XIBs are not loaded.
Now only default black window screen is shown.
Any advice to solve this?
In some cases XI 8.6.0 new msbuild-based build system can forget to copy some files into the app bundle.
This is fixed in the service release (8.6.1) which is in the alpha channel (right now). You might want to try it to see if this is the issue (if not then please file a bug report so it can be investigated).
I went to use hierarchyviewer and recieved the following message:
"The standalone version of hieararchyviewer is deprecated.
Please use Android Device Monitor (tools/monitor) instead."
So, I started up Android Device Monitor in Android Studio and could only find
"Dump View Hierarchy for UI Automator"
and it launches uiautomatorviewer in the Device Monitor...
Does anyone know if this means Google is intending to replace hierarchyviewer with uiautomatorviewer?
To start the Hierarchy Viewer from Android Studio:
Start Android Device Monitor
Click the Open Perspectives icon and select Hierarchy View.
Step 2
I used to use the hierarchyviewer in combination with monkeyrunner to do UI testing for android devices. Unfortunately, monkeyrunner was slow and limited and the tests were brittle.
I see the uiautomator as the better tool for inspecting UI elements. It has more powerful methods to identify UI objects and interact with them.
You no longer need to place sleep commands in your script. Just wait for a specific element. You can wait for an element to appear or disappear.
You can have watchers which run in case an UI object is not found. This can be helpful when handling pop-ups and error messages.
Here's a link to a tutorial.
http://developer.android.com/tools/testing/testing_ui.html
I did not see any official statement that says one replaces the other, but I think upgrading to uiautomator is the sensible thing to do. Hierarchyviewer and monkeyrunner are deprecated after all.
I would like to know if there is a tool simillar to mymobiler for Wince 5.0 which I can use to control the device from my desktop.
I use mymobiler (v1.25) but I believe it controls only devices running on WM5 and above.
Any help would be highly apprecited as the screen of my device has stopped working.
I use MyMobiler myself when I am coding for WinCE5.0 (not very often but I do know that it works.)
In your extracted MyMobiler zip file is three versions of remote.exe.
remote.exe
remote.exe.50
remote.exe.40
The only one I have gotten to work on wince5 is remote.exe.40
Just rename the existing remote.exe file (remote.exe.wm) [you may have to click tools, folder options, and uncheck hide extensions for known file types]
Next rename remote.exe.40 to remote.exe.
After that you are good to go. Copy remote.exe to the device through activesync (xp) or WMDC (>XP) and launch it on the device. It was a bit funny connecting for me the first time - I click connect on pc, then had to click the tray icon on the device, and click connect.
Good Luck!
Link to Video Showing it Running 1
This does work, the auto-install doesn't seem to work but if you copy the remote.exe over as mentioned (any location will do), then start remote.exe, click on the MYMobiler icon in the tray and select Connect, it will attach to your PC like the WinMobile version does.
Also, check the ini files in the MyMobiler directory. There's some details on the features/options.
I can confirm that Dave and Mike's solutions work on Windows CE 7 as well.
I was getting an error with the AYGSHELL.dll library when starting My Mobile after the gun was connected.
Run Mymobiler.exe before you connect the scanner to the PC and then connect to the PC using the tray icon from the gun. No error.
I am very new to j2me. I have developed a basic SMS Banking app. My app works in most phones which are touch and non touch devices (Samsung duos, Monte, Nokia 6120c …, Sony Ericson w300). But when I installed it in a Samsung SGH-D980 it installs and starts fine. But the list element which is the first screen after my loading splash screen does not respond to the touch. I have developed the app using Net beans 7.0.1 and uses CLDC 1.0 and MIDP 2.0. I have tried the defaultfxtouchphone emulator and works fine on it too. My problem is why does it work on some touch phones but not in the above mentioned touch phone. thank you,
The fact that touch events are available to MIDlet at any other phones means nothing in your case.
MIDP specification (JSR 118) does not force implementation to make touch (pointer) events available to MIDlets even for touch device. According to data provided at club-java page, this is exactly the case for SGH-D980:
Touch screen or mouse (hasPointerEvents()) No
Stylus motion events (HasPointerMotionEvents()) No
As soon as device allows to work with your list in non-touch fashion (you wrote nothing that says it ain't so), there is no problem - you just have to live with that.
of course not passing touch events to MIDlets when these are available natively means that MIDP implementation on this device sucks. But that's a different story
I know about firebug and the developer tools for the major modern desktop browsers, but I can't find any way of debugging JavaScript code on mobile browsers.
What are some high level techniques I can use to debug code on mobile browsers?
Android devices can be put into developer mode by going through settings>Phone status then tapping on "Build number" 7 times. This allows you to do a bunch of things (see step 5) including USB debugging. (Some devices might have Build number under Software Info)
To activate USB debugging, look in Settings for the newly appeared "{ } Developer Options", open this and switch on USB debugging. Connect your device using a direct USB connection.
In Chrome on your desktop, in the usual developer tools panel used for debugging, look in the menu for more tools>remote devices. With Discover USB devices selected, you should now see your mobile device on the side.
Select it to see a list of all the chrome tabs you have open and the ability to enter URLs directly.
Selecting one of the links will open up a new window with a mirror of your device screen on the left and all the familiar chrome debug tools on the right. You can still control your device directly or use the mouse on the mirrored screen. It even rotates.
full details on remote debugging from google and how to enable developer mode (link as above) from askvg.com
Android provides a tool set for these purposes:
https://developers.google.com/web/tools/chrome-devtools/remote-debugging/?utm_source=dcc&utm_medium=redirect&utm_campaign=2016q3
Apple does it a similar way:
https://developer.apple.com/safari/tools/
Tutorial: https://css-tricks.com/using-chrome-devtools-to-debug-javascript-in-any-browser-with-ghostlab-2/
You can debug on Safari Mobile with any iPhone/iPad. In Developer menu you can find your device and you can then debug your code with inspector.
If you have an Android Device instead, you can debug on Chrome Desktop (remember to active the debug mode) with chrome://inspect
On the IPhone you can go into settings>Safari>advanced and turn web inspector on
Sometimes I get bugs reported by customers that are not reproducible every time or in our testing. For such cases I recommend Lucky Orange. It records the user activity and also has the option to record console messages.
PS - I'm not an affiliate, I use them for my own projects and like it.
Another solution for basic debugging (which many times is all is needed), is having a console polyfill on mobile without the need to plug into USB on desktop.
mobileConsole is such a console polyfill.
Hope it helps someone, I found it useful.