maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Development (https://talk.maemo.org/forumdisplay.php?f=13)
-   -   Developing is soo difficult (https://talk.maemo.org/showthread.php?t=50358)

gsever 2010-04-19 00:08

Re: Developing is soo difficult
 
Quote:

Originally Posted by zimon (Post 616825)
1)
It needs bluez-compat rpm package installed.

I have this one

Quote:

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
I don't have a bnep0 listed under System/Preferences/Network Connections/ tab. I have found a few examples online but not sure how exactly to create a correct one under /etc/sysconfig/network-scripts

Quote:

3)
Configure PAN:
# cat /etc/sysconfig/pand
PANDARGS='--listen --secure --encrypt --persist --role NAP --ethernet bnep0'
This I have and modified.

Quote:

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
I dont' need to share the internet I just want to be able to vnc and ssh to N900 via bluetooth network.

Quote:

On N900 side, same instructions as for Ubuntu.
I followed the instructions on N900 exactly as they are described on the pc-connectivity documentation.

gsever 2010-04-19 00:17

Re: Developing is soo difficult
 
Quote:

Originally Posted by daperl (Post 616889)
What exactly is your hardware situation? List ALL network devices.

Are you asking ifconfig output?

Code:

ifconfig
eth0      Link encap:Ethernet  HWaddr
lo        Link encap:Local Loopback 
wlan0    Link encap:Ethernet  HWaddr
wmaster0  Link encap:UNSPEC  HWaddr


daperl 2010-04-19 00:36

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 616917)
Are you asking ifconfig output?

No, I meant actual hardware:

laptop
n900
wireless router
etc...

But I'm guessing if you [i]had[/] a wireless router, we wouldn't be having this conversation.

gsever 2010-04-19 00:40

Re: Developing is soo difficult
 
Quote:

Originally Posted by daperl (Post 616934)
No, I meant actual hardware:

laptop
n900
wireless router
etc...

But I'm guessing if you [i]had[/] a wireless router, we wouldn't be having this conversation.

You are close at you guess :) (Just 2x Laptops)

My problem was connecting to N900 and Wireless Router at the same time from my Fedora 12 laptop. Since I couldn't achieve this yet I am trying to resort to bluetooth networking. Right now without actually connecting to the N900 adhoc wireless point I can't talk to the device via ssh. And when I do that I lose the internet on the laptop.

daperl 2010-04-19 01:47

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 616936)
You are close at you guess :) (Just 2x Laptops)

My problem was connecting to N900 and Wireless Router at the same time from my Fedora 12 laptop. Since I couldn't achieve this yet I am trying to resort to bluetooth networking. Right now without actually connecting to the N900 adhoc wireless point I can't talk to the device via ssh. And when I do that I lose the internet on the laptop.

If you have a wireless router, like I said, set ALL devices (n900, laptop, router) to infrastructure mode. You won't need bluetooth anything. What's the make and model of your router?

gsever 2010-04-19 02:04

Re: Developing is soo difficult
 
Quote:

Originally Posted by daperl (Post 616977)
If you have a wireless router, like I said, set ALL devices (n900, laptop, router) to infrastructure mode. You won't need bluetooth anything. What's the make and model of your router?

The router is a NETGEAR device and serving in intrastructure mode. PC-Connectivity provides wlan_adhoc only. So I am guessing there has to be alternative way to connect the device via wireless network. I am connected to the wireless router now, and connected N900 to the same network I am in. However I can't fetch the local ip.

According to your explanation I should be able to connect N900 using these settings. What is the next step?

craftyguy 2010-04-19 02:18

Re: Developing is soo difficult
 
Last time I tried the MADDE/Qt Creator combo, I discovered that it did not support QT-4.6...
Has this changed at all?

It IS difficult to get a build environment up and running for this device. More than once I've given up on an idea for an application because I did not want to spend all afternoon tinkering with scratchbox/MADDE/whatever just to get it to work seemlessly..

