Monday, 2018-06-18

TAMplus39_Hi, Im trying to fix the autobrightness toggle but i dont have $ANDROID_ROOT/hybris/droid-configs/sparse/usr/share/csd/settings.d02:25
*** zhxt_ is now known as zhxt___02:56
MeowDudeTAMplus39_ : just create the file yourself and fill in the blanks using device specific configurations05:01
MeowDudejust borrow a template file from a nother device's github05:01
MeowDudeI reccomend an up to date device such as the OnePlusX or something, one that is up to date Sailfish OS wise05:01
MeowDudealso seriously, no one has any tips with RILD not starting?05:01
MeowDude!seen r0kk3rz05:07
merbotMeowDude: r0kk3rz was last seen in #sailfishos-porters 18 hours, 28 minutes, and 27 seconds ago: <r0kk3rz> yeah sensor.qcom is a custom service, so make sure its running and check logcat05:07
AndroUser2Hi. There are CyanogenMod 13.0 and LineageOS 14.1 for my device (Xiaomi Redmi 3). Which ROM is better for HADK?09:01
r0kk3rzwhich is better supported for the device?09:04
r0kk3rzeither of those should be fine for the HADK09:04
AndroUser2Lineage is better supported. Thanks.09:06
T4<abhishek_0> AndroUser2 try 14.1 , but i think sailfish for your device already exists09:17
AndroUser2I saw Sailfish for Redmi Note 3 (not Redmi 3). On Mer Wiki there are no Redmi 3.09:19
r0kk3rzwhats its codename?09:20
r0kk3rzdoesnt sound familiar, but its probably not that different to the other xiaomi devices we have09:21
r0kk3rzmost are well working09:21
T4<abhishek_0> AndroUser2 redmi note 3 is kenzo09:22
T4<abhishek_0> not ido09:22
AndroUser2I said about Redmi 3. It is ido. Redmi Note 3 is kenzo. I know it :)09:23
T4<abhishek_0> oh man .. these names... grrrrr09:25
T4<abhishek_0> *facepalm*09:26
r0kk3rzits not as bad as when xiaomi reuses codenames for different devices09:28
r0kk3rzthat gets more confusing09:28
AndroUser2Oh... New Xiaomi devices has a very terrible naming. Redmi 5, Redmi 5A, Redmi Note 5, Redmi Note 5 Pro, Redmi 5 Plus... OMG09:29
tbrthey always had a terrible naming convention09:32
tbrone more reason to just go by code names09:34
MeowDuder0kk3rz: hey I need help debugging rild11:11
MeowDudebased on dmesg, it starts up, spawns /dev/socket/rild, but then for whatever quits and restarts endlessly11:11
MeowDudealso it despawns /dev/socket/rild each time too11:12
malMeowDude: most likely something to do with either firmware not being found or some other android side service failing (like some inter-process communitation service)11:18
MeowDude*same IP*11:18
MeowDudemal: how do I debug or trace it?11:18
MeowDudeI tried strace -p PID but that didn't work11:18
TuringFishMeowDude: CDU?11:19
MeowDudeTuringFish: yes. huh, that's neat.11:19
malMeowDude: you need to look in logcat (and maybe dmesg), you can try to start rild manually with strace but make sure it runs with correct user so there are no permission issues11:20
MeowDudemal: open("/dev/block/platform/omap/omap_hsmmc.0/by-name/radio", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) --- I think this might be it, because that file path is incorrect11:23
MeowDudeits /dev/block/platform/omap_hsmmc.0/radio, not /dev/block/platform/omap/omap_hsmmc.0/radio11:23
malMeowDude: show your /lib/udev/rules.d/998-droid-system.rules11:24
MeowDudemal: I just rebooted after editing fstab.tuna, gimme a sec11:25
MeowDudeoof I didn't mean to ping you with that *facepalm*11:25
malMeowDude: you have fstab on your device?11:25
MeowDudeI added itmyself... which... I actually forgot that it was extra...11:26
malsailfish doesn't use fstab, at least it normally shouldn't11:26
MeowDudeit's supposedly imported by /init.rc, which is what logcat said, so I just satisifed a dependancy. I figured mer mounted everything without it anyway11:27
malit was removed for a reason11:27
malsystemd handles mounts11:27
MeowDudecan I try manually editting systemd?11:28
MeowDudeerm, the mount script?11:28
malkrnlyng: some issue with the new udev rules ^11:29
MeowDudeis it a known issue, and if so, follow up question, is there a known fix?11:29
malMeowDude: pastebin ls -lR /dev/block/11:30
malfix is to figure out what rule breaks11:30
krnlyngMeowDude, did this appear now or was it always like this on this device?11:30
krnlyngi.e. did you have success with that before the new udev rules?11:30
MeowDudekrnlyng: this is a new port device, the first version it has ever ran is
krnlyngi think i know what the issue is. but i need to know if it has always been an issue or if it is new11:31
krnlyngMeowDude, ok so probably always been like that11:32
MeowDudewhat do I do assuming it is new?11:32
MeowDudeis there any use trying out a random patch you know?11:32
malMeowDude: it's just a matter of fixing that file I asked, shouldn't be too difficult11:33
MeowDudeoh great!11:34
MeowDudelet me peep through it to see if I can personally find anything wrong with it11:34
malthe file looks quite complex if you are not used to udev rules11:35
MeowDudeyeah, basic C/C++ I can handle, but this? nah this is mostly gibberish. I didn't see any actual radio/modem related lines though, only one radio line and it was for logs not the actual radio11:35
krnlyngMeowDude, this has nothing to do with radio, it's partition symlinks11:36
malMeowDude: it doesn't have anything that specific, it's just generic rules for handling everything11:36
MeowDudeoh. that makes more sense.11:36
MeowDudewell then the symlinks for the partitions must be goofed. oh wait we already know that sorry...11:37
krnlyngMeowDude, ls -l /sys/devices/platform/omap11:37
krnlyngMeowDude, ls -l /sys/devices/platform/11:37
krnlyngboth please11:37
malMeowDude: these kinds of issue happen occasionally, you are the first one after the new udev rules though11:38
MeowDudeboth in the same paste seperated by a line11:38
MeowDudeodd, when I run "ls" inside /dev/block/platform, the "omap" folder doesn't show up11:40
krnlyngMeowDude, "udevadm info -a /sys/devices/omap" "udevadm info -a /sys/devices/omap/omap_hsmmc.0"11:42
MeowDudedidn't really work11:43
krnlyngMeowDude, same with platform11:44
MeowDudesame exact result11:45
krnlyngMeowDude, "udevadm info -a /sys/devices/platform/omap" "udevadm info -a /sys/devices/platform/omap/omap_hsmmc.0"11:45
MeowDudeha! now we are getting somwhere, give me a second11:46
krnlyngMeowDude, you can use that info to check what's wrong with the udev rules11:47
MeowDudekrnlyng: so just fill in the missing information?11:51
MeowDudehmm it didn't work.11:55
MeowDudemal: I am trying to make sense of these udev rules and I think i am KIND of getting them, basically they allow you to universally deal with multiple device file systems and blocks without needing to make specific device files12:03
MeowDudeso it would seem that by default this udev points to /dev/block/platform/FOLDER/DEVICE/* but mine doesn't do that, it's more like /dev/block/platform/DEVICE/*12:03
r0kk3rzudev is well documented, i suggest you read some of them12:03
r0kk3rzbut yes, its an abstraction layer for dealing with many different devices in a generic way12:04
T4<abhishek_0> is lbt up ?12:05
krnlyngthe rules for these partitions are a bit complicated, but if you have questions about a specific one ask12:05
MeowDudeI just need to figure out how to make it stop pointing at /dev/block/platform/omap/omap_hsmmc.0 and start pointing at /dev/block/omap_hsmmc.012:05
krnlyngno, you need to change the udev rules to create the /dev/block/platform/omap/omap_hsmmc.0/by-name/radio symlink12:06
MeowDudeI don't even know how to begin... so basically symlink /dev/block/platform/omap_hsmmc.0/by-name/radio to /dev/block/platform/omap/omap_hsmmc.0/by-name/radio?12:07
malMeowDude: you don't want to specifically symlink only one partition, but all partitions12:10
MeowDude*scratches head* How do I do that? I started writing a subsystem line at the top...12:11
MeowDudeI assume I am going in the wrong direction12:11
lbtnemo:devel:hw:wingtech:wt88047 is done abhishek_012:12
MeowDudemal: I added this line: SUBSYSTEM=="linkmain", KERNEL!="", RUN+="/bin/ln -s /dev/block/platform/$env{PLATFORM_FOLDER}/$env{PLATFORM_DEVICE} /dev/block/platform/omap_hsmmc.0"12:15
malMeowDude: you misunderstood completely what to do12:16
MeowDudesymlink the two directories12:17
MeowDudeso it reroutes any activity to the wrong one to the right one12:17
malMeowDude: that's not how it's done, check the last few lines in that rules file12:17
malthe "Create the partition symlinks" part12:17
T4<abhishek_0> sadly no third party app work on :(12:20
MeowDudemal: how does this look:
T4<abhishek_0> like telegram desktop, ytplayer.. jollagram.. and others12:21
malMeowDude: what line did you edit?12:22
r0kk3rzall my apps work at least, maybe you're just unlucky12:22
MeowDudemal: the last ones, I removed $env{PLATFORM_FOLDER} from each one since that is the one that added "omap" to it, which was plain incorrect. sorry I should have specified12:23
malMeowDude: am I missing something, I thought you needed to add something not remove?12:24
MeowDudeI just fixed the existing symlinks12:24
malI don't understand the fix, your path were missing omap from the middle and how did you add it there?12:25
T4<abhishek_0> r0kk3rz being that dank is injurious to health XD12:25
MeowDudethey weren't missing it12:25
mal14:23 < MeowDude> mal: open("/dev/block/platform/omap/omap_hsmmc.0/by-name/radio", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)12:26
r0kk3rzabhishek: fite me :P12:26
malyour paths were /dev/block/platform/omap_hsmmc.0/by-name which means it was missing omap12:26
MeowDude /platform/omap/omap_hsmmc.0/* is the WRONG path, it was trying to use this one. the "omap" in the path is wrong it leads to a different directory12:26
MeowDudeso i just told it to look in the right one instead of symlinking the right one to the wrong one (not that I'd know how to do that anyway)12:27
malMeowDude: I don't understand, wtf is doing that open commmand?12:27
T4<abhishek_0> r0kk3rz qt5 dependencies i have while installing them from storeman12:27
MeowDudestrace of /system/bin/rild12:27
malMeowDude: so you need to have that path on your system then, which means the paths are missing omap12:28
malI give up12:28
MeowDudeI think you are just misunderstanding my issue12:28
MeowDudebut thanks for all the help mal really12:28
MeowDudeI do appreciate it12:28
T4<abhishek_0> mal am i dreaming ?12:28
malMeowDude: you are the one misunderstanding12:28
MeowDudebut I just can't wrap my head around udev rules and how to symlink them12:29
malMeowDude: rild tries to open /dev/block/platform/omap/omap_hsmmc.0/by-name/radio but you have /dev/block/platform/omap_hsmmc.0/by-name/radio12:29
MeowDudeusually I would just run ln -s /dev/block/platform/omap/omap_hsmmc.0/by-name/ /dev/block/platform/omap_hsmmc.0/by-name/12:29
MeowDudeyeah that's it!12:29
MeowDudeby removing that PLATFORM_FOLDER part from the sought out file, it removes the "omap" in the path12:29
malMeowDude: how in the hell can it be so difficult to understand the udev rules12:29
MeowDudethey look incredibly verbose and I don't understand the signage.12:30
malMeowDude: just add the damn omap to the symlink rules in the rule file12:30
malhow can you not understand that12:30
malMeowDude: removes what12:30
MeowDudehmm it's like teaching a guy what "cout" and "int" and all that means without explaining why they have to add "<<" and "()" and "{" symbols and stuff, I only understand about 40% of the contents of the file12:30
malMeowDude: I'm totally lost what you mean12:30
MeowDudeI am a visual learner mal, I can't see this and I don't know where to add the "omap"12:31
malI assume rild has hardcoded /dev/block/platform/omap/omap_hsmmc.0/by-name/radio which means you need to make sure udev rules create that12:31
MeowDudeokay so i know what "PLATFORM_FOLDER" and stuff mean and how to work with those, great, but stuff like "why does it use += and {}, where and why do I use these" is something that is bothereing me12:31
MeowDudeokay so tell udev rules to symlink the real directory with the one rild points too12:32
malMeowDude: if your current udev rules create /dev/block/platform/omap_hsmmc.0/by-name/ but you need /dev/block/platform/omap/omap_hsmmc.0/by-name/, how can you not see where to add it?12:32
MeowDudethat's what you want me to do right?12:32
MeowDudethe current ones make /dev/block/omap/omap_hsmmc.0/by-name, I want to REMOVE the omap12:32
MeowDudenot add it12:32
maljust add omap to the lines 52-5412:32
MeowDudeI'll try that12:32
malbut that doesn't match what rild expects12:33
maldo I really have to give you the rules?12:33
MeowDudewait I see what you mean12:33
MeowDudeI can see the lines and how omap is missing from them12:33
malMeowDude: where did you see /dev/block/omap/omap_hsmmc.0/by-name ? that's not in any of the pastes you gave12:34
MeowDudethat was the folder rild was trying to access, the only issue is that that folder does not exist12:35
malMeowDude: the issue is probably that $env{PLATFORM_FOLDER} is empty12:35
malMeowDude: no, you said /dev/block/omap/omap_hsmmc.0/by-name but rild needs /dev/block/platform/omap/omap_hsmmc.0/by-name/radio12:35
MeowDudeENV{PLATFORM_FOLDER}="$kernel", which I assume it thinks means omap.12:36
MeowDudeI ought to just manually fill in the value12:36
malMeowDude: just replace the damn $env{PLATFORM_FOLDER} on line 52-54 with omap12:36
MeowDudefuck I replaced the wrong lines12:37
malthat's what I have been trying to tell you all the time12:37
malwell you didn't replace one of those12:43
MeowDudedmesg shows functioning ril_daemon12:43
malcould you please use your brain a little12:43
MeowDudehopefully it reflects this at boot up12:43
MeowDudeawsome rild is running but ofono is being a b****12:44
MeowDude1000 thanks mal, I couldn't have done this without you! (or krnlyng)12:45
krnlyngMeowDude, that's not the proper approach.12:45
MeowDudewell rild is running isn't it?12:45
MeowDudehuh now everytime I turn off the device it shows the loading ring until i swipe out like I am closing an app12:46
krnlyngMeowDude, put that fix on any other device and it will fail.12:46
MeowDudewell yeah I know that, because not all devices have an omap processor12:46
MeowDudealso now the lockscreen is broken12:46
MeowDude: (12:46
krnlyngMeowDude, if you can come up with a proper fix (which you should) then others can benefit from your work too12:47
MeowDudealso ofono gives this error: Jun 18 22:17:15 Sailfish ofonod[11559]: [mce] ERROR! Failed to attach to system bus: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS)12:47
krnlyngMeowDude, and may be even more welcome to helping you in turn :)12:48
MeowDudeI'll try and figure out how to better define ENV{PLATFORM_FOLDER}12:48
krnlyngthanks :)12:48
MeowDudefor now though, I need to debug ofono.. maybe later... it's late and I have school tommorow12:48
monichMeowDude: that system bus thing sounds like a missing dbus policy12:52
malMeowDude: which release did you build?12:53
T4<abhishek_0> how do i fix qt5-qtimageformats-plugin-dds dependency13:02
elrosspiiroin: I have issue with qtsensors. In messwerk there is wrong lux value when I wake up phone in dark room13:06
elrosin this example it was showing 97 instead 2 until als sensor get 3 or more13:06
elrosI don't care that much about what qt messwer shows but I have notice that brightness regulation is also affected13:14
lolekmgrover: hi, I see that there's still one failure for the xperia build, any estimate for fixing this so I can get the image and do the tests?13:26
lolekmonich: how's the wideband audio thing going?14:08
duncan^In my chroot, createrepo and android-tools aren't in the repositories. An equivalent createrepo_c and android-tools-hadk are, but I'm not sure if these are suitable (I imagine the latter is, but the former perhaps not)14:52
duncan^I mean... it build successfully so I guess it's fine...14:55
m4r0v3rlolek, that one isnt required15:01
lolekm4r0v3r: so, what's needed to to make new sfos image for X?15:02
lolekor how to continue from this?15:02
r0kk3rzgive ota another go15:02
lolekok, let's try then ;)15:03
lolekwill have info very soon15:03
lolekr0kk3rz and it's stuck again15:15
lolekr0kk3rz this time the installation took way longer than before, but in the end it started to boot, displayed for 2 s sony logo, then did reboot, to display the logo again and it's stuck15:15
r0kk3rzyeah the short reboot would've been it flashing the kernel15:16
T4<abhishek_0> when lbt will be back .. if i did everything right with obs15:16
lolekwell I don't know, the system is in freezed state, screen display sony logo on white bg, nothing else15:17
lolekI can only turn it off15:17
T4<abhishek_0> telnet into it15:18
T4<abhishek_0> device will detected as network interface on host15:19
lolekr0kk3rz so, any idea?15:22
lolekor any option how can I debug it?15:22
r0kk3rzmaybe you need to use cli ota method15:24
duncan^According to the hardware adaption document, the build_packages helper script creates a kickstart file. However, it doesn't seem to create one for me. How necessary is this, and how should I create it?15:40
r0kk3rzvery, and im sure it says in the hadk15:41
krnlyngduncan^, droid-configs is built?15:41
duncan^krnlyng: Yes15:42
krnlyngduncan^, can you check if $ANDROID_ROOT/hybris/droid-configs/installroot exists?15:43
duncan^According to the hardware adaption document, it is in hybris/droid-configs/installroot/usr/share/kickstarts/, but this directory doesn't exist15:43
krnlyngduncan^, how recently did you install/update your sdk15:44
duncan^I pulled it in yesterday, as far as I know, it's the latest15:45
krnlyngok, then you might need such a thing:
duncan^In hybris/droid-configs/, all I see are the following directories: RPMS  documentation.list  droid-configs-device  patterns  rpm  sparse  tmp15:45
duncan^OK, I'll try that. Thanks for the help.15:46
krnlyngduncan^, yes the new sdk does that. put the script i sent you into $ANDROID_ROOT and name it or something like that, then execute it with "source"15:46
krnlyngfrom $ANDROID_ROOT15:46
lolekr0kk3rz which is?15:48
duncan^krnlyng: I ran the script, so that means it's sufficient to skip the step in the hardware adaption document involving creating the kickstart file?15:56
duncan^(which involves this installroot/ directory in droid-configs)15:56
krnlyngduncan^, you have to still run the replacement stuff on it, this only copies the plain file15:56
T4<toxip> Hey guys, how are Xiaomi phones in terms of portability?16:25
T4<toxip> easy to port?16:26
T4<NotKit> if you have kernel source, generally no different from other devices16:26
T4<NotKit> [Edit] if you have kernel source, generally not different from other devices16:26
beidlhello hello! I'm back to porting sfos to the gnex again and I'm wondering where the ubu-chroot script went.16:27
T4<toxip> @NotKit [if you have kernel source, generally not diffe …], all available
T4<toxip> this seems like a nice budget phone to port to :)16:28
duncan^I see now mic is failing with the error Unable to find pattern: Jolla Configuration $DEVICE16:32
duncan^In hybris/droid-configs/patterns/, I definitely have a pattern which specifies that description.16:33
lolekr0kk3rz did update using cmd line, no visible errors, the same issue persist16:35
lolekso if you have any other ideas what I can test/do/check pls let me know16:36
malduncan^: did you process patterns as instructed?16:39
duncan^Yes, I ran rpm/dhd/helpers/ --configs as instructed in the section "8.4: Modifying a pattern"16:42
duncan^Is that the correct way to do it?16:42
duncan^Do I need to recompile?16:43
r0kk3rztheres a process patterns script too16:43
malduncan^: I mean the line hybris/droid-configs/droid-configs-device/helpers/ in chapter 8.516:44
duncan^I ran that (again?) and it is still saying that it can't find the pattern16:45
duncan^when I ran the process_patterns script, it printed a warning "C_CREATEREPOLIB: Warning: Record with type "patterns" already exists in repomd.xml16:45
duncan^but I'm not sure if that's relevant16:45
duncan^Error <creator>: Unable to find pattern: Jolla Configuration $DEVICE16:47
duncan^(if that's useful)16:47
malduncan^: how did you solve the createrepo issue you had?16:48
duncan^I appended _c to all instances of createrepo, because the programs in the package (and the package itself) appeared to have been renamed as such16:49
duncan^same with modifyrepo16:50
duncan^android-tools had been renamed android-tools-hadk so I merely renamed them to that16:50
duncan^(but the programs in android-tools-hadk were not renamed)16:51
malmaybe you need to run sudo ssu ar mer-tools
T4<abhishek_0> mal how do i improve smoothness ?16:59
T4<abhishek_0> everything is a bit jittery17:00
malit depends on what the reason for not being smooth is17:00
T4<abhishek_0> from where do i start debugging17:00
malwas there anything odd in top output? what is using cpu when that happens17:00
T4<abhishek_0> lipstick17:06
malbut how much17:06
maland some quite high cpu usage from lipstick is normal17:06
T4<abhishek_0> 31%17:06
maldoes that device have one of those cpus with two types of cores?17:08
T4<abhishek_0> no, i guess it has 4 cores all are cortex a5317:09
T4<abhishek_0> snapdragon 41017:09
T4<abhishek_0> here is the logcat doing stuff like opening camera , swiping through ui
T4<abhishek_0> even a 720p video lags17:18
malwondering if it somehow doesn't use hardware acceleration correctly17:19
T4<abhishek_0> mal where i should start looking ?17:21
malnot sure17:22
duncan^OK, I ran the configuration script again for the patterns, and it produced the attributeerror as noted in the document.17:23
duncan^However, I still can't get mic to recognize the pattern17:23
T4<abhishek_0> but still any idea .. guesses ?17:24
saidinesh5@abhishek_0 write a little sample qt application to display opengl info..17:24
saidinesh5lipstick shouldn't be eating 30% in idle17:24
malduncan^: that happened after installing the proper createrepo?17:24
r0kk3rzduncan^: do process patterns > build packages configs > mic and post the whole thing to pastebin17:25
malsaidinesh5: not on idle but when doing something17:25
saidinesh506-18 17:04:27.101 10152 10152 I Adreno-EGL: OpenGL ES Shader Compiler Version: XE031.09.00.0317:28
T4<abhishek_0> any app which uses opengl ?17:29
saidinesh5doesn't look like a problem from opengl17:29
saidinesh5@abhishek_0 all of your UI uses opengl , as it is built on QtQuick17:29
saidinesh5well opengles17:29
saidinesh5libEGL  : failed to load libgui: dlopen failed:17:30
saidinesh5that one seems dodgy...17:30
saidinesh5it keeps repeating over and over17:30
saidinesh5so maybe something is wrong17:30
duncan^here we are17:30
malduncan^: your .ks file is missing local repo?17:32
T4<abhishek_0> saidinesh5 yes it does .. i think this issue is pretty common on here17:32
malduncan^: droid-local-repo that is17:32
saidinesh5@abhishek_0 maybe worth it to look why it isn't loading. take a simple opengles app and try to run it17:33
malduncan^: something like this: repo --name=adaptation-community-zoom2-@RELEASE@ --baseurl=file:///home/duncan/build/sfos/mer-hybris/droid-local-repo/zoom217:34
saidinesh5 came up when googling for libegl and libgui17:34
Mister_Magistersaidinesh5: hello :)17:35
saidinesh5hey Mister_Magister17:35
saidinesh5oh not much.. fixing my schedule again, and finishing off work forthe day17:35
Mister_Magisterkay :P i just sit down trying to fix account management in morsender :P17:36
malduncan^: btw, you don't have to regenerate .ks file very often, I always use the same one17:39
duncan^mal, thanks, that worked. It's now able to find my patterns.17:44
duncan^OK, now I've got a different problem. mic produced a flashable zip called sailfishos-$DEVICE-release-.zip19:41
duncan^I attempted to flash this image over a known good cyanogenmod image, but it sais "Failed to extract filesystem! E: Error executing binary in zip '/data/media/sailfishos-$'19:43
duncan^(should be noted it actually says the device name in place of $DEVICE, I just write $DEVICE here because it's more appropriate)19:43
duncan^I suspect the image is broken somehow, and fixing the underlying issue causing awry naming might fix the build of the image.19:44
malduncan^: the filename looks odd, are you sure you remembered to define the needed things like RELEASE and EXTRA_NAME before running mic19:45
malthe filename should look something like this sailfishos-fp2-sibon-release-
malwith values matching your build of course19:47
duncan^Looks like I defined them the first time I ran mic, then didn't redefine them after fixing the issue with local repo19:49
duncan^sorry :/ thanks for your patience19:49
maltry building again and see if the zip looks correct after that19:50
r0kk3rzduncan^: i put those env vars into hadk.env19:52
duncan^It looks like it's getting the filenames right now19:53
malthe size of the zip should be about 300 MB19:55
duncan^Yes, it was 267M20:03
duncan^Nonetheless, I'm getting the same error.20:04
duncan^It says it's not finding the updater binary in the image.20:04
r0kk3rzpost output20:05
r0kk3rzbasically always post outputs :)20:06
duncan^I thought I couldn't, but there is obscure option in recovery to copy loog... one second20:07
r0kk3rzmic output is a good idea too20:08
r0kk3rzwhat device is this?20:12
duncan^Line 835 is the start of relevant parts20:12
duncan^r0kk3rz: Nook Simple Touch20:12
r0kk3rz1400 looks like the most relevant line to me20:12
duncan^OK, that's fine - I guess I just need to expand the partitions?20:13
duncan^It's an SD card, so that's not so hard20:13
duncan^they're set to about ~500M each20:13
r0kk3rzyeah thats probably a little small20:15
malduncan^: on one old device with limited space I used sdcard for rootfs20:17
malduncan^: ah, so you also use sdcard20:17
duncan^So it's got 2G of internal storage, it will boot from SD if you provide it with U-boot + MLO, and a valid kernel+ramdisk20:18
duncan^which is nice for recovery20:18
malbut anyway maybe at least 1 GB for sailfish rootfs is needed so there is some space for apps etc, preferrably more20:19
piggzmal: nothing in faq about new pulse configs .... what do i need for headphones to work again in 11?20:21
malpiggz: link to your config repo20:22
malpiggz: only headphones fail?20:23
piggzmal: so far20:23
malpiggz: is this still accurate
malI mean check on device that name and device are ok20:24
piggzmal: apparently not20:25
piggzhow odd20:25
piggz----====( /dev/input/event7 )====----20:25
piggzName: "msm8953-snd-card-mtp Headset Jack"20:25
malpiggz: have you done other changes that could cause the device to change, other option is to see if having only jack-match is enough20:26
piggzmal: i did a kernel upgrade20:26
malpiggz: that's probably the reason then20:26
piggzmal: likely ... this kernel maybe adds s2w20:27
piggzas event220:27
r0kk3rzmaybe some input/event roulette is going on20:30
piggzs2w doesnt seem to work anyway20:31
piggzmal: radio also stopped , but i think i remember reading about config changes for that20:34
malpiggz: your configs look reasonable20:37
malpiggz: just to be sure, were you using a patched fm radio middleware?20:38
malpiggz: if that is the case you might have wrong version in use, I updated the one in common20:38
piggzmal: hmm, i was...20:40
T4<abhishek_0> piggz do you have that or libEGL error (unrelated just asking)20:42
piggzwhen doing what?20:42
piggzmal: have no other ports had the issue of init/de-initing the radio ?20:45
malpiggz: not sure, if you check the new code it does init and deinit every time, but not via /sys20:47
malbut probably not related to your issue20:48
malpiggz: wouldn't it just be easier to patch the kernel20:49
piggzmal: what would the patch look like?20:49
piggz( i mean roughly ... not exactly!)20:50
malpiggz: most likely reverting this
piggzhmmmm, dejavu20:54
malbut might need other changes also20:54
T4<abhishek_0> piggz doing stuff .. browsing, media, swiping through the apps20:56
T4<abhishek_0> in the logcat20:56
abransonvknecht: I think you can see in there mention of the 0x7fa30c04 format that we do support. what's interesting is those C2DColorConvert errors starting around 358. it's being asked to transform the colour format internally - we don't use that class in droidmedia - and failing20:56
abransonif you want to see more of what's going on, find ACodec.cpp in your android tree - it'll be under frameworks/av, and find the #define LOG_NDEBUG line near the top that's commented out.20:57
duncan^Hmm, it is taking rather a while to unpack20:58
abransonuncomment it and build your android libs again, and all the verbose ALOGVs will be printed out, which will tell you more about the formats set for the codecs. if for some reason there's a strange transformation going on, you might see it in there.20:58
abransonother source files near ACodec might tell you things too. each one needs to have its logging enabled individually,20:59
*** Nokius_ is now known as Nokius21:03
malpiggz: a hint, please rebase, don't merge21:03
piggzmal: radio not working with patched version anyway21:06
duncan^It appeared to break /boot somehow. The partition has corrupted itself nicely.21:07
malpiggz: odd21:07
malpiggz: I assume it used to work21:07
piggzmal: it did...tho ive added a kernel upgrade tooo.....21:07
T4<abhishek_0> is lbt lbt- online ?21:07
piggzelts debug briefly21:07
T4<abhishek_0> !seen lbt21:08
T4<abhishek_0> oh wait i am a bot21:08
malpiggz: does it tune to channels?21:08
piggzmal: its working .....21:09
piggzwhen you 'su nemo' it ignores the env variable21:09
Mr_Doge!seen T421:09
merbotMr_Doge: T4 was last seen in #sailfishos-porters 59 seconds ago: <T4> <abhishek_0> oh wait i am a bot21:09
Mr_Doge!seen lbt21:10
merbotMr_Doge: lbt was last seen in #sailfishos-porters 8 hours, 57 minutes, and 56 seconds ago: <lbt> nemo:devel:hw:wingtech:wt88047 is done abhishek_021:10
malpiggz: ok, good21:10
piggzmal: panic over, headphones and radio working again in my devel:21:10
piggzsorry for sloppy git practices21:10
malpiggz: always a good idea to ask me :P21:10
Mr_Dogeoh its done,,, sorry for the ping21:11
piggzi still say my small patch is easier than hacking the kernel driver and is safe to upstream ;)21:11
malpiggz: it might be easier but whether it's better is another question21:12
piggztrue, but frigging around in the kernel driver is a lot tougher21:13
piggzand dangerous21:13
Nokiusr0kk3rz: let's see if we can do something about the cam as next21:13
piggzmal: anyone looked at FP stuff yet?21:13
malpiggz: not that I know of21:14
piggzmal: does 2.2 add better BT for your watch?21:14
malI haven't tested yet21:14
r0kk3rzNokius: recording could be tricky21:15
r0kk3rzit seems to be on android side21:15
malpiggz: probably not21:16
Nokiusr0kk3rz: yeap android is bity here21:17
T4<abhishek_0> mal it it says it is excluded
T4<abhishek_0> not sure why21:18
mal@abhishek_0 it should be like that21:19
mal@abhishek_0 on #mer-boss 00:19 < merbot> Updating patterns from nemo:devel:hw:wingtech:wt88047/droid-config-wt8804721:19
malit's in the process of updating the patterns21:20
duncan^So the zip installer tries to unpack hybris-boot.img onto /dev/by-name/boot. However, this isn't desirable for me, since I need boot to have just uImage+uRamdisk. So, I'm wondering what to do - should I repack hybris-boot.img into a kernel+ramdisk?21:21
malyou probably need to edit the updater script in hybris/hybris-boot21:22
T4<abhishek_0> after that is done, how will i know i did everything right ? maybe i am asking too much questions :P21:22
malassuming the repos are using correct versions it looks ok21:28
duncan^abootimg is claiming that it's not a valid Android bootimage, which is odd.21:33
duncan^It says: "sizes mismatches in boot image"21:34
T4<abhishek_0> sledges please create nemo:testing:hw:wingtech:wt88047, if it is already there then provide me the maintainership  username abhishek965022:02
vknechtabranson, ack, thx, 'll try s∞n ;-)22:05
MeowDudeokay so rild is running (again, thanks guys), and ofono is running but I am getting an error about connection refused, and there is no empty sim icon on my phone. I grabbed a pastebin of systemctl status ofono and ps ax | grep rild:
MeowDudeif I restart ofono manually there are no errors in systemctl status ofono, but there is still no empty sim icon of internet sharing option in settings23:27
MeowDuderunning /system/bin/logcat -b radio gives: Unable to open log device '/dev/log/radio': Not a directory23:32
MeowDudeupon manually reading /dev/alog/radio I get this:
MeowDudearg I can't symlink an empty /dev/log directory with /dev/alog because there is already something in /dev names log23:45
MeowDudeFINALLY I grabbed a log using a dirty work around:
MeowDudethis seems to be the only error in the log: E/use-Rlog/RLOG-RIL(s)(  480): loadOpnameFile: Can't open the Opname file: reason No such file or directory.23:53
MeowDudeofono seems happy now...23:57

Generated by 2.17.1 by Marius Gedminas - find it at!