Wednesday, 2023-08-23

*** amccarthy is now known as Guest33501:49
*** amccarthy_ is now known as amccarthy01:49
defhello guys15:23
defIm trying to adapt sailfish to old htc m7 (and maybe others devices).15:23
defi'm trying to follow that one :15:23
defeven if the "repo" installation wasn't easy, Im stuck on the 5.3 Configure Mountpoint Information:15:23
defI dont know if rooting by adb/usb, providing me this :15:23
defbut do I have to look after a kind of fstab (not present in /etc within the device), or the previous pastebin is enough?15:23
def" To get the correct path you must find Android’s fstab in device repository or in device itself and get by-name path like: block/bootdevice/by-name/userdata, ls -l /dev/block/platform/*/*/by-name/15:24
def``or ``block/platform/*/by-name/userdata from it"15:24
def<= I dont understand that part, nor how should I process the fixup-mountpoints...15:24
T42<elros34> find fstab file in device repository: $ANDROID_ROOT/device/*/15:44
defT42: you mean it's in that?
T42<elros34> more or less but check whole device/ including device/htc/m7-common and
defT42: thank you16:33
T42<elros34> you can call me directly not via telegram bot name16:35
T42<elros34> btw there is something wrong in telegram channel because I can see only admins16:36
T42<TheVancedGamer> @elros34 no, thats for "security"16:36
T42<TheVancedGamer> I can disable it later if you wih16:36
T42<TheVancedGamer> wish*16:36
T42<TheVancedGamer> its so that spammer bots cant PM people randomly16:36
defT42: Once you’ve patched fixup-mountpoints <= i guess it's the fstab needed to get the montpoints process working?16:37
def(that starting this chapter where my linuxies skills reaches their limits :( )16:37
T42<elros34> @TheVancedGamer oh me neither can't ping @<anybody>16:37
T42<TheVancedGamer> pings should work fine if you remember their handle16:37
T42<TheVancedGamer> it wont show up however16:37
defhow could i process the fixup-mountpoints? I dont understand that part..16:46
def(btw, do I have to come on a channel?16:46
T42<elros34> def: is m7spr similar to m7?16:46
T42<elros34> you need something like this but with correct partitions for you phone:
defT42: I have no idea, it's a pn07100 (htc m7 gsm)17:07
defT42: thank you for that link, but how should I use it with fixup-mountpoints? it's the first time I port something...17:09
deflooks like its going to a kind of C part17:11
T42<elros34> use it as an example, add similar lines but for m7 instead m7spr to fixup-mountpoint file. Then adjust all partitions according to your pastebin so all partitions are included and have correct block device17:11
maldo not highlight with T42 use @some_nick if people are using telegram17:12
defhe's using telegram through irc?17:14
defii knew it was possible with matrix..17:14
malthat T42 is a telegram tunnel bot or something like that17:16
malto highlight people from there use the @ and the nick which is after that T4217:17
defelros34, i guess that it's a mountpoint tool within the habuild tool?  i just dont understand how it's managed17:18
T42<elros34> what tool are you talking about? just go to hybris-boot/ and edit file17:19
T42<elros34> you should have all of these already cloned to $ANDROID_ROOT17:20
defim there : HABUILD_SDK [m7] HABUILD_SDK [m7] HABUILD_SDK [m7] HABUILD_SDK [m7] hd@g50-70:~$17:24
defcd $ANDROID_ROOT/17:25
defHABUILD_SDK [m7] HABUILD_SDK [m7] HABUILD_SDK [m7] HABUILD_SDK [m7] hd@g50-70:~/hadk$ ls17:25
defmy hadk folder is empty17:25
T42<elros34> then you followed instruction incorrectly because you should have whole android tree cloned in $ANDROID_ROOT17:26
T42<elros34> od you have .repo directory?17:26
def.repo$ ls17:26
defTRACE_FILE  copy-link-files.json  manifest.xmlmanifests  manifests.git  project-objects  project.list  projects  repo17:26
T42<elros34> did you finish chapter 5.2 pdf17:27
defyes, i did a repo sync which took a long time17:28
T42<elros34> are you sure? you don't even have local_manifests which you create in 5.217:29
T42<elros34> did you run repo command in $ANDROID_ROOT directory?17:30
T42<elros34> "repo has been initialized in /home/hd" but according to chapter 5.1 you should do this in $ANDROID_ROOT. Is ANDROID_ROOT even set (4.1 chapter)?17:41
T42<elros34> 'echo $ANDROID_ROOT' should prints correct path both in platform sdk and habuild17:44
defsry for delay18:20
def@elros34 : echo $ANDROID_ROOT18:20
T42<elros34> so answer is no and you should check .hadk.env and other sdk related files18:21
T42<kreatowastaken> is there a13 support yet?18:27
T42<kreatowastaken> if there is, what does work/not work?18:27
T42<kreatowastaken> my device got aosp ported recently, want to take a shot at it18:27
defi think i did something wong18:29
T42<elros34> yes it's because of repo init, see your previous pastebin. There is even info there like 'if that directory is wrong then do this'18:32
def@elros34: what do you mean by repo init?18:33
defoh i see18:33
def@elros34: you mean repo init -u -b hybris-14.1 from the hadk folder?18:34
defsorry for being so noob18:34
T42<elros34> you run repo init many times and probably in '~' instead in '$ANDROID_ROOT' so .repo directory is initialized wrongly in ~. I would show you this in your pastebin but you removed it or expired.18:39
T42<elros34> i don't know if you can simply just move .repo/ to correct directory and repo sync again but you may try18:41
defelros34 : my .repo is in /home/hd because everything is in there18:48
defelros34: where should i move .repo?18:50
T42<elros34> to $ANDROID_ROOT18:51
def@elros34: i have this  but i dont know how to do the fixup-mountpoints18:58
T42<elros34> forget about it now. First of all you are missing some repositories. in android_device_htc_m7 there is cm/lineage.dependencies which should contains additional repositories which you need to local manifest19:05
T42<elros34> add*19:05
T42<elros34> btw shouldn't you use repos from lineageos instead cyanogenmod?19:07
defelros34, repo from cm/los14 yes  (for me it's the same project, just a different brand)19:12
defthat one might be the right one?
defsry  : repo init -u -b hybris-14.119:14
T42<elros34> it maybe same project but repositories are not same19:14
defwhat i understood is that i need two urls : one from cm/los, the other is dedicated to hw specs19:15
T42<elros34> lineage one have more changes19:15
defphone is running well lineageos14.119:15
T42<elros34> then use that in local manifest19:16
defelros34: the maniest is well the xml file saying which brand/model? i modified it19:20
defbut the thing is still the fixup-mountpoints i dont understand19:21
T42<elros34> told you to forget about it now. You dont even have correct local manifest xml file. Did you add repo from cm/lineage.depenedencies file like I told you19:22
T42<elros34> ?19:22
defelros34: the manifest file you're talking about, is it well in this?
def(or maybe im wrong)19:30
T42<elros34> the local manifest xml file is what you supposed to create according to hadk pdf 5.219:32
defelros34: okay, I understand better, but what i was thinking was just to modify it with brand/model?19:32
T42<elros34> first you should add LineageOS/android_device_htc_m7 then you add other repositories which usuall are defined in lineage.dpendencies files so common and in common another lineage.dependencies file which contains another common and kernel repo19:35
defelros34: so i need to do firstly repo init  -u -b cm-14.1 ?19:39
T42<elros34> no, focus on 1 thing at a time so now correct local manifest: $DEVICE.xml19:43
T42<elros34> not any repo init or anything else, create file and show me it19:44
def<?xml version="1.0" encoding="UTF-8"?>19:45
def<project path="device/htc/m7"19:45
defrevision="stable/cm-14.1" />19:45
def<project path="kernel/htc/m7"19:45
defrevision="stable/cm-14.1" />19:45
defbut i guess its a wrong one?19:45
malwhy not
T42<elros34> here:
def@elros34: did you wrote it yourself? or find out on the web?20:04
T42<elros34> I wrote it20:05
defthe thing is, the pdf asks for lot of resources, but sometimes it's a bit hard to understand how to look for them20:05
defi know what is msm8960, a mainboard i guess ; the guy whom doesnt know much more how to port a device, would never had to guess that this file might have a such information..20:06
def@elros34 : thank you20:06
T42<elros34> porting is whole new experience, you need to learn a lot of different things like lineage.depndencies files which contains all these info I used to create this local manifest20:07
def@elros34 : i never build/porter cm/los neither, so im going  to discover a lot i guess..20:11
def@elros34: so if i want to port lineage or sailfish on others devices, maybe i need also to know how to parameter a such file?20:12
def(im wondering how much work is still remaining :o i guess a lot more)20:13
def@elros34, now could I repo init...?20:25
T42<elros34> like I said use Did you open it? It's self explanatory. Re repo: just use commands from hadk pdf and make sure .repo/ is in correct place20:47
def@elros34 : okay, but the url doesn provides information youadded in the manifest.xml.. so i dont know, what to do now..21:35
T42<elros34> it does: "project path"->"target_path", "name" >"repository". The only missing is "revision"  but this is easy because "cm-14.1" is default one21:39
T42<elros34> then you open lineage/cm.dependencies file lineageos/android_device_htc_m7-common and same thing21:40
def@€lros34: so the lineage.dependencies must be found for each different device or model to be ported to?21:44
T42<elros34> yeah21:45
def@elros34 : msm8960-common and common, i just dont get it ; it's not shown on the git page ; i think a nice draw.....21:50
def@elros34 : but after that step, i guess there are dozen of steps like that one?21:50
defi'd like so much compile the whole thing during the night, but it looks like im very far of it22:00
T42<elros34> it is
T42<elros34> building image according to instruction is easy then you may start porting (solving real device specific issues)22:04
T42<elros34> m7 is quite old with 3.4 kernel so it will not work out of the box22:04
def@elros34, i have heard that for lineage just the lineage git/repo plus the device tree was needed, but i never did it22:06
defwell, los14 (android 7.1) works well on that device22:06
T42<elros34> again some chinese guy breaks hadk-hot, can you please do not use translators directly whoever that is22:07
def@elros34, i dont udnerstand22:07
T42<elros34> this is not for you, just for some unknown porter who breaks porting notes22:09
def@elros34, oh okay22:09
def@elros34, but that said, the pdf specifies to install repo using google documentation, well ; that one doesn't works quite well, i had to get some others methods on the internet22:10
defjust to understand better : does porting los or sailfish to a device, is the same process for htc/samsung/huawei/wiko/oppo/oneplus/sony/others brands?22:15
T42<elros34> I do not know how porting los looks like but for sure not like porting sailfish. Porting sailfish for different kind of devices is similar in basics  but of course every device/platform or even kernel generates whole new set of challenges.22:21
T42<elros34> don't mixup porting sailfish with just building already working lineage port from existing repositories22:22
T42<elros34> I have added short info about creating local manifest file, feel free to imporve it:
defi would dream of a "taken hand by hand" how to, to improve the port of various devices with sfos22:28
defi took me two evennings to get a correct environnment of build for sfos, but the build itself would asks for days more I guess22:29
defso now im totally lost in the process :(22:29
def@elros34: how should i do with the manifest.xml to manage the repo part?22:46
T42<elros34> I don't get what you. just fillow pdf and do repo sync22:49
def@elros34: fatal: include [/home/hd/.repo/manifests/]default.xml doesn't exist or isn't a file23:00
defi think i wrongly named the xml file23:01
defit's called m7.xml23:02
T42<elros34> default.xml != $DEVICE.xml23:10
T42<elros34> check that file with ls -al23:13
def@elros34: -rw-rw-r-- 1 hd hd 478 Aug 23 20:12 m7.xml23:14
defso I might rename it default.xml i guess?23:14
defit's not precised in the pdf :(23:15
T42<elros34> file in error not m7.xml file23:19
def@elros34, what do you mean?23:20
defthe error comes from another file?23:20
T42<elros34> read the error you posted23:27
def@elros34:  i guess i have to indicate within the repo command?23:34
defbut how?23:34
T42<elros34> what? error is "/home/hd/.repo/manifests/]default.xml doesn't exist or isn't a file" so just do ls -al /home/hd/.repo/manifests/default.xml23:36
defls -al /home/hd/.repo/manifests/default.xml23:39
defls: cannot access '/home/hd/.repo/manifests/default.xml': No such file or directory23:39
T42<elros34> what about .repo/23:40
T42<elros34> ah it's old path23:44
T42<elros34> remove that ~/.repo23:44
T42<elros34> leave it only in $ANDROID_ROOT/23:45
def@elros34: should i do then  repo init -u -b cm-14.123:47
def or repo init -u -b cm-14.123:47
def ?23:47
T42<elros34> neither, correct command is in hadk pdf23:48
defjust repo sync --fetch-submodules?23:48
defit's the one after the xml part23:49
def@elros34: is it the right command?23:55
def@elros34: the repo sync asks for a firstly repo init one23:56
T42<elros34> whatever do both if you want23:59

Generated by 2.17.1 by Marius Gedminas - find it at!