gsever 2010-04-19 02:30

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 616988)
According to your explanation I should be able to connect N900 using these settings. What is the next step?

Replying to myself :)

Did apt-get install iproute (Very interesting that app manager GUI can't find this while it is found via shell :)

Get my IP address from ifconfig. Tadaaa... Both ssh and vnc work as I originally expected.

zimon 2010-04-19 10:09

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 616911)
I

I don't have a bnep0 listed under System/Preferences/Network Connections/ tab. I have found a few examples online but not sure how exactly to create a correct one under /etc/sysconfig/network-scripts

I do not exactly remember how I got it all working, but would be good to get it working 4 U, so then we could update instructions for Fedora.

I think I made bnep0 device with
Desktop: System/Preferences/Network_Connections/Wired/Add
Connect_automatically: Yes, name: bnep0, MAC: <your BT MAC on PC>, MTU: automatic

Then to try PAND connection manually, on PC:
# pand -c EC:9B:5B:23:XX:XX -S -E -e bnep0
X=your N900 BT MAC.
# pand -l # to check
After that you should be able manually configure bnep0 device:
# ifconfig bnep0 192.168.3.14 netmask 255.255.255.0 dstaddr 192.168.3.15

pelago 2010-04-19 10:46

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 616999)
Did apt-get install iproute (Very interesting that app manager GUI can't find this while it is found via shell :)

Get my IP address from ifconfig. Tadaaa... Both ssh and vnc work as I originally expected.

Application Manager hides some library and utility packages that end-users don't generally install directly. I believe there is a desktop widget which can show your N900 IP address too. Personally I use static DHCP in my router so that my N900 always gets the same IP.

gsever 2010-04-19 15:00

Re: Developing is soo difficult
 
Quote:

Originally Posted by zimon (Post 617428)
I do not exactly remember how I got it all working, but would be good to get it working 4 U, so then we could update instructions for Fedora.

I think I made bnep0 device with
Desktop: System/Preferences/Network_Connections/Wired/Add
Connect_automatically: Yes, name: bnep0, MAC: <your BT MAC on PC>, MTU: automatic

I followed these steps and restarted FC12. Not sure maybe a bluetooth restart would do the same.

From N900 ->Settings -> PC-Connectivity Manager I activated bluetooth. In advanced tab:

Bluetooth enabled
DHCP server checked
IP address: 192.168.3.15
Gateway: 192.168.3.14
Network mask: 255.255.255.0
Bluetooth address search successfully discover and pair with my FC12 laptop. Settings are all applied.

Quote:

Then to try PAND connection manually, on PC:
# pand -c EC:9B:5B:23:XX:XX -S -E -e bnep0
X=your N900 BT MAC.
# pand -l # to check
After that you should be able manually configure bnep0 device:
# ifconfig bnep0 192.168.3.14 netmask 255.255.255.0 dstaddr 192.168.3.15
To get N900 BT MAC address used "hcitool scan" Then
pand -c EC:9B:5B:01:XX:XX -S -E -e bnep0

pand -l # This responds after the restart
bnep0 EC:9B:5B:01:XX:XX PANU

# Guessing the last should be the IP of N900
ifconfig bnep0 192.168.3.14 netmask 255.255.255.0 dstaddr 192.168.3.15

However still isn't working :(
ssh root@192.168.3.15
ssh: connect to host 192.168.3.15 port 22: No route to host

It should be close I know. I sometimes get similar messages trying to ssh other Redhat and Fedora machines.

We hijacked the topic but we are getting useful responses for everybody (ok especially for FC12 users :) Device connectivity is an important part of the development. WLAN works nicely, however there times it is pain to connect another device (oh VPN etc..) In these situations bluetooth would provide a very simple and useful solution.

gsever 2010-04-19 15:03

Re: Developing is soo difficult
 
Quote:

Originally Posted by pelago (Post 617476)
I believe there is a desktop widget which can show your N900 IP address too.

Any idea for the name of that widget? I am not sure how to setup the router to use static DHCP mode. I guess might be easier to use the widget for the time being.

zimon 2010-04-19 15:10

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 617808)
Any idea for the name of that widget? I am not sure how to setup the router to use static DHCP mode. I guess might be easier to use the widget for the time being.

