Prototype n95

i just picked this up on All About Symbian. http://www.allaboutsymbian.com/forum/showthread.php?t=74989
seems someone has offloaded an prototype n95.
maybe nokia would be interested in thier security or are they actually selling these now?
I'd rather die on my feet, Than keep living on my knee's!

All prototypes remain the property of Nokia, and no individual has any right to sell them. Anybody who buys such a device is effectively handling stolen property.
If this or any post answers your question, please remember to help others by pressing the 'Accept as solution' button.

Similar Messages

Why no ASR (Automatic Screen Rotation) for the N95...

I saw that Nokia implemented the ASR for the upcoming version of the N95 8GB, v.20.0.016
Why wasn't it implemented in v.21.0.016 of
the N95-1 (RM-159) ?
Will it be implemented in the final version? (i hope)
Message Edited by semuelt on 03-Apr-2008 06:05 PM
Nokia N95
RM-159
v.31.0.017

04-Apr-2008 12:08 AM
psychomania wrote:
I often wonder if rotate me was actually samir's (the creator of rotateme) idea?
Did he think it up himself or did he see an N82 prototype in action with ASR?
Did nokia "borrow" samir's idea and use it in the N82?
All I can say is that I prefer the built-in ASR.
Well I don't think any of us like not having automatic screen rotation. Although I'd rather if there was an option to change the way the screen rotates. For example, the screen splashes like water or something that's more interesting than a boring "blink".
That's right people, I'm back. Where have I been? I have been getting a life, away from this electric madness.

Windows Vista + N95 + Image Store - "Error communi...

I am trying to store images from my N95 using the Image Store application. This worked beautifully in XP, but after upgrading to Vista, all I get is a dialog box telling me "Error communicating with the phone".
This happens for both Bluetooth and USB connection, and it doesn't help that I set the Image Store to XP compatability, or run as admin. I really miss the Image Store functionality, it took the fuss out of storing images from the phone completely.
How can I fix this?
Details: Nokia N95
V12.0.013
19-06-07
RM-159
Nokia N95 (03.01)
Window Vista Business
PC Sync - 6.84.10.3
Image Store 6.83.0.0
Best regards,
Goran

There is another cause and cure I think cause I just "fixed" my problem of this kind over many hours of agonising and trying the suggestions above. Another internet site tells you :
"This usually happens for the simple reason that Gallery on the S60 device is running and currently holding open one of the files you're trying to backup (and delete). Switch to Gallery on the smartphone, back out of the image or video clip and use 'Exit'. Now try the 'Store images' function again - it should work fine!"
Unfortunately I couldn't obviously see a photo open in the Gallery. I was trying to store 103 images and I noticed it was stopping at one. I had a look at that one, it was not that important so I deleted it and try again. And it worked! It was as if it was evil, and blocking the software at that point. So it backed up about 70 images and jammed again. Found another image which I remember taking with the camera about a week ago and deleted that one, again not too important. Tried again and it went all the way backing up to a photo I took yesterday.
So that's it, something is left half open when the photo is saved and it screws up image store when it reaches it. Actually, I think that last image which I took I screwed up by closing the camera cover before it had finished doing its thing. I think now the moral of the story is that the digital camera in my N82 and it's softwared needs some TLC, it is not that robust, you need to give it a few seconds to do it's thing or it half saves these corrupted images. I could view the stuffed up image perfectly on the camera and Im sure there would be a better technical way of properly closing it in symbian rather than deleting it but yay it is solved!!

Who can solve iSync problem with Nokia N95? (I use the Nokia plug already)

Hello
Since I bought my new cool Mac:, I sync my N95 with iSync and the Nokia N95 plug-in. Thinking at first that is works flawlessly (as other members here seem to think as well) I later found out, that if I make changes to any calendar or "to do" description! on either the N95 or the Mac it syncs, but only up until a certain number of characters. If I exceed this number, the description on the phone will simply be cut off - in the iCal it still fully appears though.
Rather surprising, since when syncing with a PC via the Nokia PC suite there is no such an issue. All my often lengthy descriptions are fully put on the phone. And if I sync back there are no problems either. So I guess it has to do with the iSync protocol or this Nokia N95 iSync plug-in? Any ideas, solutions...? Any help greatly appreciated!
A bit in despair
Zuckermann

