Umeaboy | Problem solved when updating the firmware. | 00:38 |
---|---|---|
*** ChanServ sets mode: +v T4 | 02:02 | |
Umeaboy | Uuuuuuuuuhm. My dist Mageia renamed the fastboot binary into fastboot-android for some reason and the flash.sh for the free version of Jolla X can't find my phone even though fastboot-android devices sees it. | 05:31 |
Umeaboy | What can I do? | 05:31 |
Umeaboy | I'm just going to try it in my new XA2. | 05:31 |
Umeaboy | I corrected the script to use fastboot-android, but I don't know what to change next. | 05:32 |
Umeaboy | Incorrect number of devices connected. Make sure there is exactly one device connected in fastboot mode. | 05:33 |
Umeaboy | That's what I see. | 05:33 |
Umeaboy | It IS connected. | 05:33 |
Umeaboy | [kristoffer@localhost Sailfish_OS-Jolla-3.0.0.8-h4113-0.0.7.10-FIXED]$ fastboot-android devices | 05:34 |
Umeaboy | CQ3001AT99fastboot | 05:34 |
*** ChanServ sets mode: +v T4 | 08: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 | P (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) was added by: P (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) | 09:54 |
T4 | <adampigg> @It_sMike [Hey sailors :) … Find a problem in camera … White …], What you need is piggz-o-vision :D | 11:56 |
Umeaboy | Just 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 |
Umeaboy | It's officially supported by Lineage 15.1 | 11: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 ok | 12:18 |
T4 | <It_sMike> :) I could help you with that .... ( testing I mean ) | 12:19 |
Umeaboy | Hey, 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 |
mal | piggz_: interesting, fix it and make a PR | 12:45 |
piggz_ | mal: yup, on it | 12:53 |
T4 | <It_sMike> :) Fixed | 13:03 |
mal | Umeaboy: 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 easy | 13: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 rather | 13:12 |
T4 | <abhishek_0> [Edit] @adampigg please dont use reply feature on tg, mention their username rather | 13:12 |
kimmoli | and no edits please... | 13:17 |
T4 | <It_sMike> mal : It was similar to sensorfw problem, just reset gst-droid to a3ead5eeb8d4aa30c1f13ee762cb439844cc16ca release | 13:20 |
Umeaboy | mal: Not sure to be honest. | 13:22 |
mal | @It_sMike very odd, the dependencies for that should be in latest droidmedia and common repo | 13:24 |
mal | Umeaboy: ? | 13:24 |
Umeaboy | You asked what base it uses. | 13:24 |
Umeaboy | https://wiki.lineageos.org/devices/pioneer/ | 13:25 |
mal | Umeaboy: well pioneer has official sailfish | 13:26 |
Umeaboy | mal: Only Free as far as I can see. | 13:26 |
mal | and the repos are in mer-hybris | 13:26 |
mal | Umeaboy: the sold version will be available Soon (tm) | 13:27 |
Umeaboy | Yeah, 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 |
Umeaboy | However 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 |
mal | Umeaboy: so change the script | 13:33 |
mal | @It_sMike verify the package versions on device are reall correct | 13:34 |
mal | *really | 13:34 |
Umeaboy | mal: I changed so that fastboot works, but it still says: https://pastebin.com/xwztJUyA | 13:37 |
Umeaboy | If 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 it | 13:38 |
Umeaboy | ? | 13:38 |
mal | how exactly did you change the script? | 13:39 |
Umeaboy | I renamed fastboot into fastboot-android, nothing more. | 13:40 |
mal | it fails for some reason, does it matter whether you use ./flash.sh vs bash flash.sh? not sure what your default shell is | 13:42 |
Umeaboy | It's bash. | 13:43 |
Umeaboy | And it doesn't make any difference. | 13:44 |
mal | either add some debug printing to the script to see it really find fastboot in there or manually run the stuff in the script | 13: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 logo | 14: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.101 | 14:22 |
T4 | <It_sMike> Is it official ? | 14:23 |
T4 | <linusdan> Yes, forked from LineageOS repo | 14:23 |
mal | @linusdan can you telnet to the device via usb connection, ip 192.168.2.15 port either 23 or 2323 | 14:24 |
T4 | <It_sMike> Any accses to device via ssh? while it's stucked at samsung logo | 14:24 |
mal | ssh is for later, telnet is for early debugging | 14:24 |
T4 | <It_sMike> Right :) sorry for mistake | 14:25 |
mal | some samsungs have issues with usb, my samsung gets wrong mac address and I need to manually set it to host interface | 14:25 |
mal | @linusdan when you connect the device to your computer via usb check ifconfig -a to see if there is interface for the device | 14:26 |
mal | @It_sMike you mean low volume? | 14:26 |
T4 | <linusdan> mal: There's no way … Not Initializes | 14:27 |
T4 | <linusdan> Cell phone not in recovery mode, do I have to Flash via odin again … Is the fifth attempt | 14:29 |
mal | what does host dmesg say when you have the | 14:29 |
mal | the usb connected | 14:29 |
T4 | <It_sMike> mal : yes, low volume on video or voice recording | 14:30 |
T4 | <It_sMike> But on voice calls everything's ok... | 14:30 |
Umeaboy | mal: Debugging the script shows this: https://pastebin.com/8JnBMB8U | 14:31 |
T4 | <linusdan> I'll try again … Wait a minute :) | 14:31 |
Umeaboy | Sorry. 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 |
mal | Umeaboy: I meant add more printing inside the script to see raw output of fastboot command, return value etc | 14:36 |
mal | @linusdan at all? no sign of usb related messages? | 14:36 |
T4 | <linusdan> nothing, just sample things notebook | 14:38 |
Umeaboy | mal: That's not my field really. | 14:38 |
mal | Umeaboy: the I can't help, it's very simple to print variable contents in shell scripts | 14:39 |
mal | also learning new things is always a good idea | 14:40 |
Umeaboy | Now I got it to debug the entire process, but still I'm not sure what's wrong: https://pastebin.com/xWZHc84J | 14:48 |
Umeaboy | Row 19 seems wrong. | 14:50 |
Umeaboy | Right? | 14:50 |
Umeaboy | 18 and 19 to be exact. | 14:50 |
Umeaboy | Should be else if fastboot-android fi...... Right? | 14:51 |
mal | Umeaboy: are you sure you have the correct image? single-sim vs dual-sim? | 14:51 |
mal | Umeaboy: check lines 40-45 | 14:52 |
mal | Umeaboy: looks like it finds a single-sim device h3113 whereas the script is looking for h4113 or h4133 | 14:53 |
Umeaboy | mal: Yes, I'm sure I have the right image. Double checked the name of the zip I downloaded. | 14:53 |
mal | Umeaboy: so do you have single-sim device or dual-sim? | 14:54 |
Umeaboy | Dual. | 14:54 |
Umeaboy | H4113. | 14:54 |
mal | check fastboot getvar for the product code | 14:54 |
mal | to me it looks like it's reporting h3113 | 14:55 |
Umeaboy | mal: 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 T4 | 14:56 | |
Umeaboy | I run stock recovery as TWRP gets overwritten somehow when I flash Lineage 16.0. | 14:57 |
mal | Umeaboy: maybe something was overwritten somewhere, maybe try installaking stock android back using official image? | 14:58 |
mal | although it would be odd that the fastboot product code is changed, not sure where that is even defined | 15:01 |
mal | Umeaboy: 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 packacing | 15:03 |
Umeaboy | Device packaging says H4113. | 15:04 |
mal | did you verify that the second sim slot actually works in android? | 15:06 |
Umeaboy | mal: Nope. I don't have another SIM card that's working currently. | 15:12 |
Umeaboy | I say Slot A and B in twrp though. | 15:12 |
mal | Umeaboy: you don't need to two sim cards, just move it to the other slot | 15:13 |
Umeaboy | I'll try that soon. Have to flash stock with XperiFirm first. | 15:13 |
Umeaboy | Commencing flash. :) | 15:47 |
Umeaboy | Installing stock rom. :) | 15:47 |
Umeaboy | Hopefully it'll boot. | 15:48 |
Umeaboy | I guess I need to unlock the bootloader again. | 15:49 |
Umeaboy | Uuuuuuuuhm. | 15:59 |
Umeaboy | 05/059/2019 16:59:27 - WARN - Unable to read TA unit 10021, error=-22 ( Hex unit value 00002725 ) | 16:00 |
Umeaboy | 05/059/2019 16:59:27 - ERROR - The bundle does not match the connected device | 16:00 |
Umeaboy | I used XperiFirm to download the firmware. | 16:00 |
Umeaboy | mal: What can I do? | 16:04 |
mal | no idea what xperifirm is | 16:08 |
Umeaboy | You know what Flashtool is? | 16:08 |
mal | only the official sony thing, not sure what the name of that was | 16:09 |
Umeaboy | Flashtool uses a program called XperiFirm to download the stock rom and then Flashtool flashes it for you. | 16:09 |
r0kk3rz | emma | 16:09 |
mal | Umeaboy: where do you see that error? | 16:13 |
Umeaboy | In the XperiFirm window. | 16:13 |
Umeaboy | No... | 16:14 |
Umeaboy | Wait.....Flashtool. | 16:14 |
mal | no idea what that error mean, I have never used flashtool, only the official emma tool | 16:14 |
Umeaboy | It still says connected device H3113. | 16:14 |
Umeaboy | That's so dumb. | 16:14 |
mal | what it? | 16:15 |
mal | *is | 16:15 |
Umeaboy | That Lineage somehow changed my physical model name from H4113 to H3113. | 16:19 |
Umeaboy | The Lineage zip was built for H3113 apparently. | 16:20 |
Umeaboy | The info page tells you that H4113 isn't supported for that modelname. | 16:20 |
mal | not nice, what partitions did it flash? | 16:23 |
Benclark006 | hey | 16:50 |
Benclark006 | when i run `repo sync --fetch-submodules` | 16:51 |
Benclark006 | it returns error: in `sync --fetch-submodules`: revision refs/tags/android-8.1.0_r26 in platform/art not found | 16:51 |
Benclark006 | what have i broken? | 16:52 |
Benclark006 | thanks | 16:52 |
mal | Benclark006: what are you trying to fetch? | 16:57 |
mal | Benclark006: I mean what repo init command did you run? | 16:57 |
Benclark006 | repo init -u git://github.com/mer-hybris/android.git -b hybris-15.1 | 17:00 |
Benclark006 | thats the one i have installed on my phone | 17:01 |
mal | Benclark006: try without --fetch-submodules | 17:01 |
mal | so only repo sync | 17:01 |
Benclark006 | thats working nicely | 17:01 |
Benclark006 | thanks! | 17:01 |
mal | just curious, which device are you porting? | 17:02 |
Benclark006 | nexus 4 | 17:02 |
Benclark006 | i got one for cheap off ebay and i wanted to get sailfish os on it once i tried it out in a vm | 17:04 |
r0kk3rz | why use such a new branch for such an old device | 17:04 |
Benclark006 | because it was the one on the lineage os site | 17:05 |
Benclark006 | so I installed it and it works very nice | 17:06 |
r0kk3rz | you'd probably have a better time with 13, or 14, but i guess you have to work with what you got | 17:12 |
Benclark006 | i'll try my luck with 15 but i'll give 13 or 14 a go if it breaks | 17:14 |
Benclark006 | thanks for the advice | 17:14 |
Benclark006 | so when the manual says about fixup-mountpoints | 17:20 |
Benclark006 | am I just supposed to do ls -l /dev/ | 17:20 |
Benclark006 | block/platform/*/by-name/ ? | 17:20 |
T4 | <It_sMike> @linusdan What's up with porting? | 17:21 |
piggz | mal: other than a specific modprobe, what else can cuase a module to get loaded? | 17:58 |
Benclark006 | hey, when i run repo sync it returns error: Exited sync due to fetch errors | 18:04 |
T4 | <linusdan> Mike: In deep depression 😂 … About to give up … I took a walk in the world and no boot! | 18:06 |
mal | Benclark006: the failing repo should be shown somewhere in the output | 18:07 |
mal | piggz: there is the module loading thing that list modules to load | 18:08 |
mal | piggz: or some init script can do it | 18:08 |
mal | @linusdan you never shower any output from dmesg, it must say something about usb device | 18:08 |
mal | *showed | 18:08 |
Benclark006 | mal: i don't see anything about a failing repo https://gist.github.com/benclarkk/0b6754f35c29610705503a650b3c2cce | 18:11 |
Benclark006 | also, where is the android build tree? | 18:18 |
mal | Benclark006: error: Cannot fetch CyanogenMod/android_device_lge_mako, you should use device repos from lineageos, not cyanogenmod | 18:18 |
mal | same for kernel | 18:18 |
Benclark006 | i see | 18:18 |
mal | android_device_lge_mako and android_kernel_lge_mako | 18:19 |
T4 | <linusdan> mal: output for dmesg: https://pastebin.com/raw/pYAfmNjw | 18:19 |
mal | Benclark006: android build tree is $ANDROID_ROOT you defined earlier | 18:19 |
mal | @linusdan really? you have that little messages in dmesg? | 18:20 |
Benclark006 | ah | 18:20 |
mal | Benclark006: why did you ask? | 18:20 |
T4 | <linusdan> mal: Oops, looks like now appeared something | 18:21 |
Benclark006 | mal: i think i've done a stupid and not defined $ANDROID_ROOT | 18:22 |
Benclark006 | where does is say to do that on the manual | 18:22 |
mal | Benclark006: chapter 4.1 in hadk pdf | 18:22 |
mal | Benclark006: in $HOME/.hadv.env file | 18:22 |
Benclark006 | oh so i /have/ done it | 18:23 |
Benclark006 | nevermind i'm dumb | 18:23 |
Benclark006 | and how do i switch from cm device repos to the lineage ones? | 18:25 |
Benclark006 | sorry for all the questions i'm new to all this | 18:25 |
mal | you defined those in .repo/local_manifests as mentioned in chapter 5.2 | 18:26 |
piggz | mal: blacklisting the driver, then later modprobing it works | 18:26 |
r0kk3rz | orly? interesting | 18:26 |
Benclark006 | i see | 18:28 |
Benclark006 | thanks | 18:28 |
T4 | <It_sMike> @linusdan Don't give up under any situation :) , Sailors are here to help | 18: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_check | 18: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 defconfig | 18:48 |
T4 | <linusdan> mike: Great you did it! … Everything is fine in the kernel | 18: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.1 | 18:51 |
mal | the android base is not the problem probably | 18:52 |
T4 | <linusdan> mal: The usb output of the cellphone appeared, but did not look right | 18:53 |
T4 | <It_sMike> What do you think mal? about this? | 18:53 |
T4 | <linusdan> mal: output appears in [1.976224], line 798 | 18: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 timestamps | 19:10 |
mal | how 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 sailfish | 19:14 |
mal | so disconnect the cable and reconnect and observe host dmesg | 19:14 |
T4 | <linusdan> mal: ok | 19:14 |
mal | how 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 deal | 19:20 |
mal | what 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-1 | 19: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 6 | 19:26 |
mal | pastebin | 19:27 |
T4 | <linusdan> sorry :D | 19:27 |
T4 | <linusdan> I took the battery out to restart and not recognized … Damn! | 19:38 |
T4 | <linusdan> *Not recognize via dmesg | 19:38 |
mal | reflash kernel and see dmesg when you boot it again | 19:42 |
T4 | <linusdan> ok! :) | 19:44 |
Benclark006 | hi again, i'm getting some errors with make hybris-hal and was wondering if anyone could find out what i did wrong, thanks | 20:09 |
Benclark006 | https://gist.github.com/benclarkk/d96ec11ed92d28a6af0efd1d723fb209 | 20: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 T4 | 20:22 | |
mal | Benclark006: how RAM does your computer have? | 20:22 |
Benclark006 | only 4 gb | 20:23 |
Benclark006 | oh i think it's randomly started working now | 20:24 |
Benclark006 | ok so it's now working except it throws an error near the end | 20:30 |
Benclark006 | ninja: error: 'libsf_compat_layer', needed by 'hybris-hal', missing and no known rule to make it | 20:30 |
Benclark006 | nevermind i googled it | 20:36 |
mal | yes, you need to clone android8-initial branch of libhybris to for example hybris/mw/libhybris | 20:39 |
Benclark006 | wow builds do take a while huh | 21:21 |
mal | depends on how fast your computer is | 21:23 |
mal | and amount of memory | 21:24 |
T4 | <elros34> @linusdan: for 3.0 kernel sometimes is better to not enable all cgroup mem configs | 21:24 |
T4 | <elros34> for my photon CONFIG_CGROUP_MEM_RES_CTLR caused bootloop | 21:25 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!