i.e.
Queen Beecon Widget (swiss army tool) can do it.
Widget type: Snippet,
Status: Enabled,
Command Selection: Internal IP
Width 130, Height 115
Font Face: 12

Beecon Command Exit Status=0
;anythingsjfdgfg

Image Filename:
;dfjfgohdganything

About PAND in F12:
Does ifconfig now show you have a bnep0 device up at least?

What does route show about routes or both ends?
I think it is only a routing problem anymore for you.

(Yep, sorry for hijacking. Moderator, if feels like it, could move these to "PAND Bluetooth tethernet in Fedora 12".)

pelago 2010-04-19 15:51

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 617808)
Any idea for the name of that widget? I am not sure how to setup the router to use static DHCP mode. I guess might be easier to use the widget for the time being.

The one I was thinking of was "Personal IP Address" widget in extras.

gsever 2010-04-19 18:23

Re: Developing is soo difficult
 
Quote:

Originally Posted by zimon (Post 617820)
i.e.
Queen Beecon Widget (swiss army tool) can do it.

Both this widget and Personal IP widget work. Thanks guys.

Quote:

About PAND in F12:
Does ifconfig now show you have a bnep0 device up at least?
ifconfig doesn't show a bnep0 device. When I created bnep0 through Network Connections it created a ifcfg-bnep0 file under /etc/sysconfig/network-scripts shown as:

Code:

HWADDR=My BT MAC
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV6INIT=no
NAME=bnep0
UUID=some number
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes

Later when I query:

ifup bnep0
Device has different MAC address than expected, ignoring.

Very interesting. Do you get a similar behavior?

Quote:

What does route show about routes or both ends?
I think it is only a routing problem anymore for you.
A simple route query doesn't list bnep0 yet. Should be something to do with the previous step. Any ideas?

zimon 2010-04-19 18:39

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 618125)
/etc/sysconfig/network-scripts shown as:

Code:

HWADDR=My BT MAC
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV6INIT=no
NAME=bnep0
UUID=some number
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes

Later when I query:

ifup bnep0
Device has different MAC address than expected, ignoring.

Code:

# cat /etc/sysconfig/network-scripts/ifcfg-bnep0
HWADDR=00:14:35:00:XX:XX
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV6INIT=no
NAME="bnep0"
ONBOOT=yes
IPADDR=192.168.3.14
NETMASK=255.255.255.0
DEVICE=bnep0
NM_CONTROLLED=yes
USERCTL=yes
PREFIX=24
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

Your PC should get bnep0 device when N900 has made a PAND connection to it.

I don't think N900 has DHCPD, so BOOTPROTO=none and manual IP address.

gsever 2010-04-19 19:19

Re: Developing is soo difficult
 
Quote:

Originally Posted by zimon (Post 618153)
Code:

# cat /etc/sysconfig/network-scripts/ifcfg-bnep0
HWADDR=00:14:35:00:XX:XX
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV6INIT=no
NAME="bnep0"
ONBOOT=yes
IPADDR=192.168.3.14
NETMASK=255.255.255.0
DEVICE=bnep0
NM_CONTROLLED=yes
USERCTL=yes
PREFIX=24
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

Your PC should get bnep0 device when N900 has made a PAND connection to it.

I don't think N900 has DHCPD, so BOOTPROTO=none and manual IP address.

I copied your settings changing the hardware address part. PC-Connectivity applet has dhcp option on it. And tried in either option. IP Address is specified as 192.168.3.15, Gateway is 192.168.3.14

