Saturday, 2020-02-08

Oksanapiggz: QDL tool? Link, please? With detailed instructions. vknecht: Reading, thank you. No NetworkManager, I think - I am using Devuan ASCII/Beowulf with wicd. T42: Yes, laptop is Linux. As for Qualcomm USB flashing tool, the device is currently in QDL mode, not EDL mode?00:00
piggzOksana: notkit gave the links00:00
piggz[11:15] <T42> <NotKit> another possibility may be to reflash with Linaro and firmware from
piggz[11:17] <T42> <NotKit> sudo ./qdl --storage ufs prog_ufs_firehose_8998_ddr.elf rawprogram_8998.xml patch_8998.xml00:01
piggz[11:18] <T42> <NotKit> will erase everything, but should bring it out of brick state00:01
evelynif I look in the items mounted, the only thing outside of the chroot that gets mounted is indeed my home directory00:04
evelynit's not clear how I could tell sb2 to mount other directories in the chroot, assuming it does just ignore ANDROID_ROOT00:05
Oksanapiggz: Thank you. But it also speaks of EDL mode, see . The device currently seems to be in QDL mode, even though it does have QUSB__BULK 05c6:900800:05
r0kk3rzevelyn: you might get some more useful information using the -d flag00:11
T42<elros34> evelyn: this is what I use to automatically bind mount my ${HOMEDIR}/$MOUNT_DIR:
T42<alexisrev> I started earning the day I took the courage to invest in Bitcoin with Amos Bauer , now I'm glad I took that courage. I just got $5500 profits sent directly to my PayPal account.00:49
vknecht@Oksana: I think EDL/QDL are the same... Also, if there's a tool tailored for your device, it's probably easier/better to try it first, rather than using generic tools generic msm programmer files. Just a thought01:13
Oksanavknecht: Thank you :-) Yes, Factory Restore Tool did restore everything to working, better than new, condition. No data lost!10:10
T42<polanobi> @alexisrev [I started earning the day I took the courage t …], report10:15
T42<RealDanct12> this server is probably not even moderated for a month or so10:21
T42<RealDanct12> btw guys, i may try out sailfishos on my pinephone :)10:22
asriel@RealDanct12, that's very cool!10:23
asrielDid you got the Braveheart or you've been using the dev phone?10:24
T42<RealDanct12> dev phone10:24
T42<RealDanct12> don't wanna buy the braveheart, since i think it's just a few minor changes that doesn't really affect the quality much10:24
T42<RealDanct12> especially they fixed that discharge while off issue in bh i believe10:25
asrielRight, that's one major change10:25
asrielStill waiting for my Braveheart PinePhone to be shipped10:26
asrielI mean, to reach my home :)10:26
asrielShipping to Vietnam is quite shitty, it takes longer than everyone else10:27
asrielEspecially the fact that you have to send them invoice of you buying the phone, otherwise they'll return it10:27
T42<RealDanct12> cool10:28
T42<RealDanct12> the invoice issue is kind of annoying though10:28
T42<RealDanct12> i had to ask TL Lim for a document though10:29
asriel:O same here10:31
asrielBut I don't really need to ask anyone since you can already print it10:31
asrielOr maybe if you lost it you can ask them or something10:32
malpiggz: yes, I still wonder why channels are not valid in that, where does the channels value come from?11:31
piggzmal: i dont know where it came from, but on 2 runs it was 197 and 21 .... unitiialised var?13:15
piggzneed a jusa!13:15
malpiggz: indeed looks like it's not initialized, maybe earlier logs show something13:17
malor full list from pactl13:17
piggzmal: i checked pactl, and all channel vas were 2.....13:18
piggzi tried forcing the value to 2, but it didnt make any difference13:18
malgrab new logs and also that output13:27
tortoisedochello & good evening!19:06
tortoisedoccould someone with the fxone keyboard extension test my debug build?19:06
tortoisedocor tell me how to enable keyboard events in the emulator? :)19:06
piggztortoisedoc: what is your extension?19:09
tortoisedocpiggz : sorry F(x)tech pro1 I meant19:11
piggztortoisedoc: debug build of what tho?19:12
tortoisedocpiggz : this one
tortoisedocthe test would be :19:13
tortoisedoc- install; start; hide settings screen19:13
tortoisedoc- go to lock screen19:13
tortoisedoc- clock on right-most (search) icon on the bar at the bottom19:13
tortoisedoctry to type on keyboard (text should appear)19:13
T42<alexisrev> I started earning the day I took the courage to invest in Bitcoin with Amos Bauer , now I'm glad I took that courage. I just got $5500 profits sent directly to my PayPal account.19:35
evelynoke thanks  re mersdk profile20:45
T42<edp_17> @r0kk3rz: Hi, IIRC you wrote hadk-faq 10.5?21:02
T42<edp_17> Never mind, I just have read your earlier comment about the hciattcah. So, I think somehow I need to bring up the bluetooth manually. My only issue with this is the persist.service.bdroid.bdaddr in /data/property/ doesn't exist.21:10
T42<edp_17> Hi guys. I have read the conversation last year between you and electro575 regarding the bluetooth.22:52
T42<edp_17> I have reached to the point what he reached when tried to build rfkill middleware with this command 'rpm/dhd/helpers/ --mw= --spec=rpm/bluetooth-rfkill-event.spec'22:52
T42<edp_17> But I got the same error what he got: "Problem: nothing provides broadcom-bluetooth needed by bluetooth-rfkill-event-1.0.8-1.armv7hl"22:52
T42<edp_17> Unfortunately in the irc history log there was no conclusion about how to resolve this issue. So, I am stuck.22:53
T42<edp_17> I also tried to bring up the bluetooth in the same way how I have done on hammerhead: created a dev-ttySAC0.device and hciattach.service in /lib/systmed/system, but this didn't work either.22:55
T42<edp_17> Can somebody help how to make the bluetooth work, please?22:55
T42<elros34> how about you just build missing package?23:12
T42<edp_17> @elros34 : Hi. I don't know how to do that.23:13
T42<elros34> same as you build other packages and bluetooth-rfkill-event23:14
T42<edp_17> Like: "rpm/dhd/helpers/ --mw= -s rpm/broadcom-bluetooth.spec"23:14
T42<edp_17> I wasn't aware that this broadcom-bluetooth did exist in mer-hybris repo on github.23:15
T42<edp_17> Now both of them successfully built. (broadcom-bluetooth and bluetooth-rfkill-event)23:18
T42<edp_17> Thanks.23:18
T42<edp_17> @elros34 : I have installed the packages on the device and created the configs as the hadk-faq says. Rebooted then tried to turn the bt on. This is in the journal:
T42<edp_17> 'bluetooth: unable to listen in channel 9: socket(STREAM, RFCOMM): Address family not supported by protocol (97)'23:31
T42<elros34> I guess you use default hciattach patcher settings in bluetooth-rfkill-event. Have you tried changing it to brcm_patchram_plus or even manually executing it? grep for hciattach in /init*rc files23:43
T42<edp_17> I have changed to brcm_patchram_plus as I read this in the irc log.23:44
T42<edp_17> I haven't try manually running. I tried but before I installed these packages.23:45
T42<edp_17> When I ran the '/usr/sbin/hciattach -f /system/vendor/firmware ttySAC0 bcm43xx 4000000 flow sleep /data/property/persist.service.bdroid.bdaddr' I got 'Initialization timed out.'23:49
T42<edp_17> This file '/data/property/persist.service.bdroid.bdaddr' doesn't exist on my device. I guess this is a problem, isn't it?23:50
T42<elros34> grep for bdaddr in init*rc or in getprop23:51
T42<edp_17> getprop | grep bdaddr: "[]: [/efs/bluetooth/bt_addr]"23:55
T42<edp_17> cat /init.smdk4210.rc | grep bdaddr: "setprop "/efs/bluetooth/bt_addr""23:55
T42<elros34> quick search in google, worth to try:
T42<edp_17> So, should I use 'bdaddr=/efs/bluetooth/bt_addr' instead of 'bdarrd=/data/misc/bluetooth/bluetooth_bdaddr' in /etc/firmware/bcm4330B1.conf?23:57

Generated by 2.17.1 by Marius Gedminas - find it at!