*** ChanServ sets mode: +v T4 | 08:45 | |
mpol | Hi people. Just yesterday I received an old Samsung Tab 2. I see there is a port for the 3100, but I have the 3110. Can I just follow the install instructions for 3100? Or is the hardware too different? | 11:03 |
---|---|---|
wdehoog | mpol: which instructions? the 3110 is the one without 3G isn't it? | 11:33 |
mpol | yes, instructions from: https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/sfos-sailfishos-galaxy-tab-2-p3100-v2-0-t3355597 | 11:34 |
wdehoog | abranson: I patched gst-plugins-base see: https://git.merproject.org/wdehoog/gst-plugins-base/blob/1.14.1-wj/rpm/ | 11:34 |
mpol | It uses CM11, but that one is gone apparently. So wondering if a CM13 for the 3110 will work with that SF zipfile :) | 11:34 |
wdehoog | abranson: this also seem to work. I added the environment variables to /var/lib/environment/nemo/60-multimedia.conf | 11:35 |
wdehoog | abranson: but I hope there is a better location to add them so it is easier to test | 11:35 |
wdehoog | mpol: sfos and cm version belong together. mixing them will probably fail | 11:37 |
mpol | so with CM11 gone for this device, all hope is lost? | 11:38 |
wdehoog | long time ago I tried one of these: http://yacuken.me/espresso3g/sfos/ | 11:39 |
r0kk3rz | you'd want to rebuild it | 11:39 |
r0kk3rz | that port is super old too | 11:40 |
mpol | yes, but that one is for the 3G model (3100), not the wifi model (3110). Will that CM work? Or could I try that SF zip for CM12 on CM13? | 11:40 |
mpol | yes, it is a really old port :) | 11:40 |
mpol | rebuild SFOS? | 11:40 |
r0kk3rz | yeah | 11:41 |
r0kk3rz | if the cm base image for the 3g version works, then you could maybe flash it | 11:41 |
wdehoog | would these work: https://androidfilehost.com/?w=files&flid=51210&sort_by=date&sort_dir=DESC | 11:42 |
mpol | okay. I would be interested in updated SFOS for it too, but I am only before the first steps, so no point in planning yet | 11:42 |
mpol | okay, so different routes to go. Preferably using the CM12 for 3G first, see how that fares | 11:43 |
mpol | wdehoog: thanks, that link looks interesting for updates | 11:43 |
T4 | <elros34> gone? there are mirrors for cm like http://cyanogenmod.altervista.org/ | 11:43 |
wdehoog | mplo: yacukens images also "work" on the 3110 but installing was complicated since it checked for 3100 | 11:44 |
mpol | wdehoog: thanks, that is good to hear | 11:44 |
abranson | wdehoog: thanks! | 13:12 |
wdehoog | abranson: I tested with sailsoma and shoutcast-sailfish, flags does not seem to have any effect | 14:15 |
wdehoog | abranson: buffer_size 128000 seems to work, less results in hickups, I use 256000 now just to be sure | 14:16 |
wdehoog | abranson: side note: I tried to add env to a desktop file but then I get | 14:17 |
wdehoog | Sailfish mapplauncherd[6175]: Booster: Failed to invoke: Booster: Loading invoked application failed: '/usr/bin/env: cannot dynamically load executable' | 14:17 |
entil | hi! is it common for the fp2's camera to break after upgrading? http://paste.debian.net/1058229/ | 14:47 |
mal | entil: no | 14:49 |
entil | mal: voi räkä :( | 14:49 |
entil | appears the main camera on my xperia x is physically broken and both cameras on the fp2 are mentally broken | 14:50 |
mal | entil: does /etc/dconf/db/vendor.d/jolla-camera-hw.txt look ok? | 14:50 |
*** ChanServ sets mode: +v T4 | 14:50 | |
entil | mal: I'll show it in just a moment, I don't know how to read it | 14:50 |
entil | mal: http://paste.debian.net/1058230/ that stuff? | 14:51 |
mal | entil: the upgrade instructions tell how to fix that | 14:52 |
mal | entil: https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_fp2#Status the camera stuff in that | 14:52 |
entil | mal: naturally I skipped on to the upgrade instructions to see there's nothing special, but I'll look at that, thanks | 14:53 |
entil | mal: where did the regression come from? | 14:53 |
mal | it has always been there | 14:54 |
entil | so it worked by accident? | 14:54 |
mal | entil: after running the commands you can check that /etc/dconf/db/vendor.d/jolla-camera-hw.txt doesn't have stuff like @PRIIMAGE43RES@ | 14:54 |
mal | entil: no it broke by accident, it works most of the time but sometimes fails | 14:54 |
mal | my script has always been like that | 14:55 |
mal | maybe I should improve the script to detect failures | 14:55 |
entil | mal: is it expected to reboot the phone? | 14:55 |
mal | I have had random issues that camera reboots the phone | 14:56 |
entil | ok, then I'm not panicking yet, just restarted the detect again | 14:57 |
entil | mal: zomg thanks for the help | 14:58 |
entil | but the status description about resolutions for camera blabla might benefit from an update, maybe, because now that I have everything fixed and can better review what happened, there's no way I would have drawn the connection between "failure of finding resolutions" to some initialization error and gstreamer locking problem :/ | 15:00 |
mal | entil: indeed, gstreamer errors are not very descriptive | 15:09 |
mal | entil: one option is to grep the resulting file and detect if it was signs of failure and then rerun droid-camres in the script | 15:13 |
entil | mal: I might remember what to grep for in the irc logs next time this happens but now I have to figure out why gnupg2 on the xperia x is fucked | 15:15 |
entil | I wish it had zypper :( | 15:15 |
mal | entil: pkcon install zypper? | 15:15 |
kimmoli | and as it might fail after update, pkcon refresh | 15:16 |
entil | Fatal error: File './armv7hl/droid-hal-version-f5121-0.2.1-1.2.13.jolla.armv7hl.rpm' not found on medium 'https://store-repository.jolla.com/releases/3.0.0.8/jolla-hw/adaptation-qualcomm-f5121/armv7hl/?credentials=store' | 15:17 |
entil | voi ny vittu oikeesti | 15:17 |
entil | but this is not the channel for it, this is the commercial version | 15:18 |
mal | entil: pkcon refresh | 15:18 |
entil | mal: really? wtf... maybe storeman doesn't refresh everything, or settings lies when it says everything is up to date ":D" | 15:19 |
mal | entil: not sure what repos storeman refreshes, maybe only the ones it uses | 15:20 |
entil | mal: yeah, maybe, that would at least fit the symptoms... but now I gotz a new gnupg2 and qmlpass works again, thanks! | 15:21 |
entil | qmlpass broke at some point and I didn't care, no idea what happened, but probably only a gnupg2 downgrade and some confusion about what's available, fixed by `pkcon refresh` | 15:22 |
mal | it's common that after upgrade repos are not refreshed properly | 15:22 |
entil | gotta try to keep that in mind | 15:23 |
mal | entil: about fp2, there is now a testing repo that brings HDR and other stuff via a community camera app | 15:23 |
entil | but sweet, I was worried for a while that I broke the camera on the fp2 as well.. considering how much I've had to mess around with the hardware, and having the camera on the xperia x broken, I was like not needing all that | 15:23 |
entil | mal: as in high dynamic range? | 15:24 |
mal | entil: yes | 15:24 |
mal | the app is a very rough version still but a good start | 15:25 |
entil | I might wait a while, then, because I barely use the camera :/ | 15:25 |
mal | I should do some testing to see if I can move the needed middleware to common so every device can use it | 15:25 |
mal | entil: I also rarely use the camera | 15:25 |
entil | maybe it's about commercial codecs or something but the pictures never looks as good as if the missus takes pictures with her lg phone | 15:26 |
entil | anyway, I need to go now that everything works; good job, thanks! -> | 15:26 |
T4 | <BusterBg_18> Hi everyone, I have some problem with sensors, can't get the screen to rotate, and light and proximity sensors aren't working, but a toggle for auto brightness and flashlight is present | 15:38 |
mal | which device? | 15:57 |
T4 | <BusterBg_18> Redmi note 3 a.k.a kenzo | 16:01 |
mal | which sfos release? does test_sensors return sensor list? | 16:03 |
mal | does the device have /usr/share/csd/settings.d/hw-settings.ini ? | 16:03 |
T4 | <BusterBg_18> 3.0.0.8 didn't try test_sensors … yes that file is present | 16:05 |
mal | did the sensors ever work? | 16:08 |
T4 | <BusterBg_18> Yes, without a problem | 16:10 |
mal | what did you do? update sfos or something else? | 16:11 |
T4 | <BusterBg_18> Rebuilded on another hdd with synced repos from github | 16:15 |
mal | are you sure nothing is missing from the build? check logs, dmesg, journalctl and /usr/libexec/droid-hybris/system/bin/logcat | 16:16 |
T4 | <BusterBg_18> Im going to check, firstly on pc and then on logs | 16:18 |
T4 | <adampigg> @eugenio_g7 try this kernel out https://github.com/piggz/android_kernel_xiaomi_latte/tree/hybris-13.0-latte-bcmdhd | 16:56 |
T4 | <adampigg> mal^^ thats my re-write with history | 16:56 |
T4 | <adampigg> only issue seems to be it doenst remember the netwroks across reboots | 16:59 |
T4 | <adampigg> maybe the mac is chaning | 17:00 |
kimmoli | that is usually due random mac | 17:00 |
T4 | <adampigg> ;) | 17:00 |
T4 | <adampigg> it actually not random though ... matches the content of /config/wifi/mac.txt | 17:01 |
kimmoli | i have that still on onyx, but it is bogus only after twrp flashing, reboot once and it is ok | 17:01 |
T4 | <adampigg> wlan0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT qlen 1000 … link/ether ac:c1:ee:9a:26:87 | 17:01 |
T4 | <adampigg> cat /config/wifi/mac.txt … ACC1EE9A2687 | 17:02 |
kimmoli | well at least it is xiaomi oui | 17:02 |
*** ChanServ sets mode: +v T4 | 20:14 | |
T4 | nicosouv was added by: nicosouv | 23:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!