I booted and used your pand settings from page 4. Still nothing happens, get no route to host messages. Neither ifconfig nor route list any activity about bnep0. N900 bluetooth is transmitting.

If I set ifcfg-bnep0 following his instructions I can get a bnep0 available option on Network Manager applet on F12. But still no ssh :(
No More Twist: Bluetooth PAN from Windows Mobile to Fedora 11

zimon 2010-04-19 21:01

Re: Developing is soo difficult
 
Have you checked the routing table on N900 is OK? Also ping usually is the first protocol which is good to try. Also ´tcpdump -i bnep0´ may reveal what is wrong.

Does hciconfig show there is data going in and out?

"BT tethering is soo difficult" :-)

gsever 2010-04-19 22:05

Re: Developing is soo difficult
 
Quote:

Originally Posted by zimon (Post 618384)
Have you checked the routing table on N900 is OK?

From Fedora 12
Code:

[gsever@ccn Desktop]$ ssh root@N900

Nokia-N900-42-11:~# route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
172.XX.XX.XX    *              255.255.252.0  U    0      0        0 wlan0
default        172.XX.XX.XX    0.0.0.0        UG    0      0        0 wlan0

No mention for the Bluetooth. One funny thing I noticed when I activated Bluetooth via PC-Connectivity manager (pc-connectivity-manager 0.7.14) -- I set bluetooth active but when I close the applet and come back later I see that bluetooth is deactive again. It doesn't do this for wlan option. (Even though I don't use wlan-adhoc to connect the device -just for information showing something might be wrong with Bluetooth settings on N900 side)

Is there an alternative way to set Bluetooth network on N900 --GUI or shell doesn't matter?

Quote:

Also ping usually is the first protocol which is good to try. Also ´tcpdump -i bnep0´ may reveal what is wrong.
As expected. It pings fine via wireless network :D

Code:

[root@ccn network-scripts]# tcpdump -i bnep0
tcpdump: bnep0: No such device exists
(SIOCGIFHWADDR: No such device)

Quote:

Does hciconfig show there is data going in and out?

"BT tethering is soo difficult" :-)
It is active...and finds me...

Code:

Nokia-N900-42-11:~# hciconfig
hci0:        Type: UART
        BD Address: EC:9B:XX:XX:XX:XX ACL MTU: 1017:4 SCO MTU: 64:1
        UP RUNNING PSCAN ISCAN
        RX bytes:19850 acl:408 sco:0 events:470 errors:0
        TX bytes:27240 acl:451 sco:0 commands:98 errors:0

Nokia-N900-42-11:~# hcitool scan
Scanning ...
        00:XX:XX:XX:XX:XX        ccn

We will get somewhere eventually simple or hard :)

zimon 2010-04-20 17:28

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 617800)
However still isn't working :(
ssh root@192.168.3.15
ssh: connect to host 192.168.3.15 port 22: No route to host

Does this command show anything? (needs package bridge-utils)

# brctl show

I noticed, if there is bridge driver connected to pan1/bnep0, then the same configuration which otherwise works do not work.

When Bluetooth network is enabled in N900, you should see these in PC:
# hcitool con
(should show there is BT connection between two)
# pand -l
(should show there is NAP-PANU connection between two)
After those OK, just "ifup bnep0" should bring bnep0 network device up with correct IP-addresses if your ifcfg-bnep0 is OK and "brctl show" doesn't show anything.

and btw, I couldn't get DHCP working either, although N900 PC-connectivity manager would have "DHCP server" option enabled.

TheAccountant 2010-04-20 17:34

Re: Developing is soo difficult
 
Hey.

Thank you for the replies everyone, really appreciate it.
Right,

Quote:

Originally Posted by arne.anka (Post 616504)
what do you mean by "slow loading up"?
what cpu/memory does your box use?

I have a Intel P4 3ghz CPU and 4GB ram that runs at 400. I do need to get a new machine, but it seems to work fine-ish!

