Related
Has anyone successfully compiled the kernel and opensrc directories from the download from Samsung's Open Source site? I am running into compiler errors for things like xt_CONNMARK.c since the file doesn't exist in the source tree. Is the Galaxy i9000s download actually compilable, and is it actually compatible with the Captivate?
Thanks,
-Atin
Oh cool, I had no idea they had the source available. Samsung just got a lot more awesome in my book. I'll be looking into this when I get back to a computer, and hopefully devs can do something interesting with it.
From my understanding of previous Samsung phones and there source code its that the source code provided is not complete. Anything proprietary is not included which includes some drivers and some extra bit of code.
I don't know if they skipped stuff but I do see binary modules, so maybe they did put every thing out, just didn't open source every thing. Given that we can still link the binary modules, this shouldn't be a problem just like under linux. My problem is more simple, the danged code won't compile because either the config or the dump itself is incorrect (missing files like xt_CONNMARK.c which is gone in later versions of the kernel, but should still be present in what they dumped).
atinm said:
I don't know if they skipped stuff but I do see binary modules, so maybe they did put every thing out, just didn't open source every thing. Given that we can still link the binary modules, this shouldn't be a problem just like under linux. My problem is more simple, the danged code won't compile because either the config or the dump itself is incorrect (missing files like xt_CONNMARK.c which is gone in later versions of the kernel, but should still be present in what they dumped).
Click to expand...
Click to collapse
If they handled the Galaxy S like they do other phones then I believe Eugenes comments apply here
http://forum.androidspin.com/showpost.php?p=12840&postcount=13
Edit: WARNING! If you do not follow the below instruction, your post WILL be deleted, not moved. Thank you for your cooperation. ~TheRomMistress
bally3 said:
Appreciate your enthusiasm, but can you move the conversations about userspace (builds) to the Discussions thread please, as this thread should be primarily for the KERNEL development only.
Appreciate your understanding,
Click to expand...
Click to collapse
Hi!
I have now a TG01 too, and started to develop some Linux stuff for it.
The branch for it is in our htcleo repository.
http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc/commits/linux-on-tg01
I did already a bit reasearch and put some new stuff in the htc linux wiki. I will update it if I found something new.
http://www.htc-linux.org/wiki/index.php?title=Tg01
17.09.11 Edit10 and last:
Hi!
I pushed my last changes. There some new stuff in repo now like:
- Powerbutton support
- Fixes for Power/USB
- Panel Code
- Notifications
- Usb cable pull/push did not crash device anymore
and much other.
I'm closing this project for me because I've no time to work on it.
One Info, the problems with the GUI after boot are ril related. The biggest work is RIL. It looks like you have to write (or find) a RPC based RIL lib.
have fun!
Markinus
Edit9:
Calls works now. But the mic not.
Battery works, a simple cable detection driver too. Problem, you cannot in the moment pull or push the cable in/out. If you do it the devices will crash after ca. 15 sec.
Build updated.
Edit8:
Audio and vibration works.
!Important: Run clrcad.exe in wince bevor you run haret and boot linux!
Edit7:
The Volume and Camera Buttons are now supported.
Edit6:
Added touchscreen buttons
Added first Test Build! Extract to sd and run haret! Look to Post 2.
Edit5:
Touchscreen is working now. I had to recalculate the calibration values. Later we have to look to better calib values, maybe a calib app for users.
Edit4:
We have now a official mach id 3197. This have to be changed in the default.txt for haret.
Edit3:
So some new stuff is checked in:
- panelfile with basic support for mdp and lcdc
- sd card works
- usb works
- rpc, pcom, works
Status: the device is booting now android till the unlock screen in the GUI, but without touchscreen ...
Edit2:
Branch is in our Leo repo:
http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc/commits/linux-on-tg01
The basic stuff is now in. Is booting. I didn't find a device ID for tsunagi, so I had to create one.
status: kernel is booting and android starting. We need to write much new stuff to get all hardware working.
default.txt:
set mtype 3197
set ramaddr 0x11800000
set ramsize 0x0e800000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline ""
boot
We need to research much stuff. And all this needs much time. So don't ask for dates
!!!IMPORTANT: USE ALL STUFF AT YOUR OWN RISK!!!
!You can break your device!
Markinus
First Test Build:
Look to top whats working.
Second testbuild:
http://www.multiupload.com/WQN1Q1SJ0E
http://www.multiupload.com/P0B04IK8S0
Have fun on test!
!!!IMPORTANT: USE ALL STUFF AT YOUR OWN RISK!!!
!You can break your device!
hi markinus! i'm glad to see another dev involved to port android on TG01! a new hope for our phone! yesterday i've thinked to sell it.. but now i've a new hope.. and can't wait for some news, good luck.. and if you need help.. just ask..
just a question.. what means "kernel is booting" status? sorry for my english
can you post a link to the kernel your using?
Good to see things moving here.
Hope that the TG01 community will get a workin' kernel
They're worth it.
Ok. I'm going to try this one but after I finish with my homework.
I'm downloading it now.
Wait for news.........
Nice thread, I hope to have good news ..
Last News...
After I download the file I had some problems. It gave me errors when I try to make arch=arm tsunagi_defconfig. Error was like a privet file and you don't have access. So I copy all the files on new directory and then I was able to do make arch=...... defconfig. Then I compiled it with success.
Then I make all changes in default.txt and it run then restart. But this time I think it's problem from some APP. What it say but I wasn't able to see it. It was to fast.
I need some help to set debug haret.
Current default.txt in haret/debug/ is: pwf tg01-ramconsole.txt 0x1FFC0000 0x40000
If some one can help me how to change it that's go be perfect.
Sorry about my English I'm still learning.
Markinus said:
Hi!
I have now a TG01 too, and will start to develop some Linux stuff on it.
I will create a new branch for it in our htcleo repository because some things we can use for both. If I have something what you could try, I will post it here.
I did already a bit reasearch and put some new stuff in the htc linux wiki. I will update it if I found something new.
We need to research much stuff. And all this needs much time. So don't ask for dates
Edit2:
Branch is in our Leo repo:
http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc/commits/linux-on-tg01
The basic stuff is now in. Is booting. I didn't find a device ID for tsunagi, so I had to create one.
status: kernel is booting, it means we go through the basic hardware init. I fixed the memory layout.
default.txt:
set mtype 1100001
set ramaddr 0x11800000
set ramsize 0x0e800000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline ""
boot
Markinus
Click to expand...
Click to collapse
That's great job what have you done. It's amazing. I thing kernel is booting now but I am not sure. With me is still restarting.
If I can help with something just tell me. I'm not professional but may be I can do something.
I was thinking about board configuration and all other configs.. but I didn't know how to do it. So
Thanks for your job.
For those who want to try himself.
1st. Download from Markinus posts his repository it's on the right side on the page http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc/commits/linux-on-tg01
2nd. Unzip it in a folder that you have created before. How to unzip it?
Go to Applications -> Accessories->Terminal
In Terminal tap: cd name of your new folder, ( example: cd myAndroid )
then you have myAndroid$
Now you tap : tar xvzf directory where you have download Markinus repository. (example: tar xvzf /home/downloads/linux-on-wince-htc-linux_on_wince-htc-linux-on-tg01.tar.gz.gz)
You will see how the file is unziped.
3rd. You will see in your folder that there is a new folder named (linux-on-wince-htc-linux_on_wince-htc-on-tg01 or something like that). If you see like a small lock in the front of this folder then do this. Create a new folder put the name you want. Then cut everything from the folder linux--on-wince-htc...........etc. and past it in your new folder.
(example what I did it was easy just in my folder myAndroid I create a folder kernel_1 and I paste everything inside.
4th Now wen we have not everything but may be a part of. Is time to download toolchan (compiler) and some libraries.
in your Terminal tap : apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev.
thats for the libraries.
and this one for tollchains or cross tools or ... what you want call it.
http://www.codesourcery.com/sgpp/lite/arm/portal/release858
download it and install it. in the same folder as repository (example myAndroid/cross_tools)
Thanks to Endrix with his tutorial help me a lot.
5th.Now enter in your kernel_1 folder or whatever you called it and tap: make ARCH=arm tsunagi_defconfig
6th When finish writing to configuration. tap: make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
enter
If you have done everything without errors then you will see how linux is building your kernel.
7th When finish building go to (exaple myAndroid/kernel_1/ARCH/arm/boot/ ) ther is your kernel Image and zImage you can use both if you want. :O)
Thanks Markinus and Endrix.
EDIT: I've only got windows at work... Can someone please upload a compiled kernel so I can try it on my TG01 so I can give feedback?
Awesome, seriously well done guys!!!
I've not had time to help like I had hoped, so simply well done to those involved so far
).
Glad to hear it finally arrived Markinus
Good to have you on board too. With regard to a compiled kernel, everyone please allow Markinus some to time to get things working before we start asking for kernels to check.
Just so that people understand, kernel booting doesnt mean kernel loading a android gui environment, so theres still nothing to see. What Markinus means by that is he can see that the hardware is being initialised and the things that should be happening when a kernel boots are happening.
Good to see things moving again though
bigandrea said:
Hopes for Windows 7 Phone?
Click to expand...
Click to collapse
This is an Linux/Android thread. You should ask the question in the appropriate thread.
Bally, I knew it wasn't ready per se, I just wanted to try and contribute by testing to see if they got the output they expected on multiple phones as I don't have the time to help with development as I expected to
One thing ttt bothers me, TG01 has a low amount of ram (or at least i think so) for winmo most roms get just 100 or so.. Running opera and some music on the backgorund may be enought to get things messsy.
Will android spend more or less in comparissom?
thanks
Kalas_22 said:
One thing ttt bothers me, TG01 has a low amount of ram (or at least i think so) for winmo most roms get just 100 or so.. Running opera and some music on the backgorund may be enought to get things messsy.
Will android spend more or less in comparissom?
thanks
Click to expand...
Click to collapse
i also worried about this too. but most android devices have 256 ram or so. and android is more effiecient with ram management than windows mobile. we also have badly optimised toshiba dlls. when running android, it shuts down windows mobile, and opens android os, so both os dont run in the background, thus saving ram. also i wonder after we manage to get functional android roms, we get skinned versions, such as HTC Sense! what do you guys think+
There you have one compiled kernel..
Is ready to execute. Just extract it to your sd card in your phone and that is all. Then run haret.
This one is from Endrix file I just replaced the Image file and set the new default text. There is a zImage as well and you cant try it if you want.
bojan6 said:
There you have one compiled kernel..
Is ready to execute. Just extract it to your sd card in your phone and that is all. Then run haret.
This one is from Endrix file I just replaced the Image file and set the new default text. There is a zImage as well and you cant try it if you want.
Click to expand...
Click to collapse
dont have a tg01 to hand at mo.. can anyone post up the output please?
Scougar said:
Bally, I knew it wasn't ready per se, I just wanted to try and contribute by testing to see if they got the output they expected on multiple phones as I don't have the time to help with development as I expected to
Click to expand...
Click to collapse
I stand corrected.
Markinus HAS got to the gui...wow!
we need a touch screen driver now.. good work...very impressive!
bally3 said:
I stand corrected.
Markinus HAS got to the gui...wow!
we need a touch screen driver now.. good work...very impressive!
Click to expand...
Click to collapse
im sorry but does this mean, we have a functional bootable androidrom??
Hello all. I am trying to checkout the CM source from the git repository.
When I try to run the initial sync by running 'repo sync' I get an error after a couple hours of downloading. Looks like it has downloaded everything as there is 3.4G under the .repo folder and another 2 gigs in the /android/system folder. Also, the scripts says if fetched 100% (215/215). The error is:
Syncing work tree: 72% (155/215) error: revision master in CyanogenMod/android_packages_apps_CMParts not found
It then fails and dies. Quite a bit of the system source is in the tree, but the vendor branch is gone, so I can't even start working on it.
I have never used git before, so I am kinda lost in it. anyone wanna give me a hand?
Please post questions in General section.
cbusillo said:
Hello all. I am trying to checkout the CM source from the git repository.
When I try to run the initial sync by running 'repo sync' I get an error after a couple hours of downloading. Looks like it has downloaded everything as there is 3.4G under the .repo folder and another 2 gigs in the /android/system folder. Also, the scripts says if fetched 100% (215/215). The error is:
Syncing work tree: 72% (155/215) error: revision master in CyanogenMod/android_packages_apps_CMParts not found
It then fails and dies. Quite a bit of the system source is in the tree, but the vendor branch is gone, so I can't even start working on it.
I have never used git before, so I am kinda lost in it. anyone wanna give me a hand?
Click to expand...
Click to collapse
i've never looked at the CM source, but post a link to the repo and Ill see what I can get tonight.
If downloading the source tree to compile and work on porting CM to Epic doesn't belong in the development forum, what does?
I found the problem; there is no longer a master revision in the CMParts project, it was renamed to froyo. After initializing the repo, you have to manually change the revision in the .repo/manifest.xml
Hello all,
i'm using this guide http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vision_(Mac) on the cyanogenmod wiki to build for my mt4g. I successfully built it a couple times with no issues, but the last couple days i've been running into a wall at the end of the build. I completely wiped out the working drive and re-init repo and everything. All steps go fine until I make bacon, then near the end of the build I get this
Code:
Target ram disk: out/target/product/glacier/ramdisk.img
target Dex: core-junit
Copying: out/target/common/obj/JAVA_LIBRARIES/ext_intermediates/classes.jar
Copying: out/target/common/obj/JAVA_LIBRARIES/bouncycastle_intermediates/noproguard.classes.jar
target Prelink: libutils (out/target/product/glacier/symbols/system/lib/libutils.so)
libelfcopy: Warning: DW_FORM_data8 is unsupported when sizeof (unsigned long) != 8
libelfcopy: Warning: DW_FORM_data8 is unsupported when sizeof (unsigned long) != 8
libelfcopy: Warning: Location lists in .debug_info section aren't in ascending order!
libelfcopy: Warning: Range lists in .debug_info section aren't in ascending order!
libelfcopy: Warning: Range lists in .debug_ranges section start at 0x318
Copying: out/target/common/obj/APPS/QuickSearchBox_intermediates/classes.jar
target Prelink: libwpa_client (out/target/product/glacier/symbols/system/lib/libwpa_client.so)
target Non-prelinked: libnetutils (out/target/product/glacier/symbols/system/lib/libnetutils.so)
target Prelink: libhardware (out/target/product/glacier/symbols/system/lib/libhardware.so)
target Prelink: libssl (out/target/product/glacier/symbols/system/lib/libssl.so)
target Prelink: libjpeg (out/target/product/glacier/symbols/system/lib/libjpeg.so)
ASSERTION FAILURE external/elfcopy/elfcopy.c:932: [ranges[i].start >= last_end]
make: *** [out/target/product/glacier/symbols/system/lib/libjpeg.so] Error 1
make: *** Deleting file `out/target/product/glacier/symbols/system/lib/libjpeg.so'
libelfcopy: Warning: Range lists in .debug_info section aren't in ascending order!
make: *** Waiting for unfinished jobs....
MacBook-Pro:android jam$ /CODE]
any ideas? this is driving me nuts! thanks for the guide peeps!
Are you trying to patch in anything from gerrit?
nope
I wish, that would be easier to figure out. Just a straight pull from source.
Unfortuately I dont have an answer for you then. The nightlies are building so it should work.
How did you "clean everything out"?
make clean
mka bacon
i deleted the disk image used for the working dir. and started over. and yeah i tried make clean.
then I'm out of ideas. Sorry man. Hopefully someone else comes along with more knowledge of it.
I tried setting up my SnowLeopard Macbook to compile AOSP and decided to give up. There are simply too many hacks/patches needed to get SnowLeopard to play nicely to compile AOSP. I am not sure about the CM build tree, but I assume CM follows AOSP, so they should be similar in setup.
My suggestion, get Parallel Desktop, install Ubuntu-64, download all the necessary libraries/tools, compile, done...
I wasted 2 days trying to get my SnowLeopard to compile AOSP, then I wised up and used Parallel+Ubuntu, then I was able to compile AOSP in 3 hours, after that, I downloaded MT4G Kernel source from HTC, compiled that in an hour... (BTW, if you decide to use Parallel, I suggest you make the virtual harddisk size to at least 20GB, I made a mistake allocating only 16 GB, but for AOSP+HTC Kernel, I ran out of space, had to use GParted to extend my virtual disk, wasted 1/2 hour there)
AOSP version 2.3 (GingerBread) and beyond requires ubuntu-64 anyways, so this is future proofing anyways...
faux123 said:
I tried setting up my SnowLeopard Macbook to compile AOSP and decided to give up. There are simply too many hacks/patches needed to get SnowLeopard to play nicely to compile AOSP. I am not sure about the CM build tree, but I assume CM follows AOSP, so they should be similar in setup.
My suggestion, get Parallel Desktop, install Ubuntu-64, download all the necessary libraries/tools, compile, done...
I wasted 2 days trying to get my SnowLeopard to compile AOSP, then I wised up and used Parallel+Ubuntu, then I was able to compile AOSP in 3 hours, after that, I downloaded MT4G Kernel source from HTC, compiled that in an hour... (BTW, if you decide to use Parallel, I suggest you make the virtual harddisk size to at least 20GB, I made a mistake allocating only 16 GB, but for AOSP+HTC Kernel, I ran out of space, had to use GParted to extend my virtual disk, wasted 1/2 hour there)
AOSP version 2.3 (GingerBread) and beyond requires ubuntu-64 anyways, so this is future proofing anyways...
Click to expand...
Click to collapse
Thanks for the advice, I've spent a few days myself trying aosp first, then CM. I actually did get a few working roms out of my mac from the cm source until about a week ago. Then i started to get the errors above. It's like they changed something in the source that no longer agrees with the tools or os installed. I'll give the parallel + ubuntu a shot. But i have a quick question for you. Did you actually get a working aosp build for mt4g? Flashed and all features working?
conclusion
Well i gave the parallels desktop a shot and it was super easy to setup,build environment setup fine and repo sync'd .. except i couldn't get adb to list my device. I searched and tried all kinds of rules (i.e. 51.android.rules) and no go. So, I decided to go back to the dual boot option. I tried to get 10.10 installed, but when I try to boot the ubuntu cd from rEFIt menu, i get
1.
2.
Select CD-Rom Boot Option.... or something like that
then I restart into osx
I tried a couple different discs and nothing. So, I went back to 10.4 and all is fine now.
I also kept searching for the rules for glacier and found them here http://wiki.cyanogenmod.com/index.php?title=Udev#MyTouch_4G
With that, I may try VirtualBox in the future, or some other free VM, but for now, I'm working with dual boot and trying to build an AOSP rom. Thanks for the help guys!
Sorry to resurrect an old thread, but for the sake of anyone who finds this thread by searching I thought I'd add that I've developed fix that allows CM7 to be built on OS X 10.6. I've submitted it to the AOSP gerrit: https://review.source.android.com/#change,22597
I need a little bit of help portingh crDroid 6 to the sm-t350. Nubianprince started then got pulled away by work. I have initalized the crdroid repo, but i when i run repo sync i think it only downloaded like, 300 mb. i do have an android pie enviroment, does repo link resources? i dont know what is going on there. I will upload my roomservice.xml. I had to remove a couple lines from the original and manually clone them because it keeped giving me an error. the original is here https://github.com/Nubianprince/local_manifests/blob/master/crdroid-ten.xml .
Currently i am using this device tree: https://github.com/Nubianprince/android_vendor_samsung_gt58wifi most custom roms i see are using this: https://github.com/Valera1978/android_device_samsung_gtaxlwifi . I have not seen any non sm-5xx devices using it though, so i hesitate to switch. i worked out a a couple errors of things being defined twice, and then built. but i think i am missing something as the build fails with this: FAILED: ninja: 'out/target/product/gt58wifi/root/init.usb.configfs.rc', needed by 'out/target/product/gt58wifi/ramdisk-recovery.cpio', missing and no known rule to make it
Is there a "quick fix" to provide this file? I am not actually sure what i am missing, or what creates it.
Any help would be appreciated.
This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.
nubianprince said:
This file "init.usb.configfs.rc" is missing from your device tree, somewhere in one of your files you have the path pointing to "init.usb.configfs.rc" which does not exist. Let me know if that makes sense.
Click to expand...
Click to collapse
Yes, it does make sense. I just don't know enough about the android environment to know where the file, or what is pointing to it, would / should be.
Okay. I believe there is a missing, or many many missing makefiles. I found the file and manually copied it to out, and then the build fails with another missing file. Rinse and repeat, there are a ton of files not being put where they should be. Now what to do with that information, i am not sure ??. I tried including a couple of the make files from android 9, but they didn't make any difference.
oh yeah, and if i do lunch instead of brunch it fails with a different file missing: FAILED: ninja: 'out/target/product/gt58wifi/system/addon.d/50-lineage.sh', needed by 'out/target/product/gt58wifi/verified_assembled_framework_manifest.xml', missing and no known rule to make it
it makes no sense adding files to the "out" folder, fix the issues in your "device" folder check your device.mk file
Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.
lividhen99 said:
Wow. That was really awful. I don't even know what i was thinking there. What i was trying to say, is that i was manual copying the files to see if it was just one or two not being copied. I have been comparing the Pie and Q makefiles to try to determine what file was supposed to be copying it to out, but i cant find it in Pie, all i know for now is that it is being copied in Pie but not Q. For now I'm gonna' keep looking for the correct file.
Click to expand...
Click to collapse
What device tree are you using, do you have it on Github?
nubianprince said:
What device tree are you using, do you have it on Github?
Click to expand...
Click to collapse
I am just using the device trees (ten branch) on your GitHub. I haven't made any changes that have gotten me anywhere so i haven't committed my local changes to my GitHub.
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I have been away for a while and haven't followed along, but the last week I spent compiling ROMs. I also tried compiling Android 10 using "stock" lineageos gt58wifi and I got stuck at the logo as well. I also tried another device from the msm8916 repository and got stuck at the logo.
The "stock" gt58wifi build, as we all know, has problems with audio, bluetooth, smart cover, etc, etc in all versions 14.1, 15.0, 16.0 and won't even boot with 17.1.
When I first compiled it, it would fail due an error with a config.xml file. I submitted a patch, like others, but haven't seen anything yet.
https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi/pulls
nubianprince said:
That crdroid ten branch still need a lot of work, the last build I did when I was working on it was not getting past the logo
Click to expand...
Click to collapse
I'm working on SM-T560NU 17.1. It too was stuck at the boot logo. I built an eng build and found it was the hardware vibrator that was getting stuck in a loop. If you remove the vibrator hal from
/device/samsung/msm8916-common/manifest.xml
that should work on the SM-T350 because both platforms share the same msm8916 code?
I did build SM-T350 with 17.1 and was stuck at boot logo and gave up. However, I have not rebuilt it knowing this new information. I will try again with the above change in a few days?
So, as retiredtab has said, he got android 10 booting. But it has all the issues android 9 did: no camera, sound, Bluetooth, or Hal sensor (sort of, it can turn the device on but not off). The system ui is also a little funny on crdroid, not sure about lineage. I don't know how to fix these issues, or where the roots of the problems may lay. Do you have any suggestions for learning more about the android source code? I feel like the aosp docs are good, but you kind of have to know what you're looking for.
I think part of the problem with the SM-T350 is that there has never been a fully working build since day 1. Lineageos 14 had problems to begin with and they were never fixed and got carried over to 15, 16 and now 17. If stock Lineageos 16 was fully working, then getting it to work on 17 would be less of a challenge.
The most likely problem to no audio, camera, bluetooth etc is the Samsung proprietary blobs are not in the correct directories or the configuration blob files are pointing to the wrong directory.
When I face this problem, I find it helpful to look at a working roomservice.xml file and do comparisons.
If there is no working roomservice.xml like "stock" lineageos 14, 15, and 16 for the SM-T350, then I look at similar models. For example, the T550 is the bigger brother and it helps to look through it's roomservice.xml file for hints.
Remember that a compiler mainly checks for syntax errors, not semantic. If you make a typo, a compiler will flag that as an error, but if you write correct syntax, but put a file or files in directory ABC instead of XYZ, the compiler won't say anything.
Another thing that might help is doing a logcat of a working build and comparing it to a non working build. There might be a very obvious error message like "can't find audio.hw.msm8916 in directory /device/samsung/msm8916" or something like that.
Learning how to use tools like meld and diff help tremendously in finding file and directory differences in case you put the blobs in the wrong place. See
https://www.tecmint.com/compare-find-difference-between-two-directories-in-linux/
I used meld when troubleshooting the stuck at boot logo.
If you are a visual learner, I found the following youtube channel helping in learning the overall process of building ROMs.
https://www.youtube.com/c/AlaskaLinuxUserAKLU/videos
I think we have lineage 16 fully working. I think the part I'm having trouble with here is the difference between where the files are read from in Android Q vs P.
If I understood what you said incorrectly, please say so.