Re: Developing is soo difficult
 

what do you mean by "slow loading up"?
what cpu/memory does your box use?

for normal development you are free to do everything on your desktop.
until you know, what to do how with qt, there's no point in doing stuff on the n900 anyway.
with a good ide, all those steps are usually hidden behind one or two mouse clicks (but it helps to know, how to do that manually).

that's up to you.
you still need to learn, how qt works, since it is done basically the same when using pyqt.
Qt Designer should be available to you, but that i don't know for sure. never really got along with gui designers (be it qt or java), however.

Re: Developing is soo difficult
 

Would you care to name these phones?

Re: Developing is soo difficult
 

I was able to connect N900 from my Fedora 12 using WLAN-AdHoc method described through PC-Connectivity documentation. I installed PC-connectivity package for N900 and similarly for Fedora 12 (Later found that I use many similar tools already and removed it)

I could access the device via ssh (both from shell and with gftp) and vnc using tigervnc. However sshfs mounting causes a hard shut-down on N900 (did twice)

Linux instructions are in that documentation geared towards Debian/Ubuntu users. I couldn't figure out Bluetooth networking. N900 and my Fedora 12 communicates fine (sending/receiving files) via bluetooth but F12 reject networking with N900. I prefer connecting wirelessly unless I need to transfer a big file or charge at the same time. Internet sharing is a bit more work, and probably I will not try providing wireless networks available most of the time around me.

Is there any body having lock-ups when they use sshfs? I could live without having a shared directory. However I would be happy if I could manage Bluetooth networking. Because I can only connect one wireless point at a time.

Leave my wireless to my Fedora 12 and communicate with N900 via Bluetooh (for ssh + vnc) seems like the easiest and most useful solution for me.

Re: Developing is soo difficult
 

I'm not sure exactly what you mean by lockups, but when I'm developing on the device with ssh, or with sshfs, I have to turn off WiFi "Power saving." No glitches after that. I turn "Power saving" back to "maximum" afterwards.

Re: Developing is soo difficult
 

How do you connect to a wireless network for internet access and to N900 at the same time? I actually meant hard-shutdowns by using lockups. It really kills the device requiring a hard restart using on/off button.

Re: Developing is soo difficult
 

This madde thing looks great! No more that shitty scratchbox.

Even though some of you are saying that embed device development is pain in the *** because it is embed device development I don't think it should be. IPhone and Android are good example of that.

Re: Developing is soo difficult
 

Infrastructure mode. I would be surprised if your problems continued if you did the same.

Re: Developing is soo difficult
 

Do you set N900 to infrastructure mode or the wireless access point? I still don't understand how to connect to the wireless internet and N900 wirelessly using one wireless device.

Re: Developing is soo difficult
 

1)
It needs bluez-compat rpm package installed.

2)
Then configure bnep0 network device to have manual IP address 192.168.3.14 and netmask 255.255.255.0
in Panel: System/Administration/Network

3)
Configure PAN:
# cat /etc/sysconfig/pand
PANDARGS='--listen --secure --encrypt --persist --role NAP --ethernet bnep0'

4)
If you want N900 to access Internet through your Fedora PC:
In Panel: System/Administration/Firewall,
configure firewall to NAT on your network device which is the gateway to the Internet,

and in /etc/sysctl.conf
# Controls IP packet forwarding
net.ipv4.ip_forward = 1


On N900 side, same instructions as for Ubuntu.

Re: Developing is soo difficult
 

If you have an access point, everything should be in infrastructure mode. Maybe a simple way to think of it is:

the n900 is an infrastructure client for routing and DNS

and

the access point is the infrastructure server for routing and DNS

Ad-hoc mode is when the roles have to possibly be negotiated, usually because there isn't a dedicated access point available. What exactly is your hardware situation? List ALL network devices.