After reading all the posts, to be honest, I think it would be better to go via the C/C++ route. Simply because its a language I have wanted to get my teeth into. I want to spend time really getting to know a language so don't want to go via python for prototyping.

Right, I need to find a new distro now that is much will run Qt quicker. I might try Arch and see what that's like....

Shame cos I quite like Arch!

EDIT:: Actually, just a thought, it cant be my Distro. Open Office loads in under 2 seconds and I do remember it taking ages in other distros... I need to investigate this further...

gsever 2010-04-20 19:35

Re: Developing is soo difficult
 
Quote:

Originally Posted by zimon (Post 619716)
Does this command show anything? (needs package bridge-utils)

# brctl show

I noticed, if there is bridge driver connected to pan1/bnep0, then the same configuration which otherwise works do not work.

I managed to turn N900 Bluetooth network on. This said, there are bugs in N900 PC-Connectivity manager because sometimes I doesn't turn on it or forget the settings. Anyways, I can see bnep0 listed for both "route" and ifconfig querries on N900. I disabled dhcp from bluetooth options as you suggested. The default IP is 192.168.3.15 unlike your .14

[gsever@ccn Desktop]$ brctl show
bridge name bridge id STP enabled interfaces
pan0 8000.000000000000 no


Quote:

When Bluetooth network is enabled in N900, you should see these in PC:
# hcitool con
(should show there is BT connection between two)
# pand -l
(should show there is NAP-PANU connection between two)
[gsever@ccn Desktop]$ hcitool con
Connec[gsever@ccn Desktop]$ hcitool con
Connections:
> ACL EX:XX:XX:XX:XX:XX handle 46 state 1 lm MASTER AUTH ENCRYPT

I use the same pand settings as yours.

PANDARGS='--listen --secure --encrypt --persist --role NAP --ethernet bnep0'

[gsever@ccn Desktop]$ pand -l
bnep0 EX:XX:XX:XX:XX:XX NAP


Quote:

After those OK, just "ifup bnep0" should bring bnep0 network device up with correct IP-addresses if your ifcfg-bnep0 is OK and "brctl show" doesn't show anything.
Does my brctl indicate any problem?

This is my ifcfg-bnep0. Again copying and modifying from yours.

HWADDR=EX:XX:XX:XX:XX:XX
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV6INIT=no
NAME="bnep0"
ONBOOT=yes
IPADDR=192.168.3.15
NETMASK=255.255.255.0
DEVICE=bnep0
NM_CONTROLLED=yes
USERCTL=yes
PREFIX=24
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
UUID=0c56a419-a51d-e7de-cc31-............
# Don't know where this UUID comes from

This is the funny part:

[gsever@ccn Desktop]$ ifup bnep0
Device bnep0 has different MAC address than expected, ignoring.

That last step is missing. What do you think?

zimon 2010-04-20 19:49

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 619903)
I managed to turn N900 Bluetooth network on. This said, there are bugs in N900 PC-Connectivity manager because sometimes I doesn't turn on it or forget the settings. Anyways, I can see bnep0 listed for both "route" and ifconfig querries on N900. I disabled dhcp from bluetooth options as you suggested. The default IP is 192.168.3.15 unlike your .14

N900 has 192.168.3.15
PC has 192.168.3.14
The default route from N900 is through 192.168.3.14 if you want access Internet through PC:
N900# route add default gw 193.168.3.14 bnep0

Quote:

[gsever@ccn Desktop]$ brctl show
bridge name bridge id STP enabled interfaces
pan0 8000.000000000000 no
Ok. I noticed if I had any bridge on BT, I couldn't use the network.
So try to delete that bridge:
# brctl delbr pan0



Quote:

[gsever@ccn Desktop]$ hcitool con
Connec[gsever@ccn Desktop]$ hcitool con
Connections:
> ACL EX:XX:XX:XX:XX:XX handle 46 state 1 lm MASTER AUTH ENCRYPT
That seems OK. You are authenticated and encrypted (so when you take ssh connection, you may want to make it less CPU hungry and quicker by using "-c arcfour" with ssh.)


