| 00:04.50 | *** join/#maemo pagurus (~user@p4FD6D7CB.dip0.t-ipconnect.de) |
| 01:06.26 | *** join/#maemo eMHa__ (~mh@p579DB9D9.dip0.t-ipconnect.de) |
| 01:09.22 | *** join/#maemo robbiethe1st (~robbiethe@50.37.243.120) |
| 01:53.33 | *** join/#maemo Humpelstilzchen (erik@x50abd1fa.dyn.telefonica.de) |
| 03:01.40 | *** join/#maemo lxp (~lxp@unaffiliated/lxp) |
| 03:49.50 | *** join/#maemo pagurus` (~user@pD950F971.dip0.t-ipconnect.de) |
| 03:51.05 | *** join/#maemo pagurus (~user@pD950F971.dip0.t-ipconnect.de) |
| 04:00.00 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 05:06.23 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 05:08.51 | *** join/#maemo Vajb (~Vajb@85-76-32-248-nat.elisa-mobile.fi) |
| 05:10.58 | *** join/#maemo till_ (~till@vispillo.org) |
| 05:13.11 | *** join/#maemo ecloud_ (quassel@nat/qt/x-wfdwjqjegbujxcot) |
| 05:13.50 | *** join/#maemo ArGGu^^ (~ArGGu^^@89.106.52.253) |
| 05:14.13 | *** join/#maemo thomasm (~sinnlos@360.vmworld.it) |
| 05:14.41 | *** join/#maemo script (~script@h2568012.stratoserver.net) |
| 05:27.45 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-zehtrqbxobdalcgf) |
| 05:45.52 | *** join/#maemo DrCode (~DrCode@5.28.134.3) |
| 06:57.45 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 07:03.54 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 07:25.11 | *** join/#maemo freemangordon_ (~ivo@92.247.16.100) |
| 07:43.33 | totalizator | oh gosh https://support.microsoft.com/en-us/kb/3053711 |
| 07:43.45 | totalizator | see the Resolution |
| 07:44.51 | kerio | the Resolution is to use windows 10 |
| 07:53.43 | Juest | Worst. Resolution. Ever! |
| 07:54.44 | Juest | lololol, task scheduler, funny bug and wnidows 10 kernel uses a LOT of disk! |
| 07:54.57 | Juest | uhh wtf |
| 07:55.05 | Juest | yeah, dont use the ovbious |
| 07:55.07 | Juest | lol |
| 07:55.27 | Juest | never mind and sorry for the noise |
| 07:58.04 | *** join/#maemo arcean (~arcean@62.159.77.166) |
| 08:07.51 | *** join/#maemo jskarvad (jskarvad@nat/redhat/x-nfuqevevxbkdsljs) |
| 08:07.51 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 08:16.42 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 08:28.59 | *** join/#maemo bredebid (~bredebid@62.64.166.178.rev.vodafone.pt) |
| 08:29.08 | *** join/#maemo Kilroo (~Kilroo@98.27.26.236) |
| 08:35.46 | *** join/#maemo eMHa__ (~mh@185.36.21.2) |
| 08:43.42 | *** join/#maemo Mek_ (~quassel@kde/mkruisselbrink) |
| 08:44.07 | *** join/#maemo eqs (~egs@sirius.mindpool.net) |
| 08:44.51 | *** join/#maemo Dynamit_ (~Mohamed@2a02:c200:1:10:2:3:6999:150) |
| 08:44.51 | *** join/#maemo kylanpaj (kylanpaj@hilla.kapsi.fi) |
| 08:45.07 | *** join/#maemo timeless_ (sid4015@firefox/developer/timeless) |
| 08:45.10 | *** join/#maemo Pelorojo (~redhair@unaffiliated/redhair) |
| 08:45.16 | *** join/#maemo netkat_ (~me@80.79.126.176) |
| 08:45.22 | *** join/#maemo g3kk3r_ (~torrkull@far.torrkulla.net) |
| 08:45.28 | *** join/#maemo HRH_H_Cr1b (~crab@kowloontong.dim-sum.org) |
| 08:46.01 | *** join/#maemo ssvb (~ssvb@dsl-espbrasgw1-54fa71-124.dhcp.inet.fi) |
| 08:46.31 | *** join/#maemo MetalGearSolid_ (~MetalGear@203.106.104.56) |
| 08:46.31 | *** join/#maemo teotwaki (~teotwaki@Maemo/community/contributor/crashanddie) |
| 08:46.59 | *** join/#maemo githogori_ (~githogori@c-73-70-12-67.hsd1.ca.comcast.net) |
| 08:47.54 | *** join/#maemo lxp (~lxp@unaffiliated/lxp) |
| 08:48.28 | *** join/#maemo skule (~svs@exitus.logiva.dk) |
| 08:54.26 | *** join/#maemo rm_work (rm_work@Maemo/community/cssu/rm-you) |
| 08:56.01 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 09:05.21 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 09:41.14 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 09:59.30 | *** join/#maemo andril (~andril@c-66-229-28-40.hsd1.fl.comcast.net) |
| 10:23.05 | kerio | Pali: does your bq24k module actually charge at 1.8A |
| 10:23.11 | kerio | i thought the limit was closer to 1A |
| 10:23.31 | Pali | kerio: you can tell hw current limit |
| 10:23.42 | Pali | and my bq module exports it via sysfs |
| 10:23.56 | kerio | yeah but why is "dedicated" 1800 :( |
| 10:23.58 | Pali | for wallchager is current limit something like unlimited (or upper limit) |
| 10:24.03 | kerio | oh i see |
| 10:24.22 | kerio | but the actual charging system will only charge at at most what the charging current for a near empty battery is? |
| 10:24.50 | Pali | do not remember |
| 10:24.54 | Pali | maybe ask doc |
| 10:25.09 | Pali | at least with bq module you have full control of it |
| 10:25.27 | Pali | so you can re-configure it with your own settings (if for some reason needed) |
| 10:26.00 | kerio | dedicated charging from usb port |
| 10:26.05 | kerio | #yolo |
| 10:31.38 | DocScrutinizer05 | WUT? 18ÃÃ? |
| 10:31.44 | DocScrutinizer05 | 1800 |
| 10:31.45 | kerio | yes, 18ssss |
| 10:31.52 | kerio | i assume it's "no limit" |
| 10:32.59 | DocScrutinizer05 | I'm realy too lazy to get out the bq24150 DS now, but I doubt it has a 1800 setting |
| 10:35.59 | DocScrutinizer05 | kerio: anyway there's USB limit, and charging current. They are only loosely related |
| 10:48.24 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 11:02.00 | *** join/#maemo buZz (~buzz@space.nurdspace.nl) |
| 11:23.13 | kerio | oh rofl |
| 11:23.29 | kerio | setting the charging mode to dedicated keeps the blinking led even when the cable is detached |
| 11:24.08 | kerio | oh ok it updated a bit later |
| 11:39.05 | *** join/#maemo MetalGearSolid_ (~MetalGear@unaffiliated/metalgearsolid) |
| 11:44.31 | *** join/#maemo MetalGearSolid (~MetalGear@unaffiliated/metalgearsolid) |
| 11:56.38 | *** join/#maemo Sicelo (Sicelo@unaffiliated/sicelo) |
| 12:13.27 | *** join/#maemo arcean (~arcean@62.159.77.166) |
| 12:38.50 | bencoh | 1800mA, really? |
| 12:39.48 | kerio | oh bonus of using dedicated mode |
| 12:39.58 | kerio | the screen doesn't light up when connecting or detaching the cable |
| 12:40.00 | kerio | for some reason |
| 12:43.28 | *** join/#maemo capitanocrunch (~capitanoc@host8-245-dynamic.18-79-r.retail.telecomitalia.it) |
| 12:44.47 | capitanocrunch | hi |
| 12:45.10 | kerio | anyway, i pulled out a ludicrous amount of lint and dust from the musb connector |
| 12:45.16 | kerio | now it works much better ^-^ |
| 12:46.21 | DocScrutinizer05 | \o/ |
| 12:46.33 | capitanocrunch | i just noticed the navit team uploaded a new version of navit on maemo repos (they managed to use cmake to compile it) |
| 12:46.59 | DocScrutinizer05 | wow |
| 12:47.52 | capitanocrunch | but then they stop to push updates... |
| 12:48.18 | capitanocrunch | how can we pull the source via git or similar? |
| 12:55.49 | *** join/#maemo xorly (~xorly@pix9.lf1.cuni.cz) |
| 13:03.41 | *** join/#maemo sunshavi (~user@190.235.18.236) |
| 13:28.59 | ceene | someone knows how to define an SPI flash on the device tree? |
| 13:29.24 | ceene | i can't get this thing to recognize my flash chip |
| 13:29.48 | Sicelo | Pali is your friend with that :p |
| 13:34.45 | KotCzarny | kerio: 1.8A is the microusb connector limit |
| 13:35.07 | KotCzarny | even if you connect bigger powersource its just too small to flow through |
| 13:46.23 | ceene | i got it! |
| 13:46.24 | ceene | :) |
| 13:46.39 | ceene | mtd0: 01000000 00010000 "spi32766.0" |
| 13:49.36 | ceene | i don't know where that name comes from, though |
| 13:55.29 | ceene | mtd0: 01000000 00010000 "spi1.0" |
| 13:55.33 | ceene | that's better now |
| 13:58.35 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 14:07.16 | ceene | ok, but where are my partitions? |
| 14:07.45 | *** join/#maemo Hurrian (~textual@unaffiliated/rikanee) |
| 14:29.19 | ceene | dev: size erasesize name |
| 14:29.22 | ceene | mtd0: 00000100 00010000 "bitfile" |
| 14:29.26 | ceene | mtd1: 00000100 00010000 "kernel" |
| 14:29.31 | ceene | mtd2: 00000100 00010000 "rootfs" |
| 14:29.35 | ceene | mtd3: 00000100 00010000 "calibration" |
| 14:29.39 | ceene | cool! |
| 14:29.39 | ceene | didn't mean to fill this out, only showing my happiness :P |
| 14:29.41 | ceene | ups |
| 14:31.34 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 14:32.14 | kerio | KotCzarny: is that a fact of life or a challenge? |
| 14:40.17 | *** join/#maemo DrCode (~DrCode@5.28.134.3) |
| 14:43.04 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 15:01.36 | *** join/#maemo tg` (~irc@tg.sch.bme.hu) |
| 15:01.54 | *** join/#maemo deepy (deepy@wrongplanet/deepa) |
| 15:02.28 | *** join/#maemo kerio (kerio@bad.memes.vs.dank.ninja) |
| 15:12.43 | *** join/#maemo DrCode (~DrCode@5.28.134.3) |
| 15:19.10 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 15:33.56 | *** join/#maemo erlehmann (~erlehmann@89.15.237.76) |
| 15:47.27 | *** join/#maemo jskarvad (~jskarvad@portal.kohoutovice.brno.cz) |
| 15:47.27 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 15:48.19 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 15:49.29 | *** join/#maemo krnlyng (~liar@178.112.187.109.wireless.dyn.drei.com) |
| 15:51.25 | DocScrutinizer05 | https://hardware.slashdot.org/story/16/05/18/1357218/nokia-announces-return-to-smartphone-tablet-markets |
| 15:56.26 | Sicelo | with Android in tow .. anyway, here's to hoping they eventually do even better |
| 16:13.16 | sunshavi | Sicelo: then waiting 4 smth better than the pyra ;) |
| 16:14.15 | Sicelo | i'd love either Pyra or Neo900. i'd choose those any day |
| 16:14.25 | Sicelo | but both are above my pay grade :) |
| 16:15.04 | sunshavi | in the stmt they say: focus on Android. So It is more of the same. Android does not fill the cup |
| 16:16.24 | Sicelo | otoh, i'm sure Nokia will get enough market share .. people, particularly here in Africa, still believe in Nokia |
| 16:16.55 | Sicelo | mobile phone is synonymous with the word "Nokia" here, even though Samsung and Apple have their place |
| 16:17.01 | sunshavi | Nokia is an strong brand |
| 16:18.35 | sunshavi | wondering if Pyra is going to beat neon900 on getting first to the market |
| 16:18.41 | Sicelo | it will |
| 16:22.00 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 16:24.17 | KotCzarny | kerio: both |
| 16:25.37 | DocScrutinizer05 | it definitely will |
| 16:26.29 | DocScrutinizer05 | Nikolaus postponed Neo900 in favor of Pyra which has venture capital to do R&D |
| 16:27.11 | kerio | :( |
| 16:27.11 | DocScrutinizer05 | however Pyra is no phone, I wouldn't want to use it as one at least |
| 16:27.20 | Venemo | hey guys |
| 16:27.28 | DocScrutinizer05 | hey! |
| 16:27.28 | kerio | will the mobile version actually be able to place calls |
| 16:27.29 | Venemo | I'm surprised to see this channel still exists :) |
| 16:27.31 | kerio | or will it only do data? |
| 16:28.13 | DocScrutinizer05 | kerio: it's supposed to be able to place calls. Standby and inbound calls is a completely different topic though |
| 16:28.29 | Sicelo | Venemo: hi :) |
| 16:28.38 | *** join/#maemo eMHa__ (~mh@p579DB9D9.dip0.t-ipconnect.de) |
| 16:28.41 | DocScrutinizer05 | Venemo: loooong time no see |
| 16:29.00 | Venemo | DocScrutinizer05: too long! |
| 16:29.10 | Venemo | I decided to revive my old N900 |
| 16:30.02 | Venemo | bought a new battery today, but the USB connector broke out years ago |
| 16:30.14 | Venemo | I still have it, just need to figure out whether it is possible to solder it back |
| 16:30.20 | Sicelo | <PROTECTED> |
| 16:31.32 | Venemo | I've never taken the device apart |
| 16:32.02 | Venemo | found a handy video on youtube, so maybe I'll do it tomorrow in the lab :) |
| 16:32.55 | DocScrutinizer05 | there's L1_2 service manual |
| 16:33.06 | DocScrutinizer05 | the YT videos are often crap |
| 16:33.22 | DocScrutinizer05 | ~l1_2 |
| 16:33.27 | DocScrutinizer05 | thought as much |
| 16:34.12 | Venemo | can you please gimme a link? google is not very forthcoming |
| 16:34.28 | Venemo | this is what I found: https://www.youtube.com/watch?v=aVEHm325-z8 |
| 16:34.29 | DocScrutinizer05 | http://pdadb.net/download/nokia_n900_rx-51_service_manual_l1-l2_v1_0.pdf |
| 16:34.57 | DocScrutinizer05 | ~#maemo l1_2 is http://pdadb.net/download/nokia_n900_rx-51_service_manual_l1-l2_v1_0.pdf |
| 16:34.57 | infobot | DocScrutinizer05: okay |
| 16:35.12 | Venemo | wow, thank you DocScrutinizer05 |
| 16:36.46 | Sicelo | DocScrutinizer05: maybe you could add factoid for l3&4 as well :) |
| 16:36.50 | DocScrutinizer05 | that YT video is crap |
| 16:37.53 | DocScrutinizer05 | it's exactly the crappy YT video I had in mind when I warned |
| 16:38.34 | Venemo | I see |
| 16:39.04 | KotCzarny | ~usbfix |
| 16:39.05 | infobot | well, usbfix is http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater), or https://www.youtube.com/watch?v=fYz5nIHH0iY#t=1866, you will basically need two irons: a small good one (or better hot-air reflow) and a 60+ Watt |
| 16:39.11 | DocScrutinizer05 | they skip important stuff that will definitely cause fatal mistakes when you disassemble |
| 16:39.59 | DocScrutinizer05 | to 'compensate', they do stuff that's absolute nonsense to do |
| 16:40.47 | Venemo | I was kinda surprised to find out that it really was an smd microusb that can really break off, but it did |
| 16:41.21 | luke-jr | good luck |
| 16:42.01 | luke-jr | IMO it's not possible to repair a broken USB :< |
| 16:42.26 | Venemo | why not? |
| 16:42.55 | luke-jr | too small, and there's no way to get at the parts that need to be soldered |
| 16:43.33 | Sicelo | luke-jr: i did it on both my N900. had never done SMD work before. just using regular soldering iron and lots of flux |
| 16:43.50 | Sicelo | i think the rest of you are far better experts than i am :) |
| 16:44.11 | Sicelo | and you probably all have better equipment at your disposal |
| 16:44.20 | luke-jr | ⦠|
| 16:44.29 | luke-jr | Sicelo: after it broke off? |
| 16:44.33 | Sicelo | yep |
| 16:44.53 | luke-jr | there's literally no way to even get at the connections with a soldering iron :/ |
| 16:45.14 | Sicelo | it's easy .. you need to remove a bit of the RF shielding |
| 16:45.21 | luke-jr | :| |
| 16:45.30 | luke-jr | that's safe? |
| 16:45.51 | Sicelo | i'd say so. they haven't exploded yet :) |
| 16:46.51 | DocScrutinizer05 | https://www.youtube.com/watch?v=b9FC9fAlfQE |
| 16:46.53 | Sicelo | but yes, proper hot air/reflow station would be best .. but i didn't have that, and didn't trust anyone else to fix my N900. |
| 16:48.38 | KotCzarny | sicelo: start n900 repair bussiness |
| 16:49.07 | Sicelo | if there were lots of N900 users here, i would. :) |
| 16:49.11 | KotCzarny | :) |
| 16:49.14 | KotCzarny | make it so! |
| 16:50.02 | Venemo | luke-jr: are you saying it isn't worth a try? |
| 16:50.23 | KotCzarny | he just says he is not believing his hands |
| 16:50.46 | KotCzarny | there are quite few people who did resolder broken usb to n900 |
| 16:50.53 | DocScrutinizer05 | Venemo: if you want to try, i'd say give it a go by all means |
| 16:51.03 | KotCzarny | you might try with some disposable phone as a practice |
| 16:51.55 | Venemo | I can solder QFN chips, how much harder can a USB port be? |
| 16:52.41 | DocScrutinizer05 | luke-jr is right, but Sicelo is also right. And you can even use 5mm long thin wires to connect the USB pins to the pads on PCB, then bend those wires while you push the USB into place and solder it down on the mechanical posts and reenforce it as suggested in ~usbfix |
| 16:53.35 | Venemo | so it just needs a bit of creativity |
| 16:53.35 | DocScrutinizer05 | I suggest to cut/file off a part of the "steel roof" of the USB component, which covers the electric pins |
| 16:53.40 | DocScrutinizer05 | yes |
| 16:54.08 | Venemo | sounds doable, unless the pads on the pcb also broke off, in which case I'd need to be even more creative |
| 16:54.20 | DocScrutinizer05 | even then there's a fix for that |
| 16:54.34 | DocScrutinizer05 | there are other solder points nearby |
| 16:54.42 | Venemo | I'll see tomorrow |
| 16:54.52 | Venemo | :) |
| 16:55.13 | KotCzarny | solder qi charger ;) |
| 16:55.18 | Venemo | hehe |
| 16:55.36 | *** join/#maemo githogori (~githogori@c-73-70-12-67.hsd1.ca.comcast.net) |
| 16:55.45 | Venemo | by the way since you guys were talking about the pyra earlier. the hardware does seem nice, but the form factor looks unconvincing to me |
| 16:55.48 | DocScrutinizer05 | http://talk.maemo.org/showpost.php?p=693493&postcount=12 the pics are gone, but they are available elsewhere ;-) |
| 16:56.13 | DocScrutinizer05 | http://talk.maemo.org/showpost.php?p=870017&postcount=27 see attachment |
| 16:56.33 | Venemo | is there a chance that the pyra's hardware would come in other form factors (maybe a Neo900 variant?) |
| 16:57.07 | Venemo | got it, I think I'll give it a go! thanks for the links DocScrutinizer05! |
| 16:57.14 | DocScrutinizer05 | yw |
| 16:57.53 | DocScrutinizer05 | (pyra) not in Neo900 / N900 formfactor, won't fit in |
| 16:58.06 | KotCzarny | sicelo, did you notice? |
| 16:58.20 | Sicelo | notice what? |
| 16:58.32 | KotCzarny | sicelo, i didnt solitice oscp yet ;) |
| 16:58.37 | DocScrutinizer05 | Neo900 Step2 however is targeted at exactly this combination of SoC and features |
| 16:58.47 | Sicelo | haha, ;) |
| 16:58.51 | Venemo | really? |
| 16:58.58 | Venemo | or you just teasin' us? :) |
| 17:01.11 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 17:13.41 | *** join/#maemo bredebid (~bredebid@es-217-129-26-160.netvisao.pt) |
| 17:16.10 | *** join/#maemo futpib (~futpib@176.214.26.205) |
| 17:21.19 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 17:28.09 | Venemo | DocScrutinizer05: do you have a timeframe on this Neo900 Step2? |
| 17:28.34 | DocScrutinizer05 | Venemo: just a "after Neo900" |
| 17:28.43 | Venemo | I see |
| 17:29.31 | kerio | neo900 2? :o |
| 17:29.38 | DocScrutinizer05 | at times I considered to already start a kickstarter for Step2, declaring Neo900 the prototyping needed to implement Step2 |
| 17:29.47 | kerio | if you don't call it neo1800 i'm going to be disappointed |
| 17:31.12 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?p=1444602&highlight=STEP2#post1444602 |
| 17:39.03 | KotCzarny | kerio: neo9000 would be better |
| 17:39.18 | KotCzarny | (adding 0s for next models) |
| 17:39.53 | ds3 | Neo901 |
| 17:42.51 | Venemo | lol |
| 17:42.54 | Venemo | the name doesn't matter |
| 17:43.01 | KotCzarny | not true |
| 17:43.06 | KotCzarny | name DOES matter! |
| 17:43.14 | Venemo | but I'd definitely be more interested in an OMAP5 platform than an OMAP3 one |
| 17:56.03 | DocScrutinizer05 | sure, as soon as we made a maemo work flawlessly on a OPEM3 platform, without any closed blobs we couldn't port to an OMAP5 platform |
| 17:56.30 | DocScrutinizer05 | s/OPEM/OMAP/ |
| 17:57.01 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 17:57.11 | *** join/#maemo Kabouik (~quassel@147.99.219.229) |
| 17:57.50 | DocScrutinizer05 | unlike Pyra we don't hope for a generic debian ecosystem where we simply apt-get $whatever from mainline repos |
| 17:58.00 | Venemo | how comfortable would you be with a Mer port? |
| 17:58.09 | DocScrutinizer05 | we heavily base on the existing maemo ecosystem |
| 17:58.21 | DocScrutinizer05 | Mer? blargh! |
| 17:58.34 | Venemo | you know, the stuff that Sailfish is based on. |
| 17:58.53 | Venemo | at least part of the heavy lifting could be shared with those guys |
| 17:59.24 | DocScrutinizer05 | there *is* *no* heavy lifting in SW done by Neo900 UG. We don't have the manpower for that |
| 17:59.31 | Venemo | yup, my point exactly |
| 18:00.29 | Venemo | to be honest I haven't been following up with maemo for several years now, so not sure how it is (or if it changed at all) |
| 18:00.52 | DocScrutinizer05 | and in my book Sailfish continued exactly the ill guided Harmattan design principles |
| 18:01.13 | Venemo | yeah, the Sailfish UI isn't something I'd use on a Neo900 |
| 18:01.25 | Venemo | but the base system is pretty adaptable |
| 18:01.57 | DocScrutinizer05 | adaptable doesn't mean *anybody* actually *will* adapt it |
| 18:02.13 | Venemo | I'm not trying to get into an argument here |
| 18:02.26 | Venemo | my personal problem with maemo (either 5 or 6) is that by now it has a 6+ years old version of basically everything |
| 18:02.32 | DocScrutinizer05 | Neo900 is meant to work OOTB with maemo5 |
| 18:02.48 | Venemo | not sure how big an effort it would require to bring it up to date, if that's even possible (and not sure if that is a goal for you) |
| 18:03.24 | FIQ | kerio, should compromise by calling it neo18000 |
| 18:03.24 | DocScrutinizer05 | the goal for Neo900 is to provide an ecosystem where apps are already available |
| 18:03.34 | DocScrutinizer05 | not a dream device for developers |
| 18:04.13 | FIQ | urgh I wasn't a huge fan of sailfish' UI |
| 18:04.23 | FIQ | I didn't find it *bad*, just... not special |
| 18:04.27 | DocScrutinizer05 | if you want a cutting edge OS you're free to port it to Neo900, this is the core design rule that Neo900 is so open that you can do with it whatever you want |
| 18:04.28 | FIQ | compared to iOS/android |
| 18:04.32 | Venemo | sure thing |
| 18:04.47 | FIQ | and having a steeper learning curve |
| 18:05.07 | Venemo | FIQ: I'm not talking about the Sailfish UI here specifically, but the underlying system that it builds on |
| 18:05.13 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 18:05.16 | FIQ | Mer? |
| 18:05.22 | Venemo | yes. |
| 18:05.27 | KotCzarny | you either want a blackbox device or pocket computer with phone function |
| 18:05.31 | DocScrutinizer05 | regardless Neo900 needs to be compatible to stock maemo5 to have a living ecosystem, we can't create a new one |
| 18:05.34 | FIQ | I think Mer might work on the Neo900 alread |
| 18:05.34 | FIQ | y |
| 18:05.54 | FIQ | (theoretically that is, the Neo900 doesn't exist yet) |
| 18:06.04 | Venemo | DocScrutinizer05: yeah I get that |
| 18:06.14 | Venemo | not suggesting to start from scratch |
| 18:06.26 | Venemo | but I'd love to have "the best of both worlds", if that's possible |
| 18:06.36 | DocScrutinizer05 | once there's a genuine Neo900 ecosystem, we can move on to whatever platform we like |
| 18:06.42 | FIQ | <DocScrutinizer05> unlike Pyra we don't hope for a generic debian ecosystem where we simply apt-get $whatever from mainline repos |
| 18:06.56 | Venemo | FIQ: yup, I got that too |
| 18:07.05 | FIQ | the pyra will not ship pure debian I think |
| 18:07.15 | DocScrutinizer05 | it won't, true |
| 18:07.35 | DocScrutinizer05 | however it already has a pandora community that ports a lot of games and stuff |
| 18:07.36 | FIQ | it will be basically debian, but also own repos (for optimized software) and some modifications |
| 18:07.47 | KotCzarny | devuan |
| 18:07.48 | FIQ | kinda similar to how earlier Maemos worked? I dunno |
| 18:07.48 | FIQ | yeah |
| 18:07.50 | KotCzarny | to be exact |
| 18:08.06 | FIQ | KotCzarny, no, the pyra will ship with debian |
| 18:08.10 | FIQ | not devuan |
| 18:08.15 | KotCzarny | i mean for neo900 |
| 18:08.18 | FIQ | ah |
| 18:09.40 | Venemo | DocScrutinizer05: what I was trying to say is that there are people out there who'd appreciate a fresh software stack |
| 18:10.09 | Venemo | I personally would love to have a device for on-the-go hacking on which I can run the latest Qt5 and the latest GCC |
| 18:10.14 | DocScrutinizer05 | possible, but that's only of marginal impact to the design rules for Neo900 |
| 18:10.27 | DocScrutinizer05 | Neo900 is hardware only |
| 18:10.31 | Venemo | I know |
| 18:10.40 | Venemo | just sayin :) |
| 18:10.58 | KotCzarny | if you have latest libs, nothing stops you from having latest gcc/qt |
| 18:11.14 | KotCzarny | and latest libs usually mean mainline kernel |
| 18:11.17 | DocScrutinizer05 | I can't see why you couldn't run latest Qt5 and the latest GCC on Neo900 or even N900 |
| 18:11.25 | Venemo | nobody has ported those to the N(eo)9(x) yet |
| 18:11.33 | DocScrutinizer05 | so? |
| 18:11.51 | Venemo | not sure if it's even possible |
| 18:11.52 | DocScrutinizer05 | that's exactly my point, Neo900 UG won't |
| 18:12.09 | FIQ | <Venemo> I personally would love to have a device for on-the-go hacking on which I can run the latest Qt5 and the latest GCC |
| 18:12.14 | Venemo | is not expecting Neo900 UG to do it, just here to discuss the possibilities |
| 18:12.33 | DocScrutinizer05 | FIQ: why you fullquote others? |
| 18:12.34 | FIQ | then debian wouldn't be optimal either since it thrives in ensuring stability over up-to-date software |
| 18:13.06 | FIQ | DocScrutinizer05, I usually do that when I want to reply to someone to reference what I'm replying to |
| 18:13.11 | Venemo | FIQ: I wouldn't want to get into an argument about debian here, let's try to stay productive |
| 18:13.15 | DocScrutinizer05 | the possibilities are all there, freemangordon runs kernel 4,over9000 on N900 |
| 18:13.21 | FIQ | (er, to clarify, I only do it when what I'm replying to is unclear) |
| 18:13.35 | FIQ | Venemo, no no I'm not either |
| 18:13.55 | DocScrutinizer05 | FIQ: then I suggest you quoze only partial and append your answer in same post |
| 18:14.19 | Venemo | FIQ: but as an aside, you are correct, I don't like debian and don't use it myself, but I respect its goals |
| 18:14.27 | FIQ | just saying since it seemed you wanted the latest of the things |
| 18:14.41 | DocScrutinizer05 | ((I usually do that when I want to reply)) nobody understands that really |
| 18:14.47 | FIQ | and thus debian wouldn't be optimal, not trying to start a distro flamewar : |
| 18:14.49 | FIQ | :) |
| 18:16.30 | FIQ | anyway Venemo, if you want a pocket computer for development, I think the pyra might arguably be a better choice due to its keyboard |
| 18:16.39 | DocScrutinizer05 | ~devuan |
| 18:16.39 | infobot | somebody said devuan was the most awesome distro, or https://devuan.org |
| 18:17.03 | FIQ | (shoulder button as modifiers is *great*, a major gripe I had with N900's keyboard apart from being 3-row which is workable) |
| 18:17.13 | *** join/#maemo xorly (~xorly@193.85.203.185) |
| 18:17.22 | DocScrutinizer05 | Venemo: maemo "secretly" moved from debian to devuan as base distro (aka 'upstream') |
| 18:17.59 | Venemo | you trying to covertly start a systemd flamewar? |
| 18:18.08 | DocScrutinizer05 | hehe no |
| 18:18.18 | DocScrutinizer05 | no systemd in maemo is a fact |
| 18:18.47 | FIQ | I'm not a fan of systemd myself but the issues I've had with systemd is minor enough for me not to make a fuss about it |
| 18:18.50 | Venemo | FIQ: I am actually considering the pyra, but I dislike its thickness and that ugly game console feeling |
| 18:19.02 | FIQ | Venemo, I see |
| 18:19.12 | DocScrutinizer05 | FIQ: well, try to install systemd on maemo. Good luck! |
| 18:19.17 | FIQ | personally I find game controls a feature, and not just for gaming purposes |
| 18:19.31 | FIQ | DocScrutinizer05, haha I don't embrace systemd at all :P |
| 18:19.36 | Venemo | @ systemd: I've been using it since F15 adopted it, never had any problems. don't wanna flame about it though :) |
| 18:19.53 | FIQ | I'd rather stay away, but on desktop I feel that avoiding it is more hassle than it's worth |
| 18:20.22 | FIQ | I've had minor issues with it, issues I never had with the previous init systems I've used |
| 18:20.27 | DocScrutinizer05 | Venemo: it simply is incompatible to maemo, and will stay so invariably |
| 18:20.28 | FIQ | but those are *minor* |
| 18:20.33 | Venemo | DocScrutinizer05: okay. |
| 18:20.57 | Venemo | on a different not: it would be interesting to know if the pyra's hw could be squeezed into an N810. that's something I would actually want. |
| 18:21.03 | Venemo | on a different note: it would be interesting to know if the pyra's hw could be squeezed into an N810. that's something I would actually want. |
| 18:21.12 | DocScrutinizer05 | e.g. both maemo5 and systemd claim exclusive use of cgroups |
| 18:21.26 | KotCzarny | venemo: http://linux-sunxi.org/User:Kc#systemd_is_evil |
| 18:21.35 | KotCzarny | just a few links i've gathered |
| 18:22.02 | FIQ | (the 3 issues that stood out for me was more tinkering needed to set things up, binary logfiles (why...), and a weird bug that made my system incredibly slow under certain circumstances) |
| 18:22.05 | DocScrutinizer05 | ((N810)) no way |
| 18:22.05 | Venemo | KotCzarny: I have a few links of my own with counter-arguments, but let's not flame here please. |
| 18:22.15 | KotCzarny | ok |
| 18:22.16 | KotCzarny | :) |
| 18:22.27 | KotCzarny | we are free to choose what we like |
| 18:22.32 | *** join/#maemo Venemo_j (~venemo@fedora/Venemo) |
| 18:22.46 | FIQ | but ultimately I wont bother messing with things either way |
| 18:23.24 | FIQ | Venemo, why the N810? |
| 18:23.40 | FIQ | hm IIRC it had some benefits with the case that the N900 lacks |
| 18:23.45 | FIQ | can't remember what exactly |
| 18:24.01 | KotCzarny | good speakers? |
| 18:24.08 | KotCzarny | big screen? |
| 18:24.11 | Venemo | DocScrutinizer05: the pyra board should be around the right size for an N810, the dimensions look somewhat similar |
| 18:24.16 | KotCzarny | dpad? |
| 18:24.27 | DocScrutinizer05 | I doubt it |
| 18:24.35 | Venemo | FIQ: bigger screen, better keyboard, room for larger battery, better overall build quality. that is just my impression though. |
| 18:24.38 | FIQ | ah, I never used the speakers myself on either device (obviously in the case of n810, I never had one) |
| 18:24.49 | FIQ | didn't know it had a bigger screen/keyboard though |
| 18:25.05 | KotCzarny | keyboard was similar in size |
| 18:25.14 | FIQ | I've seen its d-pad, I prefer an actual d-pad, but I guess it's better than what N900 had |
| 18:25.52 | DocScrutinizer05 | N810 was (is) awesome |
| 18:26.27 | DocScrutinizer05 | and I still think (unlike many other users) that the N810 kbd is superior to the N900's |
| 18:26.49 | Venemo_j | FIQ: look it up on wikipedia |
| 18:27.00 | Venemo_j | DocScrutinizer05 +1 |
| 18:27.16 | FIQ | I wish more portable keyboards had shoulder buttons :P |
| 18:28.04 | Venemo_j | I actually considered buying an N810 when I realized I wasn't gonna be as productive on the jolla phone as I was on the N900... |
| 18:28.46 | Venemo_j | >4" devices are the norm these days anyway so it wouldn't even raise any eyebrows |
| 18:29.16 | FIQ | heh |
| 18:29.19 | FIQ | smaller and smaller |
| 18:29.25 | FIQ | suddenly, bigger and bigger |
| 18:29.31 | Venemo_j | I would've got one if it wasn't for the spectaculary outdated cpu architecture |
| 18:29.44 | FIQ | what does it use, OMAP2? |
| 18:29.48 | KotCzarny | yup |
| 18:29.51 | Venemo_j | yup |
| 18:29.55 | FIQ | ah |
| 18:30.23 | KotCzarny | works great as a heart of intelligent audio system |
| 18:30.44 | DocScrutinizer05 | FIQ: ((suddenly, bigger and bigger)) the veteran users told Nokia so before N900 rollout |
| 18:31.26 | luke-jr | N810 kbd is definitely superior to N900 |
| 18:31.28 | luke-jr | by far |
| 18:31.47 | DocScrutinizer05 | if Nokia had kept the N810 formfactor for N900, that would've been a dream |
| 18:32.22 | DocScrutinizer05 | the screen feels like 3 times the size - obviously it's not but still... |
| 18:32.40 | DocScrutinizer05 | so does the kbd |
| 18:32.53 | FIQ | is it 4row? |
| 18:33.00 | DocScrutinizer05 | err |
| 18:33.03 | DocScrutinizer05 | checks |
| 18:33.13 | luke-jr | overall, I prefer the C760 formfactor |
| 18:33.14 | FIQ | should know that :P |
| 18:33.18 | luke-jr | so I have high hopes for Pyra |
| 18:33.18 | FIQ | it's a huge difference |
| 18:33.28 | FIQ | C760? |
| 18:33.30 | DocScrutinizer05 | yup |
| 18:33.34 | luke-jr | FIQ: yes |
| 18:33.34 | FIQ | oo |
| 18:33.42 | FIQ | yeah that would have been great |
| 18:33.46 | luke-jr | http://www.dreadscott.com/C760/Zaurus_C760.jpg |
| 18:34.09 | FIQ | then the only real complaint I would have with it would ultimately be trickier modifiers on thumb keyboards |
| 18:34.48 | DocScrutinizer05 | dang, that thing collected to much dust, I thought the diplay is broken and went black, while it was only a wipe where dost got removed ;-P |
| 18:34.59 | DocScrutinizer05 | s/ to / so / |
| 18:35.56 | Venemo_j | my N950's screen died :( |
| 18:35.57 | DocScrutinizer05 | again dang! I need to revivie this thing |
| 18:36.23 | DocScrutinizer05 | ooh N950, definitely not using that one for anything. Wrong OS |
| 18:36.46 | FIQ | isn't aegis easy to get rid of though |
| 18:36.53 | FIQ | luke-jr, ah |
| 18:36.56 | DocScrutinizer05 | I hate an OS that tells me "MALF!" when I touch a silly harmless init script or whatever |
| 18:38.05 | DocScrutinizer05 | http://maemo.cloud-7.de/Aegis-kills-device.jpg |
| 18:38.38 | Venemo_j | was cool in 2011 |
| 18:38.47 | DocScrutinizer05 | MALF never was cool |
| 18:38.55 | Venemo_j | not MALF |
| 18:39.06 | FIQ | that's dumb |
| 18:39.16 | Venemo_j | but the device was |
| 18:39.20 | DocScrutinizer05 | yep |
| 18:39.35 | *** join/#maemo xelo (~xelo@ip-176-198-129-195.hsi05.unitymediagroup.de) |
| 18:39.48 | DocScrutinizer05 | Werner got one a 6 months ago and went "SHIT! why didn't Nokia sell those?" |
| 18:39.53 | FIQ | but I have a feeling they "had" to |
| 18:40.10 | FIQ | as in, they were persuaded by operators to do it |
| 18:40.27 | KotCzarny | not operators, managers probably |
| 18:40.35 | Venemo_j | there were rumors |
| 18:40.45 | FIQ | IIRC the n900 got into operator trouble for not being able to be locked |
| 18:40.46 | Venemo_j | about that |
| 18:40.48 | DocScrutinizer05 | for the rationale of Aegis? |
| 18:40.55 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 18:41.13 | DocScrutinizer05 | err N900 *was* able to get locked, at least SIMlocked |
| 18:41.32 | FIQ | uh |
| 18:41.37 | FIQ | how do you lock a phone |
| 18:41.41 | FIQ | that allows you to be root |
| 18:41.53 | DocScrutinizer05 | it's a modem thing, not APE |
| 18:42.15 | DocScrutinizer05 | it's a BB5 phone like many other Nokia phones |
| 18:42.22 | FIQ | mhm |
| 18:43.41 | DocScrutinizer05 | aegis was more about overclocking and generally gaining control over the ecosystem again. More sales-speak they decided to make money from software and that didn't pan out with OVI and maemo5 |
| 18:44.16 | DocScrutinizer05 | and finally Nokia died from that ill concept of "make money from appshop" |
| 18:45.37 | Venemo | they died from the ill concept of betting too much on symbian and killing off the in-house competitors to that |
| 18:46.01 | DocScrutinizer05 | that too, to some degree |
| 18:46.18 | DocScrutinizer05 | however symbian had a working ecosystem but no future |
| 18:47.05 | DocScrutinizer05 | while maemo never had an ecosystem like a "decent product", it always was FOSS |
| 18:47.20 | DocScrutinizer05 | more FOSS than nokia sales droids liked it |
| 18:47.29 | Venemo | they should've invested more into maemo and maybe should've made a symbian runtime on top of that. by the time they realized their mistake (and bought Qt), it was too late |
| 18:48.09 | Venemo | who knows |
| 18:48.11 | DocScrutinizer05 | they should have focused on selling decent hardware rather than trying to make money from appshops |
| 18:48.17 | KotCzarny | they should've gave maemo more freedom to experiment, not trying to sell out on it |
| 18:48.29 | Venemo | anyway, I believe nokia's mistake was mismanagement, simply |
| 18:48.35 | DocScrutinizer05 | OVI was an epic failure |
| 18:48.49 | Venemo | I wasn't sorry to see them go |
| 18:49.01 | Venemo | (although I was sorry for the good engineers that worked there) |
| 18:49.36 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 18:49.56 | DocScrutinizer05 | yep. A pity some of the worst of Nokia spirit got ported to Jolla |
| 18:50.34 | DocScrutinizer05 | while some of the best got lost during that transition |
| 18:51.08 | DocScrutinizer05 | or maybe, it was already lost at that time, drowned in Aegis |
| 18:51.24 | Venemo | indeed |
| 18:51.26 | Venemo | who knows. |
| 18:51.47 | Venemo | to be honest I'm not sure if actually anyone is working on anything in jolla |
| 18:52.19 | Venemo | we gave them hundreds of bugreports since 2013, none of which have been fixed since (okay, maybe one or two) |
| 18:52.34 | DocScrutinizer05 | which is one of the nasty concepts inherited from Nokia. Completely opaque |
| 18:52.36 | KotCzarny | drowned in bugs |
| 18:53.11 | Venemo | at least from the few dozens that I personally reported,, only one or two is fixed, a few are marked as "this is a feature, not a bug", the rest just isn't cared about |
| 18:53.25 | Venemo | I was really sorry to see all that |
| 18:53.32 | FIQ | Venemo: I get the impression that they have too few engineers to be productive with the OS itself |
| 18:53.41 | FIQ | s/engineers/workers/ |
| 18:53.56 | Venemo | I don't know. they got some good people still |
| 18:54.09 | DocScrutinizer05 | I think Jolla simply didn't learn the lessons from maemo |
| 18:54.23 | Venemo | but since the communication from them is 0, I'm not sure what's going on in there |
| 18:55.24 | FIQ | and I thought they were supposed to be open |
| 18:55.26 | DocScrutinizer05 | seems there's no Quim Gill at Jolla either |
| 18:55.30 | FIQ | and transparent |
| 18:55.54 | Venemo | they were a lot more open and transparent in 2013 than they are now |
| 18:58.53 | DocScrutinizer05 | https://de.linkedin.com/in/quimgil |
| 18:59.19 | kerio | DocScrutinizer05: what about a watercooled, overclocked-to-smithereens omap3? |
| 18:59.34 | DocScrutinizer05 | Jolla seems to lack understanding of the importance of a porson like Quim in their company |
| 19:00.15 | DocScrutinizer05 | kerio: what about it? did it reach the Jupiter already? |
| 19:00.31 | kerio | no, for the neo900 2 |
| 19:00.40 | DocScrutinizer05 | no way |
| 19:00.49 | DocScrutinizer05 | OMAP3 is already almost EOL |
| 19:00.50 | kerio | replace the screen with a vat for the liquid nitrogen |
| 19:01.14 | kerio | bump the cpu to 2ghz |
| 19:01.20 | DocScrutinizer05 | OMAP3 has _no_ decent digital video interface |
| 19:01.43 | DocScrutinizer05 | OMAP3 has a max of 1GB RAM |
| 19:02.53 | luke-jr | I thought OMAP5 was EOL? |
| 19:03.15 | DocScrutinizer05 | err |
| 19:03.38 | FIQ | who is Quim anyway? |
| 19:03.45 | DocScrutinizer05 | OMAP and TI embedded is End Of R&D |
| 19:03.59 | DocScrutinizer05 | FIQ: https://de.linkedin.com/in/quimgil |
| 19:04.01 | FIQ | "OMAP3 is already almost EOL" <- almost? |
| 19:04.25 | DocScrutinizer05 | FIQ: yes, we can still buy chips |
| 19:04.52 | DocScrutinizer05 | it even seems TI still builds them |
| 19:05.43 | Venemo | FIQ: Quim was the community manager when Maemo was a thing. he stepped down after Harmattan (aka. Maemo 6) turned out to be a dead end |
| 19:05.58 | DocScrutinizer05 | actually it's rather like OMAP5 is not fully evaluated yet |
| 19:06.05 | FIQ | Venemo: ah |
| 19:06.32 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 19:06.55 | DocScrutinizer05 | Quim basically was the heart and soul of maemo |
| 19:07.16 | DocScrutinizer05 | allegedly he talked Nokia into maemo, to start with |
| 19:08.06 | Venemo | I haven't heard that before |
| 19:08.23 | Venemo | what I remember is that he turned kinda bitter by the end |
| 19:08.36 | DocScrutinizer05 | well, I heard it as hearsay or reference in some IRC gossip a few years ago |
| 19:08.36 | Venemo | which is pretty understandable considering... |
| 19:08.47 | DocScrutinizer05 | yep |
| 19:11.23 | Venemo | the thing is, I only joined the party with the N900, so I missed the really fun early days |
| 19:12.02 | DocScrutinizer05 | >> open source advocate @ MeeGo team Nokia April 2008 â January 2012 (3 years 10 months)<< |
| 19:13.11 | DocScrutinizer05 | actually Carsten Raterman Haitzler introduced me to N800 in Taipei when we shared the Openmoko apartment |
| 19:13.20 | KotCzarny | venemo, buy yourself 770, n800 and n810, just for fun (and they are cheap) |
| 19:13.23 | DocScrutinizer05 | Rasterman* |
| 19:13.51 | DocScrutinizer05 | I instantly got me a N810 and was sold to the concept |
| 19:14.34 | Venemo | KotCzarny: I considered that, and would even buy an N810 if it wasn't for the outdated cpu arch |
| 19:15.04 | DocScrutinizer05 | then Raster and me tried to convince Openmoko of the benefits of OMAP and its zeroclocking, compared to the quite awkward suspend-to-RAM concept of OM's devices |
| 19:15.51 | KotCzarny | venemo, you still can write useful apps and have use cases for it |
| 19:16.11 | DocScrutinizer05 | Venemo: sou prolly wuldn't. I tried and it's near impossible to find a N810 now, I'm happy I got two working ones |
| 19:16.20 | KotCzarny | because if you drop the bloat, its cpu is enough |
| 19:16.28 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 19:16.30 | Venemo | KotCzarny: my use case would be on-the-go hacking and productivity |
| 19:16.41 | Venemo | DocScrutinizer05: there are always some of them on the bay |
| 19:16.48 | DocScrutinizer05 | wow |
| 19:17.02 | DocScrutinizer05 | last time I checked there was zilch |
| 19:18.58 | Venemo | DocScrutinizer05: btw, is the new kernel you spoke of part of the community SSU? |
| 19:19.16 | DocScrutinizer05 | no |
| 19:19.20 | KotCzarny | not yet |
| 19:19.58 | DocScrutinizer05 | CSSU is about conservative maintenance of maemo, a new kernel would be part of FPTF I'd guess |
| 19:20.47 | DocScrutinizer05 | KP is still 2.6.28, no? |
| 19:21.21 | Venemo | ah. |
| 19:21.41 | DocScrutinizer05 | ~cssu |
| 19:21.42 | infobot | [cssu] http://wiki.maemo.org/Community_SSU, or (Community Seamless Software Update) |
| 19:21.47 | DocScrutinizer05 | ~fptf |
| 19:21.47 | infobot | extra, extra, read all about it, fptf is the Fremantle Porting Task Force, see http://talk.maemo.org/showthread.php?t=91308 |
| 19:22.14 | Venemo | okay |
| 19:22.51 | DocScrutinizer05 | http://wiki.maemo.org/Community_SSU#Testers |
| 19:23.45 | KotCzarny | im still searching for cheap nokia 770 |
| 19:23.52 | KotCzarny | (for science and stuff) |
| 19:24.29 | Venemo | btw, taking a look at the design of the pyra, I'd say that the pcb which has the CPU and RAM could fit and one would "only" need to design a smaller pcb for the connectors to fit it the hw in a smaller case |
| 19:26.10 | DocScrutinizer05 | yeah, exactly |
| 19:26.40 | Venemo | which seems to be a doable thing if you get rid of the sd card slots and the extra usb ports |
| 19:26.52 | DocScrutinizer05 | where "PCB for connectors" is a tad misleading since that PCB has a lot more than only connectors |
| 19:27.16 | Venemo | sure |
| 19:27.59 | Venemo | but (judging by the photos) most of the area is occupied by the two sd card readers and the usbs |
| 19:28.01 | DocScrutinizer05 | actually I guess 80% to 90% of the whole BOM sit on the main PCB |
| 19:28.39 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 19:28.47 | KotCzarny | http://www.ebay.com/itm/LOT-OF-11-NEW-Nokia-770-Internet-Tablet-/172175449336?hash=item281674dcf8:g:VuEAAOSwWTRW0LVi |
| 19:28.52 | KotCzarny | eheheh, any takers? |
| 19:30.57 | Venemo | DocScrutinizer05: out of curiosity, how many pcb layers are there? |
| 19:32.49 | DocScrutinizer05 | I dunno, I'm not a part of Pyra R&D team |
| 19:33.25 | DocScrutinizer05 | I *guess* they tried hard to get away with only 4 layers on main PCB |
| 19:34.18 | DocScrutinizer05 | the 8+ layers are only needed to breakout the huge SoC BGA |
| 19:34.59 | DocScrutinizer05 | Venemo: but why not ask those questions on #dragonbox-pyra ? |
| 19:35.03 | Venemo | and the Neo900? |
| 19:35.31 | Venemo | I mean, how many layers do you guys have? |
| 19:35.33 | DocScrutinizer05 | The Neo900 hopes to get away with 4 layers for LOWER and 8 layers for UPPER |
| 19:35.49 | Venemo | lower what, and upper what? |
| 19:35.57 | DocScrutinizer05 | PCB |
| 19:37.01 | Venemo | I wasn't aware that there were two pcbs in it |
| 19:37.27 | DocScrutinizer05 | http://neo900.org/stuff/cccamp15/ccc2015talk/talk.pdf page 11 |
| 19:37.54 | DocScrutinizer05 | http://neo900.org/stuff/cccamp15/ccc2015talk/neo900-wpwrak_CCC2015.webm |
| 19:38.15 | Venemo | ah, I see |
| 19:39.36 | Venemo | cool stuff |
| 19:39.58 | DocScrutinizer05 | yeah, Werner's talk is brilliant |
| 19:40.11 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 19:40.27 | Venemo | did you talk too? your name's on the slides |
| 19:41.02 | DocScrutinizer05 | hehe, I have a speacial appearance in the background a few times, bringing Werner a bottle of Club Mate |
| 19:41.24 | DocScrutinizer05 | I don't do talks |
| 19:42.40 | Venemo | you shy? |
| 19:42.42 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 19:43.16 | DocScrutinizer05 | 10:53 |
| 19:43.34 | DocScrutinizer05 | ((shy)) that too, plus I can't talk |
| 19:43.52 | DocScrutinizer05 | well, you would either cringe or fall asleep |
| 19:44.03 | Venemo | that's just another skill one can develop |
| 19:44.14 | Venemo | hm. |
| 19:44.19 | Venemo | since we're talking hardware |
| 19:44.20 | DocScrutinizer05 | I'm happy with the skillset I got |
| 19:44.43 | Venemo | there is a thing I don't understand and was too afraid to ask |
| 19:44.53 | DocScrutinizer05 | just ask :-D |
| 19:45.04 | DocScrutinizer05 | hint: #neo900 |
| 19:45.22 | Venemo | that is: why isn't there any chip vendor selling hand-solderable Cortex-A CPUs? like, I'd be pretty happy to see something in QFN |
| 19:45.52 | DocScrutinizer05 | err, it has some 500+ pins |
| 19:45.59 | Venemo | not all of them |
| 19:46.13 | Venemo | I mean, not all of them would actually need all of those pins |
| 19:46.45 | Venemo | the closest thing I found was a thing called Vybrid (with Cortex-A5) in QFP |
| 19:47.04 | Venemo | the rest of them are all BGA, which, sadly, I can't hand-solder |
| 19:47.46 | KotCzarny | make a universal 'socket' for bga? |
| 19:48.11 | DocScrutinizer05 | (two PCB) see 13:35 |
| 19:49.25 | *** join/#maemo heroux (sandroco@gateway/shell/insomnia247/x-bfoptdavxcqwdjfe) |
| 19:50.17 | sunshavi | that video sounds interesting, even i am not watching it |
| 19:50.44 | sunshavi | on n900 now |
| 19:51.03 | DocScrutinizer05 | you should watch it if you're interested in Neo900 |
| 19:51.14 | DocScrutinizer05 | and maemo history |
| 19:51.49 | sunshavi | sure. I am an n800 user |
| 19:51.50 | DocScrutinizer05 | it's prolly not suited for N900 playback, yes |
| 19:54.51 | sunshavi | KotCzarny: perhaps with oscp? |
| 19:55.24 | Sicelo | not with oscp either |
| 19:55.45 | Venemo | DocScrutinizer05: so out of curiosity, how do you make a proto with a BGA chip? |
| 19:55.47 | Sicelo | N900 just lacks the processing power for that video :) |
| 19:55.56 | Venemo | nah |
| 19:56.02 | DocScrutinizer05 | in a factory that has all the tooling |
| 19:56.17 | Venemo | but then it must be expensive even to just make one |
| 19:56.26 | DocScrutinizer05 | yes, it is expensive |
| 19:57.12 | DocScrutinizer05 | we could try to do the placement and soldering "at home", but it's prolly not worth the risk and hassle |
| 19:57.39 | DocScrutinizer05 | ~wiki vapor phase soldering |
| 19:57.49 | Venemo | placement sounds like the issue here |
| 19:57.58 | Venemo | the soldering you could do with just hot air |
| 19:58.25 | DocScrutinizer05 | https://www.google.de/search?q=vapor+phase+soldering |
| 19:58.39 | DocScrutinizer05 | easier than hot air |
| 19:58.59 | DocScrutinizer05 | placement and solder paste application, yes |
| 19:59.19 | ceene | by the way, i was yesterday at the factory that solders components for our company's boards |
| 19:59.37 | ceene | and i asked them about PoP such as n900 and ram replacement |
| 20:00.15 | DocScrutinizer05 | what did they answer? |
| 20:00.15 | ceene | i was told they can do it, but that it's q a difficult process with no guarantees |
| 20:01.00 | ceene | they showed me the machine, a vacuum extractor with several heads that can be used to fit the right size of the chip |
| 20:02.16 | ceene | he told me that even before taking out the ram, odds are the whole package would get out |
| 20:02.56 | ceene | so... basically only do that if one of the chips is broken and you're willing to give it a try |
| 20:03.24 | ceene | i asked for homemade options and he didn't think it to be feasible |
| 20:07.33 | KotCzarny | um |
| 20:07.46 | KotCzarny | if it would be feasible to fit 1gb onto n900.. |
| 20:07.54 | Venemo | PoP = ? |
| 20:08.19 | ceene | package on package |
| 20:08.26 | ceene | ram is soldered on top of cpu |
| 20:09.06 | ceene | they told me they could do try to do it, without any guarantee |
| 20:09.06 | KotCzarny | but seriously, n900 with more ram would rocke the show |
| 20:09.06 | Venemo | ah. that. |
| 20:09.20 | ceene | yeah, simply me ram would be something amazing |
| 20:09.27 | ceene | s/me/more/ |
| 20:09.43 | Venemo | @ BGA and handsoldering: I know some guys who make stencils from paper and do it that way :) |
| 20:10.28 | ceene | in a couple months we're gonna make a bga based board |
| 20:10.36 | ceene | i can tell you prices then |
| 20:13.59 | Venemo | sure |
| 20:14.24 | Venemo | let me know |
| 20:15.26 | ceene | infobot: are you able to remind me of things? |
| 20:16.21 | ceene | i'll have to remember by myself |
| 20:20.46 | DocScrutinizer05 | Venemo: (VPS) http://www.mikrocontroller.net/topic/307715 |
| 20:21.29 | Venemo | sorry DocScrutinizer05 I forgot most of my German over the years |
| 20:22.40 | Venemo | which post should I look at? |
| 20:24.16 | DocScrutinizer05 | well, the one with the pictures, it explains the pretty low resource demands for VPS |
| 20:24.49 | DocScrutinizer05 | just look at the pics, the text is less important |
| 20:24.56 | Venemo | VPS = ? |
| 20:25.03 | DocScrutinizer05 | Vapor Phase soldering |
| 20:25.07 | Venemo | ah, that |
| 20:26.33 | DocScrutinizer05 | ceene: yes, separating PoP is basically not an option |
| 20:27.10 | DocScrutinizer05 | we used new SoC too when we tested the 1GB RAM PoPs on our pimped BB-xM |
| 20:29.34 | *** join/#maemo Arch-TK (Arch-TK@fsf/member/Arch-TK) |
| 20:34.02 | ceene | which components are going to be on each board? |
| 20:34.20 | ceene | i haven't fully undertood the problem in the slides you linked before |
| 20:34.33 | ceene | *understood |
| 20:46.22 | DocScrutinizer05 | ceene: isn't that a question for #neo900 ? |
| 20:46.52 | ceene | undoubtedly, yeah |
| 20:47.21 | DocScrutinizer05 | anyway, the schematics have a note on each sheet whether it's UPPEr or LOWER, afaik |
| 20:47.41 | ceene | ah, okay |
| 20:47.51 | ceene | well, i'll watch the talk tomrrow |
| 20:48.02 | ceene | i'm sure it solves some doubts |
| 20:49.47 | *** part/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 20:52.38 | DocScrutinizer05 | anyway for most components the placement is obvious from the connections they need to make and space we have to place them |
| 20:53.43 | DocScrutinizer05 | everything RF goes to LOWER since there are the antennas. Same for audio and all the switches |
| 20:54.11 | DocScrutinizer05 | obviously also the USB jack and the AV jack |
| 20:54.48 | DocScrutinizer05 | CPU and interface to display goes to UPPER |
| 20:55.54 | DocScrutinizer05 | kbd is upper too |
| 20:58.10 | DocScrutinizer05 | camera goes to UPPER |
| 20:59.33 | DocScrutinizer05 | it will stick to upper with a doublesided sticky foam patch and connect to upper with the B2B connector |
| 21:00.43 | DocScrutinizer05 | thermo/baro/hygro sensor goer to upper right corner of upper surface of upper, to get maximum exposed to ambient |
| 21:03.46 | ceene | i guess this design has a lot more things than the n900 |
| 21:04.25 | ceene | would it be possible to fit everythin on a two side populated board? |
| 21:05.21 | ceene | don't know if it even makes sense |
| 21:05.54 | DocScrutinizer05 | falso see http://neo900.org/stuff/werner/stacking/ For the second SIM slot there's a placement diagram in stuff/ somewhere but right now I can't find it |
| 21:06.36 | DocScrutinizer05 | sure you can fit everything on a two side populated single board... given it's large enough ;-) |
| 21:07.37 | DocScrutinizer05 | I did a calculation and concluded we're at roughly 60 to 70% (iirc) use of available real estate |
| 21:07.53 | DocScrutinizer05 | when we use all 4 surfaces S1 to S4 |
| 21:08.08 | DocScrutinizer05 | honestly we should take that to #neo900 |
| 21:08.26 | ceene | sure |
| 21:18.58 | sunshavi | Hi guys, question about fm radio on n800 |
| 21:20.00 | sunshavi | I have edited the stations file on /apps/maemo/fmradio/frequency_key. How Can I tell the fmradio plugin to reload it, without rebooting |
| 21:41.02 | sunshavi | the plugin used to look for the info from this site http://sds.hpvisualradio.com/sdsweb/Search.do |
| 21:43.43 | sunshavi | if knowing the output of that operation i can simulate the output :). Any idea? |
| 21:46.50 | DocScrutinizer05 | ugh? |
| 21:48.09 | DocScrutinizer05 | I think the N810 never had a radio. And I had no N800. The N900 however hardly looks at websites to check for any parameters for the radio |
| 21:48.57 | ds3 | how wide of a freqency range is the radio on the n900? |
| 21:49.12 | DocScrutinizer05 | err japan plus worldwide |
| 21:49.29 | DocScrutinizer05 | I.E some 76(?) up to 108 |
| 21:50.41 | DocScrutinizer05 | http://wiki.maemo.org/N900_FM_radio_receiver |
| 21:51.14 | DocScrutinizer05 | mmphh, has no decent info on freq range |
| 21:52.20 | DocScrutinizer05 | http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM2048 |
| 21:54.24 | sunshavi | I am using just the transmitter |
| 21:54.31 | sunshavi | which is nice by the way |
| 21:54.32 | ds3 | oh |
| 21:54.38 | ds3 | so no chance of getting it up to like 144MHz |
| 21:54.46 | ds3 | (Ham band) |
| 21:54.48 | sunshavi | the fmradio plugin on n800 is better than on n900 |
| 21:54.58 | sunshavi | the best radio app is on n9 |
| 21:55.22 | DocScrutinizer05 | http://www.qic.com.cn/qicfileserver/readFile.action?filePath=/pdf/BOARDCOM/BCM2048.pdf 76-108 |
| 21:55.38 | DocScrutinizer05 | ds3: nope, no way |
| 21:56.13 | sunshavi | I have recorded somewhere the exact chip that cames on n800 |
| 21:56.17 | DocScrutinizer05 | sunshavi: I'm not used to the term "plugin" |
| 21:56.46 | sunshavi | 4 n900 it is the name as widget |
| 21:57.20 | ds3 | that comes up as a 2 page flyer for me |
| 21:57.30 | ds3 | oh nevermind... that is a 2 page flyer :D |
| 21:57.35 | DocScrutinizer05 | still has the range |
| 21:57.50 | ds3 | was hoping there is a register spec on the tuner |
| 21:58.10 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 21:59.31 | sunshavi | according to this page https://wiki.maemo.org/Programming_N800_FM_radio_receiver |
| 21:59.42 | sunshavi | it is tea5761 |
| 22:05.31 | sunshavi | an alternative could be to create a c prg and call it from cli. So no need 4 the plugin aka widget |
| 22:11.33 | DocScrutinizer05 | ds3: http://lxr.free-electrons.com/source/drivers/staging/media/bcm2048/radio-bcm2048.c#L311 |
| 22:13.10 | *** join/#maemo phlixi_ (~phlixi@ppp-88-217-41-170.dynamic.mnet-online.de) |
| 22:13.41 | DocScrutinizer05 | ds3: you could try what the bcm2048 can get forced resp "overclocked" (literally) into, by patching the driver, I guess |
| 22:14.15 | *** join/#maemo frals (~frals@Maemo/community/contributor/frals) |
| 22:14.27 | DocScrutinizer05 | but I wouldn't hold my breath to see it doing anything >108 as specified in that dadashit |
| 22:18.54 | *** join/#maemo Natch (~Natch@h-155-122.a444.priv.bahnhof.se) |
| 22:19.05 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 22:28.18 | ds3 | *nod* |
| 22:30.43 | APic | How do i run Andorid-Apps without Dual-Boot, but inside Maemo? |
| 22:30.49 | APic | QEMU? |
| 22:30.56 | APic | Or is there a seminative Dalvik-VM? |
| 22:31.06 | Sicelo | no |
| 22:32.23 | Sicelo | there is/was apkenv .. didn't run all android applications. i never got it to work myself |
| 22:34.29 | DocScrutinizer05 | hmm, what was that latest shit for android emu? |
| 22:34.59 | Sicelo | on N900? |
| 22:36.30 | DocScrutinizer05 | Shashlik |
| 22:36.40 | DocScrutinizer05 | https://www.pyra-handheld.com/wiki/index.php?title=Comparison_Chart |
| 22:36.49 | DocScrutinizer05 | all I know about that |
| 22:37.29 | DocScrutinizer05 | http://www.shashlik.io/ |
| 22:38.51 | DocScrutinizer05 | APic: why qemu? it's the same processor |
| 22:39.03 | DocScrutinizer05 | at least could |
| 22:40.42 | APic | DocScrutinizer05: I thought maybe QEMU could already run Dalvik-Code |
| 22:40.46 | APic | But probably not |
| 22:40.54 | APic | So yes, i can just compile the Dalvik VM for N900 |
| 22:41.07 | DocScrutinizer05 | see shashlik |
| 22:41.10 | APic | Thanks! |
| 22:41.16 | DocScrutinizer05 | sounds reasonably easy |
| 22:42.16 | DocScrutinizer05 | hmm, they mention qemu too |
| 22:43.44 | DocScrutinizer05 | sorry I have no clue, never touched android |
| 22:44.12 | DocScrutinizer05 | ooh wait, I touch it when I pick up my gf's phone |
| 22:44.42 | ds3 | did you instantly slam it down on the ground in disgust? |
| 22:51.22 | sunshavi | lol: My son got one on a contest; pretty nice hw cmp to my n800 |
| 22:51.30 | sunshavi | multitouch |
| 22:51.39 | sunshavi | awfull battery life |
| 22:53.41 | sunshavi | nice screen again cmp to my n800 (on sunlight specially) |
| 22:56.12 | ds3 | remove the google crap and the battery life will improve dramatically |
| 22:56.26 | ds3 | Google Play Services is the energy hog |
| 22:57.04 | DocScrutinizer05 | ds3: nope, actually I recommended the particular phone when she asked what to get |
| 22:57.46 | sunshavi | any command line to rm it quickly, or just gui based? |
| 22:57.53 | DocScrutinizer05 | well, actually first I gave her my hooker800 |
| 22:58.12 | DocScrutinizer05 | which she killed - maybe *she* slammed it into a wall ;-) |
| 22:59.41 | DocScrutinizer05 | cmd line? on android? welllll.... I heard there allegedly is a way to get that |
| 23:01.35 | DocScrutinizer05 | believe it or not, she killed the USB jack on that SG thing |
| 23:01.52 | DocScrutinizer05 | so it's obviously not a N900 specific problem |
| 23:03.41 | sunshavi | DocScrutinizer05, yes adb shell gives you a nice terminal |
| 23:03.58 | DocScrutinizer05 | seems people with low tech affinity tend to now waste a millisecond bothering about mechanical threats to plugs |
| 23:04.16 | DocScrutinizer05 | s/ now / not / |
| 23:05.08 | DocScrutinizer05 | she's relentlessly bending the USB plug up or down until the thing starts charging |
| 23:05.37 | sunshavi | DocScrutinizer05: hooker800=n800? |
| 23:05.47 | DocScrutinizer05 | I won't even try to teach her about the negative effects of that |
| 23:06.13 | DocScrutinizer05 | hooker = (spanish) lumia |
| 23:06.44 | DocScrutinizer05 | Nokia sent me one, like all of the N9 owners |
| 23:07.16 | sunshavi | DocScrutinizer05: thanks 4 the info. Btw i am an n9 owner where is my hooker? |
| 23:07.54 | DocScrutinizer05 | obviously they were *soooo* proud of the N9 bastard |
| 23:08.36 | DocScrutinizer05 | I guess they sent them to all who received a N9 devel device |
| 23:08.44 | sunshavi | N9: nice thing have multitouch, I am too lazy 4 having another scratchbox rootstrap, 4 experimenting with it |
| 23:09.33 | DocScrutinizer05 | well, my N9 died during disassembling it to rip out its secrets |
| 23:10.18 | DocScrutinizer05 | was well worth it, the reward was 1GB RAM PoP chips for Neo900 |
| 23:10.30 | sunshavi | lol, my is still working. I use it as a camera. |
| 23:11.01 | DocScrutinizer05 | yeah, it's a bit of a pity, the N9 was a nice device, despite the Aegis mess and all |
| 23:11.03 | sunshavi | n900 camera sucks. like 8 seconds for taking a second pic. I can't stand it |
| 23:11.17 | DocScrutinizer05 | indeed |
| 23:11.33 | sunshavi | we can have whatever that has linux inside, that's the reason my n800 still rocks |
| 23:11.38 | DocScrutinizer05 | however that's a software limitation I'd think |
| 23:12.17 | sunshavi | btw: n800 has better response as a bluetooth access point than n900, what's the reason for that |
| 23:12.20 | sunshavi | ? |
| 23:12.50 | DocScrutinizer05 | if the camera-ui would allocate more ram to buffer multiple pictures and write them to storage while already taking next one, this would feel way more snappy |
| 23:12.54 | sunshavi | connecting to an n900 (bluetooth access point) takes 10 seconds more than to an n800 bluetooth acess point |
| 23:13.15 | DocScrutinizer05 | BT access point? wth is that? |
| 23:13.33 | sunshavi | is the best use I have gave to my n800 |
| 23:14.02 | DocScrutinizer05 | nfc, never heard of it |
| 23:14.19 | sunshavi | imagine droids being feeded internet by the n800. It is like a cavern man feeding an industrial man |
| 23:14.38 | DocScrutinizer05 | you lost me |
| 23:15.10 | DocScrutinizer05 | ~bt-pan |
| 23:15.15 | DocScrutinizer05 | hmm |
| 23:15.29 | sunshavi | https://wiki.maemo.org/Bluetooth_PAN |
| 23:15.31 | DocScrutinizer05 | ~listkeys maemo*pan |
| 23:15.41 | DocScrutinizer05 | ~pan |
| 23:15.41 | infobot | i heard pan is https://wiki.maemo.org/Bluetooth_PAN |
| 23:15.46 | sunshavi | yes. that's the answer |
| 23:16.09 | DocScrutinizer05 | never heard anybody calling that an access point |
| 23:16.37 | DocScrutinizer05 | it's rather a form of tethering in my book |
| 23:17.00 | sunshavi | https://wiki.maemo.org/Bluetooth_PAN |
| 23:17.16 | sunshavi | s/https://wiki.maemo.org/Bluetooth_PAN/https://www.raspberrypi.org/forums/viewtopic.php?t=57529&p=466691/ |
| 23:17.58 | sunshavi | it is a more informal way of calling the PAN or NAP |
| 23:18.24 | sunshavi | hey infobot did not replace my urls |
| 23:18.49 | sunshavi | perhaps my urls need to be scaped |
| 23:19.09 | sunshavi | s/scaped/escaped/ |
| 23:20.02 | *** join/#maemo freemangordon (~ivo@46.249.74.23) |
| 23:24.48 | DocScrutinizer05 | maybe simply posting the right url instead of trying to replace it while it contains delimiters/ would have been the smarter idea ;-) |
| 23:25.42 | DocScrutinizer05 | infobot's sed function isn't, it's a simple strcmp based replacement without any flexibility |
| 23:26.08 | sunshavi | ok, brb on 3h from now. |
| 23:26.13 | DocScrutinizer05 | it however understands s///g |
| 23:28.05 | DocScrutinizer05 | regarding N800 being faster: I guess it has less gear to handle all different scenarios of internet connectivity |
| 23:29.02 | DocScrutinizer05 | and for sure it has a different BT chipset and firmware |
| 23:30.03 | DocScrutinizer05 | recalls tethering his N810 to a windows smartphone, to do mobile IRC |
| 23:30.30 | DocScrutinizer05 | dunno what been wrong with that siolution in the end |
| 23:31.04 | DocScrutinizer05 | prolly just that windows smartphone alone |
| 23:41.28 | DocScrutinizer05 | idly wonders what's the rationale to use an N800 to make an android smartphone |
| 23:41.48 | DocScrutinizer05 | acces the internet |
