Friday, 2019-08-16

enigma9o7I'm sorry to bother you guys.  I'm just afraid to reboot.03:35
enigma9o7REBOOT AT YOUR OWN RISK.03:35
enigma9o7+ /usr/share/sfos-moto_msm8960_jbbl-adaptation/moto_msm8960_jbbl.sh03:35
enigma9o7FATAL: kernel too old03:35
enigma9o7I thought I followed the appropriate instructions, this isn't my first time trying this,last time I got thru this no issues.03:35
enigma9o7So not sure what I did different.03:35
enigma9o7I decided to try to reboot.03:38
enigma9o7It tells me my kernel is too old.03:39
enigma9o7So, my kernel is too old to reboot.03:39
enigma9o7And I'm advised not to reboot.03:39
enigma9o7So that's why I'm hoping for some help @elros3403:39
enigma9o7The obvious advice on my derror mesasge about the upgrade couldnt be finished again, but if I try that, it says kernel too old.03:41
enigma9o7Hmmmmm I just realized I could try the power button.03:45
enigma9o7I can't edit that.  But anywas it doesnt work.03:45
enigma9o7I stillhave an open ssh to it that is responding.03:46
enigma9o7But power button the device isnt responding.03:46
enigma9o7I'm considering unplugging my usb cable, at which point I'll loose ssh access I think.... maybe not thru wifi...04:02
enigma9o7but nothing else to try, I'm doing it.04:02
enigma9o7Well appears like device is bricked.  But, considering it was still responding to ssh, maybe not.  I guess I have to wait til battery dies?04:02
enigma9o7Unplugging usb, still can't use power button, and still have ssh thru wifi.04:04
enigma9o7I have no other thought at this point besides letting battery drain.  So I'd appreciate some advice.04:07
enigma9o7To summarize, I cannot reboot or shutdown or do any single command cuz it says kernel too old thru ssh.  I cannot shutdown from the device as the button and UI is unresponsive.04:09
enigma9o7btw, I've bricked my phone05:38
enigma9o7I tried touching corners.05:39
enigma9o7That seemed like an odd suggestion, but Ill try anything.05:39
enigma9o7I can't wipe/ and start over cuz the phone is inresponvie. I'm hoping if I wait til battery dies it'll reboot with somethingI can do something with.05:40
T42<austenite> ive had a strange bug in my port , i was taking log with ofono logger app, i  removed developer settings and closed settings app while it was doing it05:58
T42<austenite> and the developer settings were not removed but all jolla apps have deleted themselves and now bootloop05:59
enigma9o7That sounds frustrating.06:00
enigma9o7I was in cousneling, and I learned, when your wife compalins, she doesnt actually want a solution, she just wants you to agree it sucks.06:01
enigma9o7It sounds pretty retarded to me, cuz then nothing moves forward, but hehy, if it makes you feel better.06:01
enigma9o7So I'll try applying it to this situation.  Instead of trying to help you sovle your problem, I'll just sympathize.06:03
enigma9o7It may sound coutner productive, but somehow it's supposedly better.06:04
T42<austenite> well there is a twist in the story, before losing all jolla apps, the settings and terminal were still functioning , but top panel had no buttons only ambiences, then the settings went away and i restarted phone —> bootloop06:04
T42<austenite> someone can reproduce this, this might be dangerous bug06:07
T42<birdzhang> how do you removed developer settings?  via terminal or UI ?06:10
T42<austenite> removed developer settings through Ui, got message ;removing developer settings' , closed the settings app—> open settings ——> developer options still there —-> try to remove again —> all jolla apps gone06:12
enigma9o7I have accientaly removed eveloper settings twice.06:14
enigma9o7So it's easy very to do.06:14
enigma9o7All you have to do, to my understanding,is accidntally tap on it once.06:15
enigma9o7Both times I did it, I just reflash sfos to srart over.06:15
T42<austenite> nah, you can reinstall developer settings without reflashing sailfish06:16
enigma9o7cuz based on a brief web search, if ou remove deeloper optionsk hou cant get em back06:16
enigma9o7Yeah, I'm definatley could be wrong.06:17
enigma9o7I dont know anhything.06:17
enigma9o7I just know I couldnt figure it out so reflashed.06:17
enigma9o7And, unrelated, I'm jus twaiting til my phone battry dies so I can try again06:18
T42<austenite> what did you do enigma9o706:19
enigma9o7I dunno.06:19
enigma9o7I really dont.06:19
enigma9o7I thought I install liked normal/06:19
T42<austenite> and it bricked by itself?06:19
enigma9o7I flash cm11, boot, flash sfos, boot, update, and now...06:20
enigma9o7I've done the exact same thing before succesfullyh.06:20
enigma9o7Now my phone led is red, and wont do anything.06:21
enigma9o7But I can ssh into it.06:21
T42<austenite> @enigma9o7 which thing? you havent mentioned what you did06:21
enigma9o7I said what I did. I flash cm11, boot, flash sfos, boot, udpate.06:22
T42<austenite> ah, you have obs to update? if not you should not update06:22
enigma9o7Which is the procedure described on xda, and I've done it bore, sucesfully.06:22
enigma9o7The problem is I'm a sfos beginner.06:23
T42<austenite> well, you seem to have different problem from mne, but we both have to reflash :)06:23
enigma9o7So I dont even know what you're asking.06:23
enigma9o7But, I'm not a cli retard, I do run linux.06:26
enigma9o7And I consider myhself an expert indos batch filez.06:26
enigma9o7If that matters 20 years ago.06:26
enigma9o7Good day saidenesh!06:27
T42<elros34> enigma9o7: Fatal: kernel too old means you did not added glibc repo like explained in OTA instruction in xda. Be aware  I didn't uploaded 3.1 yet.07:15
T42<elros34> also you can always poweroff device: hold volume buttons and power button for few seconds07:22
enigma9o7ok thanks elros07:52
enigma9o7Yeah ok the fifst time, I did your line by line cli commands.07:53
enigma9o7This time I just ran your script07:53
enigma9o7I'm about to try to hold voluem and power buttons, lets see07:54
T42<elros34> yeah, I didn't added patched glibc repo to for 3.0.2 version so you needd to manually add it07:54
T42<elros34> I will upload 3.1 image when it will be ready to avoid this glibc fail reports07:55
enigma9o7I cantget it to do anything with holding the buttons.07:55
enigma9o7I feel it vibrate, but nothing happens.07:55
T42<elros34> it must work because it's hardware way for powering off device without removing battery07:56
enigma9o7I wish I could do something.07:59
enigma9o7But holding buttons doesnt do anyting useful.07:59
enigma9o7I think I just hav eto wait til battery dies.07:59
enigma9o7sfos is still running cuz i can ssh into it07:59
enigma9o7but pq just has red led.08:00
T42<elros34> volume keys + power button is not sfos thing, it's Photon Q hardware thing, it always works. Hold it for 10s08:01
enigma9o7im wrong08:01
enigma9o7i just tried holding everything at once08:01
enigma9o7itsrebooting now08:02
enigma9o7It didnt work with just one volume button (at leas that I saw) but when I held both volume bottons plus power, it rebooted, and keeps showing my boot logo08:03
enigma9o7(which I havent yet changed to the sfos one, but I plan to, fyi)08:03
enigma9o7But it shows it a while, then black screen, then shows it again08:03
enigma9o7Still repeating.08:04
enigma9o7balck scren, bootlogo, black screen, bootlogo.08:04
enigma9o7over and over08:04
T42<elros34> like I said volume keys08:05
enigma9o7that's how I got here.  but ok.08:05
T42<elros34> no I mean 2 volume buttons are required to poweroff08:05
T42<elros34> Fixing sfos will be too hard now. I think you should reflash it08:06
enigma9o7I just treid again.08:06
enigma9o7You mean just hold both volume w/o touching the power button?  I'll try that now.08:06
enigma9o7ok it brought me to fastboot08:07
enigma9o7And in my experience, all i do here is flash twrp.  which has been done and done.08:07
enigma9o7Ok I'm more than happy to reflash.08:09
enigma9o7And then wait over an hou rfor updates.08:09
enigma9o7But question first.08:09
enigma9o7I obviously did it wrong by just running your script.08:09
enigma9o7Previusly I executed every command line by lind to watch for whatever.08:09
enigma9o7Is there something I should do diffferently?  Install then run your uipdate script again?08:10
enigma9o7(Assuming I can reboot to twrp and reflash sfos)08:10
enigma9o7fyi, i dunno if you read my xda post, but one of the reason Im installing sfos on this device, is I plan to plug it into a lapdock 500, whichi  just receivec today.08:12
enigma9o7I already tested it with cm11 which doesnt work well for video08:12
T42<elros34> hdmi dos not work in sailfish. I tried patched qt5-qpa-hwcomposer-plugin which works for example on allwiner tablet but on photon it fails08:13
enigma9o7One question, when this sfos reinstall is done, is there any way to sk9p the tutorial?08:13
enigma9o7I've seen it more than enuff times.08:13
enigma9o7Right now I'm waiting for the tarball whatever to extract.08:14
enigma9o7But I know that when it's done I haveto login to jolla then go thru that tutorial yet again.08:14
T42<elros34> touch corner clockwise starting from top left08:14
T42<elros34> for ota to 3.0.3 read "# Transition from 3.0.2 to 3.0.3" in xda08:15
enigma9o7thank you so much08:16
enigma9o7I really think that tutorial is very very useful the first time using sfos, but after that, it is very hard to abort.08:16
enigma9o7elros, do you think its gunna work in lapdock 500?08:18
enigma9o7I'm qiute anxious to try.08:18
enigma9o7I actually was ready to try like 10 horus ago.08:18
enigma9o7Until these issues.08:18
T42<elros34> I already answered 5 minutes ago that hdmi will NOT work08:18
enigma9o7Oh really.08:18
enigma9o7Sorry I didnt read yet.08:19
enigma9o7That's disappointing.08:19
enigma9o7Very disappointing.08:19
enigma9o7It doesnt work to laptop, or you mean to tv too?08:21
T42<elros34> What is unclear in: HDMI does not work in sailfish at all. Here is code which needs to improved to make it work on qcom devices
enigma9o7Ok,ijust read your xda post, more technicalthan i understand, but no worries08:23
enigma9o7Now I dont have to worry about making sfos work again, Im going back to jellybean.08:24
enigma9o7Oh... but I still gotta get back to twrp08:24
enigma9o7Of couse I'm super disappointed cuz I thought I'd have a sfos netbook.08:25
enigma9o7Hey elros, give me your mailing adress and I'll give ou this netbook if you amke it work undersailfish os08:25
T42<elros34> I tried to make hdmi work on my TV but I failed, netbook will not help.08:26
enigma9o7All this is is usb and hdmi with weird resolution.08:28
enigma9o7Although that is also kinda annoying, sfos on pq cant even use hdmi?08:28
enigma9o7under android i used to hook it up to motel tvs to watch movies on business travel08:28
enigma9o7had to order that mini hdmi to regular hdmi cable08:29
enigma9o7but had it for years08:29
enigma9o7When I was readinga bout how to use this netbook under android, and why CM/LOS dont work right, is something weird related to it sresolution not being standard 720p/1080p hd, its like 1366x768 (off the top of my head) but the first number wasnt divisibile by 808:31
enigma9o7which caused problems with something08:32
enigma9o7but this is all random info in my head08:32
enigma9o7damnit i hate it when im so drunki have to cover one eye to focus on the screen08:35
enigma9o7Im slow.09:15
enigma9o7wiped and insralled09:15
enigma9o7gunna login and abort that intro soon09:15
enigma9o7once this circle stops spinning09:16
enigma9o7unfortunateoy im retarded nd drunk and dont remember details and using irc2 and cant scrollack or serach effectiely09:17
enigma9o7i suck at passords09:20
enigma9o7i think we shoujdl elimate them09:20
enigma9o7i mean jus t trust each other09:20
enigma9o7why should i have to remember my password09:21
enigma9o7if someobdy else uses my name, they know theyre lieing09:21
enigma9o7so basifalluy they're commmiting fraud, if tey wanna kdo that let mthem09:21
enigma9o7why do i have to rmeember complciated passwords ust to pvenet fraud09:22
enigma9o7in he olden days i didnt need to reemember so much bs,09:22
enigma9o7I said who I was, unless anyone objected, i mme09:23
ghosalmartinmal: managed to get to  bt_vendor: Bluetooth Firmware and transport layer are initialized10:33
ghosalmartinprocess was start the service, then run bluebinder, then do rfkill unblock and that was it10:34
ghosalmartinoh and I had to modprobe bluetooth-power10:37
ghosalmartinhmm no /dev/socket/rild11:07
malghosalmartin: do you use ofono binder plugin, it should be used for 15.111:12
malI think usually11:12
ghosalmartinmal: dont think so but ill take look11:13
ghosalmartinmal: would I have a normal rild binary and a binder binary?11:14
malghosalmartin: rild11:14
malghosalmartin: does logcat -b radio show anything?11:15
maljust to check if ril is working11:15
ghosalmartinmal: yeah its showing some stuff11:16
ghosalmartinam guessing without the ofono binder no /dev/socket/rild appears?11:16
malghosalmartin: then build and install and configure ofono
malghosalmartin: there is no /dev/socket/rild11:17
ghosalmartinah okays11:17
malghosalmartin: for testing build that plugin on OBS, install and then copy the config to device manually11:18
ghosalmartinokays ill give that a shot thanks11:18
ghosalmartindoes the binder stuff rely on HAL headers?11:18
malghosalmartin: usually no11:20
malnormally we include the needed things in a header11:20
ghosalmartinunresolvable :(11:20
malghosalmartin: fixed it for you11:22
maljust a bit older version was needed11:22
ghosalmartinahh awesome :)11:23
malghosalmartin: usually in such cases you can check the changelog of most recent release for the version used on official devices11:23
ghosalmartinhmm nothing so far11:27
ghosalmartindo I need to stick a sim in there or will no sim show up11:28
ghosalmartinwell it worked when I booted and start ofono manually11:39
ghosalmartinmaybe its a waiting issue11:40
malghosalmartin: check journal for anything after boot11:46
*** kimmoli_ is now known as kimmoli12:02
ghosalmartinhmm maybe droid-hal-init: Sending signal 9 to service 'qti' (pid 1150) process group... HYBRIS: killing PID instead of process group.12:47
ghosalmartini cant remember what qti is for now12:47
malit's one of the important low level qcom things12:48
ghosalmartinfor modem possibly? :P12:49
malnot sure but could also affect that12:49
malghosalmartin: can you show what you have in out/target/product/bullhead/root/12:50
malghosalmartin: also is this current version show the spec you use for 15.1 build12:52
ghosalmartinnah its this one
malghosalmartin: missing /vendor12:58
malghosalmartin: try in device first, add /vendor symlink pointing to /system/vendor12:59
ghosalmartinmy vendor mount is a seperate partition of /vendor12:59
ghosalmartinso the symoink breaks the mount13:00
malghosalmartin: hmm, then why is the build creating the symlink, something is wrong13:00
ghosalmartinmal: historically its always been like that tbh13:00
ghosalmartinmal: its odd that if i mask ofono, reboot and then unmask and start ofono it works, i put in sim it detects but no signal13:01
ghosalmartinmal: hmm seems to of just started working?13:04
ghosalmartinmal: so seems loaded but no signal with sim in13:09
malcheck logs13:10
malbut probably you should fix the failing android side services13:10
malprobably some simple thing is missing causing things to fail13:13
ghosalmartini think this mabe?13:13
ghosalmartinopenat(AT_FDCWD, "/dev/rmnet_ctrl", O_RDWR) = -1 EBUSY (Device or resource busy)13:13
ghosalmartinopenat(AT_FDCWD, "/dev/rmnet_ctrl", O_RDWR) = -1 EBUSY (Device or resource busy)13:13
ghosalmartincauses qti to fail13:13
ghosalmartinor failure to open /dev/diag13:14
ghosalmartinthis also a possible openat(AT_FDCWD, "/etc/qmi_fw.conf", O_RDONLY) = -1 ENOENT (No such file or directory)13:15
maldo you see qmi_fw.conf on device?13:15
maldoes it try another location, sometimes it does13:15
ghosalmartini thought itd be in /system/etc13:15
ghosalmartinalthough maybe /vendor/etc13:15
ghosalmartinis there a utility to check whose using what under /dev13:17
malghosalmartin: show full logcat after reboot13:18
ghosalmartinmal: okays13:18
maldmesg also13:18
ghosalmartinam willing to bet money its the qti13:19
ghosalmartinsince it logs finding internal modem13:19
malcould be something related to that, rmnet is very important also13:21
ghosalmartinam going to upload them to
ghosalmartincan you see them?13:22
ghosalmartinmal: ah I think the reason its breaking is breaking qti is already running fine13:23
ghosalmartinps -ax shows it13:23
malghosalmartin: does pid change?13:25
malI can see the logs13:25
ghosalmartindoesnt seem so its 1888 so pretty early13:26
malghosalmartin: based on log it restarts once and the seems stable13:33
ghosalmartinmal: are the ril_subscription settings right?13:33
ghosalmartinthis bit seems suspect SetRadioCapability=off13:33
malghosalmartin: those might need adjusting13:37
malon some devices13:37
ghosalmartintried that with no real luck13:37
mallogcat -b radio should show if there are issues13:37
malbut the qmi errors in logcat are bad13:37
malqmi is the protocol used for modem for example13:37
ghosalmartinseems so13:42
ghosalmartinam going to have to shoot of13:42
ghosalmartinthere are errors in logcat -b radio but nothing obvious13:42
ghosalmartinmal ^^ thats them if theres anything obvious but it seems not so obvious, for me atleast13:44
ghosalmartinmal: signal seems to of tunred up haha14:02
ghosalmartintexts are failing at the moment but ringing it seems to work14:02
albertus1chapter 8.1 of HADK says, I should clone the respective repository AND then use `rpm/dhd/helpers/ --mw=<GIT_URL>`. is this correct, that I have to clone it manually beforehand? I don't understand why I provide the GIT_URL to then14:52
malalbertus1: rpm/dhd/helpers/ --mw=some_url clones the repo, rpm/dhd/helpers/ -b some/local/path doesn't14:53
albertus1okay, so I don't need to manually clone beforehands, thanks14:54
mal@austenite you cannot remove developer mode from community build currently, it will remove everything15:16
mal@austenite the reason is that developer mode is in patterns so removing one package will remove that pattern15:18
T42<austenite> mal : it worked before , i mean when i removed the developer options, the terminal was gone and when i enabled developer tools was installed from internet15:19
T42<austenite> but i added some prebuilt apps in recent build, i think that caused some trouble? im not sure if its relevant15:20
albertus1running MIC, I got the error saying "repo problem: pattern:jolla-configuration-h3113-1-1.noarch requires droid-config-h3113-bluez5, but this requirement cannot be provided, not installable providers: droid-config-h3113-bluez5-1-1.armv7hl[adaptation-community-h3113-]"15:30
albertus1now I did as specified in HADK chapter 8.5 and replaced in the .ks file the line "@Jolla Configuration h3113" by "droid-config-h3113-bluez5", and then MIC seems to have succeeded, it did quite some downloading and installing, but it said no files matrching attachmants /boot/hybris-{boot,recovery}.img and /etc/hw-release15:32
albertus1Now it's asking "Failed to apply RootPasswordConfig, skip and continue?(Y/n) "15:32
albertus1should I have come this far with the modified .ks file anyway?15:32
albertus1or should I have put droid-config-h3113-bluez-1-1.armv7hl in the .ks file instead?15:35
malsomething is conflicting with droid-config-h3113-bluez5, what repos are you using?15:41
albertus1how do I tell/know?15:41
albertus1I closely followed this guide:
albertus1and, apparently, don't know details of some of the things I've done by that15:43
albertus1it's probably something along the lines of
malwondering what the conflict is15:47
malalbertus1: which release did you try to build?15:51
albertus1I have no idea15:51
albertus1"no idea" was referring to "what the conflict is"15:52
malalbertus1: "not installable providers: droid-config-h3113-bluez5" means there is some conflict that is preventing installation of that15:55
albertus1that's what I understood from HADK, too15:56
albertus1I'd like to find out, too, but like I said, putting that in the .ks instead of the @Jolla-..... pattern just seems to have gone too far somehow16:07
malyes, it seems it didn't help determining the conflict16:08
albertus1here's what it did with that .ks modification:
albertus1well, I actually commented out the @Jolla-.... line, not delete it. could that have been wrong?16:09
malthat is of no help16:10
malwe need to find the issue some other way16:11
malcan you show the .ks file16:11
malseems ok, can you show your hybris/droid-configs/patterns/jolla-hw-adaptation-$HABUILD_DEVICE.yaml16:15
malalso hybris/droid-configs/patterns/jolla-configuration-$DEVICE.yaml16:22
malI don't see anything obviously wrong in those16:25
albertus1hm, that's probably a good thing, but leaves me without a clue how to analyse the issue further16:35
T42<AnonGhost_3301> is there any build available for ze550kl17:55
T42<AnonGhost_3301> ?17:55
albertus1mal: please let me know when something comes to your mind that I could try in order to bog down my conflict18:17
malalbertus1: I need to think a little and look at logs to see if someone had similar issue18:18
albertus1sure. I won't be around before Sunday evening, but I'll look into the logs just in case you come up with an idea in the meantime18:20
ghosalmartinmal: did pulseaudio need anything special?19:34
malghosalmartin: not really19:38

Generated by 2.17.1 by Marius Gedminas - find it at!