Quote:

PANDARGS='--listen --secure --encrypt --persist --role NAP --ethernet bnep0'
# cat /etc/sysconfig/pand
PANDARGS='--master --listen --secure --encrypt --persist --autozap --role NAP --ethernet bnep0 --devup /etc/sysconfig/network-scripts/ifup'

I try to get it run "ifup bnep0" automatically when NAP-PANU connection is up, but it just won't run that script. I have to manually do "ifup bnep0" on PC.

Quote:

[gsever@ccn Desktop]$ pand -l
bnep0 EX:XX:XX:XX:XX:XX NAP
OK, you have NAP-PANU connection working.



Quote:


This is my ifcfg-bnep0. Again copying and modifying from yours.

....
UUID=0c56a419-a51d-e7de-cc31-............
# Don't know where this UUID comes from
ifcfg-bnep0 seems OK. UUID comes from NetworkManager, I think.
Just check HWADDR is the same what you get with "hciconfig"


Quote:

This is the funny part:

[gsever@ccn Desktop]$ ifup bnep0
Device bnep0 has different MAC address than expected, ignoring.

That last step is missing. What do you think?
It says ifcfg-bnep0 file's "HWADDR" would be wrong.

Also, I don't know if it helps, but at least makes a little more restrictic yet, is to have "REMOTEBDADDR=<N900_BT_MAC>" also. Maybe even little quicker as it does not need ARP then, I think.

So, try to get rid of that pan0 bridge and check the HWADDR.

gsever 2010-04-20 19:53

Re: Developing is soo difficult
 
Quote:

Originally Posted by gsever (Post 619903)
[gsever@ccn Desktop]$ ifup bnep0
Device bnep0 has different MAC address than expected, ignoring.

That last step is missing. What do you think?

Silly me. ifcfg-bnep0 HWADDR= must be Laptop Bluetooth MAC not N900 :D It has resolved. I get it working, now I can both ssh and vnc via bluetooth without a need for a wlan.

Here is the interesting thing: When I first tried:

ifup bnep0
Error, some other host already uses address 192.168.3.15.

Although bluetooth ip is set to this one. On my next try I changed: IPADDR=192.168.3.14 from .15

And tadaaa.... :)

ifup bnep0
[gsever@ccn Desktop]$ ssh root@192.168.3.15
The authenticity of host '192.168.3.15 (192.168.3.15)' can't be established.
RSA key fingerprint is ...
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.3.15' (RSA) to the list of known hosts.
root@192.168.3.15's password:


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso26+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Nokia-N900-42-11:~#

zimon 2010-04-20 20:02

Re: Developing is soo difficult
 
Congrats, you got it working :) !

So you just had wrong IP-address and HWADDR in ifcfg-bnep0.

Now if everything just would be automatic on Fedora PC side, after Bluetooth has been enabled on N900 side, it would be good. (Haven't got that far yet, although tried....seems like some bugs.)

btw, do you have that bridge pan0 now removed or not? If not, is it visible with "ifconfig"?

EDIT:
WLAN may be quicker if your PC does not support BT 2.1 EDR (and anyway), but BT at least is VERY power efficient.
For best speed USB networking is the best, right after mounting external microSD card to PC and back to N900, or connecting N900 to PC via USB in mass-storage-mode.

(Sorry again for hijacking the thread...I wish we could transfer all to another thread.)

Nyrath 2010-04-20 20:51

Re: Developing is soo difficult
 
as a side note, I was very pleasantly surprised at how seamlessly PyQt handles cross platform.

I had a large PyQt application I had developed on the Windows platform. On a whim, I copied the source code and data files over to my Nokia 810 (with Python and PyQt). I had to convert all the Windows cr/lf into Linux lf, but that's all.

It worked wonderfully. I have to re-size the controls to fit the 800 x 480 screen, but the application works as is.

In the images, the first image in the pair is on Windows, the second image is on the N810

http://www.flickr.com/photos/nyrath/...7606410052769/
http://www.flickr.com/photos/nyrath/...7606410052769/

http://www.flickr.com/photos/nyrath/...7606410052769/
http://www.flickr.com/photos/nyrath/...7606410052769/

http://www.flickr.com/photos/nyrath/...7606410052769/
http://www.flickr.com/photos/nyrath/...7606410052769/

http://www.flickr.com/photos/nyrath/...7606410052769/
http://www.flickr.com/photos/nyrath/...7606410052769/

http://www.flickr.com/photos/nyrath/...7606410052769/
http://www.flickr.com/photos/nyrath/...7606410052769/

gsever 2010-04-20 22:05

Re: Developing is soo difficult
 
Quote:

Originally Posted by zimon (Post 619946)
Congrats, you got it working :) !

