Friday, 2020-02-07

OksanaWhen I plug in Fxtec Pro1 to computer, it is shown in lsusb as Qualcomm, Inc. Gobi Wireless Modem (QDL mode). So, Something is alive here still. But, how do I get it to charge properly?01:47
OksanaNo, fastboot devices doesn't see it.01:48
r0kk3rzfastboot wont work unless the device is in fastboot mode02:57
r0kk3rzwhat state is the device in? booted up?02:57
OksanaThe device is in black brick state. Aka, run out of battery, would not charge, would not switch on, would not do anything. Qualcomm modem does show up, though, as lsusb shows.03:04
r0kk3rzah ok03:05
r0kk3rzmaybe act dead mode doesnt work properly on that yet03:05
r0kk3rzi would plug it into a real charger and leave it for an hour03:05
Oksanadmesg says new high-speed USB device number 58 using ehci-pci ; New USB device found, idVendor=05c6, idProduct=900803:06
OksanaNew USB device strings: Mfr=1, Product=2, SerialNumber=0 ; Product: QUSB__BULK ; Manufacturer: Qualcomm CDMA Technologies MSM03:06
Oksanaqcserial :1.0: Qualcomm USB modem converter detected ; Qualcomm USB modem converter now attached to ttyUSB003:06
Oksanar0kk3rz: I had it plugged into its real 5V 3A charger for whole night.03:06
r0kk3rzhmm ok03:07
r0kk3rztry and boot it up with it connected to a charger?03:07
OksanaDid try. Just power button, or power button with volume up, or power button with volume down...03:07
* Oksana is now apt-upgrading laptop from ASCII to Beowulf, just to get Qt5.9+ instead of Qt5.7, just to get Sahara running ( ), just in case Sahara knows how to communicate with QDL mode...03:09
r0kk3rznot sure thats going to help you03:09
OksanaNot sure either. I think that if I disassembled the device and charged up the battery, then all would be well (till next flat-battery time). But, I have no idea how to disassemble it.03:10
OksanaWell, I could start with disassembling the display, it seems to have lots of screws, but that seems to be way too fragile and out of the way.03:11
r0kk3rzi wouldnt do that, id talk with chen about it first03:11
OksanaI wouldn't disassemble it either. Talk with Chen... Would be nice.03:11
r0kk3rzhe is fairly active in the fxtec thread on tmo03:13
r0kk3rzbut leave it plugged into a pc in qdl mode, maybe it slow charges the battery03:14
OksanaHmm, alright. Not sure for how long it is plugged into the laptop in QDL mode, but will leave it as it is for a few hours.03:18
T42Beverly Core %lastname% was added by: Beverly Core %lastname%05:32
piggzOksana: that rings a bell07:21
piggzOksana: QDL tool might help, i found you had to start qdl, unply usb,  plug usb08:01
vknecht@Oksana: this thread seems related (read entirely before attempting anything):
vknechtiirc it might also be necessary to disable Linux distro NetworkManager service when dealing with EDL/QDL08:30
*** Mister_Magister is now known as Mister_Magister_09:03
*** Mister_Magister_ is now known as Mister_Magister09:03
*** Oksana_ is now known as Oksana09:08
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.09:39
T42<polanobi> @alexisrev [I started earning the day I took the courage t …], report09:42
piggzmal: so, the assertion in pulse comes from
piggzpactl set-sink-volume 0 +10% works as expected11:09
piggzso, need to figure out why the above function is passing invalid data11:09
piggzwhere is jusa when u need a PA problem fixed11:10
T42<NotKit> Oksana, is your host on Linux?11:14
piggz@notkit i believe so11:14
T42<NotKit> another possibility may be to reflash with Linaro and firmware from
T42<NotKit> sudo ./qdl --storage ufs prog_ufs_firehose_8998_ddr.elf rawprogram_8998.xml patch_8998.xml11:17
T42<NotKit> will erase everything, but should bring it out of brick state11:18
piggzmal: this prevents crash, but doesnt fix problem
T42<Akatsu39> is there any sheet with syscall names? i have kernel errors with "syscall 38420:36
T42<Akatsu39> "20:36
T42<Akatsu39> How can i find if SELINUX is enabled? when i grep for SELINUX in journalctl -b i get +AUDIT +SELINUX20:52
T42<elros34> search for selinux: disabled at boot or something like that in dmesg/journal21:34
T42<meierrom> @polanobi: guess you better ping @Thaodan for this channels daily spam ;)22:30
T42<polanobi> (Sticker, 512x512)
evelynI'm trying to test sb2 as directed in the porting guide. I created the simple main.c, and tried to run the command... sb2 -t $VENDOR-$DEVICE-$PORT_ARCH gcc main.c -o test23:23
evelynHowever, it says no such file or directory. When chrooting into it, it seems that the current directory (where my ANDROID_ROOT is) isn't mounted in the chroot it creates.23:23
evelynand subsequent attempts to build my device's packages fails I think for the same reason. It's not clear to me where to start debugging this.23:25
r0kk3rzshow the full output23:25
malare you sure you used the correct target name when you created the target?23:25
r0kk3rzand double check your variables are correct23:25
evelynwell... it's complicated23:31
evelynbut here is a paste:23:31
evelynI ended up with several layers of /opt/build.. I suspect it's because my ANDROID_ROOT isn't my home directory. But I don't have room in my home directory.23:32
r0kk3rzthats ok, it doesnt need to be23:33
evelynThe target's definitely correct. I can compile things inside the target fine23:33
evelynit's slightly confusing what I ended up with.23:33
piggzmal: did you see my patch earlier?23:39
evelynI'm honestly thinking that the only thing I've done wrong is not set ANDROID_ROOT to be somewhere in my home directory.. :(23:58
r0kk3rzthats never been an issue in the past23:59
r0kk3rzand irrc sb2 doesnt do anything with that variable anyway23:59

Generated by 2.17.1 by Marius Gedminas - find it at!