yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Hello,

I am a noob. I am trying to build LineageOS 18.1 for gt58ltedo.

Repositories :

Manifest :

gt58lte manifest for lineage-18.1

gt58lte manifest for lineage-18.1. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

Device Tree :

GitHub - user20482020/android_device_samsung_msm8916-common: Common MSM8916 tree for Samsung devices

Common MSM8916 tree for Samsung devices. Contribute to user20482020/android_device_samsung_msm8916-common development by creating an account on GitHub.

github.com

GitHub - Galaxy-MSM8916/android_device_samsung_gte-common

Contribute to Galaxy-MSM8916/android_device_samsung_gte-common development by creating an account on GitHub.

github.com

lineage-18.1-gt58lte branch :

GitHub - user20482020/device_samsung_gt58lte

Contribute to user20482020/device_samsung_gt58lte development by creating an account on GitHub.

github.com

Kernel :

GitHub - user20482020/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.

MSM8916/MSM8929/MSM8939 kernel for Samsung devices. - user20482020/android_kernel_samsung_msm8916

github.com

Vendor Blobs :

GitHub - user20482020/vendor_samsung_msm8916-common

Contribute to user20482020/vendor_samsung_msm8916-common development by creating an account on GitHub.

github.com

GitHub - retiredtab/android_vendor_samsung_gte-common

Contribute to retiredtab/android_vendor_samsung_gte-common development by creating an account on GitHub.

github.com

GitHub - user20482020/android_vendor_samsung_gt58lte

Contribute to user20482020/android_vendor_samsung_gt58lte development by creating an account on GitHub.

github.com
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
@retiredtab

Where can I find camera.vendor.msm8916.so ? On my device I have camera.msm8916.so but no camera.vendor.msm8916.so ?
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
If you are going to use my roomservice.xml, upload that to your github as well so I can see what you are doing. Obviously, you will have to change some things that are gt58wifi specific to gt58ltedo.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
You can rename it when you do copy. For example,

https://github.com/user20482020/pro...ineage-17.1/gt58ltedo/gt58ltedo-vendor.mk#L26

vendor/samsung/gt58ltedo/proprietary/lib/hw/camera.msm8916.so:$(TARGET_COPY_OUT_SYSTEM)/lib/hw/camera.vendor.msm8916.so \

See how it's copied and renamed above?
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
BTW, in your first build, you will likely face stuck at boot animation problems. I highly suggest you build an "eng" build when you do a brunch or make. That way, the OS will start adbd right away and you can run

adb logcat -C

right away to see log messages.

I run

TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j2 bacon

I explain more in this thread. I helped someone who has never built LineageOS before. A lot of the questions you may have might be answered there are already so please give that a read.

https://xdaforums.com/t/need-help-building-a-sm-t555-gt510lte-lineageos-rom.4255243/

In addition, the SM-T555 is the bigger brother to SM-T355 so you might be able to use code or look at his code for clues as the two should be very similar.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Uploading it as attachment. I intend to change the account of repositories. I'll upload manifest to a repo after that.

I modified the 1st post to include link for the roomservice.xml.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
I missed that. Thanks.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
The debugging tips from that thread will be super useful. Plus a similar device that has RIL will be helpful too. Thanks.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
I used the crdroid-9.0 branch to create the device tree. Do you still use the crdroid-9.0 branch ?
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
There's something strange with the above. On my 17.1 gt58wifi build, my directory shows

l@l-8100:/media/l/gt58wifi/17/out/soong/host/linux-x86/bin$ ls -al avbtool
-rwxrwxr-x 1 l l 28148198 Apr 12 00:02 avbtool
$ file avbtool
avbtool: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, with debug_info, not stripped
$ file apexer
apexer: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, with debug_info, not stripped

whereas your shows avbtool and apexer has a directory.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
I'm wondering if your manifest.xml is somehow messing up the make? I suggest removing lines 4 to 20, doing a complete repo sync and a make clean (start over) and then your brunch or make command.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
When I made 17.1 or Android 10, I used the crdroid-9.0 branch beause at that time there was no 10.0 branch and when there was, too many things got moved around so I stuck with 9.0. Either 9.0 or 10.0 is fine as long as you know how to change and move things around.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
What desktop OS are you using? If linux, what distro? If Windows, are you using WSL version 2?
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Bare-metal Fedora 34