So you just had wrong IP-address and HWADDR in ifcfg-bnep0.

Thank you very much for your help and careful thoughts. I am so scatter minded these and trying to many things at a time. As a result skipping simple things where make huge difference in the final :) However I still claim Bluetooth networking functionality through N900 PC-Conn-manager has some bugs since it doesn't save settings properly or doesn't set BT up where it is supposed to + plus it doesn't work with dhcp enabled at least on FC12. Could you confirm on these findings again?

Quote:

Now if everything just would be automatic on Fedora PC side, after Bluetooth has been enabled on N900 side, it would be good. (Haven't got that far yet, although tried....seems like some bugs.)
Is there any progress for these improvements on the upcoming Fedora 13?

Quote:

btw, do you have that bridge pan0 now removed or not? If not, is it visible with "ifconfig"?
No, brctl still lists pan0, and I haven't removed it to get the BT networking working properly. ifconfig doesn't list pan0 only bnep0 is there in addition to eth0 and wlan0

Quote:

EDIT:
WLAN may be quicker if your PC does not support BT 2.1 EDR (and anyway), but BT at least is VERY power efficient.
I querried my laptop's BT from N900 using:
hcitool info BT-Addr

It list LMP version 2.1 Does this mean I get BT 2.1 EDR?

Quote:

For best speed USB networking is the best, right after mounting external microSD card to PC and back to N900, or connecting N900 to PC via USB in mass-storage-mode.
Setting up a USB network is the next step. For now I am content with WLAN and BT options. For the sake of integrity we can complete the steps for USB networking on FC12 and prepare a wiki page or documentation that could placed on pc-connectivity site for other Fedora viewers use.

Quote:

(Sorry again for hijacking the thread...I wish we could transfer all to another thread.)
I share the same thoughts. We should have already been moved to another thread :) I will be more careful next time speculating aloud.

LordNelson 2010-04-20 23:26

Re: Developing is soo difficult
 
Most things have already been said here, Qt Creator, scratchbox, MADDE and so on.
There's also guide for building debian packages in the wiki.

magnuslu 2010-04-21 00:08

Re: Developing is soo difficult
 
Quote:

Originally Posted by TheAccountant (Post 616238)
I will keep trying cos the applications I want/need are just things to make my everyday life easy. Like an app to manage finance, game scores, shopping lists with auto alarm reminders etc... I would even dare release anything into public domain until I am very comfortable with the coding!

Well, I'm reasonably happy with the ease of development of my Qt based score tracking app QSportsEvent (ignore the current version in Extras-Devel though). This thread is the one to follow for that app: FIFA World Cup App. Don't let you be fooled by the thread title! It does much more than the FIFA World Cup. I plan to support other sports as well.

TheAccountant 2010-05-30 19:35

Re: Developing is soo difficult
 
Thank you for the replies.
I have solved the slow issue by building a new system. i think the board and cpu were rubbish. Qt runs fine now.

Thanks!


All times are GMT. The time now is 03:00.

vBulletin® Version 3.8.8