I have installed Vmware player 4.0.4, BB10 dev alpha simulator in windows XP. While playing the virtual machine, it says [start service: screen] and after sometime gives error "Unable to open file for write. 2(No such file or directory)."
Please suggest a solution. Thank you
I just had boot load freezing at
start service:screen.
Try not to change display settings of the virtual machine, Keep it as "use host settings for monitors".
Just after your system starts it will get you briefly through a resolution list, unless you change it manually the system will continue booting 5 seconds later picking by default the first mode from the list,
to bypass this kind of error i chose one of the safe suggested modes on the bottom of the list, for example: in the following screenshot it will be 4,5 or 6
PS : don't forget to click somewhere inside the VMWarePlayer window to interact with the loaded system before typing the choice number with you keyboard then type enter (before the 5 seconds elapses)
Related
As the title says, this post is meant to highlight two bugs that weren't there before last CN1 .jar updates:
Launching a codenameone app in debug mode fails
New or modified rounded rectangle border defined through the theme file are forced in top only mode
Launching a codenameone app in debug mode fails
I'll start with the 1st one as it is the most disturbing.
On Eclipse, launching the app in debug mode results in the following error (that I wasn't getting last week):
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:735]
Initially, I thought that the socket was failing to initialize as the port was being used. That is also what you would mostly find on internet. So I checked the command line used to find out which port the socket was trying to connect to so that I can check if that port was available:
C:\Program Files\Java\jdk-13.0.1\bin\javaw.exe -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:54499 "-javaagent:C:\Users\Roman\eclipse\jee-2019-09\eclipse\configuration\org.eclipse.osgi\1095\0\.cp\lib\javaagent-shaded.jar" -Dfile.encoding=UTF-8 -classpath "D:\Work\Software_workspaces\Eclipse_IDE\Selisys\FirstOnPersonalPC\JavaSE.jar;D:\Work\Software_workspaces\Eclipse_IDE\Selisys\FirstOnPersonalPC\bin;D:\Work\Software_workspaces\Eclipse_IDE\Selisys\FirstOnPersonalPC\lib\CLDC11.jar;D:\Work\Software_workspaces\Eclipse_IDE\Selisys\FirstOnPersonalPC\lib\CodenameOne.jar;D:\Work\Software_workspaces\Eclipse_IDE\Selisys\FirstOnPersonalPC\lib\impl\cls;D:\Work\Software_workspaces\Eclipse_IDE\Selisys\FirstOnPersonalPC\lib\impl\stubs;D:\Work\Software_workspaces\Eclipse_IDE\Selisys\FirstOnPersonalPC\native\internal_tmp" com.codename1.impl.javase.Simulator be.selisys.rdf.firstonpersonalpc.FirstOnPersonalPC
We can see that it is attempting to use port 54499 (in fact, in gets incremented by 1 at each command line call). Now the funny thing is that this port (and the many following ones) is (are) effectively free!
I tried things such as rebooting Eclipse, my computer, check the dt_socket.dll, ... but none of that helped. After hours thought, I noticed the debug mode was working on other applications, but not on CodenameOne ones.
I then moved to another computer:
Turned off the internet, ran the debugger on a CN1 app ==> Works fine
Turned the internet back on, send a built to get the jars updated, ran the debugger again ==> same error as above :(
Since I now know that it is obviously related to CN1 jars last update. Have you got any idea on how to solve that? How much time should we expect for a solution to come up? Any idea of a workaround? Maybe I can use the old jars, if there is a place to find them.
New or modified rounded rectangle border defined through the theme file are forced in top only mode
That is less important, but still annoying: basically, we can't use rounded rectangle borders using theme unless we have set them before the recent updates (I have no clue on since when the bug exists except that it is no older than 1 month). If you create/edit a rounded rectangle border, I will automatically be set to top only mode upon save. The current workaround I am using is creating a hard coded RoundRectBorder.
As above, the bug appears on any computer which get its jars updated.
Hope pointing these out will help them getting resolved earlier. :)
Cheers
Does anyone know how to capture screenshot on Nokia 8110 4G (KaiOS)?
You may follow these steps to get screenshot via Firefox WebIDE.
On the device - dial *#*#33284#*#* to enable developer mode. There will be a bug icon on the status bar.
Download Firefox 58.
[Important] Disable your internet access, this is to prevent Firefox got updated to a newer version which might break the WebIDE functionality.
Launch Firefox 58 and disable auto update.
Resume your internet access.
Launch WebIDE in Tools > Web Developer > WebIDE.
Restart the WebIDE (because the ADB helper would be downloaded automatically, and need to restart it to take effect.)
Now you should be able to see Nokia 8110 detected under "USB devices" at the right panel. (if not, see below)
Click the device, "Nokia 8110", and then click Screenshot.
See here for a sample screenshot.
Troubleshooting if you failed to see Nokia 8110 detected:
I found it might fail if your Firefox got updated to a newer version automatically, in this case you might need to leverage creating new profile to start over again, see here for details.
If the Firefox version stays correctly at 58 but after you click the device, it shows an error saying "Failed to connect", try to reboot the phone and also restart the WebIDE as this post suggested.
EDIT: Yes it is - Joelbert W's answer worked and makes the other responses a bit silly by comparison, just * and # together :-)
Unfortunately, it is currently not possible :-(
https://twitter.com/KaiHelps/status/1072446931421593603
https://twitter.com/KaiHelps/with_replies
It is possible either with WebIDE connection or with a custom ROM such as GerdaOS where you can make screenshots by pressing Power with half-open slide lid.
However, I'd only recommend installing custom ROMs for experienced users only since you can't use any official updates after installing them.
So I have a go flip 3, and i stumbled on if u press * and # almost simultaneously, it takes a screenshot.
I believe it's possible on certain devices and OS versions using the Screen Capture API as well.
I have encountered a problem with uVision and Hitex emulator (Tanto2) on a Win10 laptop (fresh install).
My initial setup was UV5.23, I updated to 5.24 and made tentative with 5.25 on Keil's request.
I have a dedicated SDK release for UV5.23, I switched to a new one for UV5.24.
Firmware emulator was reflashed when I was using SDK for UV5.23, and updated when moving to UV5.24
What I can do:
- start UV5, open my project,
- start a debug session on the emulator, load my project, make the first run and stop debug session.
Whatever the release I use, the problem appears when I want to start a second debug session on the emulator. Once I click on the Start Debug, UV5 crashes with this message:
"uVision IDE has stopped working
A problem caused the program to stop working correctly. Windows will ..."
I need to relaunch UV5 to run a new debug session.
The setup using Keil 5.23 and its dedicated SDK release was OK till the end of March.
Since the end of March, the Windows updates that have appeared are: KB4088776, KB4093110, KB4093112, KB890830, KB4099989.
I tried uninstalling KB4099989, but there was no change, the problem is still present.
Is there a link with these updates?
If someone encounters the same problem and was able to solve it, I hear you :-)
The same problem appears on the laptop of my colleague whereas it is working fine before the last Windows update.
Thank you in advance for your help.
This is because of the below issue. If there is a crash in application during dll unload, windows adds an entry in registry to ignore a future unload dll request. So if the application tries to load the dll again within the same session, then the application crashes.
As a workaround goto the below location in registry,
My Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
and delete the unload registry path. Everytime if there is a new crash then the dll will be added back which needs to be removed.
[work around]
I also get crashes when entering debugger session, however I noticed that it occurs only if I click the debugger icon and then leave the pointer over that icon. I have never had it crash if I click and immediately move the pointer away.
I've just unpacked my new Pico Pro Maker Kit and started flashing procedure. After creating a product in AndroidThings platform and downloading the build I've started flashing procedure.
Command flash-all.sh failed on fastboot syntax, so I've build that manually and found that it was failing on part "set_active _a". I've skipped that and continued to flash device.
Now device is rebooted, I can see on the screen androidThings logo and version + info about network status ("not connected").
I'm unable to find this device in
fastboot devices
or
adb devices
so it looks like I have no way to connect into it.
Do you know a way of fixing that? Is there any way to force fastboot reboot on that device?
Thanks!
I had a related problem for IMX7 on initial install, I thought I'd pass along the Boundary feedback in case it helps. Tech support at Boundary devices recommended that I try the following:
Please try to add androidboot.dm_verity=disabled and
androidboot.selinux=disabled options to bootargs.
I presume these would be options you'd set at the boot prompt ==> (from the serial connection) but I haven't had a chance to test, which I may get to next week. Interested in your feedback if this has any impact to your situation in the meantime.
When the side button of the TI SensorTag is pressed, pairing with a device is possible for approx. 2-3 minutes. How do you modify the SensorTag's firmware so that it advertises forever and pressing the side button is not necessary every time?
And how do you upload the firmware with an iOS device, so without using CC-debugger?
How I did it, with help of Chris Innanen (thanks!!)
You will need a Windows virtual machine if you do it on a Mac.
Download IAR Embedded Workbench for 8051 (http://supp.iar.com/Download/SW/?item=EW8051-EVAL). Make sure to take the 30-day evaluation copy and not the 4k limited.
Download BLE-STACK from Texas Instruments (http://www.ti.com/tool/ble-stack) and install it on a Windows (virtual) machine. By default, the installer will install here: "C:\Texas Instruments\BLE-CC254x-1.4.0\Projects\ble\SensorTag\CC2541DB\SensorTag.eww".
Open this SensorTag.eww file with IAR Embedded Workbench.
Select "CK2541DK-Sensor-OAD-ImgA" in the dropdown menu in the "workspace" section on the left
To prevent a compiling error later on: go to Project -> Options... and change the value for "Number of virtual registers" from 16 to 8.
Find "SensorTag.c" in the filetree in the workspace section on the left: "SensorTag - CK2541DK-Sensor-OAD-ImgA/APP/SensorTag.c"
Search for GAP_ADTYPE_FLAGS_LIMITED and change it to GAP_ADTYPE_FLAGS_GENERAL to enable indefinit advertising
Make the build with Project -> Make. Wait until it's done
By default, the new firmware image (.bin file) is now in "C:\Texas Instruments\BLE-CC254x-1.4.0\Projects\ble\SensorTag\CC2541DB\CC2541DK-Sensor-OAD-ImgA\Exe" (Make sure to place it somewhere you can reach it from Mac OS X later, if you use a virtual machine)
Repeat steps 4 to 10, but now for "CC2541DK-Sensor-OAD-ImgB"
Now get the app to upload the new firmware over the air. Get it here: https://itunes.apple.com/us/app/ti-sensortag/id552918064?mt=8
Open iTunes in Mac OS X and open your iOS device, go to the 'Apps' section, scroll to the bottom to see the apps with filesharing possibilities. "SensorTag" should be in that list. Click on it and add the two new firmware files, both Image A and B.
If that's done, open the SensorTag app on your iOS device and connect it to the SensorTag. Then in the bottom of the app tap "Update FW" -> "Select FW file" -> Shared Files > And then tap Image B and upload it. It takes a few minutes. A firmware with type A is already on your SensorTag by default. Because you've put a B Image on it just now, with any new changes you would need to upload an Image A.
Good luck!
Additional: changing the signal strength
1) Find "HCI_EXT_ClkDivOnHaltCmd" and you'll add a new line (and optional comment) after it:
// ADDITION Adjust TX power level
HCI_EXT_SetTxPowerCmd( HCI_EXT_TX_POWER_0_DBM );
1b) You can change "_0_DBM" to "_4_DBM" or "_MINUS_6_DBM" or "_MINUS_23_DBM" as well
2) Find "GAP_ADTYPE_POWER_LEVEL" and change the value on the next line to match the above power level
The above solution didn't work for me until I changed:
initial_advertising_enable = TRUE;
In SensorTag_Init().
I am using this firmware and it will start broadcasting whenever it's not connected. The side button acts as an on and off switch.
http://www.myweathercenter.net/installing-a-new-firmware-for-ti-sensortag/