Re: Beware Personal launcher
(Oops, I suck at reply-all in gmail, apparently.) Eero Tamminen [EMAIL PROTECTED]: Just noticed that Personal launcher applet (latest v0.6-4 in extras) leaks like mad and updates the screen uselessly at high frequency. Because it's an applet within the Desktop process which allocations are guaranteed, it will cause device to run out of memory very soon. Result is that other applications start aborting and device will slow down to crawl. Constant screen updates (even when screen is blanked) drain the battery. Could this be kicked out of extras so that people don't launch their devices to oblivion? I guess it would be preferable, if possible in a timely manner, for it to be kicked out by an updated version that doesn't misbehave It's leaking 8MB/min, updates screen constantly even when screen is blanked and crashes desktop when disabled. Project with this bad QA should IMHO just be kicked out of extras. 8MB/min *blink*?! That's ...not that many minutes :) (Personally I'd like there to be some kind of quick testing before things get into extras.) -- but I don't see a bugreport on the issue in the project's garage (alas) tracker. *nudge* I didn't try this myself and I'm not using it myself so I couldn't verify the fix. fwiw, I don't think reporter-verifiability is enough of a concern here to not file bugs -- people finding out about issues seems more important. (provided your source is good enough for confident reporting, which it must be, given this thread) 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Scheduling a Bugzilla Meeting
Ryan Abel wrote: There are a number of proposed[1][2] and ongoing[3] tasks related to Bugzilla currently in the pipeline. Progress on some of these tasks (particularly the Garage tracking in Bugzilla) is currently held up until everybody involved can get together to discuss some specifics and lay down a plan of attack. To this end, I've proposed a meeting[4] for tomorrow after the sprint review. I haven't been able to get to enough of the appropriate people directly, so I'm emailing the list (probably the approach I should've started with, but I've got an IRC mindset and I know at least one important person isn't subscribed to this list). Hopefully everybody will do their homework this time around and the review wont run too far over and everybody interested will have time available afterwards. We could reschedule sometime later in the week if a lot of people can't make it, but we'll be missing timeless if we delay too long. [1]https://wiki.maemo.org/Task:Garage_bug_tracking_in_Bugzilla [2]https://wiki.maemo.org/Task:Getting_Nokia_involved_in_Bugzilla [3]https://wiki.maemo.org/100Days/Sprint2#Bugs (bug #630) [4]https://wiki.maemo.org/Talk:100Days/Sprint3#Bugzilla_Meeting ___ maemo-community mailing list Including -developers since the agenda is developer tools ...or, at the very least tools which in the scope of the proposed change are moderately irrelevant without developer participation, so there's probably useful input to be had there :) 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Replacing the standard maemo bluetooth pairing dialog.
Faheem Pervez wrote: I've made a compile of carwhisperer for the maemo platform (http://www.internettablettalk.com/forums/showthread.php?t=20780). The app itself seems to work (from what I can tell anyway) but there is one problem with this. This program works on the principle of default security pins and the program comes with a script to do just this. I've added in the pin_helper configuration option in the hcid.conf and on a standard Linux system running BlueZ, this works. However, on the OSSO versions of BlueZ, this doesn't work. I've tried rebooting, disabling the bluetooth statusbar applet, I've tried moving btcond, btsdp, btsearch to another place, I've even tried moving the relevant files in /etc/dbus-1 to no avail. I can see with top that the dbus-daemon is using a little bit more power when asking for the paircode. I've even recompiled a hcid from the BlueZ website (i.e devoid of any OSSO modifications) and replaced my binary in /usr/sbin but I still get the maemo pair dialog. So, how would I replace maemo bluetooth pairing dialog with another program I want to run externally. Or make the maemo bluetooth pairing dialog not interfere so hcid will run the program specified in the pin_helper option. http://lists.maemo.org/pipermail/maemo-developers/2006-October/023815.html seems to contain some possibly relevant keywords, whether they're of any practical use is of course another thing entirely ;) 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: no name resolution in scratchbox
Jason Edgecombe wrote: I'm using the maemo development VM and I can't seem to get DNS working in scratchbox. apt-get and wget fail under scratchbox but when outside of scratchbox. I mean wget http://www.google.com/ fails in scratchbox. I've added my dns servers to /etc/resolv.conf, but that didn't help. I also hard-coded an ip address for repository.maemo.org in /etc/hosts, but that also fails. both apt-get install kernel-source-rx-34 and fakeroot apt-get fails. Try http://lists.maemo.org/pipermail/maemo-developers/2007-March/008783.html 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Launching browser from Xterm
Denis DeLaRoca wrote: On Sun, 12 Aug 2007, Antonio Gomes wrote: $ run-standalone.sh /usr/bin/browser --url=gooogle.com --engine=[microb/opera] does it work for you ? Yes, but if the browser is already active, launching a 2nd browser session appears to start up and promptly crashes. There must be a better method to start up browser sessions from within an application. general answer: ask dbus-monitor. specific answer: dbus-send --print-reply /com/nokia/osso_browser \ --dest=com.nokia.osso_browser com.nokia.osso_browser.load_url \ string:http://maemo.org/ 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
wlan drop (Re: x11vnc no response to taps on left of screen)
Kalle Valo wrote: ext Jeffrey Barish [EMAIL PROTECTED] writes: Also, the N800 has an annoying habit of dropping the WiFi connection because it is not detecting any taps on the screen. We don't have such functionality at all. We do have idle timer which disconnects the connection after a specified timeout if there's no traffic. But if I recall correctly, it should be disabled for WLAN by default You must be seeing something else. What AP are you using and what are it's settings? And what do you mean by dropping? Does UI inform that connection is disconnected or is the WLAN connections just jammed, ie. no data is transfered? ip=x.x.x.x; s=290; while date -Is; ping -c 1 $ip; do sleep $s; s=$((s+10)); done In my case, taps don't matter, if after network use the device is pinged at an interval increasing by 10s, it responds to the ping after the 5min0s interval regardless of when blanking happened, but not after the subsequent 5min10s interval. WLAN disconnect timeout not enabled, scan interval 10min (defaults). Same effect regardless of different dim/blank timeouts. AP is dlink DI-524, WPA-PSK (AES). No presence stuff is configured (I'd guesstimate that is the relevant difference between back when I didn't see this and now), no email polling. Connection appears up in the ui, I usually just poke at the feed applet refresh to get the networking going again. timeline (accurate to ~1min): 2007-04-11T01:09 ping ok 2007-04-11T01:14 ping ok 2007-04-11T01:19 ping ok 2007-04-11T01:25 ping nok 2007-04-11T01:35 poked feed applet refresh dmesg: [ 2122.964508] EAC mode: play enabled, rec enabled [ 2125.465576] EAC mode: play disabled, rec disabled [ 2153.398864] omapfb omapfb: s1d1374x: setting update mode to disabled nothing 01:11--01:35 [ 3665.260162] omapfb omapfb: s1d1374x: setting update mode to manual [ 3670.130920] EAC mode: play enabled, rec enabled [ 3672.629699] EAC mode: play disabled, rec disabled [ 3673.933410] EAC mode: play enabled, rec enabled [ 3676.020690] DEAUTHENTICATE trap [ 3676.020782] Active scanning on null [ 3676.809539] EAC mode: play disabled, rec disabled [ 3677.002227] sm_drv_transmit: sm_frame_tx returned error -9 [ 3677.846496] Scan complete, scanned 13 channels [ 3678.002288] sm_drv_transmit: sm_frame_tx returned error -9 [ 3678.094787] cx3110x: PSM disabled [ 3678.343963] cx3110x: PSM dynamic with 1000 ms CAM timeout [ 3704.067565] omapfb omapfb: s1d1374x: setting update mode to disabled [ 4220.713134] omapfb omapfb: s1d1374x: setting update mode to manual [ 4221.450714] EAC mode: play enabled, rec enabled [ 4226.745422] EAC mode: play disabled, rec disabled [ 4228.003723] EAC mode: play enabled, rec enabled [ 4230.039825] DEAUTHENTICATE trap [ 4230.039916] Active scanning on null [ 4230.879455] EAC mode: play disabled, rec disabled [ 4231.025665] sm_drv_transmit: sm_frame_tx returned error -9 [ 4231.893402] Scan complete, scanned 13 channels [ 4232.025787] sm_drv_transmit: sm_frame_tx returned error -9 [ 4232.110443] cx3110x: PSM disabled [ 4232.349578] cx3110x: PSM dynamic with 1000 ms CAM timeout [ 4258.145751] omapfb omapfb: s1d1374x: setting update mode to disabled [ 4350.736602] omapfb omapfb: s1d1374x: setting update mode to manual dbus.session (the timestamps may lag due to buffering, mind) 01:10:14 signal sender=:1.31 - dest=(null destination) interface=com.nokia.osso_rss_feed_reader; member=refresh_started 01:10:15 signal sender=:1.31 - dest=(null destination) interface=com.nokia.osso_rss_feed_reader; member=refresh_finished 01:10:16 signal sender=org.freedesktop.DBus - dest=(null destination) interface=org.freedesktop.DBus; member=NameOwnerChanged 01:10:16 string com.nokia.osso_rss_feed_reader_refresh 01:10:16 string :1.31 01:10:16 string 01:10:16 signal sender=org.freedesktop.DBus - dest=(null destination) interface=org.freedesktop.DBus; member=NameOwnerChanged 01:10:16 string com.nokia.osso_rss_feed_reader 01:10:16 string :1.31 01:10:16 string 01:10:16 signal sender=org.freedesktop.DBus - dest=(null destination) interface=org.freedesktop.DBus; member=NameOwnerChanged 01:10:16 string :1.31 01:10:16 string :1.31 01:10:16 string 01:36:03 signal sender=org.freedesktop.DBus - dest=(null destination) interface=org.freedesktop.DBus; member=NameOwnerChanged 01:36:03 string :1.33 01:36:03 string 01:36:03 string :1.33 01:36:03 method call sender=:1.33 - dest=org.freedesktop.DBus interface=org.freedesktop.DBus; member=Hello 01:36:03 signal sender=org.freedesktop.DBus - dest=(null destination) interface=org.freedesktop.DBus; member=NameOwnerChanged 01:36:03 string com.nokia.osso_rss_feed_reader 01:36:03 string 01:36:03 string :1.33 01:36:03 method call sender=:1.33 - dest=org.freedesktop.DBus interface=org.freedesktop.DBus; member=RequestName 01:36:04 string com.nokia.osso_rss_feed_reader 01:36:04 uint32 1 01:36:04 method call sender=:1.33 - dest=org.freedesktop.DBus interface=org.freedesktop.DBus; member=RequestName
Re: Wishlist (was:Re: N800 and USB host mode)
On 3/7/07, Florent de Dinechin [EMAIL PROTECTED] wrote: Wish #1: Extend the current drag-to-shift paradigm on the virtual keyboard to 8 directions. Use these to implement accents for accented languages (e+NE for é, e+NW for è, c+SW for ç, etc), and to remove the need for shifting in general. Show the shifted letters in very small colored font in the corners of the keys. That could get a bit crowded on the small vkb -- how about showing the available tapdrag variants for a key on tapdrag (taphold repeats so it would make a weird trigger), using a larger area? What about capital accented letters such as É? Possibly implement more complex gestures (e + NE then SE for ê, for example, or tilde, etc). Rationale: French (but also Polish, Spanish and other) has a lot of accents and current input method is a pain. Proposed change should be simple to implement, considering that 4 directions are already there. Showing the shifted characters when they are not obvious (i.e. for the symbol keys, not for the letters) will benefit everybody, not only the French :) 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: N800: Loss of touch screen sensitivity/pressure detection
Tuukka Tolvanen kirjoitti: Neil MacLeod kirjoitti: inode0 wrote: I see this too when using the newsreader especially. I have noticed Agreed about the news reader - I assumed it was just another problem with the news reader application as I could usually drag an article Note that the feedreader content responds differently to tap-hold.5s-drag than e.g. the browser or pdfreader; the former does not pan unless you drag very quickly after pressing, the latter two do. - https://maemo.org/bugzilla/show_bug.cgi?id=1091 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Home Applet Troubleshooting
Levi Bard kirjoitti: Anybody have any tips on troubleshooting (my custom) home applets? Is there a way to get error output on the device? You can write to a log file, or use osso system notes to show msgs. :-) How about for error messages coming from glib or the wm... The desktop spews glib foo into syslog. 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Automatic wifi at startup
ext Diego Zimet kirjoitti: I'm trying to write a program that connects to a certain IAP, and tries to reconnect if the connection is lost or disconnected. I want to run this program at startup, so that there is wifi connectivity when I turn on the phone. I'm using the osso-ic api, and everything seems ok. However, when the function osso_iap_connect cannot find the iap I specified, then a message box shows up, asking if I want to try to connect again. However, the whole idea of this program is to manage internet connectivity automatically. Is there a way to have the osso_iap_connect function return some value or bypass that message box? /*/*/osso-connectivity-ui.sh stop could be useful. 't. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
