Wednesday, 2020-05-13

T42<edp_17> There is no IMEI number and SIM card is not detected. I have tried the legacyImeiQuery=true in ril_subscription.conf but didn't help. The logcat -b radio | grep RIL gives me:
T42<ankaos> Egl not work.00:19
T42<ankaos> systemctl list-units -t service —all output01:04
rinigusmal: such sensor fusion would probably do what vendor blobs are doing as well. By default, in sensorfw config, we have magnetometer not requiring calibration. Is that correct?05:20
*** kimmoli_ is now known as kimmoli05:21
T42侯琪媚 %lastname% was added by: 侯琪媚 %lastname%05:29
T42<edp_17> Good morning. Can I get a help with the modem, please? SIM is not detected and the ofono service shows that 'ERROR! RIL read failed' :
T42<edp_17> Full dmesg :
T42<edp_17> logcat -b radio :
T42<Sasank %lastname%> Hi Everyone, I am Sasank. I am newbie on Porting Sailfish to other devices. As per the documentation given, Do I need complete Linux environment or Can I use Windows Subsystem for Linux in Windows 10 to port Sailfish OS09:52
T42<edp_17> I recommend to use a complete Linux environment like Ubuntu.09:53
T42<edp_17> If you would like to keep Windows as your main OS, you can install ubuntu on a Virtual Box on Windows. It should work.09:55
malrinigus: yes sensor fusion would be what vendor blobs do but sometimes blobs are broken or missing things and native ports don't have those10:03
T42<Sasank %lastname%> @edp_17 If I do run Linux on VirtualBox the compilation time will take much more longer10:15
T42<edp_17> Sasank : Why would it? It is virtualization which means the Linux in the VM is directly using the PC hardware, so shouldn't be slower. Of course if you don't have enough memory in that PC, running the extra OS in the VM on top of the crap Windows, that obviously will have an impact on every process that runs in Linux.10:18
T42<edp_17> However I didn't think the extra time that would be significant.10:19
T42<Rock %lastname%> (Photo, 774x874) .微信电报群发推广,电报群.微信群.Patato增粉\非小号mytoken关注排名,twitter.facebook.Linkedin关注.电报群微信群Patato活跃聊天\,KYC出售,币圈朋友圈广告\中英文群管理客服,私聊指定电报群成员.出售微信号脸书推特号,出售支付宝,国内外交易所代实名认证.请咨询 @lduduo10:36
*** birdzhang1 is now known as birdzhang11:07
T42premnikumbh was added by: premnikumbh11:39
rinigusmal: understandable and makes sense.11:49
T42<edp_17> @pketo : Please add Galaxy Note 4 access to the store. Device model: Samsung (treltexx / treltexx). Thanks.12:18
T42<ankaos> Miko power button work14:07
T42<ankaos> But screen only mi logo14:07
T42<edp_17> Have you done what I suggested?14:13
T42<ankaos> @edp_17 [Have you done what I suggested?], Yes14:26
T42<ankaos> @edp_17 [Have you done what I suggested?], hadk/hybris/droid-configs/droid-configs-device/ add14:29
T42<ankaos> @edp_17 add this line14:30
T42<ankaos> (Document)
T42<edp_17> No, this meant to go into $ANDROID_ROOT/rpm/droid-hal-device.inc14:31
T42<ankaos> @edp_17 [No, this meant to go into $ANDROID_ROOT/rpm/dr …], ı send error.14:31
T42<edp_17> Not into hybris/droid-configs/droid-configs-device/droid-configs.inc14:31
T42<edp_17> That is a different location.14:31
T42<ankaos> @edp_17 [That is a different location.], hadk/rpm/dhd/ true location?14:34
T42<edp_17> No. This: $ANDROID_ROOT/rpm/droid-hal-device.inc14:38
T42<edp_17> Okay, start a command line on your host.14:38
T42<edp_17> then type: sfossdk14:38
T42<edp_17> then type: ls $ANDROID_ROOT14:39
T42<edp_17> What message did you get?14:39
T42<ankaos> @edp_17 [No. This: $ANDROID_ROOT/rpm/droid-hal-device.i …], PlatformSDK enes@enes:~/hadk$ ls rpm/14:45
T42<ankaos> dhd  droid-hal-tissot.spec14:45
T42<edp_17> okay, type: cd $HOME14:47
T42<edp_17> then: ls $ANDROID_ROOT14:47
T42<ankaos> @edp_17 [then: ls $ANDROID_ROOT], PlatformSDK enes@enes:~$ ls $ANDROID_ROOT14:47
T42<ankaos> Android.bp                        generated_android_filesystem_config.h14:47
T42<ankaos> Jolla-@RELEASE@-tissot-@ARCH@.ks  hardware14:47
T42<ankaos> Makefile                          hybris14:47
T42<ankaos> RPMS                              hybris14.1fix.sh14:47
T42<ankaos> abi                               kernel14:47
T42<ankaos> bionic                            kernel.files14:47
T42<ankaos> bootable                          libcore14:47
T42<ankaos> bootstrap.bash                    libnativehelper14:47
T42<ankaos> build                             out14:47
T42<ankaos> device                            prebuilts14:47
T42<ankaos> documentation.list                rpm14:48
T42<ankaos> droid-hal-tissot.log              sfe-tissot-
T42<ankaos> droid-local-repo                  system14:48
T42<ankaos> git submodule add dhd this is bad?14:49
T42<ankaos> branch master??14:50
T42<edp_17> Your $ANDROID_ROOT looks ok. However the I sent you should be in home on your host system, rather than here.14:51
T42<edp_17> Now type: ls rpm14:52
T42<ankaos> @edp_17 [Now type: ls rpm], I chose the wrong branch.14:56
T42<edp_17> What version of Sailfish are you building?15:00
T42<ankaos> @edp_17 [Now type: ls rpm], PlatformSDK enes@enes:~/hadk$ ls rpm/15:01
T42<ankaos> build-from-android  droid-hal-@DEVICE@.spec.template  droid-hal-tissot.spec  helpers  rpmlintrc15:01
T42<edp_17> For you need master branch of dhd.15:01
T42<ankaos> @edp_17 [For you need master branch of dhd.],
T42<edp_17> For 3.2xxx you need the upgrade-3.2.1 branch.15:01
T42<ankaos> git submodule add upgrade-3.2.1 true?15:03
T42<edp_17> Are you building 3.3 or 3.2?15:03
T42<ankaos> @edp_17 [Are you building 3.3 or 3.2?], build15:03
T42<edp_17> Then you need upgrade-3.2.1 branch.15:04
T42<edp_17> Your $ANDROID_ROOT/rpm is wrong!!!15:05
T42<edp_17> You should have the following in there:15:05
T42<edp_17> dhd15:05
T42<edp_17> droid-hal-tissot.spec15:05
T42<edp_17> .git15:05
T42<edp_17> .gitmodules15:05
T42<elros34> just a note, you should use
T42<edp_17> Within rpm/dhd you should have:15:06
T42<edp_17> build-from-android15:06
T42<edp_17> droid-hal-@DEVICE@.spec.template15:06
T42<edp_17> .gitignore15:06
T42<edp_17> rpmlintrc15:06
T42<edp_17> droid-hal-device.inc15:06
T42<edp_17> .git15:06
T42<edp_17> Hi @elros, yeah I just wanted to suggest him. I think he should read hadk and hadk-faq again then update all sub modules properly and start over.15:08
T42<ankaos> ı use
T42<edp_17> Plus I am not sure his target and tooling are correct as the latest is not pointing to
T42<ankaos> @edp_17 [Plus I am not sure his target and tooling are …], because I compile
T42<ankaos> @edp_17 [Within rpm/dhd you should have:15:10
T42<ankaos> build-from-and …], PlatformSDK enes@enes:~/hadk$ ls rpm/dhd/15:10
T42<ankaos> build-from-android  droid-hal-@DEVICE@.spec.template  helpers  rpmlintrc15:10
T42<ankaos> (Photo, 1280x719)
T42<edp_17> A few minutes earlier you said:15:12
T42<edp_17> PlatformSDK enes@enes:~/hadk$ ls rpm/15:12
T42<edp_17> build-from-android  droid-hal-@DEVICE@.spec.template  droid-hal-tissot.spec  helpers  rpmlintrc15:12
T42<ankaos> @edp_17 [A few minutes earlier you said:], yes. because I bought it in a higher folder.15:13
T42<edp_17> So, where are those files? In 'rpm' or in 'rpm/dhd'?15:13
T42<ankaos> rpm/dhd'15:14
T42<edp_17> Then it's ok.15:14
T42<edp_17> And what is in rpm?15:14
T42<ankaos> dhd and droid-hal-tissot.spec15:15
T42<edp_17> This is ok too.15:16
T42<edp_17> Then you need to remove the current dhd and get the upgrade-3.2.1 branch.15:17
T42<ankaos> git submodule add upgrade-3.2.115:17
T42<ankaos> what is read "dhd/droid-hal-@DEVICE@.spec.template > droid-hal-hammerhead.spec"15:18
T42<ankaos> dhd or upgrade-3.2.115:18
T42<edp_17> No. Do the following:15:20
T42<edp_17> 1. delete content of the dhd folder15:20
T42<edp_17> 2. cd dhd15:20
T42<edp_17> git init15:20
T42<ankaos> yes?15:20
T42<edp_17> 3. git fetch
T42<edp_17> 4. git pull upgrade-3.2.115:21
T42<edp_17> 5. done.15:21
T42<edp_17> Am I right @elros?15:21
T42<ankaos> okey finish :)15:21
T42<edp_17> Try to re-build.15:23
T42<ankaos> rpm/dhd/helpers/ —droid-hal?15:23
T42<edp_17> I usually do the whole, rpm/dhd/helpers/
T42<elros34> @edp_17 like I said, and master branch is correct now. Latest target contains important fix in rpm15:28
T42<edp_17> I know, I use that but he insisted to build
T42<ankaos> I do whatever is in the book.15:32
T42<ankaos> @edp_17 [I know, I use that but he insisted to build 3. …], for the ones in the book
T42<edp_17> The book says, always use the latest version.15:35
T42<edp_17> I highly suggest you to upgrade your sdk, target, tooling and sub-modules to the latest and only then re-build.15:36
T42<ankaos> @edp_17 [I highly suggest you to upgrade your sdk, targ …],
pketo@edp_17 added16:54
T42<edp_17> @pketo : Thank you!17:35
T42<edp_17> @ankaos : Add following into the .hadk.env file:17:39
T42<edp_17> export RELEASE=
T42<ankaos> @edp_17 [export RELEASE=], okey. added17:40
T42<ankaos> @edp_17 [@ankaos : Add following into the .hadk.env fil …], changing the version doesn't work. the screen does not appear.17:46
T42<ankaos> used.17:48
T42<ankaos> systemctl list-unit-files —all17:49
deathmist> droid-hal-init.service                   disabled   ? if you want anything to work you need that service to run and be active, if it fails you will not even have a chance to get GUI.17:58
piggz_<cough>unless on a native port</cough>17:59
T42<ankaos> I do not know what to do. I am trying to ask him.17:59
deathmistpiggz: well sure but that's irrelevant in this case17:59
T42<ankaos> I finally managed to explain my problem. 😂18:00
T42<ankaos> I am waiting for the solution.18:00
T42<ankaos> ubuntu touch did not cause such trouble.18:01
deathmistyour problem is that droid-hal-init is not enabled?18:01
T42<ankaos> is not active. how can I activate it.18:02
deathmistyou must have disabled it yourself, it isn't disabled by default unless you've done something very wrong. "systemctl enable droid-hal-init" will enable the service18:02
deathmistafter that reboot and get full journal output18:03
T42<ankaos> @deathmist [after that reboot and get full journal output],
deathmistI said JOURNAL which means journalctl, you have given output of this command before, right? also now that I investigated the output you just pasted is useless because it shows incorrect states for services (for example droid-hal-init), stop giving output of "systemctl list-unit-files", it is useless.18:22
T42<ankaos> @deathmist [I said JOURNAL which means journalctl, you hav …],
T42<ankaos> it's getting slow. sorry.18:23
deathmistthat entire log is from the span of 13 seconds and definitely doesn't contain useful info from the early boot process to understand why droid-hal-init would fail. if you don't see the Linux kernel version as the first line in journal output I'd say that output is useless too at this stage; something is clearly causing your kernel's socket buffer code to constantly crash (seen 39 times in that log snippet alone)18:30
deathmist@ankaos could you create new pastes for "zcat /proc/config.gz" and maybe "cat /proc/cmdline" as well?18:31
T42Win32_downdadup was added by: Win32_downdadup18:46
T42realSiRiSn0w was added by: realSiRiSn0w18:50
deathmist@ankaos you could try setting the following ( watchdog driver options at the end of your kernel defconfig, recompile a hybris-boot image and boot using it instead, hard to tell what would cause the network socket buffer code to print backtraces so much in the logs, maybe get the output of "/usr/libexec/droid-hybris/system/bin/logcat" too after attempting to boot and waiting for18:53
deathmist30 seconds or so18:53
T42<ankaos> @deathmist [@ankaos you could try setting the following (h …], dont open pastebin. please send paste ubuntu or paste suse18:54
T42<ankaos> ookey. now clean. and build18:58
T42fredldotme was added by: fredldotme19:32
*** Oksana_ is now known as Oksana23:15

Generated by 2.17.1 by Marius Gedminas - find it at!