| *** M4rtinK <M4rtinK!~M4rtinK@ip-89-177-124-246.net.upcbroadband.cz> has quit IRC (Ping timeout: 250 seconds) | 00:01 | |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has quit IRC (Quit: leaving) | 00:09 | |
| *** olafh <olafh!~olafh@p5B021E73.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 246 seconds) | 00:35 | |
| *** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has quit IRC (Ping timeout: 255 seconds) | 01:13 | |
| *** Tassadar <Tassadar!~tassadar@ip4-83-240-20-212.cust.nbox.cz> has quit IRC (Ping timeout: 264 seconds) | 01:21 | |
| *** Sfiet_Konstantin <Sfiet_Konstantin!~sk@212-198-218-185.rev.numericable.fr> has quit IRC (Quit: Konversation terminated!) | 01:27 | |
| *** johnnydavey <johnnydavey!~androirc@124.6.181.84> has joined #sailfishos-porters | 01:35 | |
| johnnydavey | good am to everyone | 01:35 |
|---|---|---|
| *** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has joined #sailfishos-porters | 01:36 | |
| johnnydavey | i would like to try sailfishos | 01:36 |
| johnnydavey | how can i port the os in myphone. | 01:37 |
| johnnydavey | myphone is a rebranded cubot s208 | 01:37 |
| *** johnnydavey <johnnydavey!~androirc@124.6.181.84> has quit IRC (Client Quit) | 01:39 | |
| *** iTune <iTune!~PhompAng@ppp-124-122-70-28.revip2.asianet.co.th> has joined #sailfishos-porters | 01:56 | |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has joined #sailfishos-porters | 02:42 | |
| *** RaYmAn <RaYmAn!rayman@rayman.dk> has quit IRC (Ping timeout: 245 seconds) | 04:41 | |
| *** faenil <faenil!~faenil@static.186.47.47.78.clients.your-server.de> has quit IRC (Ping timeout: 245 seconds) | 04:41 | |
| *** faenil <faenil!~faenil@static.186.47.47.78.clients.your-server.de> has joined #sailfishos-porters | 04:41 | |
| *** RaYmAn <RaYmAn!rayman@rayman.dk> has joined #sailfishos-porters | 04:43 | |
| *** RaYmAn is now known as Guest65508 | 04:43 | |
| *** harha <harha!~harha@a91-153-12-92.elisa-laajakaista.fi> has joined #sailfishos-porters | 05:04 | |
| uhhimhere | so anybody know what dalvik turbo is and how you use it? | 05:12 |
| *** trt` <trt`!~androirc@ip70-174-22-208.hr.hr.cox.net> has joined #sailfishos-porters | 05:38 | |
| *** olafh <olafh!~olafh@p5B022663.dip0.t-ipconnect.de> has joined #sailfishos-porters | 05:47 | |
| *** Elephant454 <Elephant454!~matthew@pool-71-107-187-219.lsanca.fios.verizon.net> has joined #sailfishos-porters | 05:49 | |
| Elephant454 | Can someone clear something up for me real quick? What is the difference between CyanogenMod 10.1 and 10.2? | 05:50 |
| *** iTune <iTune!~PhompAng@ppp-124-122-70-28.revip2.asianet.co.th> has quit IRC (Ping timeout: 245 seconds) | 05:54 | |
| *** harha <harha!~harha@a91-153-12-92.elisa-laajakaista.fi> has quit IRC (Quit: Leaving.) | 06:08 | |
| *** iTune <iTune!~PhompAng@ppp-124-122-70-28.revip2.asianet.co.th> has joined #sailfishos-porters | 06:09 | |
| klopsi-u3 | moin | 06:09 |
| locusf | morning | 06:13 |
| Elephant454 | In the porting guide, it says that an Android device supported by CyanogenMod 10.1.x is required. What is the difference between 10.1 and 10.2? I am curious to see if the LG G2 could be ported. | 06:20 |
| tbr | you'd need to ask the CM people what the differences are. | 06:21 |
| tbr | the thing is that the patches are written for 10.1, so they might not apply cleanly → more problems, more work | 06:21 |
| * tbr has recently also seen 11.0 and L based stuff floating around here, not sure how usable | 06:22 | |
| Elephant454 | Ok... I see... That's what I was afraid of. I am facinated by this stuff, but I'm not in a position to be able to actively develop for my phone. I can't risk bricking it. Any idea how I could go about learning more and gaining experience without the threat of a bricked phone over my head? | 06:23 |
| tbr | depends on the definition of "brick" | 06:24 |
| Elephant454 | I'm sorry if it seems like a ridiculous question. I'm not some kid asking for party tricks. I have a passion for Linux and would love to be a part of the porting process... | 06:24 |
| tbr | if you need your phone to work at all times, then you can't develop on it anyway | 06:24 |
| Elephant454 | Of course. I'm willing to go without it for a while. That's a given. | 06:25 |
| tbr | there is no risk difference between 10.1 or 10.2, the difference is that it might be harder to make it work | 06:25 |
| Elephant454 | I can't have no phone for the year and a half between now and when my contract expires. Not having it ever turn on after all possible recovery efforts is my fear. Doing something to the boot partition to render the phone useless... | 06:26 |
| Elephant454 | Alright... | 06:26 |
| tbr | by that you mean a "real" brick, not what today's kids claim a brick | 06:28 |
| Elephant454 | The process as a whole isn't set in stone, though. Right? There are clear risks in using an OS that isn't a finished product. Sorry if these questions aren't very well suited for here. The kind of responses I get on Reddit and XDA are "Well as long as you follow the guides and do what your supposed to, nothing will go wrong." | 06:28 |
| Elephant454 | Precicely. | 06:28 |
| tbr | the classic meaning is: not recoverable from with any reasonable tools | 06:28 |
| tbr | today "phone doesn't boot because battery is empty - It's bricked, LOL!" | 06:29 |
| Elephant454 | Drives me crazy... | 06:29 |
| Elephant454 | "My phone won't turn on, gaiz, halp" | 06:29 |
| Elephant454 | "Oh, it just wasn't charged. Sorry. Thx." | 06:29 |
| tbr | anywoo, if your phone can boot CM and if there is a sensible recovery boot option for it, then you should be fine and risk should be very low | 06:30 |
| tbr | and by sensible I mean something along the lines of that clockworkmod stuff | 06:31 |
| Elephant454 | I should be good to go through the rest of the guide without fear? | 06:31 |
| Elephant454 | Already have a TWRP backup. Willing to do fastboot if necessary. | 06:31 |
| Elephant454 | Or wait... can that even be done on the G2? | 06:32 |
| * tbr isn't familiar with that phone | 06:32 | |
| Elephant454 | LG G2: d800 | 06:33 |
| locusf | hmm if its different from the g3 which has locked bootloader, then it might be doable | 06:33 |
| locusf | remember that following hadk and building the HA layer is just 25% of the work :) | 06:34 |
| Elephant454 | It has a locked bootloader. Recovery and flashing is only accessable through a LOKI exploit. | 06:34 |
| locusf | hmm | 06:35 |
| Elephant454 | Will this present problems of it's own? | 06:35 |
| locusf | not sure | 06:36 |
| locusf | can you flash custom kernel on it? | 06:36 |
| Elephant454 | Trying to remember if I ever have in the past... | 06:36 |
| locusf | cm zip usually does that | 06:37 |
| Elephant454 | I have flashed CM 11 through recovery and run that on there before. | 06:37 |
| locusf | ah and its at&t g2 | 06:38 |
| Elephant454 | Yes | 06:38 |
| tbr | well, if you have a working recovery, then things should be possible | 06:39 |
| Elephant454 | This seemed far-fetched at first, but now I feel very excited by the posibilities... | 06:39 |
| tbr | btw: if there is cm11, then it might be easier to go with the cm11 version of the hybris patches? | 06:39 |
| locusf | yes | 06:39 |
| locusf | not just easier but required | 06:40 |
| locusf | afaik | 06:40 |
| Elephant454 | Hybris? | 06:40 |
| locusf | eg. sailfishos compatibility layer which gives you linux glibc on android libraries | 06:40 |
| locusf | thingamagic | 06:41 |
| Elephant454 | Interesting... | 06:41 |
| Elephant454 | So I would be using the pieces of CM 11 that I would need to port Sailfish as opposed to the CM 10.1 pieces? I haven't read over the rest of the porting guide yet. I wanted to make sure that the CM version wouldn't present a roadblock, first. | 06:44 |
| tbr | if there is no cm10.1 for your phone, then using CM11 as the base is the sensible choice | 06:45 |
| Elephant454 | Ok. Thank you guys so much for your help. I should hit the hay so I can tackle this with a clear head later. I'll let you know how it goes. | 06:46 |
| *** Elephant454 <Elephant454!~matthew@pool-71-107-187-219.lsanca.fios.verizon.net> has quit IRC (Quit: leaving) | 06:46 | |
| uhhimhere | what is dalvik turbo ? | 07:00 |
| locusf | no idea | 07:01 |
| *** tanty_off is now known as tanty | 07:02 | |
| uhhimhere | https://en.wikipedia.org/wiki/Dalvik_Turbo | 07:04 |
| uhhimhere | This article's factual accuracy may be compromised due to out-of-date information. | 07:05 |
| uhhimhere | i guess its a dead thing | 07:05 |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has joined #sailfishos-porters | 07:10 | |
| ruthenianboy | I successfuly build hybris boot and recovery images. THey are both the same in size. When I flashed them to phone, after reboot phone booted into fastboot mode (download mode). | 07:11 |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has quit IRC (Quit: leaving) | 07:19 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has joined #sailfishos-porters | 07:26 | |
| *** ruthenianboy <ruthenianboy!~198811@ip-85.163.158.198.o2inet.sk> has joined #sailfishos-porters | 07:31 | |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has quit IRC (Quit: Leaving) | 07:56 | |
| *** cxl000 <cxl000!~cxl000@c27-253-5-120.brodm4.vic.optusnet.com.au> has joined #sailfishos-porters | 07:58 | |
| *** plfiorini <plfiorini!~plfiorini@net-93-71-167-190.cust.vodafonedsl.it> has quit IRC (Quit: Sto andando via) | 07:59 | |
| *** eleroux <eleroux!~Adium@192.194.199.34> has joined #sailfishos-porters | 08:04 | |
| sledges | ruthenianboy: fastboot boot hybris-recovery.img | 08:10 |
| *** carepack <carepack!~carepack@HSI-KBW-078-042-018-044.hsi3.kabel-badenwuerttemberg.de> has joined #sailfishos-porters | 08:13 | |
| carepack | good morning | 08:13 |
| ruthenianboy | sledges: i flashed it via fastboot flash recovery hybris-recovery.img. Why to boot image via fastboot. Isnt't it supposed to be pernamently flashed in phone? | 08:14 |
| tbr | ruthenianboy: for testing it makes sense to NOT make it permanent... | 08:16 |
| *** alin_ <alin_!~alin@178.167.254.188.threembb.ie> has quit IRC (Quit: Konversation terminated!) | 08:20 | |
| ruthenianboy | Will try and see. Maybe it is really not working and phone is stucked in fastboot instead of booting | 08:21 |
| *** BluesLee <BluesLee!~sailfish@ip-109-41-167-255.web.vodafone.de> has joined #sailfishos-porters | 08:23 | |
| BluesLee | sledges: can you point me to the jolla camera app sources? | 08:24 |
| sledges | BluesLee: what are you up to?;) | 08:26 |
| BluesLee | sledges: or point me to the changes which have been made to get the cam running on the nexus4? | 08:27 |
| sledges | BluesLee: they are in the .ks | 08:27 |
| BluesLee | sledges: i followed the gst0.1 -> gst1.0 discussions on jolla together, it makes no sense to wait | 08:29 |
| sledges | BluesLee: and will work only with android camera HAL v1 | 08:29 |
| sledges | BluesLee: linky? | 08:29 |
| BluesLee | sledges: and what is the current hal version? | 08:29 |
| sledges | BluesLee: depends on device | 08:30 |
| BluesLee | sledges: nexus5 | 08:30 |
| sledges | v2 | 08:30 |
| BluesLee | sledges: any chances to pull sone gst1.0 libraries from ubuntu touch and write a small qt/qml app to take rudimentary cam shots? | 08:31 |
| BluesLee | sledges: is there an overview what is open-source and what not in sfos? | 08:33 |
| sledges | you need to collab with MSameer who's rolling out gst1.0 (they should already be there to compile and natively integrate side-by-side), and then to write the HAL adaptor for gst1.0, hope he can alrady parallelise the effort | 08:33 |
| BluesLee | sledges: he is already delivering gst1.0 with his own camera app, the work has to be done on the hal adaptor i guess | 08:35 |
| sledges | BluesLee: https://wiki.merproject.org/wiki/SailfishOSS | 08:35 |
| sledges | BluesLee: it's not that simple as it sounds | 08:35 |
| sledges | to bundle gst in a separate app, as opposed system-wide, but like i said, you can have gst1.0 libs already on sfos | 08:36 |
| BluesLee | sledges: the introduction of gst1.0 has a big impact on the whole system, thats the reason why it takes so.long | 08:36 |
| sledges | it can stay side-by-side with no side-effects (sic):) | 08:36 |
| BluesLee | as on some desktop distros | 08:36 |
| sledges | as per gst design itself, it's possible | 08:37 |
| BluesLee | sledges: i read an ubuntu touch introduction for devs, parallels to sfos are interesting | 08:38 |
| BluesLee | sledges: is sfos cooperating with the utouch guys to build synergies? | 08:38 |
| sledges | ubuntu had camera's working via compay layer, via which we never took on | 08:39 |
| sledges | *compat | 08:39 |
| *** jerpelea <jerpelea!d5730a62@gateway/web/freenode/ip.213.115.10.98> has joined #sailfishos-porters | 08:45 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has quit IRC (Quit: Leaving.) | 08:56 | |
| *** Guest65508 is now known as RaYmAn | 09:00 | |
| *** plfiorini <plfiorini!~plfiorini@sei.yacme.com> has joined #sailfishos-porters | 09:04 | |
| *** BluesLee_ <BluesLee_!~sailfish@ip-109-41-248-170.web.vodafone.de> has joined #sailfishos-porters | 09:04 | |
| *** BluesLee_ <BluesLee_!~sailfish@ip-109-41-248-170.web.vodafone.de> has quit IRC (Client Quit) | 09:04 | |
| *** BluesLee <BluesLee!~sailfish@ip-109-41-167-255.web.vodafone.de> has quit IRC (Ping timeout: 250 seconds) | 09:05 | |
| *** PhompAng <PhompAng!~PhompAng@ppp-124-122-70-28.revip2.asianet.co.th> has joined #sailfishos-porters | 09:11 | |
| *** iTune <iTune!~PhompAng@ppp-124-122-70-28.revip2.asianet.co.th> has quit IRC (Ping timeout: 252 seconds) | 09:13 | |
| *** BluesLee_ <BluesLee_!~sailfish@ip-109-41-248-170.web.vodafone.de> has joined #sailfishos-porters | 09:16 | |
| *** BluesLee_ <BluesLee_!~sailfish@ip-109-41-248-170.web.vodafone.de> has quit IRC (Client Quit) | 09:17 | |
| *** ruthenianboy <ruthenianboy!~198811@ip-85.163.158.198.o2inet.sk> has quit IRC (Ping timeout: 245 seconds) | 09:39 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has joined #sailfishos-porters | 09:42 | |
| *** gogeta <gogeta!~gogeta@5.90.99.246> has joined #sailfishos-porters | 10:11 | |
| *** beidl_ <beidl_!~quassel@188-22-81-78.adsl.highway.telekom.at> has quit IRC (Read error: Connection reset by peer) | 10:14 | |
| *** piggz <piggz!~piggz@host-80-43-93-242.as13285.net> has joined #sailfishos-porters | 10:14 | |
| *** alboe <alboe!~alboe@dynamic-166.l27.ber.netsign.net> has joined #sailfishos-porters | 10:15 | |
| *** gogeta <gogeta!~gogeta@5.90.99.246> has quit IRC (Ping timeout: 252 seconds) | 10:28 | |
| *** Lipevakala <Lipevakala!~sailfish@85-76-165-133-nat.elisa-mobile.fi> has joined #sailfishos-porters | 10:31 | |
| *** Lipevakala <Lipevakala!~sailfish@85-76-165-133-nat.elisa-mobile.fi> has quit IRC (Ping timeout: 256 seconds) | 10:38 | |
| *** Lipevakala <Lipevakala!~sailfish@85-76-142-132-nat.elisa-mobile.fi> has joined #sailfishos-porters | 10:42 | |
| *** Lipevakala <Lipevakala!~sailfish@85-76-142-132-nat.elisa-mobile.fi> has quit IRC (Client Quit) | 10:44 | |
| *** Lipevakala <Lipevakala!~sailfish@85-76-142-132-nat.elisa-mobile.fi> has joined #sailfishos-porters | 10:45 | |
| *** krnlyng <krnlyng!~liar@83.175.90.24> has quit IRC (Ping timeout: 240 seconds) | 10:49 | |
| mal- | sledges: I was looking at the source code to see if that modification would work or not, I don't see why it would help in my case since in test_hwcomposer.cpp all function calls have HWC_NUM_DISPLAY_TYPES which is also used in hwc.cpp reset-function which was to be patched | 10:54 |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has joined #sailfishos-porters | 10:54 | |
| sledges | mal-: but libhwcomposer.so has other values being passed (so a test for qmlscene would then also be in order) | 10:55 |
| sledges | i.e. qpa-hwcomposer-plugin is sending different values depending on hwc hw version | 10:55 |
| sledges | and those may be also not the only codepaths taken | 10:56 |
| mal- | ok | 10:56 |
| sledges | it is a long shot, but have you got a better plan?;) | 10:56 |
| mal- | no :) | 10:56 |
| sledges | and a shot in the dark too, i'd say ;) | 10:56 |
| sledges | if it fails (or if we want to have test_hwcomposer working), we'll still be looking at that assert | 10:57 |
| sledges | but before that, I'll need to check how test_hwcomposer and test_eglfs(or _fbdev? can't remember now) work on a working UI device, and what env variables they take | 10:57 |
| * sledges afk or a bit | 10:58 | |
| *** carepack <carepack!~carepack@HSI-KBW-078-042-018-044.hsi3.kabel-badenwuerttemberg.de> has quit IRC (Quit: Lost terminal) | 11:05 | |
| *** dr_gogeta86 <dr_gogeta86!~gogeta@2.228.32.65> has quit IRC (Ping timeout: 256 seconds) | 11:12 | |
| *** beidl <beidl!~quassel@188-22-81-78.adsl.highway.telekom.at> has joined #sailfishos-porters | 11:17 | |
| *** iGhost <iGhost!~PhompAng@ppp-124-122-99-19.revip2.asianet.co.th> has joined #sailfishos-porters | 11:21 | |
| *** krnlyng <krnlyng!~liar@83.175.90.24> has joined #sailfishos-porters | 11:22 | |
| *** dr_gogeta86 <dr_gogeta86!~gogeta@151.22.5.65> has joined #sailfishos-porters | 11:24 | |
| *** PhompAng <PhompAng!~PhompAng@ppp-124-122-70-28.revip2.asianet.co.th> has quit IRC (Ping timeout: 252 seconds) | 11:24 | |
| *** beidl <beidl!~quassel@188-22-81-78.adsl.highway.telekom.at> has quit IRC (Ping timeout: 245 seconds) | 11:26 | |
| mal- | sledges: just wondering what is the actual error code in the failure, I only see that there is some error but which one | 11:47 |
| sledges | mal-: strace? | 11:48 |
| *** carepack <carepack!~carepack@HSI-KBW-078-042-018-044.hsi3.kabel-badenwuerttemberg.de> has joined #sailfishos-porters | 11:48 | |
| sledges | or gdb ;) | 11:48 |
| mal- | at least I cannot figure it out from strace | 11:49 |
| mal- | looking at the code, in most failures there should be something in android logs since there are calls to ALOGE | 11:51 |
| mal- | I'll need to look into that this evening | 11:52 |
| *** phdeswer <phdeswer!~phdeswer@91-159-55-220.elisa-laajakaista.fi> has quit IRC (Ping timeout: 252 seconds) | 11:59 | |
| *** birdzhang <birdzhang!~kvirc@223.73.195.97> has joined #sailfishos-porters | 12:00 | |
| *** beidl <beidl!~quassel@188-22-81-78.adsl.highway.telekom.at> has joined #sailfishos-porters | 12:00 | |
| *** birdzhang <birdzhang!~kvirc@223.73.195.97> has left #sailfishos-porters ("Once you know what it is you want to be true, instinct is a very useful device for enabling you to know that it is") | 12:11 | |
| *** zhxt <zhxt!~zhxt@118.244.255.148> has joined #sailfishos-porters | 12:14 | |
| *** zhxt <zhxt!~zhxt@118.244.255.148> has quit IRC (Read error: Connection reset by peer) | 12:17 | |
| *** zhxt <zhxt!~zhxt@118.244.255.148> has joined #sailfishos-porters | 12:17 | |
| *** phdeswer <phdeswer!~phdeswer@2001:998:2a:dead:6267:20ff:fe47:e16c> has joined #sailfishos-porters | 12:38 | |
| vakkov | Developer Taixzo needs a Jolla phone to port his Google now-like client Saera t Sailfish. https://www.indiegogo.com/projects/supporting-the-development-of-saera-on-sailfishos | 12:42 |
| *** cmazieri <cmazieri!~kvirc@gate-tx3.freescale.com> has joined #sailfishos-porters | 12:45 | |
| *** harha1 <harha1!~harha@192.194.199.34> has joined #sailfishos-porters | 13:03 | |
| *** phdeswer <phdeswer!~phdeswer@2001:998:2a:dead:6267:20ff:fe47:e16c> has quit IRC (Ping timeout: 250 seconds) | 13:04 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has quit IRC (Ping timeout: 250 seconds) | 13:06 | |
| *** Tassadar <Tassadar!~tassadar@ip4-83-240-20-212.cust.nbox.cz> has joined #sailfishos-porters | 13:50 | |
| *** zhxt <zhxt!~zhxt@118.244.255.148> has quit IRC (Quit: Konversation terminated!) | 13:50 | |
| *** phdeswer <phdeswer!~phdeswer@91-159-55-220.elisa-laajakaista.fi> has joined #sailfishos-porters | 13:52 | |
| *** zhxt <zhxt!~zhxt@118.244.255.148> has joined #sailfishos-porters | 13:54 | |
| *** trt` <trt`!~androirc@ip70-174-22-208.hr.hr.cox.net> has quit IRC (Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )) | 13:55 | |
| *** trt` <trt`!~trt@ip70-174-22-208.hr.hr.cox.net> has joined #sailfishos-porters | 13:58 | |
| *** beidl_ <beidl_!~quassel@91-114-202-232.adsl.highway.telekom.at> has joined #sailfishos-porters | 14:06 | |
| *** beidl <beidl!~quassel@188-22-81-78.adsl.highway.telekom.at> has quit IRC (Ping timeout: 246 seconds) | 14:09 | |
| *** harha1 <harha1!~harha@192.194.199.34> has quit IRC (Quit: Leaving.) | 14:10 | |
| *** eleroux <eleroux!~Adium@192.194.199.34> has quit IRC (Quit: Leaving.) | 14:11 | |
| *** zhxt <zhxt!~zhxt@118.244.255.148> has quit IRC (Quit: Konversation terminated!) | 14:21 | |
| *** zanac <zanac!~stevel@S01060019d19187c9.cg.shawcable.net> has joined #sailfishos-porters | 14:45 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has joined #sailfishos-porters | 15:12 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has quit IRC (Ping timeout: 250 seconds) | 15:23 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has joined #sailfishos-porters | 15:26 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has quit IRC (Ping timeout: 245 seconds) | 15:33 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has joined #sailfishos-porters | 15:36 | |
| *** zama <zama!~zama@unaffiliated/stryx/x-3871776> has quit IRC (Ping timeout: 245 seconds) | 15:39 | |
| *** zama <zama!~zama@unaffiliated/stryx/x-3871776> has joined #sailfishos-porters | 15:41 | |
| *** Lipevakala <Lipevakala!~sailfish@85-76-142-132-nat.elisa-mobile.fi> has quit IRC (Ping timeout: 250 seconds) | 15:55 | |
| *** Lipevakala_ <Lipevakala_!~sailfish@85-76-21-43-nat.elisa-mobile.fi> has joined #sailfishos-porters | 15:55 | |
| *** harha <harha!~harha@mobile-internet-bcee07-8.dhcp.inet.fi> has quit IRC (Quit: Leaving.) | 15:59 | |
| *** Lipevakala <Lipevakala!~sailfish@85-76-47-30-nat.elisa-mobile.fi> has joined #sailfishos-porters | 16:00 | |
| *** Lipevakala_ <Lipevakala_!~sailfish@85-76-21-43-nat.elisa-mobile.fi> has quit IRC (Ping timeout: 256 seconds) | 16:02 | |
| *** jerpelea <jerpelea!d5730a62@gateway/web/freenode/ip.213.115.10.98> has quit IRC (Ping timeout: 246 seconds) | 16:21 | |
| *** Tassadar <Tassadar!~tassadar@ip4-83-240-20-212.cust.nbox.cz> has quit IRC (Ping timeout: 240 seconds) | 16:24 | |
| *** arcean <arcean!~arcean@aafr222.neoplus.adsl.tpnet.pl> has joined #sailfishos-porters | 16:37 | |
| *** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has quit IRC (Ping timeout: 245 seconds) | 16:48 | |
| *** plfiorini <plfiorini!~plfiorini@sei.yacme.com> has quit IRC (Quit: Sto andando via) | 17:01 | |
| *** vakkov <vakkov!~vakkov@134.83.207.29> has joined #sailfishos-porters | 17:01 | |
| *** tanty is now known as tanty_off | 17:02 | |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has joined #sailfishos-porters | 17:07 | |
| ruthenianboy | Do someone know what's the problem when I am trying to boot via "fastboot boot hybris-recovery.img" and I am getting following error: "FAILED (remote: dtb not found)" ? I think that image was not packed correctly | 17:09 |
| ruthenianboy | Porting journey will be very complicated for me as I see... | 17:11 |
| sledges | your boot.img should be made via these commands: https://github.com/CyanogenMod/android_device_lge_w7/blob/cm-11.0/mkbootimg.mk | 17:13 |
| sledges | or it can be as simple as http://pastie.org/9884259 | 17:13 |
| sledges | ruthenianboy: see how hybris-*.img are made: https://github.com/mer-hybris/hybris-boot/blob/hybris-10.1/Android.mk | 17:13 |
| sledges | and adjust accordingly. to be sure, doublecheck with how the boot.img from cm.zip looks like via split_bootimg command in mersdk | 17:14 |
| *** carepack <carepack!~carepack@HSI-KBW-078-042-018-044.hsi3.kabel-badenwuerttemberg.de> has quit IRC (Quit: Lost terminal) | 17:15 | |
| locusf | yeah the dtb is apparently vital for some devices | 17:25 |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has quit IRC (Ping timeout: 246 seconds) | 17:31 | |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has joined #sailfishos-porters | 17:34 | |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has quit IRC (Ping timeout: 255 seconds) | 17:34 | |
| ruthenianboy | unfortunatelly this is to much complicated for me. I do not know where to place that files | 17:35 |
| *** alin <alin!~alin@opensuse/member/ealin> has joined #sailfishos-porters | 17:38 | |
| *** gogeta <gogeta!~gogeta@net-188-217-76-5.cust.vodafonedsl.it> has joined #sailfishos-porters | 17:39 | |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has joined #sailfishos-porters | 17:40 | |
| ruthenianboy | can I make image manually from files in out/target/product/w7? There is kernel, initrd, etc. | 17:41 |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has quit IRC (Max SendQ exceeded) | 17:43 | |
| *** iGhost <iGhost!~PhompAng@ppp-124-122-99-19.revip2.asianet.co.th> has quit IRC (Ping timeout: 244 seconds) | 17:43 | |
| sledges | ruthenianboy: just split_bootimg is your friend | 17:44 |
| sledges | use it with boot.img from your cm.zip, and it will give you cmdline how to re-create it (substituting kernel, initrd and dt) | 17:45 |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has joined #sailfishos-porters | 17:46 | |
| sledges | ruthenianboy: where it says "second", that means device tree image | 17:46 |
| *** gogeta <gogeta!~gogeta@net-188-217-76-5.cust.vodafonedsl.it> has quit IRC (Ping timeout: 264 seconds) | 17:48 | |
| ruthenianboy | generated files are not usable. They do not have device tree (I tried to boot kernel and initrd directly). I must recompile everything from begining. How can split_bootimg help me? | 17:51 |
| sledges | 19:45 < sledges> use it with boot.img from your cm.zip | 17:52 |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has quit IRC (Ping timeout: 252 seconds) | 17:52 | |
| sledges | your device tree file should reside after kernel build: https://github.com/CyanogenMod/android_device_lge_w7/blob/cm-11.0/mkbootimg.mk#L13 | 17:53 |
| sledges | is the missing piece | 17:53 |
| *** piggz <piggz!~piggz@host-80-43-93-242.as13285.net> has quit IRC (Ping timeout: 264 seconds) | 17:53 | |
| *** uhhimhere <uhhimhere!~uhhimhere@1.9.98.123> has joined #sailfishos-porters | 17:54 | |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has quit IRC (Ping timeout: 246 seconds) | 18:00 | |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has joined #sailfishos-porters | 18:16 | |
| ruthenianboy | I used split_bootimg to see how to build image. Then I used mkbootimg with parameters from split_bootimg to build boot.img but file again do not contain dt. | 18:17 |
| locusf | ruthenianboy: whats your device? | 18:18 |
| locusf | mkqcdbootimage usually takes in the dtbs | 18:18 |
| *** trt` <trt`!~trt@ip70-174-22-208.hr.hr.cox.net> has quit IRC (Ping timeout: 252 seconds) | 18:18 | |
| ruthenianboy | lge w7 - LG L90 D405n | 18:19 |
| *** plfiorini <plfiorini!~plfiorini@net-93-71-167-190.cust.vodafonedsl.it> has joined #sailfishos-porters | 18:24 | |
| *** trt` <trt`!~trt@173.209.212.240> has joined #sailfishos-porters | 18:24 | |
| *** plfiorini <plfiorini!~plfiorini@net-93-71-167-190.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 18:24 | |
| *** alin <alin!~alin@opensuse/member/ealin> has quit IRC (Quit: Konversation terminated!) | 18:26 | |
| *** plfiorini <plfiorini!~plfiorini@net-93-71-167-190.cust.vodafonedsl.it> has joined #sailfishos-porters | 18:30 | |
| *** alboe <alboe!~alboe@dynamic-166.l27.ber.netsign.net> has quit IRC (Quit: :tuiQ) | 18:35 | |
| *** trt__ <trt__!~trt@173.209.211.148> has joined #sailfishos-porters | 18:36 | |
| *** trt` <trt`!~trt@173.209.212.240> has quit IRC (Ping timeout: 252 seconds) | 18:38 | |
| locusf | ruthenianboy: https://github.com/xiaolu/mkbootimg_tools <- try this | 18:38 |
| *** trt__ is now known as trt` | 18:38 | |
| ruthenianboy | locusf: that tools are working, bootable img was created | 18:55 |
| *** Tassadar <Tassadar!~tassadar@ip4-83-240-20-212.cust.nbox.cz> has joined #sailfishos-porters | 18:55 | |
| *** trt` <trt`!~trt@173.209.211.148> has quit IRC (Ping timeout: 250 seconds) | 18:57 | |
| *** trt` <trt`!~trt@ip70-174-22-208.hr.hr.cox.net> has joined #sailfishos-porters | 18:58 | |
| ruthenianboy | i flashed newly created boot.img to boot. Now when I power on the phone, LG logo appear and aftere some time it will boot to recovery menu. It is correct behavior? | 19:05 |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has quit IRC (Quit: leaving) | 19:06 | |
| *** CardenalJimenez <CardenalJimenez!~CardenalJ@2a01:e35:2422:60d0:b054:75a6:4b11:8364> has joined #sailfishos-porters | 19:08 | |
| *** piggz <piggz!~piggz@host-80-43-93-242.as13285.net> has joined #sailfishos-porters | 19:19 | |
| mal- | sledges: I might have found the actual error in hwc.cpp, the condition is otherwise ok, but it has <= instead of < | 19:23 |
| mal- | in other places, such as the one that was patched before, it is the correct < | 19:24 |
| sledges | mal-: oh cool, in the for(;;) loop? | 19:25 |
| mal- | yes | 19:25 |
| mal- | since I could not see any errors in log there is no other way for it to fail | 19:25 |
| mal- | now I just need to compile a new version of the library | 19:28 |
| *** zanac <zanac!~stevel@S01060019d19187c9.cg.shawcable.net> has quit IRC (Remote host closed the connection) | 19:28 | |
| mal- | that is not the only place where there is similar mistake, but in the other place it does not cause any problems, it hwc_set the count goes 0->3 but in the other place it goes 3->0 and therefore the final handled situation is actually successful | 19:31 |
| sledges | but if 3 also get's in the loop (when it should be max=3-1=2) | 19:32 |
| sledges | on the first reversing iteration | 19:32 |
| mal- | yes, for other devices it is like that | 19:33 |
| mal- | for msm8960 and msm8974 at least | 19:33 |
| mal- | those have for (int32_t i = numDisplays - 1; i >= 0; i--) | 19:34 |
| mal- | I have for (int32_t i = numDisplays; i >= 0; i--) | 19:35 |
| sledges | so it's 2->0, all good;) | 19:35 |
| sledges | yep, you are missing - 1 | 19:35 |
| mal- | but 3->0 also works in that case, even though it's incorrect | 19:35 |
| sledges | does it call set() inside the loop? | 19:35 |
| mal- | no, set is called separately | 19:36 |
| mal- | that other error is in hwc_prepare | 19:36 |
| sledges | probably non critical on MAX | 19:36 |
| sledges | (when it should be MAX-1) | 19:37 |
| mal- | https://github.com/CyanogenMod/android_hardware_qcom_display-caf/blob/cm-11.0/libhwcomposer/hwc.cpp#L282 | 19:37 |
| mal- | there it is | 19:37 |
| mal- | the error is critical only when going 0->3 | 19:38 |
| sledges | on the same structs? | 19:39 |
| sledges | i mean maybe displays is allocated [MAX>numDisplays] ? | 19:39 |
| *** Nekron_ <Nekron_!~nekron@p5B3F03C7.dip0.t-ipconnect.de> has joined #sailfishos-porters | 19:39 | |
| mal- | what do you mean? | 19:40 |
| sledges | hwc_display_contents_1_t** displays is allocated somewhere as displays[NUM_DISPLAYS] | 19:40 |
| *** Nokius_ <Nokius_!~Nokius@p5DDB590C.dip0.t-ipconnect.de> has joined #sailfishos-porters | 19:40 | |
| sledges | and NUM_DISPLAYS is 4 | 19:40 |
| sledges | and numDisplays is passed as 3 | 19:40 |
| sledges | that's why things don't blow up | 19:40 |
| sledges | with displays structure | 19:40 |
| sledges | and with _prepare | 19:40 |
| sledges | but blowsup elsewhere | 19:41 |
| sledges | ^ a speculation | 19:41 |
| mal- | look at the switch after that place | 19:41 |
| mal- | it only has 3 options | 19:41 |
| mal- | 0,1,2 | 19:41 |
| sledges | and it's strict 1:1 mapping? | 19:41 |
| mal- | yes | 19:42 |
| sledges | and it never returns -EINVAL? | 19:42 |
| sledges | so maybe the alloc is filled with zeroes, and it goes 0,2,1,0 | 19:42 |
| mal- | it does in hwc_set, that is the condition I get | 19:42 |
| mal- | that causes the assert to fail | 19:43 |
| sledges | yes, we're talking about the loop which doesn't blow up | 19:43 |
| *** Nokius <Nokius!~Nokius@p5DDB561B.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 240 seconds) | 19:43 | |
| sledges | but there's nothing better to do now than to debug;) | 19:44 |
| mal- | in the hwc_prepare, the loop just continues even after failure and since the next loops are ok, it eventually return success | 19:44 |
| sledges | mal-: well spotted, ofc!:) | 19:45 |
| locusf | I'm getting this error while compiling libhybris for lollipop: nativewindowbase.cpp:10:23: fatal error: sync/sync.h: No such file or directory | 19:47 |
| mal- | we'll see what problems I run into after I fix this | 19:47 |
| sledges | Stskeeps: ^^ | 19:47 |
| locusf | sledges: hes off to bed, just asked him | 19:47 |
| *** piggz <piggz!~piggz@host-80-43-93-242.as13285.net> has quit IRC (Quit: Konversation terminated!) | 19:48 | |
| *** piggz <piggz!~piggz@host-80-43-93-242.as13285.net> has joined #sailfishos-porters | 19:48 | |
| sledges | locusf:p | 19:48 |
| locusf | I've got system/core/libsync/sync/sync.h but its not picked up to droid-headers | 19:49 |
| sledges | locusf: how does a 10.1/11.0 tree looks like wrt? | 19:49 |
| locusf | I don't have one right now | 19:49 |
| *** M4rtinK <M4rtinK!~M4rtinK@ip-89-177-124-246.net.upcbroadband.cz> has joined #sailfishos-porters | 19:51 | |
| *** SamZaNemesis <SamZaNemesis!~Sam@189.59.135.129> has joined #sailfishos-porters | 19:53 | |
| locusf | ah it has changed location | 19:54 |
| locusf | extract-headers.sh expects it to be in system/core/include/sync | 19:54 |
| mal- | sledges: the easy way for me to see what happens after fixing that problme would be to just remove the assert from test_hwcomposer, since that error is really not fatal | 19:54 |
| sledges | mal-: go ahead | 19:55 |
| mal- | I'll of course fix the real cause later but it might take a while to compile it | 19:56 |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has joined #sailfishos-porters | 19:56 | |
| locusf | aand we don'tt have bionic headers either | 19:57 |
| locusf | and I really don't know if your bionic is patched | 19:57 |
| locusf | surely some work tomorrow for me then | 19:57 |
| locusf | laters, nigh | 19:57 |
| *** saidinesh5 <saidinesh5!~quassel@static.49.20.251.148.clients.your-server.de> has quit IRC (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) | 19:57 | |
| locusf | +t | 19:57 |
| sledges | your?,) | 19:57 |
| *** saidinesh5 <saidinesh5!~quassel@static.49.20.251.148.clients.your-server.de> has joined #sailfishos-porters | 19:57 | |
| locusf | sonys | 19:58 |
| locusf | aosp | 19:58 |
| sledges | bionic patches is part of hadk, not aosp:) | 19:58 |
| *** vakkov <vakkov!~vakkov@134.83.207.29> has quit IRC (Ping timeout: 265 seconds) | 19:59 | |
| sledges | ruthenianboy: the correct behaviour is when you see same events that happen via fastboot boot boot.img and your re-created boot.img duplicate | 19:59 |
| ruthenianboy | Looks like my attempt to build hybris boot was not successful. I think it something to do with local manifest. I do not know why it did not created proper image (without dtb). | 19:59 |
| sledges | ruthenianboy: the time-consuming method would be to build cm on your own | 20:00 |
| sledges | in a separate tree | 20:00 |
| sledges | your device is not officially supported on cm wiki | 20:01 |
| locusf | sledges: well won't we still use aosp bionic? | 20:01 |
| locusf | it is compiled like the rest of the system | 20:01 |
| sledges | locusf: yes, but if you checked out aosp, surely it wouldn't have bionic patches out of the box | 20:01 |
| sledges | for mer | 20:01 |
| locusf | yes sure | 20:02 |
| sledges | gninight:) | 20:02 |
| ruthenianboy | But it is included in cyanogenmod git as android_device_lge_w7. I will try to repack original boot.img from phone with kernel generated in step 5.2 to see if kernel is functional. Or I will try to use kernel and device source provided from LG on their site. I am in impasse now as my knowledge is limited. Any other ideas where I can start looking? Thanks | 20:05 |
| sledges | ruthenianboy: that's a good try - swapping in and out, given the situation that it's not officially supported cm device (presence of git repos doesn't mean you have instructions to reproduce the build sanely at hand)? | 20:06 |
| sledges | (no question mark:) | 20:06 |
| piggz | is there anything like planet-sailfish ... or just use planet-maemo? | 20:07 |
| piggz | the planet-maemo rss feed is rejected by owncloud news :/ | 20:07 |
| mal- | sledges: it works!!! | 20:08 |
| sledges | mal-: \o/ | 20:08 |
| mal- | there is some nice animation on screen when I run test_hwcomposer | 20:09 |
| sledges | you get picture!? 8D | 20:09 |
| sledges | \\o// rock'n'roll!! \m/ | 20:09 |
| sledges | bloody caf :DDD | 20:09 |
| mal- | indeed :D | 20:09 |
| sledges | EGL_PLATFORM=hwcomposer ? | 20:10 |
| mal- | yes | 20:10 |
| sledges | so, next victim - qmlscene :)) | 20:11 |
| mal- | yes :) | 20:11 |
| sledges | which now might need intervention into hwcomposer.msm*.so... | 20:12 |
| ruthenianboy | sledges: I will try to build CM on my own from lg sources or from existing gits. I still do not understand difference between CM build and step 5.2 HADK. What is the purpose of hybris-boot and hybris-recovery? Hybris-boot contain same kernel but different initrd which provide debug via telnet and modified init script which boot SFOS? | 20:12 |
| sledges | ruthenianboy: hybris-boot contains modified kernel config too, which needs to pass mer-kernel-check | 20:12 |
| mal- | sledges: looking at the qmlscene with HYBRIS_LOGGING_LEVEL=debug, it could be failing in the same place | 20:18 |
| mal- | but it just crashes for some reason | 20:19 |
| sledges | it asks for more | 20:19 |
| sledges | juice;) | 20:19 |
| mal- | in both cases last debug output is EGL hwcomposer_window.cpp:220 (virtual int HWComposerNativeWindow::queueBuffer(BaseNativeWindowBuffer*, int)) | 20:19 |
| mal- | onw I need to look for the source of qmlscene | 20:20 |
| mal- | or whatever is actually implementing HWComposerNativeWindow when you run qmlscene | 20:23 |
| Nokius_ | sledges: did you find a way to get the problem solved? may its find5 time again :) | 20:24 |
| *** Nekron_ <Nekron_!~nekron@p5B3F03C7.dip0.t-ipconnect.de> has quit IRC (Remote host closed the connection) | 20:24 | |
| sledges | Nokius_: patience my friend:)) | 20:25 |
| Nokius_ | sledges: all day long :P | 20:29 |
| Nokius_ | looks like you had similar effect last night | 20:30 |
| *** Sfiet_Konstantin <Sfiet_Konstantin!~sk@212-198-218-185.rev.numericable.fr> has joined #sailfishos-porters | 20:32 | |
| mal- | sledges: I cannot understart why that error could cause segfault, maybe there is something else wrong also | 20:32 |
| Nokius_ | so thats why ask ;) I'm not interested to rush annoy anyone | 20:32 |
| sledges | Nokius_: no worries:) | 20:32 |
| mal- | but still it would quite a coincidence that the crash just happens to happen at the same place | 20:32 |
| *** ruthenianboy <ruthenianboy!~root@chello085216159245.chello.sk> has quit IRC (Ping timeout: 252 seconds) | 20:34 | |
| mal- | hmm, there could be a reason why might segfault, it does access an out-of-bounds access to an array | 20:36 |
| *** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has joined #sailfishos-porters | 20:45 | |
| sledges | mal-: found all sources you needed? | 20:52 |
| mal- | not yet | 20:53 |
| mal- | well, I haven't looked much yet | 20:54 |
| mal- | needed some food | 20:54 |
| sledges | mal-: https://github.com/libhybris/libhybris/blob/master/hybris/egl/platforms/hwcomposer/hwcomposer_window.cpp#L144 | 20:54 |
| mal- | could this "hwc_display_contents_1_t *list = displays[i];" cause a segfault if "i" is too large | 20:55 |
| sledges | trace where displays is alloced | 20:55 |
| mal- | sledges: I knew about that source, but that calls this->present, which was implemented in test_hwcomposer | 20:57 |
| mal- | queueBuffer calls that, and that was the location of the problem | 20:58 |
| mal- | virtual void present(HWComposerNativeWindowBuffer *buffer) | 20:59 |
| mal- | so that has to be implemented somewhere else also | 21:00 |
| sledges | zypper in qt5-qtdeclarative-qmlscene | 21:00 |
| mal- | it seems qt5-qpa-hwcomposer-plugin | 21:00 |
| sledges | qtdeclarative is to look for | 21:00 |
| sledges | or that | 21:01 |
| mal- | there is HWC_PLUGIN_EXPECT_ZERO(err); | 21:01 |
| mal- | so a similar check is done, now I need check what HWC_PLUGIN_EXPECT_ZERO does | 21:01 |
| *** piggz <piggz!~piggz@host-80-43-93-242.as13285.net> has quit IRC (Ping timeout: 256 seconds) | 21:02 | |
| mal- | that should only print a warning, so it never reaches that far, so my guess for the reason of segfault look likely | 21:03 |
| mal- | *looks | 21:03 |
| mal- | actually I'm not sure where it outputs the warning since it calls qWarning | 21:04 |
| mal- | I'll try to compile the fixed hwcomposer tomorrow to see if that fixes things | 21:10 |
| sledges | ok, good progress today | 21:10 |
| sledges | it might boil down to modifying caf bits, but you'll confirm that from a distant approach;) | 21:11 |
| mal- | I'm very pleased with today's progress, thanks a lot | 21:12 |
| sledges | u2! | 21:13 |
| mal- | I was starting to lose hope already with the lack of graphics | 21:13 |
| sledges | we finally dug the tunnel into the rabbit hole of android gpu stack :D | 21:14 |
| sledges | this should've been done 8 months ago, but oh well;p | 21:14 |
| mal- | it was Stskeeps that made the first discovery which enabled all this progress | 21:15 |
| sledges | he gave a push, but i still wonder how test_hwcomposer would look like without QCOM_BSP bits;) | 21:16 |
| mal- | what does that do actually? | 21:17 |
| sledges | ion mem alloc, might be related, might be not (yet) affecting | 21:17 |
| * sledges afk dinner | 21:17 | |
| sledges | as numdisplays has been issue in the past, with flagships like nexus5 | 21:20 |
| mal- | it would be interesting to look at how android uses hwcomposer, since it does not fail with those bugs in hwc.cpp | 21:21 |
| *** Tassadar <Tassadar!~tassadar@ip4-83-240-20-212.cust.nbox.cz> has quit IRC (Ping timeout: 245 seconds) | 21:24 | |
| *** alin <alin!~alin@178.167.254.223.threembb.ie> has joined #sailfishos-porters | 21:35 | |
| *** alin <alin!~alin@178.167.254.223.threembb.ie> has quit IRC (Changing host) | 21:35 | |
| *** alin <alin!~alin@opensuse/member/ealin> has joined #sailfishos-porters | 21:35 | |
| *** Sfiet_Konstantin <Sfiet_Konstantin!~sk@212-198-218-185.rev.numericable.fr> has quit IRC (Quit: Konversation terminated!) | 21:43 | |
| *** piggz <piggz!~piggz@host-80-43-93-242.as13285.net> has joined #sailfishos-porters | 21:44 | |
| alin | sledges: Stskeeps lbt this is funny... http://www.tizenexperts.com/2015/02/russian-federation-help-tizen-sailfish-battle-android-ios/ | 21:44 |
| *** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has quit IRC (Ping timeout: 256 seconds) | 22:01 | |
| *** cxl000 <cxl000!~cxl000@c27-253-5-120.brodm4.vic.optusnet.com.au> has quit IRC (Quit: Leaving) | 22:04 | |
| M4rtinK | armor support :) | 22:11 |
| alin | M4rtinK: yap... intercontinental sailfish... | 22:19 |
| M4rtinK | Nemo Mobile attack submarine! :) | 22:20 |
| alin | M4rtinK: with nuclear battery | 22:25 |
| M4rtinK | "Sailfish Class" would make a nice ship or submarine class :) | 22:26 |
| M4rtinK | OH! http://en.wikipedia.org/wiki/Sailfish-class_submarine | 22:27 |
| M4rtinK | http://en.wikipedia.org/wiki/USS_Sailfish_%28SSR-572%29 | 22:29 |
| sledges | https://www.youtube.com/watch?v=45d5lzzTQlk | 22:30 |
| M4rtinK | Cool! | 22:43 |
| klopsi-u3 | moin | 22:45 |
| sledges | noin | 22:45 |
| klopsi-u3 | hey cool toy | 22:46 |
| alin | sledges: got the tizen phone... | 23:03 |
| alin | blimey... i did not know they can dumb down proper linux to android | 23:04 |
| alin | i wonder if we can put sailfish on it | 23:07 |
| klopsi-u3 | alin: what for example, is dumbed down? | 23:14 |
| alin | no ssh... some adb clone... no software management app... the interface is ugly.... and believe I have very low aesthetical expectections from software | 23:18 |
| alin | all the interface looks like a cheap android clone | 23:19 |
| *** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has joined #sailfishos-porters | 23:24 | |
| klopsi-u3 | meh | 23:47 |
| alin | klopsi-u3: ok apparently there is a way to downlaod other stuff on it | 23:49 |
| alin | and put a better tizen... if supports it... | 23:49 |
| klopsi-u3 | it is the samsung z1? | 23:50 |
| alin | klopsi-u3: yap | 23:50 |
| klopsi-u3 | so jolla has the better UI? | 23:51 |
| alin | klopsi-u3: yap | 23:52 |
| alin | klopsi-u3: ubuntu one is not bad | 23:52 |
| alin | klopsi-u3: anyhow will be a good experience to put the proper tizen on it to see | 23:52 |
| klopsi-u3 | yes i suppose | 23:53 |
| klopsi-u3 | do you work with phones for a job alin?> | 23:54 |
| alin | klopsi-u3: nope | 23:56 |
| alin | klopsi-u3: just curious | 23:57 |
| *** vakkov <vakkov!~vakkov@s3n104.brunel.ac.uk> has quit IRC (Ping timeout: 250 seconds) | 23:57 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!