I did that. It still fails at the same step.

There were a few more warnings (?) in both builds :

[ 53% 353/660] Target boot image: out/target/product/gt58ltedo/boot.img
patch boot out/target/product/gt58ltedo/boot.img out/target/product/gt58ltedo/boot.img.lok
cp: bad 'out/target/product/gt58ltedo/boot.img.lok': No such file or directory
Made boot image: out/target/product/gt58ltedo/boot.img
[ 55% 366/660] ----- Making recovery image ------
patch recovery out/target/product/gt58ltedo/recovery.img out/target/product/gt58ltedo/recovery.img.lok
cp: bad 'out/target/product/gt58ltedo/recovery.img.lok': No such file or directory
Made recovery image: out/target/product/gt58ltedo/recovery.img

Actually python trace shows where in the source file the error occured. I too have avbtool and apexer in out/soong/host/linux-x86/bin directory as single file.

I tried enabling dm-verity in kernel config (required by apex image according to

https://source.android.com/devices/tech/ota/apex#required_kernel_configuration_options). It still fails.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
what command do you use to build ?

I am using source build/envsetup.sh && lunch lineage_gt58ltedo-userdebug && mka
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Maybe Relevant

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
LINEAGE_VERSION=17.1-20210801-UNOFFICIAL-gt58ltedo
TARGET_PRODUCT=lineage_gt58ltedo
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.13.4-200.fc34.x86_64-x86_64-Fedora-34-(KDE-Plasma)
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES= hardware/qcom-caf/msm8916
============================================
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Also were you trying to compile TWRP for T350/T355 ? If yes, then can you provide the link for twrp device tree ?
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
recovery.img zipped.

Removed by me.
[Samsung Galaxy Tab A series Questions & Answers] Rahul.raj:
Hi,

I have an SM-T355Y (gt58ltedo) Tab and I was keen to get this compiled as well.

I tested the recovery you sent. It does boot properly. There is some issue in the zip path due to which it does not extract/ install directly, but when I navigated through the structure and took out the recovery.img, it flashed fine with TWRP and I was able to then reboot to recovery using this.

Hope that helps.

Waiting with baited breath for a LineageOS for my Tab. ♥
[Samsung Galaxy Tab A series Questions & Answers] Rahul.raj:
An update - the adb does not work properly in this recovery.

It gives an option under 'Advanced' to switch on ADB, but on the PC, it keeps showing as offline.

The same was working fine on the TWRP v3.1.1 and v3.1.0 recoveries I was using. Have shifted back to that recovery as I needed the ADB link to upload files to the tab.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Thanks for doing this. It helped me pinpoint that the issue is missing dependencies on os and not manifest error. I installed lubuntu and the build succeed. I also switched to lineage-18.1 from 17.1. Right now the device boots to lineageos logo and then restarts. I attached a logcat with this post (cat logcat.1.log prints it in console with colours). Could you give me some pointers (apart from missing files) to fix bootloop ? I also noticed that your repositories enforce SELinux. Is there a easy way to disable it ?

I am using TWRP from ashyx. The device model is not set in it so I have to patch the zip created by android build system and remove device verification. Do you by any chance have a manifest for building twrp ?

I wondered about that. Official docs say dm_verity is required to enable apex image integrity verification. Plus all the other things required by apex image is enabled/set in config. Does it slow our device if dm_verity is not enabled (by falling back to other verification methods) ?

== Logcat ==

02-16 05:06:57.943 366 366 E android.hardware.drm@1.0-impl: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libprmediadrmdecrypt.so: dlopen failed: library "libdiag.so" not found: needed by /system/vendor/lib/libdrmfs.so in namespace (default)

02-16 05:06:58.004 392 392 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/rmt_storage": library "libqmi_csi.so" not found: needed by main executable

But the libraries are being copied according to makefile.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
I'm sure lots of people use something other than Ubuntu flavours to build LineageOS. You just have to find the correct libraries/dependencies for your distro.

Any .txt or .log files that are in plain ascii for some reason NEVER show up as an attachment in xda. Resend the file ZIPPED. That's why I zipped the recovery.img file above. It's zipped so that it shows up on xda, not zipped to be installed by TWRP as a zip file.

Revert this commit

https://github.com/retiredtab/andro...mmit/775ca9d472eb1013214f4f91be86b056f4ff1443

and recompile. If your policies aren't written correctly, your device will never boot properly or function properly.

In 17.1, I had no sepolicy and decided to try learning about in 18.1.

No and neither does ashyx when I look at

https://github.com/ashyx?tab=repositories

I suggest you build TWRP using

https://github.com/SebaUbuntu/TWRP-device-tree-generator

So use the existing ashyx TWRP recovery as the file to feed into Seba's generator OR you can use the recovery.img that LineageOS builds.

It's what I use and it works if you use it with TWRP 7.1. I built SM-T710, SM-P550 and SM-T560NU TWRP using this procedure and all work fine.

https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1

It only takes about 10 minutes to build on my slow machine (about 8,000 files to compile). TWRP 7.1 will likely generate an image size smaller than 16MB. I had problems with TWRP 9.0 and 10.0 building images > 16MB which won't fit on the recovery partition.

Unless you are building an "official" rom, there's not need to worry about it. All my 17.1 and 18.1 builds for SM-T350, SM-T550, SM-P550 and SM-T560NU work fine without dm-verity for 1+ years (for 17.1 builds). My 18.1 builds were used by me first in March 2021, then released to xda in July 2021.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
Go to your out directory and search for both those files that are reported missing.

I see the code copying them

https://github.com/user20482020/and...lte/blob/lineage-18.1/gt58ltedo-vendor.mk#L59

and

https://github.com/user20482020/and...lte/blob/lineage-18.1/gt58ltedo-vendor.mk#L96

but you should actually double check they got copied.

If both are there, then it's possible that libprmediadrmdecrypt.so/libdrmfs.so and rmt_storage are looking for their respective files in /system/lib and not /vendor/lib. You can check by using a hexeditor and looking at libprmediadrmdecrypt.so and rmt_storage for the libraries OR you can change $(TARGET_COPY_OUT_VENDOR) to $(TARGET_COPY_OUT_SYSTEM) for the 2 lines above.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Uploaded zipped logcat
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
Your logcat shows a bunch of missing files. Your problem lies inside this make file. See if you can spot the problem?

https://github.com/user20482020/android_device_samsung_gt58ltedo/blob/los-18.1/lineage_gt58wifi.mk
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
I edit post #27 because it wasn't pointing to the latest 18.1 code.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
If you are going to build 18.1, you should update all your github repos to default to branch lineage-18.1. That way, when I go there, I don't have to choose it all the time. That's why I had to edit post #27 and #28 because I was looking at the older revisions and not the latest. Still your problem lies in that make file.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
Thanks.

Ok

I have updated the github repositories to point to correct branches. The makefile you linked above refers to old repository and I was using lineage-17.1-gt58lte branch. I have updated manifest and first post to point to correct branches and repositories. I am terribly sorry about the branches and repositories.

I built the rom and booted into the OS.

Wifi works.

Bluetooth works (File transfer, don't have hardware to test bluetooth audio)

Audio Works through speakers and headphones but logcat has a lot of errors.

Camera does not work.

GPS gets fix after 3-4 minutes (satellite only).

Somehow I managed to make UI very large (google keyboard now takes half the screen). Before the latest build the notification panel was small and appeared only where I swiped (in small width). Now it takes entire screen width. I think the changes I made were : https://github.com/user20482020/dev...4a557825aee073e20b0112ab76f4ca8e4bc4eL98-R105

How can I bring back telephony packages (phone,sms,etc) ?

Do you have this too ?

02-17 05:26:17.762 378 378 E android.hardware.drm@1.0-impl: Failed to lookup symbol createDrmFactory in library /vendor/lib/mediadrm/libprmediadrmdecrypt.so: undefined symbol: createDrmFactory

Could you look at the recent commits (mainly in device tree repo and msm8916) and offer some pointers ? I have also attached logcat.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
For future logcats, I don't need them in color. I can read them using gedit and it knows how to interpret the various messages into color. It's a lot easier for me to view and search logcats in gedit. Thanks.

Actually, your logcat shows bluetooth crashing hard so it's not going to be stable. Anytime you see those messages, they have to be fixed otherwise your system won't be stable.

If you have a bluetooth adapter for your PC, this is what I do.

https://ostechnix.com/turn-your-lin...tooth on your,Bluetooth devices and list them.

Try using opencamera. I couldn't get stock camera to work in 18.1 for some things and gave up because opencamera works. Evervolv 11 has stock camera working and I tried using his repos, but that breaks a lot of other things for my other devices.

Did you go by a window to do the test?

When testing new roms, it's probably best to do a complete data wipe or factory reset to get rid of any old settings that may be causing the above.

I think you have to change

device_samsung_gt58lte/lineage_gt58lte.mk at lineage-18.1-gt58lte · user20482020/device_samsung_gt58lte

Contribute to user20482020/device_samsung_gt58lte development by creating an account on GitHub.

github.com

to something that is suitable in the vendor/lineage/config directory. Perhaps common_full_phone.mk? I don't know for sure. I don't have any RIL devices.

Yes, getting DRM to work is problematic. I suggest you load devcheck by flar2 and scroll to the system tab to check the DRM settings. At best, you will only get L3. You will probably need to implement something like

https://review.lineageos.org/q/_ZN6google8protobuf8internal13empty_string_E

At one point, I thought I had it working using the above, but something could have broken? DRM is needed for $treaming services.

For bluetooth, because your device is different from T350, I suggest you work on that first. There's only so many combinations that you can try to find out what works.

https://github.com/user20482020/and...916-common/blob/lineage-18.1/manifest.xml#L23

https://github.com/user20482020/and...6-common/blob/lineage-18.1/msm8916.mk#L76-L78

For manifest.xml you can try changing

<transport>hwbinder</transport>

to

<transport arch="32">passthrough</transport>

and see if you stil get crashes. You can also try removing either android.hardware.bluetooth@1.0-impl or android.hardware.bluetooth@1.0-service. You will probably have to do a

make installclean

to clear out all the old bluetooth files if you are going to try the above. This process will be iterative. I don't know what combination will work. It's something I have been through several times and you need persistance to figure it out.
[Samsung Galaxy Tab A series Questions & Answers] retiredtab:
You will probably want to revert this change of mine for your RIL 355

vendor msm8916-common: remove qmuxd from wifi only devices

https://github.com/user20482020/ven...mmit/3c3c2b77b8db15219000ff148ce0a1bd56f04906
[Samsung Galaxy Tab A series Questions & Answers] Rahul.raj:
Do you need any help in testing your build?

Aside:

Has anyone tested flashing a gt58wifi LineageOS build on a gt58lte/do?

I do not need Cellular service on my Tab and if wifi, bluetooth and speakers work, then it could be enough for me.

I am sure, many other would feel the same.
[Samsung Galaxy Tab A series Questions & Answers] Rahul.raj:
@user655362020 : Hi,

Can you share if you were able to proceed further?

Thanks for your time and effort.
[Samsung Galaxy Tab A series Questions & Answers] user655362020:
You can download the dev build : https://sourceforge.net/projects/li...18.1-20210804-UNOFFICIAL-gt58lte.zip/download

Last I checked bluetooth, wifi and speakers do work but logcat will have errors.

Due to time constraints I won't continue to port this device.
[Samsung Galaxy Tab A series Questions & Answers] ansprasanth:
Hi @Rahul.raj did you manage to find any roms for T355Y / gt58lte? I'm in the same boat as you still looking for a custom rom.
[Samsung Galaxy Tab A series Questions & Answers] Rahul.raj:
The dev build shared by @user655362020 in the message above ( https://xdaforums.com/t/need-help-building-a-sm-t355-gt58lte-lineageos-rom.4312671/post-85862337 ) seems to work for me.

I am not sure if it is the OS, or some issue it has with particular apps, but I do see some issues on performance and frequent lags for some apps which requires me to regularly clear cache and restart them.

But given that no one yet has done anything close to what this member has done, I am insanely grateful to him and would not bug him given he does not have time to work on this port anymore.
[Huawei P50 Pro] MikeChannon:
See:

https://www.xda-developers.com/huawei-p50-series-specifications-features-pricing/
[General Questions and Answers] Soumitra k:
I think i messed up while flashing a custom rom on my nokia 7.1 and now my device is on a bootloop. I can't go into recovery mode (volume up+power button) or bootloader (volume down+power button). I can't even shut it down. The phone is just keep on rebooting to android one logo. Please help.
[General Questions and Answers] :
Reflash phone's Stock ROM to get rid off of all modifications you applied so far.
[General Questions and Answers] LR7875:
He cannot, the buttons are not doing anything.
[General Questions and Answers] :
Then OP should take phone to authorized service center and let them try to fix it. :)
[General Questions and Answers] LR7875:
No offence to the OP, but as this is an 2018 phone, the warranty should be as dead as a stone.

Hope the OP managed to somehow use the buttons to boot into at least bootloader(fastboot), or the phone is R.I.P.
[Motorola Edge 20] MikeChannon:
See:

Motorola Edge 20 series spotted on certification site ahead of launch

The upcoming Motorola Edge 20 and Edge 20 Pro have stopped by the TENAA certification website, revealing key specs and design.

www.xda-developers.com
[Motorola Edge 20] snickersmini:
I installed Elixir4.0 GSI, but I can't use SMS. help me
[8125, K-JAM, P4300, MDA Vario Software Upgrading] insanavaca:
:D Was asked to re-post in upgrading and wm6

I had my 8125 flash a bad rom and was stuck on splash screen.

fixed it with mtty1.42

connect in bootloader mode with usb

choose usb connection not com1, or com2

you will get a white screen press enter

then you see cmd>

type format will show you what you can format

you want to format the os part starts with a b cant remember exactly

once its formated flash a rom and you should be good to go if you have any questions just let me know.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] end123:
I dont have the option for USB.. just COM1 and COM2

Please advise??
[8125, K-JAM, P4300, MDA Vario Software Upgrading] tempoct:
Have the same problem. I'm running Vista. Do I need XP to do this?

or, is it possible to flash via MiniSD?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] insanavaca:
Then you probably have active sync on turn if off and disable it so when you plug in the usb cable it doesnt automatically come up.

