**** BEGIN LOGGING AT Fri Dec 13 02:59:58 2019 Dec 13 12:26:28 The error which I get shows no space in device https://paste.ubuntu.com/p/zNCc4JXybK/, when i checked there is no cpuset in /dev Dec 13 12:26:35 why is it so Dec 13 12:45:14 the above link is that of console-ramoops Dec 13 12:45:24 this is kmesg: https://paste.ubuntu.com/p/bb7w6XwxZ5/ Dec 13 12:45:39 im not even able to connect to system via usb Dec 13 12:45:52 it just keeps trying to connect and fails Dec 13 13:11:30 I tried plasma mobile and got in console-ramoops : https://paste.ubuntu.com/p/xKdRKDkyCw/ Dec 13 13:25:08 bgtm11 was added by: bgtm11 Dec 13 13:25:53 @Win32_downdadup: /dev/cpuset/system-background/tasks: No space left on device is not critical here Dec 13 13:26:10 These are "normal". LuneOS was working perfectly fine with these errors being present Dec 13 13:27:07 @Herrie [These are "normal". LuneOS was working perfectly fine with these errors being pr …], Oh I see Dec 13 13:28:01 @Win32_downdadup [The error which I get shows no space in device https://paste.ubuntu.com/p/zNCc4J …], Herrie but my device was not booting, but it was a blank scree Dec 13 13:28:11 *screen Dec 13 13:28:36 I saw the a list of no space remaining issues Dec 13 13:28:46 And a few permission issues Dec 13 13:29:25 Win32_downdadup: Let me see if I can find some of my Xiaomi logs Dec 13 13:29:32 My device is mido, I had borrowed the kernel config from you a couple of days for checking if it was a problem with my kernel issue Dec 13 13:29:44 @Win32_downdadup [My device is mido, I had borrowed the kernel config from you a couple of days fo …], From webos irc Dec 13 13:29:49 😊 Dec 13 13:29:58 @Herrie [Win32_downdadup: Let me see if I can find some of my Xiaomi logs], Yes please, thanks Dec 13 13:30:36 @Win32_downdadup: There is also SFOS port for Mido by piggz, I used his kernel. Some of these messages look weird, but they are actually OK :S Dec 13 13:30:55 I’m in USA looking for hacker to work with for longterm business Dec 13 13:31:15 @Herrie [@Win32_downdadup: There is also SFOS port for Mido by piggz, I used his kernel. …], So why would I get a blank screen I'm wondering Dec 13 13:32:33 @Herrie [@Win32_downdadup: There is also SFOS port for Mido by piggz, I used his kernel. …], I'll check it out Dec 13 13:37:34 @Win32_downdadup: I thought you had LUneOS booting at some point? Dec 13 13:37:49 @Herrie [@Win32_downdadup: I thought you had LUneOS booting at some point?], It was working fine Dec 13 13:38:18 But it seems halium has some issues, gives me a black screen Dec 13 13:38:29 And I can't connect Dec 13 13:38:36 Usb attempts connection but fails Dec 13 13:38:45 @Win32_downdadup [Usb attempts connection but fails], Repeatedly Dec 13 13:39:00 Win32_downdadup: You would need to add fixup_mountpoints step for Halium itself Dec 13 13:39:06 To be honest we were lazy there ;) Dec 13 13:39:17 😄I see Dec 13 13:39:24 I had seen it already had it all Dec 13 13:39:26 So I thought Dec 13 13:39:30 It was not needed Dec 13 13:39:32 We don't use the Halium rootfs ourselves, so we don't need all these bits Dec 13 13:39:45 So we just made sure that the Android part built Dec 13 13:39:53 @Herrie [So we just made sure that the Android part built], Oh Dec 13 13:40:12 @Herrie [Win32_downdadup: You would need to add fixup_mountpoints step for Halium itself], Then it should be the problem Dec 13 13:40:17 Thanks a lot Dec 13 13:40:28 You would need to follow: https://docs.halium.org/en/latest/porting/build-sources.html#include-your-device-in-fixup-mountpoints Dec 13 13:40:38 Shouldn't be rocket science to fix really Dec 13 13:40:40 Just never got to it Dec 13 13:40:42 Oh yeah Dec 13 13:40:47 Too many things to do, too little time ;) Dec 13 13:41:01 Lol yeah Dec 13 13:41:24 @Herrie [Too many things to do, too little time ;)], Thanks a lot herrie, u helped me a lot Dec 13 13:41:32 😁👍 Dec 13 13:46:17 @Win32_downdadup [Repeatedly], Actually it mounting before and I did telnet into diagnosis.log, after I added CONFIG_AUTOFS4_FS=Y it woulf stay stuck and gave the above errors Dec 13 13:46:27 And usb stopped connecting Dec 13 13:47:03 *usb was mounting Dec 13 13:47:15 @Win32_downdadup [*usb was mounting], Before Dec 13 14:03:13 Anybody into porting phonelines?...pummeled Dec 13 14:06:42 [Edit] Anybody into porting phonelines?...pmme Dec 13 14:27:45 Marcus Nickel was added by: Marcus Nickel Dec 13 14:30:57 Hey guys. Switched from UBports Porting to the Halium grp, because I'm planning a UBTouch port to an older Android device with a 3.0.6+ Kernel running. Does anyone in here has any experiences with that kernel? Dec 13 14:46:28 @Marcus Nickel [Hey guys. Switched from UBports Porting to the Halium grp, because I'm planning …], Oh boi Dec 13 14:46:53 I tried on the Samsung S3. I tried legacy porting at this time, when Halium was in early stages only Dec 13 14:47:42 Well I failed for Halium, since it uses systemd and that requires a hihger kernel version Dec 13 14:48:06 So if you want to make a UT port, you could try it still, as it usese upstart right now Dec 13 14:48:15 Which device is it Dec 13 14:48:21 @Flohack [I tried on the Samsung S3. I tried legacy porting at this time, when Halium was …], Oh okay... Wanted to use an old Tolino Tab from 2012 in my FHEM infrastructure Dec 13 14:48:30 ouch that sounds really old ^^ Dec 13 14:48:39 Do you have all repo sources for that? Dec 13 14:50:13 Right now not, just collecting the information if it makes sense to reuse it for this project. But it seems that it's more easier to buy an used compatible device and install UT there Dec 13 14:51:27 @Marcus Nickel [Right now not, just collecting the information if it makes sense to reuse it for …], Well if you want to use a device soon then its easier. It can take you months to get a device into a usable state with porting, and I am talking about newer devices that people were working on ^^ Dec 13 14:52:36 @Flohack [Well if you want to use a device soon then its easier. It can take you months to …], :D Got it. … Any tips which device has the actually best compatibillity? Dec 13 14:53:35 @Marcus Nickel [:D Got it. … Any tips which device has the actually best compatibillity?], Basically all of them are ok: https://devices.ubuntu-touch.io/ - plus there is Sony Xperia X and Oneplus 3/3T nearly finished, those need further work, but are already quite usable Dec 13 14:54:56 @Flohack [Basically all of them are ok: https://devices.ubuntu-touch.io/ - plus there is S …], Many thanks! Will check the list. Dec 13 15:22:02 wrt to ril and ofono .. i get a startup message of ril daemon complaining about a missing qcril.db - I found a bunch of sqlite databases called qcril db Dec 13 15:22:12 some contain emergency numbers .. flags.. Dec 13 15:22:38 other only contain operator numbers? .. and short string "3gpp" and so on.. Dec 13 15:46:09 i am unsure if that file is actually necessary.. Dec 13 16:02:16 found an empty one and placed it in the expected location: Dec 13 16:02:19 12-13 15:52:16.321 78 78 E RILQ : (0/78): RIL[0][rild] qcril_db_check_and_upgrade: Unable to find vendor version. Not upgrading … 12-13 15:52:16.567 71 71 E SSLM : ERROR: RF: [17/01/02 10:57:05]: 973: rfc_lte.cpp: MIPI device init failed LTE ASM device! instance=8 | Phone may bootup on offline mode. Modem won't work and yo Dec 13 16:02:19 u can't find SIM. **** BEGIN LOGGING AT Fri Dec 13 17:33:43 2019 Dec 13 17:38:20 @anpok [12-13 15:52:16.321 78 78 E RILQ : (0/78): RIL[0][rild] qcril_db_check_a …], You miss this probably from vendor or device tree Dec 13 17:40:42 Yup none for any of the kitakami devices Dec 13 17:43:35 And Android works well with that? Dec 13 17:43:55 I mean it must either ship or be generated Dec 13 18:17:18 Hm I found an empty sqlite DB.. That changed the error message Dec 13 18:17:47 I havent used the default android on that device Dec 13 18:18:57 It now complains that it will not Upgrade the device device because the vendor version is missing, and there is a table for that in the DB Dec 13 18:19:13 Fwd from anpok: 12-13 16:17:23.266 78 78 E RILQ : (0/78): RIL[0][rild] qcril_db_check_and_upgrade: Unable to find vendor version. Not upgrading … 12-13 16:17:23.516 71 71 E SSLM : ERROR: RF: [17/01/02 11:22:11]: 973: rfc_lte.cpp: MIPI device init failed LTE ASM device! instance=8 | Phone may bootup on offline mode. Modem w Dec 13 18:19:13 on't work and you can't find SIM. … 12-13 16:17:23.516 71 71 E SSLM : ERROR: RF: [17/01/02 11:22:11]: 973: rfc_lte.cpp: MIPI device init failed LTE ASM device! instance=4 | Phone may bootup on offline mode. Modem won't work and you can't find SIM. Dec 13 23:11:33 曹博棠 was added by: 曹博棠 Dec 13 23:20:48 @anpok [12-13 16:17:23.266 78 78 E RILQ : (0/78): RIL[0][rild] qcril_db_check_a …], I found smth for Samsung S4 Dec 13 23:22:52 @anpok [I havent used the default android on that device], Well maybe can you download default ROM for it, and extract just that file? Dec 13 23:23:48 In which folder this would be? **** ENDING LOGGING AT Sat Dec 14 02:59:57 2019