For some odd reason the TastePhone page has not added the results from testing the Vodafone 710 (made by Huwei) on the list site, but I managed to dig out the results;)
see http://mobile.myshack.mine.nu/Vodafone_710_%28Tastephone%29 for the results.
Monthly Archives: April 2007
Nokia S40(series) Subscribe to GPRS (or PACKET) first
I had this error message when I tried to access the internet via a java application.
I knew that GPRS was set up correctly and working (since I had downloaded that java application and more), so what could the problem be?
Turns out that Nokia S40 phones only use the internet settings that are sent from the operator for Wap browsing, not for applications and that I need to make these settings my self.
Most phones I have tried this on so far have had very similar menus for doing this (the biggest difference so far has been that some phones calls it PACKET instead of GPRS (witch does stand for General Packet Radio Services;).
I will now make a general instruction (and add phone specific as comments, please add how it looks on your phone if you have another Nokia S40 model). The values within () are those I used for Telenor Sweden.
Settings -> configuration settings -> Personal configuration settings
Use add new -> Access point
Account name – Use something remember able
Access point settings [check your providers settings and use the correct once]
Data bearer
GPRS/PACKET
Bearer settings
GPRS/PACKET Access point (this is sometimes called Access Point Name (APN), and ought to be an ip or a domain name).
(internet.telenor.se)
Authentication type (not all carriers use this, but check your settings).
(Normal)
User name (not all carriers use this – leave blank if not needed, but check your settings).
()
Password (not all carriers use this – leave blank if not needed, but check your settings).
()
Simply use “back” when you are done (it will save the changes).
Back to the “Personal config. settings” menu
Options -> Activate
Now we (should be) done and all should be working well. One phone (I can’t remember what one just) was unable to surf WAP after doing this but getting new settings from my carrier worked.
Nokia security code
Hmm, having a default code to make a factory reset, this might be a good thing (in a way), but wouldn’t it have been better to have it turned off as default and make up a own code if I feel I would need one. Having it active and using a default sems like an odd idea. (Then again letting the user = me?) know this code is nice. We are still missing our handset code for one of the sharp phones at work 🙁
A: The default security code for your Nokia phone is 12345.
Changing resolution on a nokia java file (S60 3rd ed or later)
or how to cheat and support a Nokia 352×416 using “normal” S60 (176×208).
Either in the manifest file or the jad file enter these two lines. (thus making it possible to use a Nokia S60 file on a Nokia N80 (et al)
Nokia-MIDlet-Original-Display-Size: 176,208
Nokia-MIDlet-Target-Display-Size: 352,416
This parameter works on all S60 3rd ed (or later).
Making it possible to rename File to file under Samba
Had a slight issue with samba.
It didn’t see an upper case name as different from a lower case, i.e. it didn’t let me rename file to File (directly, I could rename it to ile first and then to File). Adding the following line in smb.conf (and restarting Samba) allowed me to do this.
case sensitive = yes
(The manual says, controls whether file names are case sensitive. If they aren’t then Samba must do a file name search and match on passed names. Default no)
Installing Pine (or Pico) from source
Installing Pine on Debian might seem a bit tricky, but it isn’t as hard as it might look.
Due to the licensing rules of Pine (and Pico) these are not included as deb packages in the mirrors.
However the source of these two are.
Step 1 is to ensure that you have a deb-src in /etc/apt/sources.list (for instance)
deb-src http://http.us.debian.org/debian stable main contrib non-free
deb-src http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free
To make Debian install from sources:
If you have never installed from source before we need to install a compiler and dpkg-dev
$apt-get install dpkg-dev
$ apt-get install gcc
Done, now we can start compiling Pine
A short note now: When building from source apt will download the source (and compile) to the directory where you start from. I think it is nice to make sure you are in a new directory that is clean from other files (and at a logical location if you intend to save the compiled package (like for instance /src/pine)
$ apt-get -b build-dep pine
$apt-get –only-source -b source pine
(now it will download and compile Pine. Be patient.
$ dpkg -i pine_4.64-3_i386.deb
Another option is downloading a deb package directly from Washington University here
Any program in the Debian archive can be compiled from sources using the steps above, important to note is that in “apt-get -b build-dep” -b means build from source and build-dep that apt should download any libraries that is needed at the same time.
Removing config files when un-installing
If you want apt to remove the config files as well when you uninstall a program (or maybe as I have removed them manually and is unable to reinstall using apt-get install)
$apt-get –purge remove pkg-name
This is a command i had to learn the hard way as I (accidenly) removed the /etc/munin (a server monitor tool) directory. After I had done this I was unable to get apt-get install to make any new config files in the /etc/ directory. Turns out that removing without using –purge (normaly) leaves the old config files (if I wish to re install later I assume).
apt-get update and key problems
After updating my installation to etch I ran into a sligt problem with apt-get.
I just got an odd error message from apt-get update
GPG error: ftp://www.se.debian.org unstable Release:
The following signatures couldn’t be verified
because the public key is not available:
NO_PUBKEY F1D53D8C4F368D5D
W: You may want to run apt-get update to correct these problems
Well, running apt-get update again (and again…) has no effect;)
What it (tries to) tell me is that the key used to verify the files in the archive was not found
The solution to this is simply
$ gpg --keyserver wwwkeys.eu.pgp.net --recv-keys F1D53D8C4F368D5D $ gpg --armor --export F1D53D8C4F368D5D | apt-key add - $ apt-get update |
The wwwkeys.eu.pgp.net can be exchanged for any other key server that hosts the key, the only thing to note is that you should only use a key server that you feel is trusted.