Active Topics
-
Phone Camera Competition April 2021: "Funny & Foolish" (33)
to General by Fellfrosch - 14 hrs, 20 mins ago -
What's the best Handheld gnu/linux machine for 20XX? (78)
to Competitors by clort - 19 hrs, 6 mins ago -
Unofficial Storage for camera phone competition... (62)
to General by catbus - 1 day, 3 hrs ago -
Maemo-Leste pre-alpha announcement (512)
to Maemo 7 / Leste by nonsuch - 2 days, 4 hrs ago -
The Intel RealSense Smartphone prototype (0)
to Competitors by n950 - 2 days, 7 hrs ago -
Maemo Leste Playground (57)
to Maemo 7 / Leste by clort - 3 days, 4 hrs ago -
A Palm OS thread ... and a thank you to the community (23)
to Alternatives by bradvesp - 4 days, 3 hrs ago - more...
|
2007-03-26
, 04:05
|
|
Posts: 103 |
Thanked: 10 times |
Joined on Feb 2007
|
#182
|
I read your other thread nspeer. I know this sucks. I resisted, too. But the best bet is to flash gregale. You can upgrade to the latest Maemo Mapper version that has a couple of nice new features. Sorry.
 |
|
2007-03-26
, 16:38
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#183
|
(nspeer: same reply as in your other thread)
I can offer no suggestion as to how exactly Maemo Mapper could have caused this.
Maemo Mapper runs in the (protected) user account (as opposed to the privileged administrator account), just like any other program, so theoretically it is impossible for it (or other normal, non-OS programs) to destroy the rest of the operating system. At worst, programs can corrupt user data (i.e. in "Documents", "Videos", etc.), but application code (including the OS itself) should be protected from corruption by a rogue application. That is the Unix way, and it's why Windows has recently tried to follow suit with the introduction of Vista's security features.
So, either Maemo screwed up and allowed Maemo Mapper to do something it shouldn't have been able to do (and I'm not sure what that would be, unless you manually invoked the "Reset Bluetooth" feature), or Maemo screwed up and took Maemo Mapper down with it as collateral damage. The latter, more systemic option would also explain why none of your other applications work, including the OS programs like the Application Manager.
Unfortunately, neither of those explanations provides for a solution. The first thing I would try is properly switching off your device. It sounds like you haven't been able to do that (because "the hard button won't cause it to shut down"), so try either letting the battery run out or removing the battery entirely.
If you still have problems, I can think of no other solution for you than, as you suggested, re-flashing your device. If you continue to have problems after you re-flash, then it is a hardware problem for which (unfortunately) you must send the device to Nokia for repair.
I can offer no suggestion as to how exactly Maemo Mapper could have caused this.
Maemo Mapper runs in the (protected) user account (as opposed to the privileged administrator account), just like any other program, so theoretically it is impossible for it (or other normal, non-OS programs) to destroy the rest of the operating system. At worst, programs can corrupt user data (i.e. in "Documents", "Videos", etc.), but application code (including the OS itself) should be protected from corruption by a rogue application. That is the Unix way, and it's why Windows has recently tried to follow suit with the introduction of Vista's security features.
So, either Maemo screwed up and allowed Maemo Mapper to do something it shouldn't have been able to do (and I'm not sure what that would be, unless you manually invoked the "Reset Bluetooth" feature), or Maemo screwed up and took Maemo Mapper down with it as collateral damage. The latter, more systemic option would also explain why none of your other applications work, including the OS programs like the Application Manager.
Unfortunately, neither of those explanations provides for a solution. The first thing I would try is properly switching off your device. It sounds like you haven't been able to do that (because "the hard button won't cause it to shut down"), so try either letting the battery run out or removing the battery entirely.
If you still have problems, I can think of no other solution for you than, as you suggested, re-flashing your device. If you continue to have problems after you re-flash, then it is a hardware problem for which (unfortunately) you must send the device to Nokia for repair.
|
|
2007-03-26
, 16:41
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#184
|
Originally Posted by fldude99
If you weren't using POI at all, just remove the POI database file (in the location indicated in the "POI" tab of the "Settings" dialog) and restart Maemo Mapper.
I had to do a backup/restore on my 800...now mapper displays an error that it can't open the POI database and the POI option is grayed out when holding down on a point on the map..any ideas? Seems to work in all other respects
If you were using POI, and if you want to keep that POI, then you'll have to find another solution. Did you re-flash your N800 between backup and restore? Were you using an older version of Maemo Mapper before your backup/restore? If so, you may need to convert your database file from sqlite2 to sqlite3 format (search the forums on how to do this).
|
|
2007-03-26
, 17:11
|
|
Posts: 101 |
Thanked: 14 times |
Joined on Jan 2007
|
#185
|
Thanks for the help Gnuite..before any of that I did a backup/restore and somehow it restored the database file for POI's..why..who knows..but it works
|
|
2007-03-27
, 19:27
|
|
Posts: 75 |
Thanked: 4 times |
Joined on Apr 2006
|
#186
|
I made a patch so that maemo mapper will look for a file called "poi.jpg" if it can't find any other icon. This is so that if you don't like the purple square, you can make a different default.
patch against maemo mapper 1.4.4
And here's the icon I made for it (a blue "X"):
patch against maemo mapper 1.4.4
And here's the icon I made for it (a blue "X"):
|
|
2007-03-28
, 01:29
|
|
Posts: 197 |
Thanked: 4 times |
Joined on Jan 2007
|
#187
|
Originally Posted by gnuite
Thanks for your reply.
(nspeer: same reply as in your other thread)
I can offer no suggestion as to how exactly Maemo Mapper could have caused this.
Maemo Mapper runs in the (protected) user account (as opposed to the privileged administrator account), just like any other program, so theoretically it is impossible for it (or other normal, non-OS programs) to destroy the rest of the operating system. At worst, programs can corrupt user data (i.e. in "Documents", "Videos", etc.), but application code (including the OS itself) should be protected from corruption by a rogue application. That is the Unix way, and it's why Windows has recently tried to follow suit with the introduction of Vista's security features.
So, either Maemo screwed up and allowed Maemo Mapper to do something it shouldn't have been able to do (and I'm not sure what that would be, unless you manually invoked the "Reset Bluetooth" feature), or Maemo screwed up and took Maemo Mapper down with it as collateral damage. The latter, more systemic option would also explain why none of your other applications work, including the OS programs like the Application Manager.
Unfortunately, neither of those explanations provides for a solution. The first thing I would try is properly switching off your device. It sounds like you haven't been able to do that (because "the hard button won't cause it to shut down"), so try either letting the battery run out or removing the battery entirely.
If you still have problems, I can think of no other solution for you than, as you suggested, re-flashing your device. If you continue to have problems after you re-flash, then it is a hardware problem for which (unfortunately) you must send the device to Nokia for repair.
One thing I have noticed. I was able to get to Control Panel > Memory. It shows device memory used as 31% at times and other times when I open Memory it shows 55%. Curious. before my problems started, device memory was at 3%.
So, what is hogging all my memory?
|
|
2007-03-28
, 14:55
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#188
|
Originally Posted by nspeer
When you say "Device Memory", do you mean the internal flash memory (as opposed to the external or internal memory cards)? If so, 3% seems rather low, so perhaps you are referring to your memory card's memory.
Thanks for your reply.
One thing I have noticed. I was able to get to Control Panel > Memory. It shows device memory used as 31% at times and other times when I open Memory it shows 55%. Curious. before my problems started, device memory was at 3%.
So, what is hogging all my memory?
If you've set up Maemo Mapper to use your memory card, then it will use your memory card's disk space for maps. This might be using up your memory.
Or, if you have a "core-dumps" directory in your memory card, then it could be core files that are taking up memory, especially if programs have been crashing a lot since your problems started.
|
|
2007-03-29
, 04:11
|
|
Posts: 197 |
Thanked: 4 times |
Joined on Jan 2007
|
#189
|
Gnuite,
I really do mean device memory, I assume that's the internal flash memory of the 770. It always did read at 3%. So, now since my problems began, something is using A BUNCH more memory. There is lotsl of room left on my 1 gb memory card (and yes, MM is set up to store my maps on that card). I read another post on these boards where someone said their device got all messed up when they let the battery get too low. Thinking back, I was navigating with MM and downloading a map with my phone as a modem when MM shut down and all my problems began. I only had one bar on the battery meter at the time. So, maybe this was a contributing factor.
Anyway, it looks like I am going to flash to Gregale to hopefully fix my OS. This is not all bad as now I'll be able to upgrade to the latest Maemo Mapper (yeah!). Following Gnuite's advice in an earlier post, I want to "backup" my system files to my 1gb memory card using an Xterm command line and then restore it back once I've flashed. This is to preserve my GPE-Pim contacts and calander. Since my 770 has been constantly locking up and rebooting itself, I am worried that this might happen while I am in Xterm and that I'll BRICK my 770 if that happens. Is that possible? I mean, if I'm in Xterm, could whatever is causing my 770 to lock up and reboot still happen or is that not possible in Xterm?
Last edited by nspeer; 2007-03-29 at 04:13.
I really do mean device memory, I assume that's the internal flash memory of the 770. It always did read at 3%. So, now since my problems began, something is using A BUNCH more memory. There is lotsl of room left on my 1 gb memory card (and yes, MM is set up to store my maps on that card). I read another post on these boards where someone said their device got all messed up when they let the battery get too low. Thinking back, I was navigating with MM and downloading a map with my phone as a modem when MM shut down and all my problems began. I only had one bar on the battery meter at the time. So, maybe this was a contributing factor.
Anyway, it looks like I am going to flash to Gregale to hopefully fix my OS. This is not all bad as now I'll be able to upgrade to the latest Maemo Mapper (yeah!). Following Gnuite's advice in an earlier post, I want to "backup" my system files to my 1gb memory card using an Xterm command line and then restore it back once I've flashed. This is to preserve my GPE-Pim contacts and calander. Since my 770 has been constantly locking up and rebooting itself, I am worried that this might happen while I am in Xterm and that I'll BRICK my 770 if that happens. Is that possible? I mean, if I'm in Xterm, could whatever is causing my 770 to lock up and reboot still happen or is that not possible in Xterm?
Last edited by nspeer; 2007-03-29 at 04:13.
|
|
2007-03-29
, 14:49
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#190
|
Originally Posted by nspeer
It's unlikely that a copy operation done in an xterm would do anything to cause your 770 to lock up, although in your situation, I suppose anything is possible.
Since my 770 has been constantly locking up and rebooting itself, I am worried that this might happen while I am in Xterm and that I'll BRICK my 770 if that happens. Is that possible? I mean, if I'm in Xterm, could whatever is causing my 770 to lock up and reboot still happen or is that not possible in Xterm?
In any case, you can't brick your 770 in xterm. No matter what happens, you'll be able to re-flash your device. It's actually extremely difficult to brick a 770 - the hardware pretty much has to be broken for that to happen.
I just tried to uninstall Maemo Mapper using the Application Manager. The App. Manager loads but immediately begins to "update". The update dialog box then freezes, and I get a reboot. When I tried clicked the installed apps box, it said that no apps are installed, which is of course incorrect.
Is a reflash my only option now?