| *** krnlyng <krnlyng!~liar@77.117.11.111.wireless.dyn.drei.com> has quit IRC (Ping timeout: 258 seconds) | 01:25 | |
| *** krnlyng <krnlyng!~liar@77.116.104.144.wireless.dyn.drei.com> has joined #sfdroid | 01:38 | |
| *** ChanServ sets mode: +o krnlyng | 01:38 | |
| *** horuxan <horuxan!~horuxanxx@201.46.181.44> has quit IRC (Read error: Connection reset by peer) | 02:18 | |
| *** NotKit <NotKit!~nekit@95-83-61-209.saransk.ru> has joined #sfdroid | 04:11 | |
| *** horuxan <horuxan!~horuxanxx@201.46.181.44> has joined #sfdroid | 04:15 | |
| *** TheKit <TheKit!~nekit@95-83-51-132.saransk.ru> has quit IRC (Ping timeout: 268 seconds) | 04:15 | |
| *** krnlyng|mobile_ <krnlyng|mobile_!~sailfish@213162068208.public.t-mobile.at> has quit IRC (Ping timeout: 260 seconds) | 06:57 | |
| *** NeKit <NeKit!~nekit@188.162.51.177> has joined #sfdroid | 06:58 | |
| *** NeKit <NeKit!~nekit@188.162.51.177> has quit IRC (Ping timeout: 248 seconds) | 07:52 | |
| *** locusf_ is now known as locusf | 07:53 | |
| *** NeKit <NeKit!~nekit@188.162.51.177> has joined #sfdroid | 07:56 | |
| *** baddea <baddea!059ca7d5@gateway/web/cgi-irc/kiwiirc.com/ip.5.156.167.213> has joined #sfdroid | 08:00 | |
| *** rinigus <rinigus!~rinigus@kybi.ioc.ee> has joined #sfdroid | 08:26 | |
| *** baddea <baddea!059ca7d5@gateway/web/cgi-irc/kiwiirc.com/ip.5.156.167.213> has quit IRC (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) | 08:27 | |
| *** NeKit <NeKit!~nekit@188.162.51.177> has quit IRC (Read error: Connection reset by peer) | 08:56 | |
| *** krnlyng|mobile_ <krnlyng|mobile_!~sailfish@213162068201.public.t-mobile.at> has joined #sfdroid | 11:17 | |
| *** krnlyng|mobile_ <krnlyng|mobile_!~sailfish@213162068201.public.t-mobile.at> has quit IRC (Ping timeout: 256 seconds) | 11:44 | |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068163.public.t-mobile.at> has joined #sfdroid | 12:06 | |
| entil | krnlyng: I have no idea how to start looking even :( restarted with init.sfdroid.rc enabled and there's nothing related to surfaceflinger in logcat output | 12:06 |
|---|---|---|
| mal | entil: I rememver having some strange issue that I needed to manually start surfaceflinger or something to get it working | 12:08 |
| entil | [22:28] <@krnlyng> entil: try killall surfaceflinger zygote main servicemanager | 12:08 |
| entil | [22:28] <@krnlyng> entil: and if that helps try and figure out a proper solution for the problem :D | 12:08 |
| entil | [22:28] < entil> zygote: no process found | 12:08 |
| entil | that's still what happens to me | 12:08 |
| entil | [22:28] <@krnlyng> thats fine | 12:08 |
| entil | [22:28] < entil> the screen went black | 12:08 |
| entil | the "best" "results" I get | 12:08 |
| entil | mal: does your sfdroid work so well you can actually use eg. whatsapp on it? | 12:09 |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068163.public.t-mobile.at> has quit IRC (Ping timeout: 265 seconds) | 12:11 | |
| mal | entil: never tried to install any apps, just the included ones | 12:21 |
| entil | mal: but you have got it running at some point? | 12:30 |
| entil | apparently you have :P | 12:30 |
| entil | be that as it may, the surfaceflinger process was running | 12:31 |
| entil | guess what I need is some other way of debugging than logcat cuz apparently nothing relevant shows up there | 12:31 |
| mal | getting it running was a matter of randomly killing surfaceflinger, servicemanager and then doing some initialization command | 12:35 |
| entil | maybe krnlyng will know about initialization | 12:41 |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068203.public.t-mobile.at> has joined #sfdroid | 13:25 | |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068203.public.t-mobile.at> has quit IRC (Ping timeout: 248 seconds) | 13:44 | |
| *** rinigus <rinigus!~rinigus@kybi.ioc.ee> has quit IRC (Quit: Leaving) | 15:13 | |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068190.public.t-mobile.at> has joined #sfdroid | 16:03 | |
| krnlyng|mobile | entil: there was a permissions error last time, wasn't there? | 16:13 |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068190.public.t-mobile.at> has quit IRC (Remote host closed the connection) | 16:16 | |
| *** krnlyng|mobile_ <krnlyng|mobile_!~sailfish@213162068142.public.t-mobile.at> has joined #sfdroid | 16:30 | |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068129.public.t-mobile.at> has joined #sfdroid | 16:39 | |
| *** krnlyng|mobile_ <krnlyng|mobile_!~sailfish@213162068142.public.t-mobile.at> has quit IRC (Ping timeout: 260 seconds) | 16:42 | |
| *** nh1402 <nh1402!~Thunderbi@95.148.89.25> has joined #sfdroid | 16:59 | |
| *** krnlyng|mobile <krnlyng|mobile!~sailfish@213162068129.public.t-mobile.at> has quit IRC (Ping timeout: 244 seconds) | 16:59 | |
| entil | krnlyng: I think that was a red herring from journalctl | 16:59 |
| entil | krnlyng: like with nothing better to go for I saw that in journalctl and thought it was relevant | 17:00 |
| krnlyng | entil: i am pretty sure i saw that in the logcat output | 17:20 |
| krnlyng | entil: what would help is a full logcat output... i am sure you already sent one but i was busy sorry. and it's probably expired by now | 17:22 |
| entil | krnlyng: how does logcat actually work? if I start the phone with init.sfdroid.rc enabled, start sfdroid, do a killall on the certain processes _and then_ run logcat, will it capture everything relevant or do I need to set it up somewhere in init to catch everything? | 17:30 |
| krnlyng | entil: if you kill these processes it will capture everything relevant | 17:32 |
| entil | krnlyng: ok, I enabled init.sfdroid.rc and told my phone to reboot | 17:33 |
| entil | actually what I'll do is set logcat to output to a file as soon as I can log in | 17:34 |
| entil | just to be sure | 17:34 |
| entil | krnlyng: http://mjt.nysv.org/scratch/sailfish/logcat-2016-12-06.01.txt | 17:37 |
| entil | krnlyng: there's a lot of text there but it won't expire | 17:37 |
| entil | E/SurfaceFlinger( 697): Permission Denial: can't access SurfaceFlinger pid=1389, uid=1000 # <- that caught me last time | 17:37 |
| entil | caught my eye, that is | 17:37 |
| entil | krnlyng: bear in mind that I may have messed something up while compiling, or something | 17:42 |
| krnlyng | https://android.googlesource.com/platform/frameworks/native/+/2a23184/services/surfaceflinger/SurfaceFlinger.cpp#2199 | 17:42 |
| krnlyng | entil: can you try disabling minisf? | 17:43 |
| entil | what's minisf? | 17:44 |
| entil | and/or how? | 17:44 |
| krnlyng | a mini surfaceflinger service used because of AppOps or something iirc | 17:44 |
| krnlyng | which interferes with surfaceflinger most likely | 17:45 |
| krnlyng | in init.rc add disabled to the minisf service | 17:45 |
| entil | should I comment it out in /init.rc? | 17:45 |
| entil | ok | 17:45 |
| krnlyng | or comment it out | 17:45 |
| entil | rebooting now | 17:45 |
| entil | krnlyng: http://mjt.nysv.org/scratch/sailfish/logcat-2016-12-06.02.txt that's the new run, but I still get a black screen | 17:49 |
| krnlyng | it seems something needs to be in the graphics group and it isn't | 17:51 |
| krnlyng | err uid | 17:51 |
| entil | nemo is there | 17:52 |
| entil | [root@Sailfish nemo]# grep gra /etc/group | 17:52 |
| entil | graphics:x:1003:nemo | 17:52 |
| krnlyng | bootanimation doesn't get permissions | 17:55 |
| krnlyng | as well as system_server | 17:56 |
| krnlyng | TheRealJohnGalt[: didn't you have similar issues? | 17:56 |
| krnlyng | entil: can you try building servicemanager and use it as a replacement for /system/bin/servicemanager? | 18:00 |
| entil | krnlyng: like a debug version? how hard is it to build? cuz I don't have a lot more of computer time today :/ | 18:01 |
| entil | have to be early at work in the morning | 18:01 |
| krnlyng | entil: frameworks/native/cmds/servicemanager | 18:02 |
| krnlyng | entil: mm | 18:02 |
| krnlyng | also comment out miniaf | 18:03 |
| entil | miniaf's easy, commented it out and issued a reboot | 18:05 |
| entil | except I get the invalid unlock code thing :( hold on | 18:06 |
| entil | this might take another reboot or few | 18:06 |
| entil | this is really an annoying bug, and then it sometimes gets stuck on the boot screen and I have to boot it again | 18:09 |
| entil | wtf, it's never been this bad | 18:13 |
| krnlyng | entil: if the android services are starting up booting might take longer | 18:17 |
| entil | krnlyng: http://mjt.nysv.org/scratch/sailfish/logcat-2016-12-06.03.txt | 18:17 |
| entil | the phone finally accepted my security code | 18:17 |
| entil | ^ that link is with miniaf disabled as well | 18:17 |
| krnlyng | sure? | 18:18 |
| krnlyng | E/ServiceManager( 3185): add_service('media.audio_flinger',7) uid=1013 - ALREADY REGISTERED, OVERRIDE | 18:18 |
| krnlyng | wait | 18:18 |
| krnlyng | do you have the mediaserver patches? | 18:18 |
| entil | both miniaf and minisf are disabled | 18:18 |
| entil | frameworks/av/media/mediaserver you mean? | 18:19 |
| entil | https://gist.github.com/mjtorn/6cf8ed8b33fd91b3ffa05e7981b8f769 | 18:20 |
| entil | that's what I build with | 18:20 |
| entil | krnlyng: I'm sure there are no patches there | 18:21 |
| entil | krnlyng: would that be the android_frameworks_av repo? | 18:24 |
| krnlyng | entil: yes | 18:24 |
| entil | krnlyng: whose repos are the best btw?-) I use smurfynet's forks, should I go with that for this as well? | 18:25 |
| entil | asdf, I use the sfdroid forks, I mean | 18:25 |
| krnlyng | entil: sfdroid forks | 18:25 |
| entil | yay | 18:25 |
| krnlyng | mako_12 branch | 18:25 |
| entil | mako_12 for the fairphone2? | 18:26 |
| krnlyng | erm | 18:26 |
| entil | there is an fp2-sibon branch | 18:26 |
| krnlyng | you need to use your base cyanogenmods sources | 18:27 |
| krnlyng | and apply the patches on top | 18:27 |
| entil | I have the aosp sources | 18:28 |
| krnlyng | the mako_12 shall only be used as a reference implementation | 18:28 |
| entil | all this is built with the fp2-sibon branches due to that | 18:28 |
| entil | so my understanding has been that this would work with the aosp as its base | 18:30 |
| krnlyng | entil: you need to be very careful about the base, you need exactly those sources which where used to build the base rom you install | 18:30 |
| krnlyng | entil: because even a slight change can cause weird problems | 18:30 |
| krnlyng | difference* | 18:30 |
| krnlyng | MisterMagister had linker errors ;) | 18:31 |
| krnlyng | (for example) | 18:31 |
| krnlyng | with official cyanogenmod ports it is easy, you just take the build-manifest.xml | 18:31 |
| krnlyng | or if you know which base you're working on you can use another yog7pa or whatever brancht if you're lucky | 18:32 |
| mal | krnlyng: fp2 has nice tags for releases also | 18:32 |
| entil | I have the fairphone open android aosp thing for my branch | 18:32 |
| entil | base* | 18:32 |
| mal | krnlyng: so it's easy to pick the correct release | 18:33 |
| entil | there is of course a chance that the build script will do something wrong with checking out the repos for that | 18:33 |
| entil | it checks out the device branch but if that's drifted beyond where I currently am or somehow become incompatible, that would cause errors | 18:33 |
| entil | but it's 16.10 now, iirc mal said sailfish won't even run with anything older | 18:34 |
| entil | I can reflash that to be sure though | 18:34 |
| mal | it will but gps might be a problem | 18:34 |
| mal | there were some symlinks broken with some android releases | 18:34 |
| mal | entil: next sailfish release for fp2 will be 16.11 based, but the new releases only have bug fixes and should work fine | 18:35 |
| entil | hmm | 18:35 |
| krnlyng | so if you're flashing 16.10 you will need to use the 16.10 as base for sfdroid | 18:36 |
| entil | I think I just noticed that my gits for these may be way old | 18:37 |
| entil | mjt@ishtar:~/src/git_checkouts/fp2/fairphone_os/kernel ((a89df05...))$ git show HEAD | 18:37 |
| entil | Date: Wed Jun 22 08:40:52 2016 +0800 | 18:37 |
| entil | not much poing in doing anything about this until I teach my build script to be sure it's got the correct code | 18:38 |
| entil | ie. it knows to sync the fairphone open stuff correctly | 18:39 |
| mal | it's easy to get the correct version in manifest | 18:40 |
| mal | you can even get the correct manifest by tag | 18:40 |
| entil | which manifest is this now? | 18:40 |
| entil | ok, this is actually quite bad! at least some of these repos use tags, so I should not blindly rely on running repo sync, but checking out the tags | 18:47 |
| entil | at least that's what it looks like when I did a spot check | 18:47 |
| entil | but the github.com/sfdroid/ repos aren't tagged, so I have to assume (and pray to the devil) that the fp2-sibon branch is close enough in sync with the tagged releases from code.fairphone.com | 18:48 |
| mal | entil: assuming you originally got a manifest for a tag it should contain something like this <default remote="origin" revision="refs/tags/FP2-open-16.11.0" dest-branch="fp2-sibon" /> | 18:48 |
| entil | mal: you're losing me here, where would that manifest be? in the fairphone sources? | 18:49 |
| mal | entil: in your case ~/src/git_checkouts/fp2/fairphone_os/.repo/manifest.xml | 18:50 |
| entil | <default remote="origin" revision="fp2-sibon" dest-branch="fp2-sibon" /> | 18:50 |
| mal | so you don't use a tagged release, repo sync will always get the latest for you but the patched repos are based on some tag | 18:51 |
| mal | so that can cause problems | 18:51 |
| entil | besides which the sailfish port will more or less expect a tagged base install | 18:51 |
| entil | judging by two spot checks, the tags are consistent, FP2-open-${version} where version looks like 16.10.0 | 18:52 |
| mal | entil: fp2-sibon always matches the latest tagged release | 18:52 |
| mal | there is no code aded between releases, only after a new release the new code will be added to fp2-sibon and the tagged | 18:53 |
| mal | *then | 18:53 |
| entil | mal: they develop somewhere else and only release here? | 18:53 |
| mal | yes | 18:53 |
| entil | because then I might as well update my base to 16.11 if it would work with my current sailfishos setup | 18:53 |
| mal | they have their internal git and they just push the releases to that public one | 18:53 |
| entil | and forget all this hömpötys about tags and crap | 18:53 |
| mal | entil: I suggest you update now and use the tagged 16.11 | 18:54 |
| mal | that way in the future you won't accidentially break it | 18:54 |
| entil | but be that as it may, `repo sync` will update fp2-sibon so I need to add that to my build script | 18:54 |
| entil | because otherwise I might drift | 18:54 |
| entil | so 1) update the base to 16.11 2) update sailfish for fun 3) patch my build script to check for repository sanity 4) 4.1) rebuild 4.2) repackage 4.3) reinstall sfdroid and see what happens | 18:56 |
| entil | too bad I have to head off now, let's see if I can get back to this tomorrow | 18:56 |
| entil | mal: btw wasn't there an mms problem or something in the latest sailfish port? or is it fixed now? | 18:57 |
| entil | this is the wrong channel for that subject, but I've been holding off on updating | 18:57 |
| entil | and I need to go, thanks for the help, good night, hopefully I can get back to this soon :) -> | 18:57 |
| mal | in the latest devel version that is fixed | 18:58 |
| mal | check here https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_fp2 | 18:58 |
| mal | that will be in the next release I hopefully manage to made within the next few days | 18:58 |
| mal | *make | 18:58 |
| *** rinigus <rinigus!~rinigus@jyri-gw.levikom.ee> has joined #sfdroid | 20:44 | |
| *** nh1402 <nh1402!~Thunderbi@95.148.89.25> has quit IRC (Ping timeout: 268 seconds) | 22:15 | |
| *** rinigus <rinigus!~rinigus@jyri-gw.levikom.ee> has quit IRC (Quit: Leaving) | 22:26 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!