Saturday, 2019-01-05

UmeaboyProblem solved when updating the firmware.00:38
*** ChanServ sets mode: +v T402:02
UmeaboyUuuuuuuuuhm. My dist Mageia renamed the fastboot binary into fastboot-android for some reason and the for the free version of Jolla X can't find my phone even though fastboot-android devices sees it.05:31
UmeaboyWhat can I do?05:31
UmeaboyI'm just going to try it in my new XA2.05:31
UmeaboyI corrected the script to use fastboot-android, but I don't know what to change next.05:32
UmeaboyIncorrect number of devices connected. Make sure there is exactly one device connected in fastboot mode.05:33
UmeaboyThat's what I see.05:33
UmeaboyIt IS connected.05:33
Umeaboy[kristoffer@localhost Sailfish_OS-Jolla-]$ fastboot-android devices05:34
*** ChanServ sets mode: +v T408:04
T4<It_sMike> Hey sailors :) … Find a problem in camera … White balance effects are not working.... … Guess it relates to gst-droid … Any idea for fixing this issue?08:32
T4<adampigg> @It_sMike [Hey sailors :) … Find a problem in camera … White …], What you need is piggz-o-vision :D11:56
UmeaboyJust out of curiosity, how does one do the HADK for a seperate device like I just bought? Do I really need to start it all over on a clean slate?11:57
UmeaboyIt's officially supported by Lineage 15.111:58
T4<It_sMike> @adampigg WoW, the most awesome sailfish camera app I've ever seen :) , Great job Adam, Can I include it to my image?12:17
T4<adampigg> @It_sMike [@adampigg WoW, the most awesome sailfish camer …], sure ... I need testers, and you need to be sure you have all the required deps ... ports should be ok, but make sure you have the correct camera hal options, and confirm if effects/hdr work ok12:18
T4<It_sMike> :) I could help you with that .... ( testing I mean )12:19
UmeaboyHey, guys....... The bash script that Sony made to flash the Jolla X to my Sony Xperia XA2 can't work since Mageia (my Linux dist) apparently insists on calling the binary for fastboot......fastboot-android. I don't know why exactly.12:26
piggz_mal: yes, the mkfstab section of dhd skips the fstsab file completely becuase there is no . in the name!12:29
T4<It_sMike> @adampigg Everything were fine with old build of gst-droid, but the new build mess up the effects again :(12:33
T4<It_sMike> Should find out what's the problem exactly.12:34
malpiggz_: interesting, fix it and make a PR12:45
piggz_mal: yup, on it12:53
T4<It_sMike> :) Fixed13:03
malUmeaboy: do both devices use same base or not? I have one copy of all android bases and you can use the same source tree for several devices if those use the same android base, but it needs some scripting to make it easy13:08
mal@It_sMike what was the reason for the problem?13:09
T4<abhishek_0> @adampigg please font use reply feature on tg, mention their username rather13:12
T4<abhishek_0> [Edit] @adampigg please dont use reply feature on tg, mention their username rather13:12
kimmoliand no edits please...13:17
T4<It_sMike> mal : It was similar to sensorfw problem, just reset gst-droid to a3ead5eeb8d4aa30c1f13ee762cb439844cc16ca release13:20
Umeaboymal: Not sure to be honest.13:22
mal@It_sMike very odd, the dependencies for that should be in latest droidmedia and common repo13:24
malUmeaboy: ?13:24
UmeaboyYou asked what base it uses.13:24
malUmeaboy: well pioneer has official sailfish13:26
Umeaboymal: Only Free as far as I can see.13:26
maland the repos are in mer-hybris13:26
malUmeaboy: the sold version will be available Soon (tm)13:27
UmeaboyYeah, I was thinking of purchasing that on the 16th.13:28
T4<It_sMike> mal : I don't know, everything were at its last release, maybe I should take look at logcat again....13:29
UmeaboyHowever I can't install the Free version with the included bash script in their zip file due to Mageia (my Linux dist) naming the fastboot binary as fastboot-android. I'll tell them to change it for the Pie version of android-tools.13:31
malUmeaboy: so change the script13:33
mal@It_sMike verify the package versions on device are reall correct13:34
Umeaboymal: I changed so that fastboot works, but it still says:
UmeaboyIf fastboot DOES see the device and I'm running Lineage 16.0 (unofficial build made by one of the maintainers for the 15.1 build), shouldn't that mean that the script will flash it13:38
malhow exactly did you change the script?13:39
UmeaboyI renamed fastboot into fastboot-android, nothing more.13:40
malit fails for some reason, does it matter whether you use ./ vs bash not sure what your default shell is13:42
UmeaboyIt's bash.13:43
UmeaboyAnd it doesn't make any difference.13:44
maleither add some debug printing to the script to see it really find fastboot in there or manually run the stuff in the script13:44
T4<It_sMike> mal : OK, I'll notify you once it dones!13:48
T4<linusdan> Do you have any idea to operate the system? I did everything, even the FAQ and all the manual (read again carefully) and just hangs on the samsung logo14:17
T4<It_sMike> mal, is there anyway to improve sound on recording? sound quality on videos it's too low ( also on voice recording )14:18
T4<linusdan> I don't want to give up 😢14:18
T4<It_sMike> @linusdan hmmm what's your kenel version?14:22
T4<linusdan> Is 3.0.10114:22
T4<It_sMike> Is it official ?14:23
T4<linusdan> Yes, forked from LineageOS repo14:23
mal@linusdan can you telnet to the device via usb connection, ip port either 23 or 232314:24
T4<It_sMike> Any accses to device via ssh? while it's stucked at samsung logo14:24
malssh is for later, telnet is for early debugging14:24
T4<It_sMike> Right :) sorry for mistake14:25
malsome samsungs have issues with usb, my samsung gets wrong mac address and I need to manually set it to host interface14:25
mal@linusdan when you connect the device to your computer via usb check ifconfig -a to see if there is interface for the device14:26
mal@It_sMike you mean low volume?14:26
T4<linusdan> mal: There's no way … Not Initializes14:27
T4<linusdan> Cell phone not in recovery mode, do I have to Flash via odin again … Is the fifth attempt14:29
malwhat does host dmesg say when you have the14:29
malthe usb connected14:29
T4<It_sMike> mal : yes, low volume on video or voice recording14:30
T4<It_sMike> But on voice calls everything's ok...14:30
Umeaboymal: Debugging the script shows this:
T4<linusdan> I'll try again … Wait a minute :)14:31
UmeaboySorry. Didn't have the phone booted into bootloader mode at first, but it is now and still the same result.14:35
T4<linusdan> mal: dmesg not recognized the device :(14:36
malUmeaboy: I meant add more printing inside the script to see raw output of fastboot command, return value etc14:36
mal@linusdan at all? no sign of usb related messages?14:36
T4<linusdan> nothing, just sample things notebook14:38
Umeaboymal: That's not my field really.14:38
malUmeaboy: the I can't help, it's very simple to print variable contents in shell scripts14:39
malalso learning new things is always a good idea14:40
UmeaboyNow I got it to debug the entire process, but still I'm not sure what's wrong:
UmeaboyRow 19 seems wrong.14:50
Umeaboy18 and 19 to be exact.14:50
UmeaboyShould be else if fastboot-android fi...... Right?14:51
malUmeaboy: are you sure you have the correct image? single-sim vs dual-sim?14:51
malUmeaboy: check lines 40-4514:52
malUmeaboy: looks like it finds a single-sim device h3113 whereas the script is looking for h4113 or h413314:53
Umeaboymal: Yes, I'm sure I have the right image. Double checked the name of the zip I downloaded.14:53
malUmeaboy: so do you have single-sim device or dual-sim?14:54
malcheck fastboot getvar for the product code14:54
malto me it looks like it's reporting h311314:55
Umeaboymal: Yeah, but About the device still says H4113 and the desktop icon when the phone is mounted says H4113. fastboot-android getvar all shows h3113. Don't know why though.14:56
*** ChanServ sets mode: +v T414:56
UmeaboyI run stock recovery as TWRP gets overwritten somehow when I flash Lineage 16.0.14:57
malUmeaboy: maybe something was overwritten somewhere, maybe try installaking stock android back using official image?14:58
malalthough it would be odd that the fastboot product code is changed, not sure where that is even defined15:01
malUmeaboy: not sure where android gets the code it reports, it could be a build time define so flashing incorrect android could make it should h4113 in UI even if the device is really h3113. double check in device packacing15:03
UmeaboyDevice packaging says H4113.15:04
maldid you verify that the second sim slot actually works in android?15:06
Umeaboymal: Nope. I don't have another SIM card that's working currently.15:12
UmeaboyI say Slot A and B in twrp though.15:12
malUmeaboy: you don't need to two sim cards, just move it to the other slot15:13
UmeaboyI'll try that soon. Have to flash stock with XperiFirm first.15:13
UmeaboyCommencing flash. :)15:47
UmeaboyInstalling stock rom. :)15:47
UmeaboyHopefully it'll boot.15:48
UmeaboyI guess I need to unlock the bootloader again.15:49
Umeaboy05/059/2019 16:59:27 - WARN  -    Unable to read TA unit 10021, error=-22 ( Hex unit value 00002725 )16:00
Umeaboy05/059/2019 16:59:27 - ERROR - The bundle does not match the connected device16:00
UmeaboyI used XperiFirm to download the firmware.16:00
Umeaboymal: What can I do?16:04
malno idea what xperifirm is16:08
UmeaboyYou know what Flashtool is?16:08
malonly the official sony thing, not sure what the name of that was16:09
UmeaboyFlashtool uses a program called XperiFirm to download the stock rom and then Flashtool flashes it for you.16:09
malUmeaboy: where do you see that error?16:13
UmeaboyIn the XperiFirm window.16:13
malno idea what that error mean, I have never used flashtool, only the official emma tool16:14
UmeaboyIt still says connected device H3113.16:14
UmeaboyThat's so dumb.16:14
malwhat it?16:15
UmeaboyThat Lineage somehow changed my physical model name from H4113 to H3113.16:19
UmeaboyThe Lineage zip was built for H3113 apparently.16:20
UmeaboyThe info page tells you that H4113 isn't supported for that modelname.16:20
malnot nice, what partitions did it flash?16:23
Benclark006when i run `repo sync --fetch-submodules`16:51
Benclark006it returns error: in `sync --fetch-submodules`: revision refs/tags/android-8.1.0_r26 in platform/art not found16:51
Benclark006what have i broken?16:52
malBenclark006: what are you trying to fetch?16:57
malBenclark006: I mean what repo init command did you run?16:57
Benclark006repo init -u git:// -b hybris-15.117:00
Benclark006thats the one i have installed on my phone17:01
malBenclark006: try without --fetch-submodules17:01
malso only repo sync17:01
Benclark006thats working nicely17:01
maljust curious, which device are you porting?17:02
Benclark006nexus 417:02
Benclark006i got one for cheap off ebay and i wanted to get sailfish os on it once i tried it out in a vm17:04
r0kk3rzwhy use such a new branch for such an old device17:04
Benclark006because it was the one on the lineage os site17:05
Benclark006so I installed it and it works very nice17:06
r0kk3rzyou'd probably have a better time with 13, or 14, but i guess you have to work with what you got17:12
Benclark006i'll try my luck with 15 but i'll give 13 or 14 a go if it breaks17:14
Benclark006thanks for the advice17:14
Benclark006so when the manual says about fixup-mountpoints17:20
Benclark006am I just supposed to do ls -l /dev/17:20
Benclark006block/platform/*/by-name/ ?17:20
T4<It_sMike> @linusdan What's up with porting?17:21
piggzmal: other than a specific modprobe, what else can cuase a module to get loaded?17:58
Benclark006hey, when i run repo sync it returns error: Exited sync due to fetch errors18:04
T4<linusdan> Mike: In deep depression 😂 … About to give up … I took a walk in the world and no boot!18:06
malBenclark006: the failing repo should be shown somewhere in the output18:07
malpiggz: there is the module loading thing that list modules to load18:08
malpiggz: or some init script can do it18:08
mal@linusdan you never shower any output from dmesg, it must say something about usb device18:08
Benclark006mal: i don't see anything about a failing repo
Benclark006also, where is the android build tree?18:18
malBenclark006: error: Cannot fetch CyanogenMod/android_device_lge_mako, you should use device repos from lineageos, not cyanogenmod18:18
malsame for kernel18:18
Benclark006i see18:18
malandroid_device_lge_mako and android_kernel_lge_mako18:19
T4<linusdan> mal: output for dmesg:
malBenclark006: android build tree is $ANDROID_ROOT you defined earlier18:19
mal@linusdan really? you have that little messages in dmesg?18:20
malBenclark006: why did you ask?18:20
T4<linusdan> mal: Oops, looks like now appeared something18:21
Benclark006mal: i think i've done a stupid and not defined $ANDROID_ROOT18:22
Benclark006where does is say to do that on the manual18:22
malBenclark006: chapter 4.1 in hadk pdf18:22
malBenclark006: in $HOME/.hadv.env file18:22
Benclark006oh so i /have/ done it18:23
Benclark006nevermind i'm dumb18:23
Benclark006and how do i switch from cm device repos to the lineage ones?18:25
Benclark006sorry for all the questions i'm new to all this18:25
malyou defined those in .repo/local_manifests as mentioned in chapter 5.218:26
piggzmal: blacklisting the driver, then later modprobing it works18:26
r0kk3rzorly? interesting18:26
Benclark006i see18:28
T4<It_sMike> @linusdan Don't give up under any situation :) , Sailors are here to help18:42
T4<linusdan> ❤️❤️❤️18:43
T4<It_sMike> @linusdan Did you run mer_kernel_check under PlatformSdk?18:44
T4<linusdan> I did Mike, there was only one dependency that was ignored because the kernel version for the i9100 is 3.0 and has only 3.4. Recommendation of the mer_kernel_check18:46
T4<It_sMike> I had the same problem ( stucking at boot logo ) when I was trying to port kernel 3.10 to my device, It's solved by making some changes to my kernel defconfig...18:46
mal@linusdan which one?18:48
T4<It_sMike> Hmmm..... maybe mal should check your kernel defconfig18:48
T4<linusdan> mike: Great you did it! … Everything is fine in the kernel18:48
T4<It_sMike> Thanks Dan :)18:49
T4<It_sMike> 🤔 Have you tried changing the android base?18:50
T4<linusdan> mike: :) … I'm thinking of doing this, but for now I'll leave it at the base of android 7.118:51
malthe android base is not the problem probably18:52
T4<linusdan> mal: The usb output of the cellphone appeared, but did not look right18:53
T4<It_sMike> What do you think mal? about this?18:53
T4<linusdan> mal: output appears in [1.976224], line 79818:56
T4<adampigg> mal: interesting ... the module now correctly  loads the mac address according to the kernel output .... but still has a random one until connma starts, so, my problem persists!18:59
mal@linusdan you had the phone connected when you booted your computer, just wondering why it's so early in dmesg timestamps19:10
malhow does the device behave, does it look like it reboots?19:10
T4<linusdan> mal: Or resumes, just hangs on the samsung logo. I left for several minutes and stayed in the same way. … To get back to normal have to TWRP flash going to odin. … Not enter in TWRP after flash.19:13
T4<linusdan> of sailfish19:14
malso disconnect the cable and reconnect and observe host dmesg19:14
T4<linusdan> mal: ok19:14
malhow did you install sailfish? normally via zip?19:16
T4<linusdan> mal: yes, via zip … I flashing the Lineage and Sailfish together. … At the end it gives an error saying invalid command, but no big deal19:20
malwhat invalid command?19:20
T4<linusdan> says: [Done![]]19:21
T4<linusdan> oops, so don't … says: [done! … Here comes … Error: Unknown command: []]19:23
T4<linusdan> mal: Ah, connecting and disconnecting the appliance appears: … [18169.054808] usb 2-1: new high-speed USB device number 6 using xhci_hcd … [18169.197127] usb 2-1: New USB device found, idVendor=04e8, idProduct=685d, bcdDevice= 2.1b … [18169.197134] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 … [18169.197139] usb 2-119:26
T4: Product: Gadget Serial … [18169.197143] usb 2-1: Manufacturer: SAMSUNG … [18169.873081] usbcore: registered new interface driver cdc_acm … [18169.873083] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters … [18187.456302] usb 2-1: USB disconnect, device number 619:26
T4<linusdan> sorry :D19:27
T4<linusdan> I took the battery out to restart and not recognized … Damn!19:38
T4<linusdan> *Not recognize via dmesg19:38
malreflash kernel and see dmesg when you boot it again19:42
T4<linusdan> ok! :)19:44
Benclark006hi again, i'm getting some errors with make hybris-hal and was wondering if anyone could find out what i did wrong, thanks20:09
T4<linusdan> mal: I'm leaving tomorrow, my head is not processing anything else. Thanks for the help!20:10
*** ChanServ sets mode: +v T420:22
malBenclark006: how RAM does your computer have?20:22
Benclark006only 4 gb20:23
Benclark006oh i think it's randomly started working now20:24
Benclark006ok so it's now working except it throws an error near the end20:30
Benclark006ninja: error: 'libsf_compat_layer', needed by 'hybris-hal', missing and no known rule to make it20:30
Benclark006nevermind i googled it20:36
malyes, you need to clone android8-initial branch of libhybris to for example hybris/mw/libhybris20:39
Benclark006wow builds do take a while huh21:21
maldepends on how fast your computer is21:23
maland amount of memory21:24
T4<elros34> @linusdan: for 3.0 kernel sometimes is better to not enable all cgroup mem configs21:24
T4<elros34> for my photon CONFIG_CGROUP_MEM_RES_CTLR caused bootloop21:25

Generated by 2.17.1 by Marius Gedminas - find it at!