Sorry took so long to get back
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ~The_Sultan~:
I had the same problem when i've flashed the black diamond wm6.1 rom, but all i had to do is to turn the device into bl mode (camera key + power key) and then reflash it..

If that wont work for me again ill give your tip a try. thanks! :)
[Motorola Edge 20 Pro] MikeChannon:
See:

Motorola Edge 20 series spotted on certification site ahead of launch

The upcoming Motorola Edge 20 and Edge 20 Pro have stopped by the TENAA certification website, revealing key specs and design.

www.xda-developers.com
[Motorola Edge 20 Pro] fire159:
Hey everyone . I Wana buy edge s pro ( Chinese version of edge 20 pro ,)

İs anybody here has this phone . I Wana know how is the phone and can I install Google apps on Edge s pro ?

There is a seller on AliExpress who sell Edge s pro with global rom , But hi unlock the bootloader ( so I will miss the ota Updates of motorola ) and it makes me disagreeable .
[Motorola Edge 20 Pro] ilia3367:
Yes, you can install it.
[Motorola Edge 20 Pro] ijuanp03:
Yes you can install it. Just go to Settings > System and enable Google Play Services. After enabling, install Google Play Store apk and install all other Google apps from there.

No root required.View attachment 5435783
[Motorola Edge 20 Pro] retekevo:
Hi!

Is Hungarian language present on the s version?
[Motorola Edge 20 Pro] monsmons262626:
help how to fix deadboot​

Motorola Edge 20 pro help how to fix deadboot​

i use blank-flash.bat but not work​
[General Questions and Answers] Phrezh:
Do anyone have a software update for this type of unit..
[General Questions and Answers] Deleted member 1890170:
Android updates ( read: patches ) get rolled out by OEM if they deem it necessary.
[General Questions and Answers] Phrezh:
Huh
[General Questions and Answers] Phrezh:
View attachment 5385537

Can u help me find a update 4 this type of set up