The flex cable is damaged. Some years back when I had a Nokia N95 8GB the flex cable was damaged and for a few days the screen was showing strange colours at the display and eventually the screen became black. I went to a local repair shop and I replaced the flex cable and what I noticed was that the flex cable that it had no proximity sensor on it so I told the technician to remove the proximity sensor on the original one and replace it with the new flex cable. Another thing I discovered was that after fitting the flex cable and returning the cover the front camera was not in its usual position so the technician had to do some modifications to get it back to its normal position and after a few months it was damaged and this time I went to Nokia Care Centre and replaced the flex cable for a small fee and what I noticed was that the flex cable that I previously bought was a fake cable. The one bought from Nokia Care Centre had its proximity sensor and when the cover was returned the camera was in its exact position the same as it was with the original flex cable. What I wanted to say is that please beware of fake flex cables on the market and I suggest that you buy it from an authorised Nokia Dealer.
Ngwangwa - Six Million Ways To Die Choose One

N95 lock ups

Hi have just got my n95 and its great apart from it has started to lock up. The screen illuminates black and blank and the nav keys on the front light up. From this point all I can do is remove the battery and re boot it? Anyone got any ideas ???

28-Sep-200706:14 PM
sjwlifts wrote:
23-Sep-200706:04 PM
sjwlifts wrote:
Got it back o Friday, taking it back on Monday, same fault.....................watch this space...
Just to keep saga up to date my phone went back to car phone warehoue on Monday, went to there technical department on Tuesday and today is apparently on its wy back to Nokia as they cant fix it. Phone only out of the box two weeks, maybe it will be back in time so I can give it to myself for Christmas...............
update. MY PHONE IS BACK. Dont know what fault was but its been to Denmark had it back two hours. And so far so good.
Watch this space..............

N95 Help Application not working!

i have trouble with my N95 Help Application,
it dose'nt work, i can only run it, and see the main list,
i did'nt complain before cause i hardly used it!
but now, when i use help from other software, i get the same error "
message Memory Full. Close some applications and try again."
i have the latest firware!
what could be causing this!

I have the same problem - no in any applications or using the Help application itself.
Of possible interest ?>: is a 'help folder' I have with a name displayed in the Help application as 4x boxes.
Using: -Menu -Tools -Utilities -Help
...I have an odd looking file listed at the end (after 'ZipManager' & before '3-D ringing tones'). The name is displaying as 4 x boxes - presumably non display characters ?>
Is this folder on all N95s ? (i.e even those with a working Help) ?
Anyone know how/where to locate this folder ?
HammY

N95 8GB unlokced , Vibrating alert does not work

