Active Topics
-
Maemo repository (4)
to Community by teroyk - 1 day, 5 hrs ago -
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 2 days, 12 hrs ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 2 days, 21 hrs ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 6 days, 6 hrs ago - more...
| The Following 6 Users Say Thank You to 412b For This Useful Post: | ||
|
2012-07-18
, 22:30
|
|
Posts: 105 |
Thanked: 106 times |
Joined on Jul 2011
@ Hungary
|
#212
|
hey,
since this update, sometimes i can't connect to wifi after once i disconnected
disabling the module and re-enable doesn't help, just rebooting, but then this again..
any suggestions?
since this update, sometimes i can't connect to wifi after once i disconnected
disabling the module and re-enable doesn't help, just rebooting, but then this again..
any suggestions?
|
|
2012-07-18
, 23:55
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#213
|
Originally Posted by 412b
Keep in mind, that because buttons are so small in status menu, operator name doesn't fit and you end up being unable to see the connected/unconnected bit of info at a glance.
- cell part now show operator name (like in status bar) in messages and in status menu
So I think it's great that it shows operator name in the notification messages, but I think it should stick to just showing "<>" in the status menu button when connected.
Originally Posted by 412b
While we're on the subject, the JP setting is currently not supported in the injection capable driver (I have no desire to call it bleeding edge at this point, it's ~ a year old by now). I believe the regulatory region for that driver is hardcoded.i'm a taking a look at the custom user scripts to be run at some event. suggestions and ideas are welcomed. @Estel, that one about setting JP i took into account
So that leads me to point out that if you have support for custom scripts, I hope you remember to make them flexible enough to be able to decide if they fire on events for either wifi driver, or for both.
| The Following 2 Users Say Thank You to Mentalist Traceur For This Useful Post: | ||
|
|
2012-07-19
, 06:37
|
|
Posts: 462 |
Thanked: 550 times |
Joined on Sep 2008
@ Moscow
|
#214
|
Originally Posted by dy1ng
what exact build are you using?
hey,
since this update, sometimes i can't connect to wifi after once i disconnected
disabling the module and re-enable doesn't help, just rebooting, but then this again..
any suggestions?
by "can't connect" do you mean that network is visible, but connection fails? (for consistance also check, is wlancond is started)
i had that behaviour in recent builds, but in last can't reproduce, meanwhile i'll upload an update this week/begining of next week, on which i can't reproduce that behaviour.
| The Following 3 Users Say Thank You to 412b For This Useful Post: | ||
|
|
2012-07-19
, 06:45
|
|
Posts: 462 |
Thanked: 550 times |
Joined on Sep 2008
@ Moscow
|
#215
|
Originally Posted by Mentalist Traceur
Good point, I'll think about improvements during weekend
Keep in mind, that because buttons are so small in status menu, operator name doesn't fit and you end up being unable to see the connected/unconnected bit of info at a glance.
So I think it's great that it shows operator name in the notification messages, but I think it should stick to just showing "<>" in the status menu button when connected.
Originally Posted by Mentalist Traceur
At the moment scripts are flexible enough
While we're on the subject, the JP setting is currently not supported in the injection capable driver (I have no desire to call it bleeding edge at this point, it's ~ a year old by now). I believe the regulatory region for that driver is hardcoded.
So that leads me to point out that if you have support for custom scripts, I hope you remember to make them flexible enough to be able to decide if they fire on events for either wifi driver, or for both.
5 main events:
1. if down (/usr/bin/advifsw/post-down)
2. loaded default driver (/usr/bin/advifsw/post-load0)
3. loaded injection driver (/usr/bin/advifsw/post-load1)
4. unloaded driver (/usr/bin/advifsw/post-unload)
5. if up (/usr/bin/advifsw/post-up)
In those dirs you can put your scripts (don't forget to +x them).
| The Following 4 Users Say Thank You to 412b For This Useful Post: | ||
|
|
2012-07-19
, 12:13
|
|
Posts: 105 |
Thanked: 106 times |
Joined on Jul 2011
@ Hungary
|
#216
|
Originally Posted by 412b
what exact build are you using?
by "can't connect" do you mean that network is visible, but connection fails? (for consistance also check, is wlancond is started)
i had that behaviour in recent builds, but in last can't reproduce, meanwhile i'll upload an update this week/begining of next week, on which i can't reproduce that behaviour.
my version: 0.3.11-9
all networks are visible, but i can't connect to any of them untl i do not restart the system
however, since i reinstall the package, this behaviour is gone.. i hope it's don't come back
and i'll check this wlancond thing
sorry for my noobish english, and thanks for the fast reply
 |
|
2012-07-19
, 18:50
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#217
|
Did you play with "bleeding edge" driver and lost signal while connected to an AP?
This would explain that behaviour (would have needed unload of bleeding and reloading stock/bleeding again).
This would explain that behaviour (would have needed unload of bleeding and reloading stock/bleeding again).
|
|
2012-07-19
, 19:05
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#218
|
Originally Posted by Mentalist Traceur
For my use case and networks, it matches easily to distinguish.
Keep in mind, that because buttons are so small in status menu, operator name doesn't fit and you end up being unable to see the connected/unconnected bit of info at a glance.
Having a dual sim adapter and switching automatically via icon/app click between networks Vodafone (shown as Vod) and o2 - de (o2 ).
But for other maybe not so easy and not really needed, so I do not have a favourite here, keep it or change back.
Originally Posted by Mentalist Traceur
Really? Sad.
While we're on the subject, the JP setting is currently not supported in the injection capable driver (I have no desire to call it bleeding edge at this point, it's ~ a year old by now). I believe the regulatory region for that driver is hardcoded.
| The Following User Says Thank You to peterleinchen For This Useful Post: | ||
 |
|
2012-07-20
, 09:40
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#219
|
Not so much, as "bleeding-edge-year-ago" drivers are open for all channels, by default
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
|
|
2012-07-20
, 13:53
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#220
|
Originally Posted by peterleinchen
I didn't know you could do that on the N900 - switch between two sim cards in a dual sim card adapter easily. That's awesome. Mind pointing me to a thread/post where this is covered?
For my use case and networks, it matches easily to distinguish.
Having a dual sim adapter and switching automatically via icon/app click between networks Vodafone (shown as Vod) and o2 - de (o2 ).
But for other maybe not so easy and not really needed, so I do not have a favourite here, keep it or change back.
Originally Posted by Estel
Are you sure? I don't believe you can actually access channels 12 and 13 with it? (Admittedly I don't remember if I ever tried, say, using aireplay-ng those channels, or airmon-ng to sniff on those channels....)
Not so much, as "bleeding-edge-year-ago" drivers are open for all channels, by default
| The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
Main features:
- support for WLAN driver switching (needs backports modules or any corresponding to your kernal
- removed connected button
- cell part now show operator name (like in status bar) in messages and in status menu
- added "connecting" and "disconnecting" to wlan and "connecting" to GSM
- some minor fixes
- POT file for translations is now available in garage's svn
i'm a taking a look at the custom user scripts to be run at some event. suggestions and ideas are welcomed. @Estel, that one about setting JP i took into account
Advanced Power, Advanced Interface Switcher, MediaBox Home Widget