**** BEGIN LOGGING AT Sun Jan 08 03:00:01 2017 Jan 08 03:50:09 Hi . My n900 seems t have a hardware problem of proximity sensor being "Closed" always. Is there any way to disable it ? Jan 08 03:54:24 Huh... One: try to shine a really bright flashlight into it, see if it helps. Is it the sensor responsible for backlight of hardware keyboard? If yes, I have the same problem, but then, I have a paper sticker over the sensor. Jan 08 04:15:24 Oksanaa: No it did not help. Jan 08 04:17:05 I dont think keypad light are related to proximiity sensor. Is there anyway to disable proximity sensor during call so that it is easy to pick up the call. Jan 08 04:25:55 Ah, have no problems with call, I think. https://talk.maemo.org/showthread.php?t=71188 Might be problem with flex ribbon cable? Jan 08 04:31:29 Most probably no. It remains active irrespective of keyboard being closed or not. And technicians here do not want to repair this phone because of lack of spare parts. So, I want a software solution if possible. Jan 08 04:36:48 Okay... Never seen a technician agreeing to repair my N900, either. https://talk.maemo.org/showthread.php?p=974759 software and proximity sensor Jan 08 04:37:50 Not quite solver, though ^ Jan 08 04:40:50 Oksanaa: i do not think it is the solution. But thank you. :) I tried /sys/devices/platform/gpio-switch/proximity/disabled -> 0 ( it is 1 by default) but nothing happened. Jan 08 04:45:51 Different device, similar problem? https://talk.maemo.org/archive/index.php/t-86100.html try editing /etc/mce/mce.ini to remove proximity; from Modules=? Jan 08 04:49:52 Would recommend back-up of anything important from phone, if possible. To restart mce, either reboot, or sudo gainroot \n stop mce; start mce Jan 08 04:54:52 newbieAlert : How are you? I am not sure myself if proximity is listed in N900's mce.ini Jan 08 08:02:44 Dont think proximity is there in mce modules list. Jan 08 08:16:43 newbieAlert: I suppose you tried rebooting, obviously? Jan 08 08:18:36 Vajb: hangouts on n900? Jan 08 08:29:58 hi Jan 08 08:38:47 bencoh: hangouts smiley theme in pidgin Jan 08 08:39:36 ah Jan 08 10:34:00 omg, clutter 1.x depends on gtk3 ?!? Jan 08 10:42:24 KotCzarny: ^^^ any clue? Jan 08 10:42:31 its gnome project after all, right? Jan 08 10:42:49 problem is with gtk>3 Jan 08 10:43:21 because their versioning plan is weird Jan 08 10:43:27 KotCzarny: I built h-d on gtk2 with clutter 1.0 Jan 08 10:43:47 you can try backporting clutter to gtk2? Jan 08 10:43:47 but it refuses to start as clutter1.0 loads gdk3 libs Jan 08 10:43:59 o.O Jan 08 10:44:24 this is insane Jan 08 10:44:46 https://developer.gnome.org/clutter/stable/building-clutter.html Jan 08 10:44:57 nothing about gtk/gdk version Jan 08 10:45:52 http://www.linuxfromscratch.org/blfs/view/svn/x/clutter.html Jan 08 10:45:54 similarly Jan 08 10:46:18 seems there is gdk backend build by default Jan 08 10:46:37 maybe it autodetected gdk during build and used it Jan 08 10:47:12 you can check unused raw lib dependencies (ldd -u) Jan 08 10:47:26 to see if it really depends on gdk3 or gets it from some subli b Jan 08 10:49:17 already did and it uses gdk3.so Jan 08 10:49:59 check the build config/log Jan 08 10:50:40 --enable-gdk-backend=yes, in debian/rules :) Jan 08 10:50:58 check if you can point to v2 Jan 08 10:51:43 tried, fails Jan 08 10:51:53 does it build without gdk? Jan 08 10:52:52 seems like yes Jan 08 10:53:04 benchmark Jan 08 10:53:05 ;) Jan 08 10:56:45 hmm? Jan 08 10:56:53 this is for x86 Jan 08 10:56:55 to see if it will be slower without gdk Jan 08 10:57:23 isn't that supposed to use GL?!? Jan 08 10:57:45 why should I care about gdk? Jan 08 10:57:52 was it linked to opengl when built with gdk? Jan 08 10:58:14 no idea, but afaik backend is runtime-detected Jan 08 10:58:53 and deffinitely I don;t want gdk backend for hildon-deskto Jan 08 10:59:18 but e/gl Jan 08 10:59:52 ok, something got build, lets see :) Jan 08 11:01:16 or not :( Jan 08 11:16:35 KotCzarny: it runs :) Jan 08 11:16:56 anything being different? Jan 08 11:17:32 so far nothing Jan 08 11:22:02 freemangordon: hildon-desktop+clutter on recent gtk2? Jan 08 11:22:09 yes Jan 08 11:22:13 neat Jan 08 11:22:27 how comes you're back to gtk2 though? Jan 08 11:22:37 bencoh: themes ;) Jan 08 11:22:41 huhu Jan 08 11:22:48 and i bet its easier to upgrade one by one Jan 08 11:22:53 than all at once Jan 08 11:22:59 well, "back"... Jan 08 11:23:12 I just want to see which option is more viable Jan 08 11:30:43 hmm, it looks almost like the real one, needs just some more work on libhildon Jan 08 12:42:30 bencoh: Yes :D Did not work :( Or is there atleast a way to unlock screen during call ? That is the main problem. Can it be done using dbus for call state and disabling lock based on that ? Jan 08 12:43:39 I guess it could Jan 08 12:44:48 you might try patching whichever part of the code is responsible for the proximity sensor as well Jan 08 16:04:48 I wonder if changing vibrate pattern for messages/notifcations based on proximity/lumonisity sensor and whether keyboard is opened/closed would be feasable/easy Jan 08 16:06:30 probably by patching mce Jan 08 16:07:06 you do want strong vibrations when phone is in your pocket, but once it's already in your hands, or even worse, sitting on a wooden table .... Jan 08 16:13:04 modified mce.ini & restart mce works, but only several times Jan 08 16:13:11 and then start: mce respawning too fast, stopped Jan 08 16:15:44 why OS doesn't allow unlimit restart daemons? Jan 08 16:16:28 I wouldn't want to edit/restart mce everytime I open/close keyboard Jan 08 16:16:36 and I dont wanna monitor light sensor either Jan 08 16:16:49 can't you just SIGHUP mce Jan 08 16:16:51 I want it to check system status before issuing a vibrate command Jan 08 16:16:52 to make it reload the config Jan 08 16:17:00 kerio: no idea, but still Jan 08 16:17:14 I dont want a kludge/workaround :) Jan 08 16:17:37 I guess I'll have a look at this part of the code Jan 08 16:19:37 it would be nice feature :) Jan 08 16:19:55 actually there is already something close in "policy Jan 08 16:20:06 in the policy field of vibrating patterns Jan 08 16:20:36 but it only checks whether display is on/off and/or device in acting dead Jan 08 17:54:53 KotCzarny: T520 bought. Now im just waiting to get my hands on it :) Jan 08 17:55:05 yay! Jan 08 17:55:09 what config? Jan 08 17:56:10 i5 2520M, 8GB ram and 160GB ssd. Win 7 pro. Jan 08 17:56:28 integrated card or dedicated? Jan 08 17:56:54 that i do not know Jan 08 17:57:07 do you know exact model-type ? Jan 08 17:57:22 or have a photos of the bottom? Jan 08 17:57:49 nope Jan 08 17:58:01 you will love it anyway Jan 08 17:58:05 :) Jan 08 17:58:21 will know when i get it :) Jan 08 17:59:27 if you dont use cd/dvd, you can get bay 2nd hdd adapter Jan 08 17:59:36 and put some storage drive there Jan 08 18:04:19 bencoh : tried dbus-scripts.. did not work. Can not find a reason :/ Jan 08 18:06:44 KotCzarny: oh i see. Is it possible to get dock with dvd drive for this model? Jan 08 18:08:05 hum? Jan 08 18:08:19 tho i have usb dock for hdd's so maybe i use that :) Jan 08 18:08:58 i've found that cd/dvd is obsolete these days Jan 08 18:09:14 just popout the optical drive and put hdd dock in there Jan 08 18:09:58 i see Jan 08 18:10:18 something like this: https://www.aliexpress.com/item/Aluminum-2nd-HDD-Caddy-12-7mm-2-5-SATA-3-0-SSD-Case-HDD-Enclosure-for/32364238935.html?spm=2114.01010208.3.18.8lzRYB&ws_ab_test=searchweb0_0,searchweb201602_2_10065_10068_10000009_10084_10083_10080_10082_10081_10060_10062_10056_10055_10037_10054_10059_10032_10099_10078_10079_10077_10000012_426_10103_10073_10102_10000015_10096_10052_10053_10107_10050_10106_10051,searchweb201603_1,afswitch_5,single_sort_0_p Jan 08 18:12:39 oh that's one cheap improvement Jan 08 18:12:45 yup Jan 08 18:13:02 but that depends if you need optical drive, some people have work that requires it Jan 08 18:13:14 otherwise 2nd hdd is much better idea Jan 08 18:13:27 in wiki it said it supports 16gb ram, but i guess there r only two slots Jan 08 18:14:23 Hi i have another question. I have shortcudD but stilol camera button actually opens Camera. Isn't there any way to remove this functionality ? Jan 08 18:14:38 you might check which thickness you need htough, 9.5mm or 12.5 Jan 08 18:14:54 price is the same, just physical size differs depending on the slot Jan 08 18:15:04 newbieAlert: u can change this from camera settings i think Jan 08 18:17:39 can't wait to get my hands on it! Jan 08 18:18:55 Vajb: My camera button seems to work in a different way .. proper press of it tends to open the camera but improper press ( like just pressing it without clicking it) actually executes the shortcutD commands . Jan 08 18:19:29 yes it has zoom feature Jan 08 18:19:48 but that camera opening can be changed Jan 08 18:20:07 i just can't remember where and looking for it now Jan 08 18:20:37 Vajb: That's changed. It was in the settings . :) Thanks :) But shortcutd is still not working :/ Jan 08 18:22:25 go to settings menu and check that u have correct settings in shortcutd Jan 08 18:22:43 yeah just found those settings too :) Jan 08 18:23:15 from shortcutd settings u can change actions for short and longpress Jan 08 18:23:33 newbieAlert: not really. There are things in extras to "suppress" the camera-ui appearing. Shortcutd uses cam-focus to activate commands. Jan 08 18:23:44 hmmm mce/modules/vibrator.c is plain ugly Jan 08 18:23:52 :> Jan 08 18:24:03 Vajb: Still not working.. I mean it works randomly . Jan 08 18:24:27 is ur camera button good? Jan 08 18:24:36 sixwheeledbeast: camera-ui can be swithced off from the settings it self as Vajb suggested. Jan 08 18:25:01 Vajb: for opening cmaera.. 100% strike rate ... For shortrcutd, depends on luck. Jan 08 18:25:04 i think u can use syslog or something to check if it detects all ur presses Jan 08 18:25:29 what u have set it to do then? Jan 08 18:26:01 act as power button or unlock the screen Jan 08 18:26:02 I don't believe you can you have installed something from extras for that option in settings. Jan 08 18:26:05 Vajb: ^^ Jan 08 18:26:20 dmesg will show cam_focus Jan 08 18:26:43 i have mediaplayer play/pause as short press and panucci play/pause for longpress and if i hold button tad too long it executes long press one. It is easy to miss Jan 08 18:27:29 sixwheeledbeast: Maybe. But i found the setting in the UI itself. Checking dmesg. Last time I had checked it had something something for cam-launch or something. Jan 08 18:27:40 sixwheeledbeast: setting camera ui triggering from cam button was implemented in cssu Jan 08 18:27:50 setting off* Jan 08 18:28:54 so you would need something from extras to disable it, or gconftool I imagine Jan 08 18:29:31 do u have device with cssu in hand now sixwheeledbeast? Jan 08 18:29:39 yep Jan 08 18:30:06 open camera. Tap screen to show title. Click title and select settings. From there u can change it Jan 08 18:31:10 that will be camera-ui2 not camera-ui Jan 08 18:31:20 ~nicocam Jan 08 18:31:31 oh? Jan 08 18:32:09 apt-cache policy camera-ui Jan 08 18:32:09 camera-ui: Installed: 1.1.29.2+0cssu18 Candidate: 1.1.29.2+0cssu18 Jan 08 18:33:03 Vajb: Found. CAm focus is not working properly. :( Cam launch is perfectly working. Jan 08 18:33:12 or is this camera-ui2 already? Jan 08 18:33:31 1.1.29.1+0m5 is stock camera Jan 08 18:33:56 newbieAlert: im glad to be right at once :) Jan 08 18:34:03 maybe os is eating cam-focus Jan 08 18:34:35 sixwheeledbeast: ok i installed something from repos then or it came with cssu Jan 08 18:35:01 it will be testing version that's why Jan 08 18:35:04 i have cssu-testing btw Jan 08 18:35:10 :nod: Jan 08 18:35:16 ah :) Jan 08 18:36:28 Vajb: :) Thanks. Anyway to make it use cam-launch instead of focus ? Jan 08 18:37:13 Or volume buttons ? They can also made available in a locked device,so may replace cam-button funcitonality. Jan 08 18:37:13 i think it can be done, sixwheeledbeast? Jan 08 18:37:18 http://wiki.maemo.org/Community_SSU/Features/Camera_UI Jan 08 18:37:50 volumebuttons control mediaålayer volume already Jan 08 18:38:06 mediaplayer* Jan 08 18:38:19 shortcutd only works with cam_focus Jan 08 18:38:34 or prox sensor Jan 08 18:40:03 sixwheeledbeast: I meant something other than shorcutd. Dont they fire dbus signal?? Something like HildonVolsomething. Jan 08 18:41:48 Use command in terminal to test your cam_focus -> while true; do cat /sys/devices/platform/gpio-switch/cam_focus/state; done Jan 08 18:42:11 you can use "inotifywait -qq -e access /sys/devices/platform/gpio-switch/cam_launch/state" in loop and do whatever you like Jan 08 18:43:52 inotifywait is in "inotify-tools", so just "apt-get install inotify-tools" Jan 08 18:45:10 Thanks guys :) :) Jan 08 18:45:27 cam_focus is fragile here also, WD40 helped :) Jan 08 18:47:23 actually it was faulty :) Jan 08 18:57:59 or if you want volume shortcuts or any other keyboard shortcut find out somewhere in arm distro "evkey" and command "evkey -d -t -1 /dev/input/event1" gives you number of pressed key Jan 08 18:58:44 volume gives 65 and 66 Jan 08 19:00:53 thank you :) Jan 08 19:03:34 what's a nice crew here :) Jan 08 20:42:47 I thought inotify doesn't work on /sys Jan 08 20:45:26 but wow, it does Jan 08 20:46:11 ff_: great! :-) Jan 08 21:04:24 alas cam button (GPIO?) is disabled when screen locked Jan 08 21:04:54 might be possible to change that in /etc/mce/mce.ini - don't know Jan 08 21:06:42 not even syslog shows Jan 08 21:06:44 Jan 8 22:06:21 IroN900 kernel: [29036.340728] cam_focus (GPIO 68) is now active Jan 08 21:06:46 Jan 8 22:06:22 IroN900 kernel: [29036.965698] cam_focus (GPIO 68) is now inactive Jan 08 21:06:50 when screen locked Jan 08 21:07:12 so must be GPIO (kernel facility) that gets disabled Jan 08 21:12:33 anyway, great! thanks again! IroN900:~# cat `which waitforcamtriggerbutton` Jan 08 21:12:35 #!/bin/sh Jan 08 21:12:37 inotifywait -e access /sys/devices/platform/gpio-switch/cam_launch/state Jan 08 21:12:48 yes, when it's locked cam button is disabled, only volume keys can be working in this state Jan 08 21:14:31 i'm pretty sure this isn't terribly complicated to fix, with a few lines like `echo "export 68">/sys/devices/platform/gpio-switch/fooobar` Jan 08 21:14:50 ff_: btw where did you hide the last 7 years? Jan 08 21:14:56 :-) Jan 08 21:15:07 for enable volume keys, needs change "DisableKPImmediately=2 Jan 08 21:15:24 " in /etc/mce/mce.ini Jan 08 21:15:44 yep, volume keys know to be handled in mce.ini Jan 08 21:16:02 not sure about cam button Jan 08 21:16:11 prolly not Jan 08 21:17:43 but from a kernel and hw PoV there's not much difference between volume keys and cam button, and even less between cam button (GPIO68) and e.g. lockswitch (GPIO113) Jan 08 21:18:20 so it's for sure pretty simple to enable cam button when screen locked Jan 08 21:18:29 I've n900 for two years Jan 08 21:20:27 I've seen you only recently in here, first time Jan 08 21:20:55 you're right Jan 08 21:21:03 so a late "welcome!" :-) Jan 08 21:21:26 :) Jan 08 21:22:09 I saw oscp from KotCzarny, and he mentioned in his threads about this channel Jan 08 21:22:38 great! Jan 08 21:23:31 so, in last Friday I checked it out, and I'm positive surprised Jan 08 21:23:39 :-D Jan 08 21:26:17 there was somewhere in /proc or /sys one file, in which all gpio are counter Jan 08 21:28:41 and I think that counter for cam pressed also increase during locked device Jan 08 21:29:57 I know IRQ file listing all IRQ counts Jan 08 21:30:10 not sure if there's same for GPIO Jan 08 21:30:38 if there is, it must be pretty non-standard I guess, like complete GPIO implementation Jan 08 21:31:21 gosh! my locate db doesn't index /sys and /proc?!? Jan 08 21:31:28 I'll try to find it out Jan 08 21:33:00 http://paste.opensuse.org/17589632 Jan 08 21:37:41 in this file /proc/interrupts Jan 08 21:38:56 count when it's locked but only once per look/unlook cycle Jan 08 21:39:02 cat /sys/kernel/debug/omap_gpio Jan 08 21:39:21 no counts Jan 08 21:41:57 from `watch cat /proc/interrupts` you can see not even kernel receives an IRQ when pressing cam button while locked Jan 08 21:44:10 this might be interesting for you: http://paste.opensuse.org/40386599 - monitored device lock via tk_lock switch Jan 08 21:47:02 nice Jan 08 21:47:53 watch cat /sys/devices/platform/gpio-switch/cam_launch/disable ;-) Jan 08 21:48:11 ls -l /sys/devices/platform/gpio-switch/cam_launch/disable Jan 08 21:49:22 echo 0 >/sys/devices/platform/gpio-switch/cam_launch/disable ; #:-) done Jan 08 21:51:16 don't know who's doing the "echo 1 >/sys/devices/platform/gpio-switch/cam_launch/disable" on tk_lock, prolly mce. Anyway should be simple enough to undo it Jan 08 21:51:39 or even just change permissions of that file? so write is forbidden? Jan 08 21:52:05 let's try Jan 08 21:53:33 sudo "echo 0 >/sys/devices/platform/gpio-switch/cam_launch/disable && chmod -w /sys/devices/platform/gpio-switch/cam_launch/disable" Jan 08 21:54:41 yes, it works Jan 08 21:54:47 :-) Jan 08 21:55:39 don't forget to chmod +w the file on cleanup-on-exit of whatever monitoring process is interested in cam button getting pressed Jan 08 21:58:35 ~beasttweaks Jan 08 21:58:48 note item number 2 ;) Jan 08 22:00:46 and it's caveat of not persisting a reboot. Jan 08 22:01:49 so, it's another handy shortcuts for multiple uses Jan 08 22:03:07 me kicks ass of bot Jan 08 22:04:11 ~wb lazy ass Jan 08 22:04:13 * infobot welcomes lazy ass back Jan 08 22:04:33 ~infobot Jan 08 22:04:34 it has been said that infobot is A program on the IRC that helps users, ask it to do something by putting a ~ and then say a command! Jan 08 22:05:17 ~powervr Jan 08 22:05:30 ~listkeys powervr Jan 08 22:05:32 Factoid search of 'powervr' by key returned no results. Jan 08 22:05:41 ~listvalues powervr Jan 08 22:05:47 Factoid search of 'powervr' by value returned no results. Jan 08 22:05:53 ~listvalues pvr Jan 08 22:05:55 Factoid search of 'pvr' by value (6): weathercode roxas ;; toppy ;; port 4006 ;; toppy #DEL# ;; port 4002 ;; weathercode vila real. Jan 08 22:06:05 ~listkeys pvr Jan 08 22:06:06 Factoid search of 'pvr' by key (3): airport pvr ;; weathercode rpvr ;; weathercode lpvr. Jan 08 22:07:07 ~status Jan 08 22:07:07 Since Sun Jan 8 22:03:08 2017, there have been 0 modifications, 2 questions, 0 dunnos, 0 morons and 5 commands. I have been awake for 3m 59s this session, and currently reference 119643 factoids. I'm using about 79256 kB of memory. With 0 active forks. Process time user/system 2.13/0.09 child 0/0 Jan 08 22:07:34 ~listkeys #maemo Jan 08 22:07:34 did you create this infobot, DocS? Jan 08 22:07:35 Factoid search of '#maemo' by key (17 of 115): #maemo 9 ;; #maemo bmo ;; #maemo bootloop ;; #maemo broken ;; #maemo clone-rootfs ;; #maemo dmo ;; #maemo emmc2 ;; #maemo emmc3 ;; #maemo expired-key ;; #maemo fam ;; #maemo hot ;; #maemo kbd ;; #maemo kp ;; #maemo l1_2 ;; #maemo lazyflashing ;; #maemo logs ;; #maemo mhd. Jan 08 22:07:40 ff_: nope Jan 08 22:07:44 ~owner Jan 08 22:07:45 TimRiker is my owner Jan 08 22:08:53 ff_: I'm only (one of) admin of the bot Jan 08 22:09:17 so I can kick her ass ;-) Jan 08 22:09:34 ~+help die Jan 08 22:09:35 no help on die. Use 'help' without arguments. Jan 08 22:09:45 o.O Jan 08 22:10:26 is it only this channel, or it needs manually start? Jan 08 22:10:59 ~chaninfo Jan 08 22:11:00 122/122 channels, 4543 users, 3471 unique: #debian/1647, #kde/520, #gsoc/258, #devuan/168, #asterisk/165, #maemo/160, #wowuidev/147, #oe/121, #wowace/94, #neo900/82, #cubieboard/56, #harmattan/55, #bzflag/49, #arm-netbook/49, #wowhead/46, #qi-hardware/46, #meego/46, #openmoko/42, #utah/41, #curseforge/40, #maemo-ssu/39, #elinux/36, #openmoko-cdevel/33, #webos-internals/32, #asterisk-dev/32, #brlcad/27, #uphpu/24, #slug/23, #sc2mapster/23, ... Jan 08 22:11:31 nice Jan 08 22:11:35 sometimes^H always after netsplits, the bot doesn't log in again Jan 08 22:12:01 so I reboot it via ssh Jan 08 22:13:00 it can be helpfull Jan 08 22:13:23 it is, unless people simply reject it Jan 08 22:13:49 in some channels the concept of an infobot isn't appreciated Jan 08 22:14:52 the matter of choice Jan 08 22:14:55 without infobot i'd feel lost. I wouldn't know all the URLs I offloaded to her, particularly Jan 08 22:15:56 ~flashing Jan 08 22:15:57 i heard maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh; or see ~flashing-cmdline, or see ~lazyflashing Jan 08 22:16:16 ~eink Jan 08 22:17:20 something like n900 with eink & lcd display would be fantastico :) Jan 08 22:17:31 hehe yes Jan 08 22:19:05 e-ink 11" rolled up to only form a 10mm*25mm* device Jan 08 22:19:06 and with a litte bit more of memory, cpu as second but ya Jan 08 22:19:35 would 4 times the memory suffice? ;-) Jan 08 22:20:55 still no e-ink, but... neo900 at least provides as much memory as technically feasible Jan 08 22:21:40 min 512MB, 1GB is fine, 2GB with maemo will be great Jan 08 22:23:30 but it's pricey Jan 08 22:25:21 2GB isn't feasible on OMAP3 Jan 08 22:25:34 missing addr lines Jan 08 22:25:41 r0kk3rz sed: "I think for mass appeal and ease of procurement it should be a straight forward android device with a keyboard. After delivery we can worry about porting various operating systems to it, like fremantle or sailfish or whatever people want. Jan 08 22:25:45 I know many people here wont like that idea, but its the best way to keep costs down maximise volume" Jan 08 22:25:50 you'd need paging, like on early DOS PCs Jan 08 22:26:47 won't fly Jan 08 22:28:12 so, with OMAP3 is 1GB max? Jan 08 22:28:15 you can't compete to Samsung, LG et al on an android playground, when your only seeling point is a hw lbd Jan 08 22:28:20 yes Jan 08 22:28:43 selling* Jan 08 22:29:15 selling point is a hw keyboard* - now Jan 08 22:30:51 and actually you can't port fremantle to all arbitrary android devices. Not only because of fremantle closed blobs (which we mostly REed meanwhile) but particularly because of android closed blobs for the hardware Jan 08 22:33:32 struggle on two sides, hm it can be more difficult then I thought in first glance Jan 08 22:35:37 if porting would be that easy, then maemo6 aka HARM(attan) aka N9's OS would have ported to a vast number of more recent hardware already Jan 08 22:38:11 many devs probably is trying it already Jan 08 22:38:44 Jolla tried to implement a maemo resurrection called sailfish (based on nemo/mer) *on top* of existing Android hardware abstraction layer. Seems while they achieved to roll out something, the appeal of maemo got lost Jan 08 22:39:17 or maybe few, because they know :) Jan 08 22:41:32 I for one barely touch my jolla phone once a year, since the hardware-introduced quirks suck donkey balls. E.G you can't do a clean full reflash on jolla phone, since Jolla Inc doesn't own the copyright to the blobs and thus can't provide a full "firmware image" to do a full reflash of that snapdragon crap in jollaphone Jan 08 22:42:29 so, is it music of past - light, clean, fast, mobile OS? Jan 08 22:43:41 unlike many others, I consider maemo fremantle a viable alternative Jan 08 22:44:44 it's probably still the best cleanest comprehensive phone OS I've seen so far Jan 08 22:46:02 and right this moment already gets ported to a cheap tablet by freemangordon and a few others Jan 08 22:46:32 and it's the OS of choice for Neo900 Jan 08 22:46:32 and still some parts of hardware are great, like fmtx, hw kb and so on Jan 08 22:48:20 we'll see what future bring Jan 08 22:49:46 I hope Neo900, "soon". Right now we're in layout of prototype_v2 Jan 08 22:50:14 "porting" of fremantle to Neo900 should be a nobrainer Jan 08 22:50:30 certainly another opportunities Jan 08 22:50:46 ~fptf Jan 08 22:50:47 it has been said that fptf is the Fremantle Porting Task Force, see http://talk.maemo.org/showthread.php?t=91308 Jan 08 22:50:54 http://talk.maemo.org/showthread.php?t=91142 Jan 08 22:51:04 :) Jan 08 22:53:38 http://xkcd.com/1782/ :-P Jan 08 22:59:55 "2078: He announces that he's finally making the jump from screen+irssi to tmux+weechat." LOL Jan 08 23:00:04 must be ME Jan 08 23:00:27 wait, I never really used irssi Jan 08 23:02:17 :) Jan 08 23:05:55 beauty of simplicity Jan 08 23:30:08 ~irc Jan 08 23:30:08 irc is, like, Welcome to IRC, where the men are of reduced skin pigmentation, the women are all above average, and the little girls are FBI agents. Most of the best developers to be found are on irc--only watch your step--this place can be a little rough. Jan 09 00:06:23 DocScrutinizer05: would you mean tmux+weechat+glowing-bear? Jan 09 00:07:44 no idea, never heard of the latter Jan 09 00:10:12 https://github.com/glowing-bear/glowing-bear Jan 09 00:11:39 git clone it in a subfolder of your apache rootdir and you are done Jan 09 00:47:24 hmmf oneclick install of CSSU seems to not work here, lets reflash from 0 :P Jan 09 01:01:05 hmm? Jan 09 01:01:23 fresh n900 flash (lazy flasher) and oneclick testing cssu Jan 09 01:01:29 going for attempt #2 Jan 09 01:01:29 :P Jan 09 01:01:34 result? Jan 09 01:01:58 on attempt #1 i ended up with constant portrait mode, a 'zoomed out screen' and no working application launcher Jan 09 01:02:12 duh! Jan 09 01:02:25 hm? Jan 09 01:02:40 sounds like major crash Jan 09 01:02:47 gigantic failure Jan 09 01:02:54 oh ok, thought you ment there was an obvious error :P Jan 09 01:03:10 no, absolutely non-obvious and scary Jan 09 01:04:07 please make sure to let device finish optimization after full-flash Jan 09 01:04:08 ah its fine, its just a fresh flash Jan 09 01:04:48 how could i be sure? Jan 09 01:04:58 hmm, wait 5 minutes ? Jan 09 01:05:10 after first reboot Jan 09 01:06:21 also make sure to do a full-reflash, not only rootfs Jan 09 01:08:05 it's a tad tricky to actually know if immediately after full-reflash the device already booted and started optimization, or it's still waiting for reboot that it often needs to get triggered manually after flash Jan 09 01:08:35 is there a tool for transferring contacts numbers and calendar dates to android? Jan 09 01:08:43 from n900 Jan 09 01:08:46 errr Jan 09 01:08:48 my last one has died Jan 09 01:09:25 and texts Jan 09 01:09:48 I assume that stuff can't be stored on the simcard Jan 09 01:09:59 no, can't Jan 09 01:10:13 how can I transfer it to an android phone? Jan 09 01:12:01 it's 2017 and I just got an android handset, and have never tried to transfer the texts numbers and whatnot Jan 09 01:19:08 is there a way to do this? Jan 09 01:20:30 yay, attempt #2 worked Jan 09 01:22:43 buZz: great Jan 09 01:23:23 is there a way to transfer stuff from n900 to an android handset Jan 09 01:24:00 fishbulb: only way i could think off , is syncing to a pc program first Jan 09 01:24:09 then sync that to which ever cloud you want to use Jan 09 01:24:16 your data is in backup, this could be another possible approach Jan 09 01:24:47 which backup Jan 09 01:25:02 I don't have any program to sync to Jan 09 01:25:10 does one exist? Jan 09 01:25:58 contacts can also get exported as vcard Jan 09 01:26:44 what's that Jan 09 01:27:14 can it be converted to a format some android thing can use/ Jan 09 01:28:15 in backup, files are in e.g. YourBackupDir/comm_and_cal.zip/uzip://Root/home/user/.calendar/calendardb.backup Jan 09 01:28:30 nobody knows android in here Jan 09 01:28:57 nobody uses a phone from this decade? Jan 09 01:29:02 ever? Jan 09 01:29:07 and you can speak for everyone? Jan 09 01:29:20 $YourBackupDir is the name you gave to the backup in backup app Jan 09 01:29:33 *plonk* Jan 09 01:30:41 I can speak for the #channel Jan 09 01:31:05 please /join #android and ask there, about any android related questions Jan 09 01:32:16 that is so incredibly pedantic Jan 09 01:32:26 i know android Jan 09 01:32:45 android usually doesnt store contacts or txt msgs on the device Jan 09 01:32:49 its in the cloud man Jan 09 01:33:00 dependancy on external servers, thats whats android about Jan 09 01:33:54 I'm incredibly pedantic when it's about incredibly arrogant and insulting users Jan 09 01:34:03 what is android? Jan 09 01:34:13 phones that weren't made in 2009 don't exist Jan 09 01:34:36