Hi
I just bought used N95 8 GB from my friend which is locked to a network provider.
My friend took it to shop to unlock service provider (he didn't realise that service provider does it for free), now I tried to test income call vibration but it seems to me it does not work , I tried under Tool > Profile > Create new profile (vibrating on) ,,,,but still there is no vibration when I receive call!!!
I tried "Factory Settings" for the mobile but still same problem
Would unlock be the reason for that (I don't know if vibration was working before unlock) ?
Any other suggestion how to test that ?
Thanks

jimmyireland wrote:
1st see if you have the latest firmware installed, if you dont have the latest update and if problem still occurs after the update try a hard reset the code is Press *#7370#
if this fails you will need to take it to a nokia care centre.
1- Yes it already has updated firmware
2- I did a hard resst without any success.
3- Would unlocking process normally create this problem ?
Message Edited by zillah on 20-Jun-2009 12:02 AM

After update N95 8gb i got big problems.

I make a backup of all but not the 8gb-memory, and restured all after upate, and everyting seems to work fine.
First problem; i see now i have no 3g 3 (no connection) competely dead, i can not use the phone to communicate.
Strange everything work fine after update yesterday and this morning, something happen when it was in the locker at work.
And now i can't use Maploader, it say i have no memorycard, i understand that problem, i delete the whole Cities-folder this morning, because i dont need Nokia GPS-program Wayfinder anymoore, i choose Nav4all instead, i try the maploader only to for testing, i don't want to download any maps.
I test maploader now only bacause my phone is completely dead in communication, try to find out why.
I check in Nokia Nseries PC Suit everything on PC & mobil are the latest update.
I have another mobile SE M600i with 3g 3-cashcard, i by that cashcard only to enable the phone to start, not for communication, that mobile have full 3g (and probably work fine).
Was it the thing that i delete the Cities-map, no it can't be, because i use the N95 8gb and it work fine after that.
after work i even have a missed call on that mobile, but i can't call back, it's dead in communication now.
Strange things happens now.
Kjell O

15-Apr-2008 11:48 PM
kjello wrote:
Where can i change networksettings, all settings i find is; 3, tre, tre(01), tremms, tremms(01)
Is your phone in another language? You should normally see 2 or 3 options.
1. Dual Mode
2. UMTS
3. GSM
Maybe you could try reseting the phone if nothing else works.
Always remember to backup your phone before performing resets as your data may be lost.
Try these
*#7780# - Restore factory settings - resets all the settings to the default
*#7370# - Reformat your phone

N95 USB id not recognized if behind two levels usb...

Hi,
I spent a lot of hour, to reconnect my N95 via USB, because, explanation at the end, it seems impossible to connect the phone is there is a HUB between the N95 and the computer (else than the native buitin-the-computer).
Before everything was installed since two years. By accident equipement bluetooth have been destroyed and Windowd XP SP3 installation should have to be redone.
Even I many people that I am a professionnal in informatics, expert in some subjects, I have been lost. I pass on erratics ways, and lost hours to go to the diagnostic : mine :
The USB driver is unable to recognize a N95 (always set to the right USB connection PC-Suite or OBVI) if it is connected on a second level USB Hub.
as I have only three USB main ports I use two USB (USB2 and USB ... ) on my portable (DELL Latitude D800 and XP SP3)
During installation of PC-Suite or OVI, the soft see the "new usb device", sometimes says 'N95 master...." but never reaches to end the installation : what happends :
- the windows USB detection sees too at the same time (behind the HUB) the new USB device and propose to install it automatically, while PC-suite says "installing" (what ?).
then :
If you don't make anything this can spend as long siecles you want.
If you say OK to windows : it answers "impossible to install" and later PC-suite say "you have problems with your connection". If you disconnect you N95 you can have the "blue screen on <ousbehci.sys at address F76BE41D based at F76B7000 datestamp 433c099a>
If on windows you answer "cancel" it immediately detects "a new device" and so on... eternally. But it will create for each try an undefined device into the device manager (stopped at 32).
Some times the main N95 is detected and some others are seen but never all the link devices are detected and soft installed you are reconducted to the previous situation.
This as been repeated on clean installations (unistalling part of drivers installed)
If you connect your N95 directly on the first level of HUB it is perfectly installed.
But as my Hub are well alimented and Ucc controlled (7 disks, camera, Micro-cards reader etc...) ir is not a current alimentation problem.
Later when you reconnect your N95 is not detected if it his not connected on the first HUB level (integrated to computer)
So after this bad experience I have one advice to the others users (by security) :
- never install threw a second level HUB
- if after a good installation at a reconnect via an HUB, the 'new USB device found' main USB installer panel appears (if you change of connection this can be normal) but fails, which is not normal, connect directly your phone only on a main USB connection of your computer (and clean your device manager - XP SP3)
Trebly
03/01/2011 16:15

im having the same problem i think. When I plug my bionic into my computer nothing happens on my computer or my phone. I can't access any files from my computer. I think I may be stuck in charge only mode but I don't know how to get out of it. I have tried this on multiple computers. Anyone know how to fix this?

HOW TO EASILY SET UP WIFI WITH TH N95 AND A MAC WI...

Hi this is how to connect a mac running os x 10.4 (tiger) to a n95's network and succsesfully share the macs internet via airport (wifi)
first (on mac) go to:
system preferences then sharing on sharing click services and turn personal web sharing on (tick the box)
next go to internet and on the drop down menu next to "share your conection from" select built in Ethernet (or what ever you use to access net)
now tick the box that says airport and click airport options
copy in as follows:
network name: -what ever you want-
channel: automatic
tick enable encryption (WEP)
password: -use a word thats 13 characters long-
Wep key length: 128
click ok and click start!
now on n95 go to:
settings>connection>access points
then go options and new access point
connection name: use any name you like
data bearer: wireless LAN
Wlan networkname: search for network > select the network that you no is yours
network status: puplic
Wlan network mode: infrastructure
!!!!!!!!!before you go to wlan security mode push options!!!!!!!!!!
then advanced settings then IPV4 settings and enter in the following numbers
phone ip: 10:0:2:5
subnet mask: 255:255:255:0
default gateway: 10.0.2.1
primary dns address: 10:0:2:1
!!!!!before you enter secondery go back to you mac and go system prefs and then network on network it should say:
location: automatic
show: network status
from there copy your ip adress into your phones "secondary DNS address"
(you ip is located after built in ethernet where it says ip then somthing like 211:243 ect.)
now on the n95 go back until you get to where it said wlan security mode
wlan security mode: WEP
wlan security settings:
WEP Key in use: (hash)1
authentication tyoe: shared
WEP key setting's:
WEP encryption: 128 bits
WEP key format: ASCII
WEP KEY: - the 13 charictor password types in on the mac-
now go back until you you reach your main n95's menu
select tools then WLAN WIZ.
the network you created on the mac should apear as known select it then start web browsing!!!
hope it works for you as it did for me thanks

Hi ogigacz
On Leopard they hid away the APN field under advanced configuration options for bluetooth modems.
I don't know whether you have found this workaround:
http://n95blog.com/using-the-nokia-n95-as-modem-for-a-mac-over-bluetooth-on-vodafone-live-in-holland...
Happy to have helped forum in a small way with a Support Ratio = 37.0

Snooze problem since software update on N95

I've had my N95 for about 18 months now. I don't use a lot of the things on it, but one I do use is the alarm clock to get me out of bed in time for work. I like to have a bit of "coming around" time so I usually have a few snoozes before getting up. I generally switch the phone off at night so I don't get woken by text messages and calls.
This has worked fine since I got the phone.
However, this week I upgraded to the new software and since then I've had the following problem -
When the alarm goes off and I press snooze (which makes the phone switch off again)the alarm doesn't come on after 5 minutes. However, once I turn the phone on the snooze alarm immediately comes on even if this is 10 minutes after it should have.
I tried the following test to try to replicate it once I had got to work. With the phone on, set the alarm for a few minutes in the future, then snooze - works fine. With the phone off do the same - works fine.
So it appears that this problem either happens when the alarm is for the following day or when the phone has been off for some time.
Has anyone else found this and does anyone have any suggestions of how it could be resolved?
Thanks

This all happened a while ago so it's going to be buried deep down in the forum. What I can do is summarize the problem here.
If the phone was switched off before midnight and left off overnight the clock would jump forward several days from time to time.
This would cause alarms not to go off at the desired time.
The snooze function was dysfunctional. Regardless of the snooze time set in the clock's settings, if you decided to snooze an alarm it would snooze for the default 5 minutes and sometimes freeze the phone up when the snooze time was up.
The workaround for these problems is to leave the phone switched on overnight, which is why I never noticed them on my N96 until reading about them here - I leave it on overnight. It doesn't fix the snooze duration problem but it does prevent the phone from freezing, which is a good start.
I think you'll find that the Nokia developers are already aware of this problem. When there's a huge outcry of despair like this on these forums, the moderators do pass the information back to the dev teams.
Was this post helpful? If so, please click on the white "Kudos!" star below. Thank you!

Missing prototype and Undefined Symbol errors

So, I am using an Opal Keyy XEM3005 board.
Depending on the documentation I read, this board has a native ANSI C interface with a C++ wrapper.
In their forums, they say to rename the ".cpp" file to "c", and then go forward with calling the default constructor & keep track of the pointer. Their functions are all in an externally loadable DLL.
Well and good.
Their API documentatin is available here: http://www.opalkelly.com/library/FrontPanelAPI/
I have written a REALLY simple app to ease my way in - it does nothing more than allow the user to throw a switch, and when this happens, it goes off to connect to the board:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#include <cvirte.h>
#include <userint.h>
#include "Try1.h"
#include "XEM.h"
#define _WIN32_WINNT 0x0501
//#define _WIN32
#include <windows.h>
static int panelHandle;
static okFrontPanel_HANDLE   XEM_Device;
int __stdcall WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance,
LPSTR lpszCmdLine, int nCmdShow)
if (InitCVIRTE (hInstance, 0, 0) == 0)
return -1;   /* out of memory */
if ((panelHandle = LoadPanel (0, "Try1.uir", PANEL)) < 0)
       return -1;
   DisplayPanel (panelHandle);
   RunUserInterface ();
   DiscardPanel (panelHandle);
   return 0;
int CVICALLBACK Connect (int panel, int control, int event,
       void *callbackData, int eventData1, int eventData2)
   int   Value = 0;
    switch (event)
       case EVENT_COMMIT:
           GetCtrlVal(PANEL, PANEL_CONNECT_SWITCH, &Value);
           SetCtrlVal(PANEL, PANEL_CONNECT_LED, Value);
           if( Value )
               XEM_Connect(XEM_Device);
           else
               XEM_Disconnect(XEM_Device);
            break;
   return 0;
int CVICALLBACK Quit (int panel, int control, int event,
       void *callbackData, int eventData1, int eventData2)
   switch (event)
       case EVENT_COMMIT:
           QuitUserInterface (0);
           break;
   return 0;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This, of course, works fine by itself (with empty _Connect() and _Disconnect() functions)
I then started working with the XEM_Connect function.
The first step is to run their LoadDLL function as such:
int XEM_Connect ( okFrontPanel_HANDLE   XEM_Device )
   int   NoDevices = 0;   //   Number of devices attached to the PC
   //   Load the DLL (?)
   // Load the FrontPanel DLL
   if (FALSE == okFrontPanelDLL_LoadLib(NULL))
       printf("Could not load FrontPanel DLL\n");
       exit(-1);
    return XEM_SUCCESS;
And this would compile and run just fine.
Now, when I added the functions to start trying to get info about the device, I started getting "missing prototype" errors.
int XEM_Connect ( okFrontPanel_HANDLE   XEM_Device )
   int   NoDevices = 0;   //   Number of devices attached to the PC
   //   Load the DLL (?)
   // Load the FrontPanel DLL
   if (FALSE == okFrontPanelDLL_LoadLib(NULL))
       printf("Could not load FrontPanel DLL\n");
       exit(-1);
   //   Find out how many devices are attached
   XEM_Device = okFrontPanel_Construct( );
//   XEM_Device = okCFrontPanel( void );
//   NoDevices = GetDeviceCount( );
   printf("%d OK devices attached\n", NoDevices);
   //   Call the contructor?
//   okCFrontPanel ();
    return XEM_SUCCESS;
Now, I searched the forums and found the bits about adding #define _WIN32_WINNT 0x0501 prior to inclusion of windows.h. Did that. No joy.
Then I searched some more and found the bit about changing the build options to uncheck the "prototype required" flag.
Done.
This seemed to work at first (the above code could be built with no errors, and appeared to run).
So I thought maybe I had it, and added the next line, so:
int XEM_Connect ( okFrontPanel_HANDLE   XEM_Device )
   int   NoDevices = 0;   //   Number of devices attached to the PC
   //   Load the DLL (?)
   // Load the FrontPanel DLL
   if (FALSE == okFrontPanelDLL_LoadLib(NULL))
       printf("Could not load FrontPanel DLL\n");
       exit(-1);
   //   Find out how many devices are attached
   XEM_Device = okFrontPanel_Construct( );
   OpenBySerial( XEM_Device, "UaLgzvVpBJ" );
//   XEM_Device = okCFrontPanel( void );
//   NoDevices = GetDeviceCount( );
   printf("%d OK devices attached\n", NoDevices);
   //   Call the contructor?
//   okCFrontPanel ();
    return XEM_SUCCESS;
Now it doesn't complain about no prototypes (duh), but instead I get linker errors:
Undefined symbol '_OpenBySerial@0' referenced in "XEM.c".
So, dredging through the .h and .c files, I found a couple of things:
in the okFrontPanel.c file I found the following:
okDLLEXPORT ok_ErrorCode DLL_ENTRY
okFrontPanel_OpenBySerial(okFrontPanel_HANDLE hnd, const char *serial)
   if (_okFrontPanel_OpenBySerial)
; return((*_okFrontPanel_OpenBySerial)(hnd, serial));
   return(ok_UnsupportedFeature);
In the okFrontPanel.h file I found:
and also:
okDLLEXPORT ok_ErrorCode DLL_ENTRY okFrontPanel_OpenBySerial(okFrontPanel_HANDLE hnd, const char *serial);
So, I see them in the .h & .c files, but the linker is bombing out.
I smell a problem with actual code to link being in the DLL... How do I resolve this, any ideas? Or am I doing something so stupidly (and obviously) wrong that I'm being blinded to it?

Hi tomii,
My suspicion is that these issues are due to using a C++ dll in a C environment. There are inherent challenges with performing such an operation as you have to make sure all your parameters and settings are correct.
I also could not find the documentation that the Opal Kelly dll is ANSI C but it sounds like you can use this in C with some reconfiguration. I would recommend using their forums to get more information on what steps need to take place to get things working in ANSI C.
From the information you provided, I did find some resources on the missing prototype error and undefined symbol issue with the linker.
For the missing prototype I found a thread of someone actually using LabWindows and seeing this compiler error you may want to look at
http://bytes.com/topic/c/answers/695019-missing-prototype
I found a few cases where using a function definition of int func(void) removes such issue when int func() does not.
Another link I found that may be worth a look can be found at http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html
It gives some good pointers to mixing C and C++ code. Some of it may be applicible in your case.
And, a resource for your undefined symbol linking issue.
http://www.cprogramming.com/tutorial/compiler_linker_errors.html
Hopefully these resources will give some context for getting things compiling and working with your dll.
Good luck!
James W.
Applications Engineer
National Instruments

N95 8GB: Problem on deleting video file

Hi,
Is there any body experienced this problem. When I'm trying to delete a file from Video Centre > My videos directory, I'm receiving this error... "Unable to delete. File video.mp4 is open."
Do you have resolution for this? Tnx in advance.
Br,
Pete

21-Nov-200709:06 PM
pmpinguel wrote:
posted my detailed steps in the n95 8gb main discussion thread. go see
I followed your steps but I got this message.... "USB data transfer mode activated. MASS MEMORY MAY NOT BE USED DURING THIS TIME."
Actually the video file was not there anymore in my File Mgr folder but the problem is the video file is still there in Video centre > My videos folder. When I tried to delete the file using "c" or Options > delete, the error says "Unable to delete. File video.mp4 is open."
I also tried to reset the phone to its factory settings but still video file was there.
I think this is a bug. Pls advice. Tnx in advance.
Br,
Pete

N95-3 disconnection from laptop error

Everytime i disconnect my n95-3 via memory card eject, it automatically connects again straight away. So i have no option but to disconnect it via safely remove. When i do so i then get error on phone stating data may have been lost. data transfers should be stopped before removing the cable. Either way its a no win situation with an error.
History is a mirror of the past!
And a lesson for the present!
(Persian Proverb)

I mean the connection settings called "USB". There you can choose a default mode for the connection. I wondered if you have set that to "Data transfer". And mainly the second point of that menue "Ask on connection": if you have set that to "Yes"?
Sometimes the solution is closer than you think... sometimes farther

New Firmware Update for Nokia N95 (RM-159 ) :Decem...

Hello All,
It looks like new firmware update is available for Nokia N95 basic model .
Earlier Version of Firmware was : 30.0.015
Now the latest available Firmware was : 31.0.014
When i connected my N95 to PC using PC-Suite, it notified me about this. But when i searched the internet for change log , i found none. Is it right firmware , why Nokia didn't disclose change log, which it used to do it earlier ???
I will wait for 2 more days for official communication from Nokia....

Ok, so no one wants to install this firmware because theyre affraid they loose their freedom?
Somebody should shine a light on this FW, or nokia has
done a lot of work for nothing!

Prototype n95

Similar Messages

Maybe you are looking for