Saturday, 2018-06-16

TAMplus39Hey all, Now i have passed the droidmedia but as always another thing shows up02:49
TAMplus39In short: It says that hybris.c doesnt exist02:51
TAMplus39Do I have to rebuild hybris-hal?02:52
MeowDudewew time to use hybris-10.1 for maguro and manta02:55
TAMplus39Oh and r0kk3rz was right, tar and even git were missing form the target03:02
birdzhang_piggz: does mido's FM works on  on vince it not works anymore, some ACDB-LOADER error03:17
TAMplus39So rebuilding hybris-hal, and after that libaudioflingerglue_32 and miniafservice did the trick04:07
mishaorHello everyone04:36
mishaorCan I use a non-LineageOS source code as a base for my port?04:37
mishaorMy device doesn't supports Sailfish OS04:37
mishaorBut there is a project that maintains a source code for CyanogenMod 13.004:38
TAMplus39For f*cks sake now on mic i get "nothing provides pattern:jolla-sailfish-applications needed by pattern:jolla-configuration-kenzo-1-1.noarch, "04:38
mishaorFor my phone04:38
birdzhang_TAMplus39: the pattern name changed04:51
TheKitmishaor, yes, CyanogenMod was surely supported before LineageOS04:55
TheKituse hybris-13.0 branch04:55
MeowDudeargh stupid IRC just let me ping04:57
MeowDudeTAMplus39: rebuild all your packages, re make kickstart and re run mic04:58
MeowDudeI am having audio flinger dependency issues with as well04:58
MeowDudeit sucks04:58
MeowDudeack who am I kidding I pretty much have to use the 14.1 branch, but I really miss camera05:00
TAMplus39birdzhang_: Thanks, your pattern changes made it work once more05:02
TAMplus39MeowDude: Try gettoing it as i did (make hybris-hal, next make libaudiofinglerglue_32 miniafservice) and retry it until it works05:04
MeowDudemy error is that libaudioflinger and libminiaf both conflict with the rpm build of audioflinger and droid-hal-manta05:04
TAMplus39Oh, so you got further than where i was05:05
MeowDudeI get to the 16th to last package in mic and get that error05:07
MeowDudeit breaks my hear05:07
MeowDudedo tablets even need audioflinger?05:07
TAMplus39Now I have a question: I have to build a full unofficial build of LOS right? not that it was official to begin with05:09
TAMplus39all right now my sailfish os zip is ready05:12
MeowDudeyou need a basei image that matches the kernel and device sources you are using05:12
MeowDudemake of that what you will05:12
TAMplus39Sorry that was inteded for my ssh window05:13
TAMplus39So i guess that i will have to build, since i used 6.0 sources and the last with stock kernel was from a time ago05:24
MeowDudeSUDO MIC CREATE FS!!!!06:33
T4<abhishek_0> camera just wont work.... i'm checking out that PR08:00
shark1abhishek_0 : hybris-15.1 also wont build :p08:12
malit does if you use correct hybris-boot branch08:12
shark1mal : from mer hybris it is not enough?08:13
malcheck the PR in that repo08:14
shark1oh! ok08:14
T4<abhishek_0> mal i am checking out  … this right way to build libhybris right ? rpm/dhd/helpers/ --build=hybris/mw/libhybris ?08:17
malyes I think so08:17
MeowDudeis hybris 15.1 public yet08:38
shark1MeowDude : yes08:43
T4<abhishek_0> MeowDude its github ..everything is public08:44
malbut many additional changes to other repos are not merged yet08:46
shark1Oh lol I'd rather wait then :p08:48
malthere are PRs for those08:49
T4<abhishek_0> git pull pr08:49
T4<abhishek_0> shark108:49
mallike dhd, libhybris, hybris-boot etc08:49
shark1abhishek_0 : Yes that is an option but still tracking which all to pull would be tedious08:50
T4<abhishek_0> agreed08:50
malalso the undocumented changes needed to config repo08:51
shark1and In my old port I have one more problem. The zip wont flash in 6gb 128GB storage varient devices08:52
shark1but flashes properly with 4gb 32gb varients08:52
shark1TWRP shows error 7 on 6GB varient08:53
T4<abhishek_0> shark1 did you check the partitions blocks and sizes ?08:53
shark1abhishek_0 in where?08:54
shark1Lineage os doesnt have different versions for 6/128 and 4/3208:54
T4<abhishek_0> i had that issue with the 1 gb variant, people which had 1gb vairant couldnt flash, so i had to make them flash a new bootloader and resize the partition to match the ones with 2gb variant08:56
shark1well any documentation on how to do that?08:58
T4<abhishek_0> shark1 i dont think so, but you can start with comparing /dev/mmcblkXpY blocks and sizes of both versions09:01
shark1abhishek_0 : When I last checked, both have same mountpoints so blocks and sizes also should be same09:02
T4<abhishek_0> mounting error is all i can think of now.. but you'll have to check twrp logs for more09:10
Nokiusr0kk3rz: battery life is fantastic deivce is at 48% after nearly a week of idling09:22
malvknecht: you can delete ngfd-plugin-droid-vibrator, I have just been lazy to delete that from OBS09:26
T4<abhishek_0> Nokius sailfish doesnt use much resources.. since not many crappy services running in the background .. ready to notify you because your friend has uploaded a selfie with his two spanish girlfriends09:31
vknechtmal, alright, thanks :-)09:40
malvknecht: I didn't remove it from testing project so the old targets are still valid, I just disabled it there09:41
malfrom devel it can be removed09:42
T4<abhishek_0> where is the option to disable the autobrightness ?09:42
MeowDudemal: is there any reason I shouldn't use hybris10.1 as long as I update all the rpm directories and stuff?09:57
mal@abhishek_0 in Setting->Display (or screen) and in there Adjust automatically09:57
MeowDudeI am willing to go to hybris 11 but I have a great install of CM10.1.3 on maguro and really really don't want to switch to kitkat09:58
malMeowDude: 10.1 should be used only if nothing else works09:58
MeowDude*sigh* I figured as such. Any reason why?09:58
MeowDudeI figured you could manually update everyhting, you know what you're right I need to get up to date, well , atleast with the hadk09:58
T4<abhishek_0> *sigh* I Give Up , no matter what i do camera and meda playback just wont work... maybe that build was a wonder10:00
malMeowDude: I think there are some things in the camera and media related stuff that are done differently in 10.1 based ports but I don't remember the details10:01
mal@abhishek_0 I'm pretty sure it can be fixed10:01
T4<abhishek_0> mal i just cant figure out what i am missing or what i am doing wrong, i mean like patterns are same, methods are same.. it just wont work, i have tried almost every possible combination of build10:04
T4<abhishek_0> gst-droid , gst-omx , libhybris pr 377, removing shims (that actually gave me mediaplayback working), adding shims back10:06
MeowDudesyncing hybris 11.0 now. Gee I sure hope this works. If sailfish OS 2.1 is anything like 1.1 on the galaxy nexus this is going to be great10:08
T4<abhishek_0> my dmesg rn
mal@abhishek_0 so are you trying to get omx or gst-droid  working?10:24
mallogcat is the most interesting log for codec related debugging10:24
T4<abhishek_0> mal seems like gst-omx depend on gst-droid , it will install gst-droid no matter what10:26
malyes, it does depend on it but the codec priorities determine which ones are used10:28
malalso gst-droid should be the priority to get working10:28
T4<abhishek_0> gst-droid work with media playback if i remove camerashims  .. like here
T4<abhishek_0> mal here is the logcat
malis mini* services running when you got that log? or is it restart all the time10:37
T4<abhishek_0> i just got this log just after reboot, think they were running10:39
malcan you show your config repo, with all changes you have10:40
malcheck the pids of the mini* services to see if those change after a while10:41
T4<abhishek_0> this contains everything10:41
malalso show ls -lR /dev/video*10:41
T4<abhishek_0> here
T4<abhishek_0> and process id of the mini services here
malas I told you need to check those a few times to see if the pids changes or not, I don't what the pids are, only thing I care is if those change or not10:45
malhmm, I always thought hybris-14.1 needs to have droid-hal-$DEVICE-detritus installed for the property contexts or something10:48
T4<abhishek_0> in last 5 minutes only minimediaservice has changed10:49
malso that keeps crashing then10:49
malat least that package was needed in the past, maybe things have changed? I would test if that has any effect10:49
malalso show all .rc files which have mini* services10:54
maleither in / or in /usr/libexec/droid-hybris/system/etc/init10:54
T4<abhishek_0> i can confirm it is not in /10:55
MeowDudefinally I found the Galaxy Nexus kernel sources10:55
mal@abhishek_0 so you did grep -RI mini /init*rc and same for the other folder?10:56
mal@abhishek_0 also test installing the detritus rpm manually to the device and check logs again10:57
T4<abhishek_0> mal yes, no *.rc file contains anything related to mini10:58
malthe ones in /usr/libexec/droid-hybris/system/etc/init should contain10:59
T4<abhishek_0> mal /usr/libexec/droid-hybris/system/etc/init/servicemanager.rc10:59
malas I said, show that file11:00
T4<abhishek_0> how do i build detritus package ? git url ?11:05
T4<abhishek_0> for testing11:05
MeowDudemal: Do you know what to do for this mic error off the top of your head?
MeowDudedeleting the conflicting files does nothing11:07
MeowDudeI ran zypper dup to twice and rebuilt everything11:07
maldetritus is built automatically wih droid-hal so it's already in droid-local-repo11:10
malyou would know that if read what hadk said11:11
maland you would already have it installed11:11
malMeowDude: you rebuilt audioflingerglue in android side build but forgot to package it again11:12
MeowDudemal: that is actually embarrasing11:13
malwhich has to be done before packaging droid-hal11:13
MeowDudethanks for that11:13
T4<abhishek_0> detritus is already installed ...11:17
malI didn't see it in your patterns11:20
T4<abhishek_0> 'droid-hal-wt88047-detritus = 0:0.0.6-201806160835' is already installed.11:21
T4<abhishek_0> not lying tho11:21
T4<abhishek_0> :P11:21
T4<abhishek_0> mal would you be surprised if told you, i found the issue and the solution ?11:40
T4<abhishek_0> *if i11:40
T4<abhishek_0> god damn sensorservice is the culprit11:42
T4<abhishek_0> i did /system/bin/sensorservice , and camera works, media playback works, and so does flashlight11:42
malhmm, but minimediaservice should start a dummy sensorservice11:43
T4<abhishek_0> but it doesnt... any solutions to that ?11:44
elrosmaybe it's related to this commit:, I had to revert it for cm11:
malyou had to revert something11:52
mal@abhishek_0 check your external/droidmedia in android source tree to see if that is up to date with
elrosyes I had to move FakePermissionController::instantiate(); FakeAppOps::instantiate(); back to minifs, now it's fixed (second commit)11:53
malok, so now you don't have to do it anymore?11:54
T4<abhishek_0> mal , yes $ANDROID_ROOT/external/droidmedia HEAD:master is uptodate11:58
maljust ot be sure check the git log and compare with the repo I gave12:00
T4<abhishek_0> mal yes, completely even,12:04
shark1anyone knows how to find out the bluetooth firmware name to symlink as in here ?
malshark1: so your device has broadcom bt chip?12:11
malif so then just look for files that look similar to that (but might have slightly different name) in /firmware or some places on the device12:12
shark1Ok will check12:12
shark1but mal: How to determine whether it is broadcom?12:12
malbut that link name would probably be seen in either kernel, init scripts (like .rc) or elsewhere in android sources, or dmesg or logcat12:13
malshark1: kernel configs12:13
shark1ok will check kernel configs12:13
shark1"No provider of 'createrepo' found"12:13
mallook for config flags with BT and seem what you find12:13
shark1So is that something wrong with server or something? Creatrepo not found!12:14
malis the createrepo command available12:14
T4<abhishek_0> zypper in createrepo12:14
T4<abhishek_0> i had that issue too12:14
shark1abhishek_0: still getting same12:15
T4<abhishek_0> shark1 did it install correctly ?12:15
maldid you check if the command is available12:16
T4<abhishek_0> sudo zypper in android-tools createrepo zip run this12:16
shark1mal : yes, it is not available12:17
malzypper se createrepo ?12:17
shark1abhishek_0 : that too doesnt work12:17
shark1mal :
shark1Is present but not createrepo12:18
T4<abhishek_0> ssu ar mer-tools; sudo zypper ref12:19
malso try installing that?12:19
T4<abhishek_0> mal, instructions for me ? i sooo not want to add a startup script to execute that hack12:20
shark1yes trying to install that but shows no provider of creatrepo12:25
T4<abhishek_0> shark1 did you do ssu ar mer-tools; sudo zypper ref ?12:27
shark1abhishek_0 : yes, ssu ar mer-tools is showing error12:28
shark1and zypper ref shows everything upto date12:28
T4<abhishek_0> sudo zypper in android-tools-hadk createrepo_c zip12:29
malshark1: did you try installking createrepo_c12:30
shark1mal : yes I have done that12:30
shark1abhishek_0 : I have done that earlier itself12:30
mal@abhishek_0 add the service to some init*.rc file, maybe in /usr/libexec/droid-hybris/system/etc/init you can even add a new .rc file for it12:31
malshark1: so what did it install?12:31
malrpm -ql createrepo_c12:31
shark1mal : It installed this "/usr/bin/createrepo_c"12:32
shark1and few similar ones12:32
malmaybe try adding alias to use that when you call createrepo?12:34
elrosshark1: sudo ssu ar mer-tools12:47
shark1elros : WARNING: DBus call failed, falling back to libssu: The name org.nemo.ssu was not provided by any .service files12:49
elrosssu lr shoud print now mer-tools enabled12:49
shark1ok now it worked12:50
T4<abhishek_0> mal i added "service sensorservice /system/bin/sensorservice"13:08
T4<abhishek_0> class main13:08
T4<abhishek_0> user root13:09
T4<abhishek_0> group root13:09
T4<abhishek_0> device feels warm and i cant ssh anymore lol13:09
T4<abhishek_0> there must be a better way13:13
T4<abhishek_0> device is not warm.. it is hot af13:17
malwell you did something wrong obviously13:20
T4<abhishek_0> just added it to /init.qcom.rc13:21
malso why didn't you add a new rc file to folder I said, that would have been the easier way13:23
MeowDude>can't find cryptfs.h13:56
MeowDude>comment out include line for cryptfs.h13:56
MeowDudethere are no shades cool enough for me13:57
T4<abhishek_0> mal does this look nice to you ?
shark1Do I have to build gstreamer again when Iam building from source ? (Which I imported from my git)14:06
T4<abhishek_0> if it has some new change .. then yes14:08
shark1hmm ok14:09
mal@abhishek_0 this is how it has been on some devices
MeowDudeI resolved the cryptfs.h issue14:25
MeowDudewill be adding the solution to faq-hadk14:25
T4<abhishek_0> what is this dependency i am facing whie installing harbour warehouse14:52
MeowDudepackagekit is what actually installs the application, or, atleast it plays a large role in the installation14:53
elrosyou can't use warehouse anymore, use storeman14:53
MeowDudewhats funny is that running "zypper in packagekit" will most likely result in an error due to missing packagekit14:53
T4<abhishek_0> i cant install storeman either XD , also i do i fix this package kit issue ..14:57
T4<abhishek_0> and why there is no option to disable autobrightness ?15:04
shark1 anyone got this error before?15:08
shark1It says "tar" not found while it is installed15:08
T4<abhishek_0> yes me15:08
shark1yee, how to resolve it :p15:08
T4<abhishek_0> shark1 sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install zypper in tar15:08
shark1ok thank you15:09
T4<abhishek_0> i am at a point i have seen every possible error that can/will happen during build ..lol15:09
shark1so your cam still out of order?15:10
T4<abhishek_0> fixed, just an hour ago15:10
shark1did you try anbox?15:11
T4<abhishek_0> no, not yet .. but i want to...  i saw a new repo for kernel modules for anbox15:12
T4<abhishek_0> it was made a week ago,15:12
T4<abhishek_0> now i am just trying to fix every error possible, to get a perfectly finished final build,15:13
shark1abhishek_0 : Nice, I had earlier made few unsuccessful trials to build it15:13
T4<abhishek_0> which kernel version?15:14
T4<abhishek_0> probably thats why it didnt build ..15:16
T4<abhishek_0> i got 3.1015:16
shark1No, I meant I tried to build for 3.1815:17
shark13.10 already there is image15:17
shark1by mal15:17
T4<abhishek_0> you'll still need those kernel patches15:18
T4<abhishek_0> idk how good they are with 3.1815:19
shark1Yes, binder patches only probably15:19
shark1coz overlay is already present15:20
T4<abhishek_0> binder patches got removed15:21
shark1in latest version?15:22
T4<abhishek_0> this15:23
T4<abhishek_0> they said it is not needed15:23
T4<abhishek_0> ashmem modules are needed15:23
T4<abhishek_0> anyway ... how do i fix and autobrightness option ? anyone?15:40
OctoNezdI cant compile sailfish using WSL, or I can?15:41
T4<abhishek_0> whats WSL ?15:41
OctoNezdwindows subsystem for linux15:42
OctoNezdaka bash on ubuntu on windows15:42
T4<abhishek_0> OctoNezd you can15:42
OctoNezdso I dont have to install ubuntu in dualboot15:42
OctoNezdNow about base. I have lineage 13, 14.1 and unofficial 15.1. Which I should pick?15:43
elros@abhishek_0: it's hard to tell without showing error15:44
shark1OctoNezd which device?15:44
OctoNezdLeEco Le 215:44
OctoNezdI think you remember me15:44
shark1Ye I remember you15:44
shark1Long time ago15:44
OctoNezdI was not able to do stuff cause college15:44
OctoNezdforgot almost everything about porting :P15:45
shark1hybris 15.1 isnt fully buildable15:45
shark1so dont go for it15:45
OctoNezdso should I better go with ubuntu or WSL?15:45
shark1mal : elros: in a firmware folder I have name "bt_qca6174" so this is the bluetooth name right?15:46
shark1OctoNezd : ofc WSL. WSL will change development on windows for ever in coming times :p15:47
elrosdunno, I would search bluetooth name in kernel config15:47
shark1well config just states the general config "BT_HCAIRT" something like that15:49
T4<abhishek_0> WSL is shit15:50
shark1well it is improving15:50
T4<abhishek_0> elros this15:51
OctoNezdAlso, I see there is people with Telegram on it's name, so there is sailfishos-porters telegram chat?15:51
T4<abhishek_0> shark1 i dont want it to improve, it will take away the same thing linux the kernel always stood for15:52
elros@abhishek_0: lol, I told you you can't use warehouse anymore15:52
T4<abhishek_0> i heard it is abandoned,, but not unusable15:53
elrosit's broken due to changes in packagekit15:53
shark1abhishek : your bluetooth is working?15:54
T4<abhishek_0> shark1 flawlessly15:56
shark1you fixed something for it?15:56
T4<abhishek_0> elros , i dont have any option to disable the autobrighness15:56
T4<abhishek_0> shark1 just the faq15:56
malshark1: that means you chave qcom bt15:56
elrosdo you have latest droid-configs?15:57
T4<abhishek_0> elros yes15:58
shark1but I see it as RFCOMM in configs15:59
elroslooks like no15:59
elrosshark1: CONFIG_QCA_CLD_WLAN looks like wifi/bt module16:01
shark1yes I have wifi working16:01
shark1Only Bluetooth is lacking currently16:01
OctoNezdconfused about PORT_ARCH16:11
OctoNezdasked one of devs, he said it arm64, other one said arm64-v8a16:11
shark1no it isnt16:15
shark1leave it as it is for now OctoNezd16:16
malshark1: it's possible your device has one of the currently not supported bt chips16:19
OctoNezdyou cant install platform sdk on windows16:20
T4<abhishek_0> why i dont have disable autobrightness option16:20
shark1mal : ohk. Probably same as oneplus3.. It also doesnt have working bluetooth16:20
OctoNezdthere is a bunch of files in it with :, which is prohibited in NTFS16:20
elros@abhishek_0: upgrade your submodules first16:21
T4<abhishek_0> elros .. they are updated16:21
elrosas you wish16:22
shark1OctoNezd : thats sad :p give then feedback16:23
shark1*give them feedback16:23
T4<abhishek_0> elros no really they are updated ;)16:41
mal@abhishek_0 did the sensorservice work now?16:48
T4<abhishek_0> mal yes, camera works, media works .. so yay!16:49
T4<abhishek_0> what should i do about autobrightness and screen time out ?16:50
malI have no idea what you have done so you don't see the brightness control toggle in settings app16:53
malwhy don't you want to have automatic brightness control?16:53
T4<abhishek_0> yes .. i do have brightness slider.. but i afaik i there use to be a auto brightness disable option16:54
T4<abhishek_0> ambient light sensor is just too sensitive16:55
T4<abhishek_0> way too sensitive16:55
elrosyou can edit als behavior in /sparse/etc/mce/20als-defaults.ini17:01
T4<abhishek_0> thanks ... screen timeout doesnt work either elros17:12
elrosrun jolla-settings in terminal and search for errors, lack of screen timeout it's probably related to mce so debug it also17:13
mal@abhishek_0 I have the switch in sailfish
Mister_Magister mal: there is no auto brightness turning on/off switch in
vknecht@abhishek_0: here's an intro to debugging non-blanking screen :
vknecht(in my case it was the gyro, seen with evdev_trace, so I had to add this :
malMister_Magister: then how do you explain that I have it17:28
Mister_Magistermal: then how do you explain i have it in jolla phone17:29
Mister_Magisterhmmm then we have bug17:29
Mister_MagisterMANY ports dont have it since 2.217:29
malMister_Magister: jolla c and fp2 has it17:30
Mister_Magistermal: then how comes <many ports> dont have it?17:31
malMister_Magister: is it missing from your ports?17:32
Mister_Magisternot only from my but yes17:32
malwhich one specifally so I can have a look17:32
Mister_Magisterall of them17:32
Mister_Magistermoto x217:32
Mister_Magisterpick this one its victara17:32
Mister_Magistermaybe outdated patterns17:33
vknechtI don't have the autobrightness setting on idol3 neither17:34
Mister_Magister>not only my ports17:35
Mister_Magisterbut yeah i actually went around house checking all of my ports and none of them has it17:36
malMister_Magister: are sensors working without issue on that device? verify again the light sensor with messwerk17:36
maljust to be sure17:36
spiiroinmal Mister_Magister: in some places in settings and elsewhere "hw feature config" is used to hide/show some settings17:36
Mister_Magisterchecked light sensor on every device during update testng17:36
spiiroinif no light sensor is declared -> autobrightness is hidden etc17:36
Mister_Magisterspiiroin: but autobrightness works17:37
Mister_Magisterjusa: ping17:37
Mister_Magisterspiiroin: what configs do you mean17:37
spiiroinMister_Magister: /usr/share/csd/settings.d/hw-settings*.ini, or so17:38
malspiiroin: that explains it, I have that on fp2
Mister_Magisterand EVERY normal port doesnt17:39
Mister_Magisterso we need some PSA17:39
malstill a bit strange that it follow csd configs for that information17:39
T4<abhishek_0> mal is usb OTG supported ?17:39
elrosI have enable/disable switch17:39
Mister_Magisteryep empty on my device17:39
malelros: which device?17:39
elrosphoton q:
Mister_Magistermaybe ytou had some specific configs or something for led17:40
malelros: link to config repo please17:40
Mister_Magisterfor brightness17:40
Mister_Magistermal: why do you have this file17:40
spiiroinmal: csd just happened to have such thing, being extended & brought under one api, then it can be moved around17:40
elrosmy repos are not yet updated17:40
elrosbut in jolla-settings there is only TextSwitch {} without any disabled or visible properties17:41
spiiroinmal: something like "test for hw feature is enabled in csd" -> "device has such hw feature"17:41
malspiiroin: are many other settings following that?17:41
spiiroinmal: settings, sensorfwd is about to, ...17:42
Mister_Magistermal: but why do you have this file in first place lol17:42
spiiroinmal: ssu-sysinfo --list-hw-features17:42
malMister_Magister: it's used for the csd app which is the app used for testing all hardware features of a device, I have configured in so the app works well, that app has to be launched for commandline17:42
Mister_Magisterim using csd app17:43
malMister_Magister: I use the app for testing new releases17:43
Mister_Magisterno it doesnt17:43
Mister_Magisteryou can tap build number and csd launch17:43
maloh, ok17:43
Mister_Magistermal: [19:36] <Mister_Magister> checked light sensor on every device during update testng17:43
malMister_Magister: but you probably haven't configured it properly17:43
Mister_Magisterwas doing same17:43
Mister_Magistermal: yeah17:43
malsome things needed some changes to work correctly17:44
Mister_Magisterso you have solution then mal spiiroin?17:44
spiiroinmal, Mister_Magister: the things you can put to config files ->
Mister_Magisterspiiroin: so i need to setup that file?17:44
elrossorry, I was wrong I looked at wrong phone17:45
Mister_Magisterspiiroin: i have two other problems do you have a second?17:45
spiiroinMister_Magister: yes, I think it is installed from hw specific droid-config packages17:45
T4<abhishek_0> mal this worked thanks :)17:45
Mister_Magisterspiiroin: kkk17:45
Mister_Magisterabhishek_0: you should setup it not copy paste it17:46
mal@abhishek_0 make sure the enabled setting match your device features17:46
Mister_Magisterthats what i said :P17:46
Mister_Magisterspiiroin: so do you have a second?17:46
malMister_Magister: I was writing at the same time17:46
T4<abhishek_0> mal , yeah they are exactly same17:46
spiiroinMister_Magister: maybe - be quick ;-)17:47
Mister_Magisterspiiroin: i have p8lite with rgb led but its actually 3 channels that are binary 0 or 255 everything above 0 is full specific channel17:47
Mister_Magisteroh sorry no its turns on at 25517:47
Mister_Magisterso actual rgb backend doesnt work as it sets values like 5017:48
Mister_Magistersecond one phone vibrates on unlock and my brother doesnt like vibrations (it doesnt vibrate on other phones)17:48
spiiroinMister_Magister: that would take more than a second.. but I guess whenever I get enough breathing time to check that other led thingy -> the same should then be applicable to 3 channel led too17:49
spiiroini.e. config file based on/off strings/numbers/whatnots & binary logic17:49
Mister_Magisteri mean we need new backend?17:50
Mister_Magisterspiiroin: i wrote it in second XD17:51
* vknecht is interested in binary led backend changes too17:55
vknechtrather, the white backend17:56
elrosspiiroin: from where to get all this feature names to define in hw-settings.ini?17:57
malelros: the he gave
elrosoh thx17:57
T4<abhishek_0> okay .. autobrightness toggle fixed and screentime out fixed .. \o/17:59
T4<abhishek_0> this stuff needs to be in faq18:01
malso write it there18:03
shark1lol twrp is getting stuck while flashing sailfish :p18:10
shark1New headache to check.. TWRP logs :|18:10
T4<abhishek_0> mal okay while this builds i am gonna fill faq18:10
vknechtthe Key entry must be 1 as soon as there are power/vol keys, or is it for hardware android buttons ?18:11
shark112GB of space is enough to flash sailfish right?18:12
T4<abhishek_0> yes18:13
T4<abhishek_0> more than enough i say18:13
shark1ok, so its failing to extract file system18:14
shark1Error 718:14
T4<abhishek_0> shark1 are you doing hybris15 ?18:15
T4<abhishek_0> strange .. you had it working before right ?18:17
shark1But now twrp gets stuck. I doubt some changes in TWRP not letting it flash18:19
malas a reference this has some more hints
T4<abhishek_0> Done18:40
T4<abhishek_0> shark1 try flashing an older recovery18:57
shark1yes did that18:57
shark1and it works now18:57
shark1but Iam cursing the camera again :p18:57
T4<abhishek_0> lol .. why?18:57
shark1coz its not working :p18:58
T4<abhishek_0> check the logs ... who knows what you may find :P18:59
shark1yes just checked. I flashed the lineage build with no camera :p19:00
shark1Going to change now19:00
T4<abhishek_0> you can look for other 7.1 based roms too .. they might have camera working19:02
shark1na my camera works probably19:02
shark1Just flashed the wrong zip19:02
T4<abhishek_0> XD19:04
shark1and I hate the long flashing times of :p19:04
shark1Takes like 3-4mins19:05
T4<abhishek_0> ikr ?19:05
T4<abhishek_0> it is frustrating19:05
shark1probably .tar is to blame19:05
shark1coz android roms flash easily19:05
T4<abhishek_0> sadly there is no other option .. like we had for startup sailfish introduction19:06
T4<abhishek_0> lol19:06
shark1I wonder if I should try to build open source cam for 14.1 or wait for hybris15.1 :p19:06
shark1Coz last time I tried opensource cam, I failed at it19:07
shark1abhishek_0 : where is this framerate thing19:07
shark1I dont see in settings19:07
T4<abhishek_0> it will not be that hard tho, since 14.1 and 15.1 are mostly same19:07
T4<abhishek_0> development settings19:08
shark1there were commits but it wasnt ultimately merged for 14.119:08
shark1probably cam didnt work19:08
shark1I see it is empty19:08
shark1I mean few settings19:08
T4<abhishek_0> really is under Developer tools > framerate display19:09
mal@abhishek_0 it's completely possible to make fastboot flashable sailfish image, I have done it in the past, quite simple, just some patching of hybris-boot if I remember correctly19:09
shark1mal : that means no need of lineage?19:10
malof course we need lineage also, that would just make an image for userdata partition where sailfish is installed19:10
piggzabranson: ping19:11
T4<abhishek_0> mal why some hasnt done it yet ? it sounds cool tho.. and having an installer like ubports19:11
malalso it's of course also possible to package the system image and other needed stuff but there could be issues with distribution in that case19:11
piggzabranson: on my new 2,2 without omx, build in player cant play recorded video, but lls can .... and in browser on youtube, funny colours at bottom ov video19:12
mal@abhishek_0 I only made those builds because at one point it was not possible to install unsigned zips from fp2 recovery, but that was fixed so I stopped releasing fastboot images19:12
abransonpiggz: that sounds unusual. which device?19:13
piggzabranson: mido19:13
T4<abhishek_0> abranson and wt8804719:13
piggzabranson: also, official jollatab has bad colours in browser on youtube19:14
piggzbut, thats a seperate issue19:14
shark1lol my frame rate is worse19:14
shark1what is the max value I can set forQPA_HWC_IDLE_TIME ?19:15
T4<abhishek_0> mal .. i can make a cool looking installer tho :P if we can make fastboot images for more device19:16
T4<abhishek_0> shark1 5 did the job for me19:16
shark1let me check it then19:16
abransonhmm, will have a look at the tablet. the colours at the bottom sounds like the colour format is wrong19:17
*** Nokius_ is now known as Nokius19:17
mal@abhishek_0 installer.. , why would you want that?19:17
abransonpiggz: any GST or logcat errors when the recorded playback fails?19:18
T4<abhishek_0> installers look cool ! ( ͡° ͜ʖ ͡°)19:18
shark1it shows it is readonly19:18
shark1that file19:18
T4<abhishek_0> shark1 are you sudo ?19:19
shark1sudo is asking password19:19
shark1I havent set19:19
T4<abhishek_0> then set it lol19:19
shark1how to?19:20
T4<abhishek_0> ssh password is devel-su password19:20
Nokiusr0kk3rz: let#s see if tehre is aay to read the bt mac19:21
T4<abhishek_0> ssh password can be set from Developer Tools19:21
malno sudo, devel-su19:21
piggzabranson: nothing with GST_DEBUG=719:22
shark1can I go still more ?19:22
shark1Like 719:22
piggzits odd ... it plays old recorded videos, and also shows thumbnails for them ... but doesnt show thimbnails for the new ones19:22
T4<abhishek_0> shark1 maybe19:24
shark1ok.. abhishek_0 : camera works. But flash is badly out of sync (No hal1 to try hal1) :p19:24
shark1Everything normal19:24
T4<abhishek_0> good, flash can be synced19:28
T4<abhishek_0> some ini file it was .. i cant remember19:28
shark1I guess not coz it is dual flash19:30
vknechtmaybe in kernel/devicetree too ? iirc I saw something like that19:30
shark1One goes befor shot one after :p19:30
T4<abhishek_0> vivo nex would be the best device to use sailfish on19:32
shark1abhishek_0 any tests to perform to check which sensors are working19:33
shark1and which are not?19:33
T4<abhishek_0> call someone to test proximity :P '19:36
T4<abhishek_0> test_vibrator19:36
T4<abhishek_0> or to test tab completion to see which ones are available19:37
T4<abhishek_0> test_sensors would do the job19:38
malmesswerk app is good for sensor testing19:39
T4<abhishek_0> *test + tab19:39
T4<abhishek_0> or yeah .. try messwerk19:39
malhe disconnected already19:40
T4<abhishek_0> sadly this bot doesnt inform me XD19:41
T4<abhishek_0> Lets see how to setup obs19:44
T4<abhishek_0> on obs sailfish_latest_armv7hl has armv8l ..i should uncheck it and select armv7l19:53
T4<abhishek_0> armv7l or armv7el19:54
T4<abhishek_0> 2.2 doesnt have build targets19:55
T4<abhishek_0> okay nv,19:57
T4<abhishek_0> *nvm19:57
abransonpiggz: logcat?20:04
T4<abhishek_0> @adampigg will ping him20:07
Nokiusr0kk3rz: opened a BT mac fix PR ;)20:22
elrospiggz: somebody had issues with thumbnails:
TAMplus39Holy cow, Flashing over an old cm13 works for my zip but now i have to rebuild eveything because of selinux:/20:32
TAMplus39Oh and what server do you recommend for uploading my zips? currently uploading them from google cloud platform to gdrive20:34
TAMplus39And i dont wanna fill my free space20:35
T4<adampigg> abranson, nothing interesting in logcat....its like it doesnt even try becuase there is no thumbnail20:36
abransonso there's no attempt to create the codec at all?20:36
piggzabranson: correct, i dont think there is .... if I click on a video with a thumbail, it creates a codec in logcat ..... if i click on a newly recorded one with no thumbail, it says 'coudl not load video' in the player, and nothing in logcat20:39
abransonthat error should be more visible in gstdebug20:41
piggzthe errorlabel error, is from clicking the video that doesnt play, the gst errors are from another video20:45
abransonhmm that's not getting very informative...20:48
elroslooks like the same issue like birdzhang had20:49
filip__hi there. can you help me please? I have XperiaX official and it appears that sound settings have somehow corrupted (during upgrade or CSD test?) as bottom speaker volume is at least 20dB bellow top one on headphones and heavily distorted when played on phone itself.20:49
piggzabranson: clicking the info button in the player says it is 0x0 size20:50
piggzand 0 duration20:51
piggzi wonder if the indexer is failing, and thus the media player doesnt even try20:51
T4<abhishek_0> TAMplus39 mega ?20:52
TAMplus39For hosting them for other people i guess mega is a good option but for myself i find the bandwith limit quite annoying21:05
malTAMplus39: this place has quite many images
TAMplus39Yeah i can see that in there are images for a lot of devices21:11
duncan^In the mer-hybris tree, hybris-boot looks for any file with fstab in its name. My board has a number of files destined for recovery called that, and this confused hybris-boot. I guess the best thing to do is to rename them, but this is annoying given that other parts of the source tree looks for these filenames. Thoughts?21:16
duncan^It is confusing hybris-boot because it decides /boot is three different partitions.21:16
duncan^(since I have three different files with 'fstab' in their name, for three different components)21:17
malother option is to edit the search conditions in hybris-boot21:23
duncan^I guess that makes it more difficult to upstream work.21:24
TAMplus39Ok so now I have succesfully booted my sailfish build21:28
malTAMplus39: which device is that?21:35
TAMplus39Redmi note 321:35
malI thought there was a port for that already? was the original abandoned and did you reuse the repos for that?21:38
TAMplus39Yes it was abandoned the last year, and i didnt reuse anything21:41
TAMplus39The only thing that I took was its local manifest21:41
TAMplus39Ok so right now i can tell that camera isnt working, web browser is a black screen21:55
malTAMplus39: for browser you need to enable adreno quirks, not sure if you have built all of the needed things for camera and configured it properly22:01
malTAMplus39: instructions for adreno quirks can be found in faq
TAMplus39I just read that off the faq BTW: How can i check if audio is working?22:02
malgo to audio settings and play some ringtone or something22:03
TAMplus39Well one more to the list of things that arent working22:05
TAMplus39Calls arent working either, however the proximity sensor is22:09
TAMplus39I think im gonna release the zip on xda and see what other bugs people find22:11
TAMplus39Oh and data is working also22:12
malTAMplus39: did you read chapter 13.2 to 13.4 in hadk pdf?22:24
malTAMplus39: for 13.2 you should also check faq topic "Current droidmedia build instructions"22:25
TAMplus39I didnt follow after "to prevent camera lockup"22:26

Generated by 2.17.1 by Marius Gedminas - find it at!