Friday, 2019-09-13

ghosalmartini have a lovely "Networking is not available. Please restart deviec". Has a particualr service failed?10:10
ghosalmartinmal: any idea if keystore needs selinux_stubs13:49
malnot sure13:50
ghosalmartinactually feels like it should be disabled13:50
malghosalmartin: it's running on xa2 and x1013:53
ghosalmartinhmm okay disbling for me seems ield some results but android.frameworks.schedulerservice seems to be holding up the show13:56
ghosalmartina quick disable of te sensor service and things seem to work14:10
ghosalmartinmodem is up and running14:15
ghosalmartini had to manually set setprop sys.time.set true14:16
ghosalmartinotherwise everything halted14:16
ghosalmartincamer works too14:16
ghosalmartinbluetooth is trying to enable but hten failing :(14:17
ghosalmartinnot sure why wifi doesnt work, the module is loaded or it attempts it atleast14:17
malghosalmartin: update bluebinder14:23
ghosalmartinmal: to the latest?14:23
malghosalmartin: that had hardcoded commit hash in the service14:24
ghosalmartinalso any idea where this would go14:24
ghosalmartinsetprop sys.time.set true14:24
malnot sure14:24
ghosalmartinive set it as a post to timed-qt5 but wo knows14:24
ghosalmartindoes it fix this error by any chance? :P android.hardware.bluetooth@1.0-impl: VendorInterface -> Unable to call initializationComplete()14:25
malhmm, not sure14:28
ghosalmartinwe'll find out soon14:28
malit had fixes to various timing issues etc14:28
ghosalmartinno dice14:30
malanything in journal or logcat, other than that one message?14:31
ghosalmartintons of stuff14:32
ghosalmartinbt just keeps reiniting14:32
maldoes the bluetooth android service keep restarting or something?14:33
ghosalmartinthis is an iteration
malso probably some other issue then14:33
ghosalmartinbloody rome chipset14:33
ghosalmartinive gotta head off14:34
ghosalmartinthis device is shaping up okay. i think soon itll be cheap enough to be the commnity option like the nexus 5 was14:34
malghosalmartin: maybe related to wifi issue you have, those are often in same chip afaik?14:34
ghosalmartinmal: could be tbh. but that could just be because I installed the wifi module over zypper dup rather than a fresh zip14:35
malghosalmartin: btw, check rfkill to see what it lists14:35
ghosalmartinbt is there, no wlan14:35
ghosalmartinnot blocked on either14:36
malso only 1 for each wlan and bt?14:36
malwhich ones?14:36
ghosalmartinnah just bt14:38
ghosalmartinbut not soft or hard blocked14:38
malghosalmartin: maybe first focus on fixing wifi, then bt if it's not fixed after wifi14:46
malghosalmartin: does it find wifi firmware?14:46
electro5hi mal, do you see an error here ?
electro5i have no logcat access14:53
electro5who can help me just a minute with this log ?
electro5end of log, my phone restart without display GUI15:38
electro5why this ? droid-hal-init: Sending signal 15 to service15:40
electro5mal, systemd[1125]: Failed to start Load initial part of start-up wizard before user session begins.15:41
electro5@elros34 : maybe you can say to me the main problem15:41
electro5Sailfish kernel: hcismd_set_enable 115:42
electro5Sailfish kernel: hci_smd_register_smd: Cannot open the command channel15:42
electro5mal, i have a 32 bit cpu15:49
T42<elros34> remove this broken service for loading bluetooth15:49
electro5the old ofono is build with 32 or 64 bit ?15:49
electro5Sailfish droid-hal-init: loglevel: invalid log level 6416:03
electro5i have 32 bit cpu16:03
maldo not think about 32-bit vs 64-bit, only place you might need to think about that is if you need to use selinux_stubs16:04
electro5Sailfish kernel: unknown_usb_detect_worker16:04
electro5mmc0: data txfr (0x00100000) error: -110 after 5369 ms16:04
electro5sdhci: =========== REGISTER DUMP (mmc0)===========16:05
electro5i don't know what i must do to continue debugging :
electro5mal, it's maybe the ofono version 1.0.4 for htc16:21
electro5@elros34 : have you an idea ?16:21
electro5why this ? Sailfish ueventd: Unable to open '/ueventd.qcom.rc': No such file or directory16:21
r0kk3rzsounds like a straight forward message16:23
Mister_Magisterr0kk3rz: some people can't read16:24
malr0kk3rz: I thought we have disabled ueventd stuff and use udev instead16:25
r0kk3rzmal: yes thats true16:26
T42<PacoLanciano> mal: i managed to boot, (deleted everything and started from cm13) but i have only one issue... every 20/30 seconds the display turn off and then after some seconds lights up on the lock screen. i can see also some artifacts when i am navigating in the UI20:03
T42<PacoLanciano> in logcat i can see ServiceManager: service 'display.qservice' died when this happen20:04
piggz_monich: any progress on your miband ?20:09
monichpiggz_: I killed it trying to flash it :)20:20
monichI've ordered one more to give it another try20:20
piggz_monich: oh no!20:20
Mister_Magistersacrifices were made20:21
piggz_monich: do u know where u went wrong?20:22
monichpiggz_: I managed to flash wrong firmware, it became Wuhan and refused to reflash20:23
piggz_monich: ah, someone did that with amazfish ... flashed a bip firmware to a cor!20:23
piggz_they sent me their dead cor ... i cant do anything with it20:24
piggz_monich: so, can i expect a PR on amazfish adding support?20:26
monichpiggz_: not sure yet20:29
mal@PacoLanciano did you add the QCOM_BSP changes?20:34
T42<PacoLanciano> mal: i'm rebuilding now after adding QCOM stuff20:35
piggz_monich: cmon, u wont write a new cos of NIH? :)20:36
piggz_mal: any other ports using pulseaudio-modules-droid-hidl?20:37
malpiggz_: that is for android 9+ qcom devices afaik20:39
piggz_mal: so, im in the minority then!20:40
T42<PacoLanciano> mal: same problem20:54
malthen you need to figure out from logcat why the display service fails20:55
T42<PacoLanciano> if i run strace lipstick as nemo it fails with write(2, "[C] unknown:0 - Failed to create"..., 69[C] unknown:0 - Failed to create display (No such file or directory)21:11
maldo not take just parts of the logs, the real reason can be anywhere in the logs21:29
Mister_Magistermal: vendor.dataqti vendor.imsrcsservice vendor.ims_rtp_daemon any of those needed? well dataqti is useless but what about other two?21:30
T42<PacoLanciano> ok21:33
mal@PacoLanciano just to be sure, did you use correct kernel and so on, you said moved to cm13 (from what?)21:46
T42<PacoLanciano> yes, i started from the working porting by zhxt21:48
T42<PacoLanciano> so i used his repos21:48
malso why doesn't it work then if you used the same repos21:48
T42<PacoLanciano> it's a porting of  SFOS , i wanted to build last version, i don't know why gives me some problems21:51
malI saw similar errors in logs from 2 years ago, in that device those were caused by broken hwcomposer in kernel21:51
malbut if you say those repos used to work then in must be something else21:52
T42<PacoLanciano> in known issues section there is something about lipstick, i can check21:53
malthat mentions hwcomposer workaround21:57
T42<PacoLanciano> can be my issue?21:59
malso you are using the local manifest mentioned in that?21:59
T42<PacoLanciano> @mal [so you are using the local manifest mentioned …], yes, i only changed vendor repo because its unavailable due to DMCA takedown with a legacy version22:02
maloh, themuppets is gone, that's not nice22:05
malwell only that one repo it seems22:07

Generated by 2.17.1 by Marius Gedminas - find it at!