I second that. There are quite a lot of changes to features such as the On-screen keyboard in Belle FP2, and since this update won't be available to many of the first-gen Symbian^3 devices,...
Type: Posts; User: mgroeber9110; Keyword(s):
I second that. There are quite a lot of changes to features such as the On-screen keyboard in Belle FP2, and since this update won't be available to many of the first-gen Symbian^3 devices,...
The variable was set to this bogus value on my machine, too (except for the pathname being garbeled, as @wizard_hu_ observed), so the emulator worked as intended initially.
However, setting this...
Confirmed. It had the same value here, so I guess this is another bug.
Bug report: if the EPOCROOT variable is not set, the emulator (epoc.exe) will start up with an incorrect screen mode, with screen contents and the emulator skin not visible. The effect is immediately...
So the first thread about the DBMS example is probably the best place to continue the discussion, as it has the most detail in already.
That mis-parsed error message is still confusing to users......
Perhaps it is best if you could briefly describe what you are trying to do, and what error message you are getting exactly that keeps you from running your software on the device.
For example:...
One possible workaround to get started with testing on the device could be rebuilding from the command line using the standard Symbian build tools (bldmake/abld...), as it is only Carbide's error...
Hi,
I noticed that the E6-00 devices all still run the 21.x firmware. Would it be possible to upgrade some of them to 22.x (released about 2-3 weeks ago), as this is probably the most advanced...
For what it's worth, the error went away after I tried to submit my application for the first time - now I can see a history of my old submissions (from one account; it seems that the...
I find that, with the latest Symbian Browser 7.3 (NokiaBrowser/7.3.1.26, tested on E52), the behavior of the JavaScript focus() method for some controls has changed, at least for web pages in...
Of course this brings up the unexplored, unacknowledged link between Symbian Signing and ant-piracy measures again. To my knowledge, this was never part of the official goals of Symbian Signing (with...
I find that this is still an issue for me - is anyone else seeing this problem as well, or is this a specific bug with my account? It occurs with both Internet Explorer and Firefox.
Screenshot...
I am beginning to wonder if there is actually a disconnect here between the way users (and freeware developers) look at applications in different regions of the world - could it be that there are...
Perhaps worth putting into the "Known Issues" sticky post?
I just downloaded the certificate again, and get this from devcertlist:
Listing all Capabilities's in devcert
NO TCB
CommDD
Power Management
MultimediaDD
Read Device Data
I just tried re-downloading my certificate, but no luck - installation still fails with "Requested application access not granted".
Another quirk that I noticed for our account on the new portal is that the page "My Dashboard" (https://www.symbiansigned.com/signedui/submission/history) doesn't seem to work for me. Both...
Did you already re-apply and get approval with the new portal? In this case your problem is the same as mine - the approval appears at the end of the list on the "All Files, DRM, TCB" tab (note that...
Looking at the new extension in one of my certificates, it seems that it contains a list of all our UIDs - I suspect that the new DevCerts are actually somewhat more restrictive than the old ones,...
Did you try re-applying for the capability on the "All, DRM, TCB" tab already? I did this yesterday, and got a confirmation of my approval last night - I assume that accounts have to be manually...
I am trying to do a similar thing, though for "All -TCB" capabilities (i.e. AllFiles, DRM). If I understand the instructions right, it is necessary to re-applyusing the "New request" button on the...
Thanks a lot - that is indeed the best place to continue discussion.
As a follow up, I'll still cross-post a thought here that I originally wrote as a comment on AAS, as this relates specifically...
In my view one important aspect of this whole discussion is not so much the possibility to somehow adapt any un-supported constructs to managed code, but the cost to do it. Will it be as easy as...
There is some discussion about possible options here
http://stackoverflow.com/questions/2455372/windows-phone-7-and-c-cli
but they all seem to converge on the idea that a "safe subset" of C++...
I am not entirely sure what section to post this is, but given the assumption that people in the Open C forum are probably the ones most interested in portability of "core engine" or "legacy"...