yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] drinks_rootbeer:
Edit: When I first wrote this comment I was really frustrated. I've since edited it to change my tone. I appreciate all of the hard work and effort put in by everyone working on these projects. I'm having some trouble understanding the instructions for installing LineageOS with Magisk & TWRP. This is what my current process looks like:

1. Flash stock firmware:

- Use Frija to search for latest firmware, download

- Use Odin3 to flash this firmware to my S10+

- Reboot, go through setup, connect internet.

2. Setup Magisk

- Download latest magisk .apk from their site, install.

3. Download TWRP .tar file (TWRP's recovery.img inside)

4. Use Magisk to patch both stock firmware AP .tar file, as well as the TWRP .tar file (I've also tried extracting the recovery.img and patching just that)

- Using "adb pull", copy files off of phone and onto computer.

- Copy the patched TWRP recovery.img file into the patched AP .tar file (have also tried extracting the .tar file to a directory, copying patched recovery.img into the directory, and using 7zip to compress into .tar file)

5. Reboot phone into download mode.

6. Using Odin3, flash the BL, Magisk-patched AP (with TWRP recovery), CP, and CSC_OMC (not CSC_HOME) onto the device. Made sure that "auto-reboot" is un-ticked so I can manually reboot and boot into recovery mode.

7. Multi-disabler

- Reboot to TWRP

- Copy multi-disabler from PC, flash with TWRP (per John Wu instructions for Magisk / s10+)

- Using TWRP menu, reboot into recovery

8. Once in Magisk-rooted android, install Magisk .apk again and allow it to process whatever setup it does at this point.

- It will auto-reboot as part of the final setup. After the phone vibrates and shows the samsung logo as it shuts down, I hold down the recovery key combo so it reboots into the recovery / Magisk-rooted system.

9. test reboot into "recovery"/magisk-rooted android.

- For my own sanity.

10. TWRP Setup

- Reboot into TWRP

- Format Data

- (I wasn't sure if I should reboot TWRP between these steps, but I've done both)

- Wipe Cache / Dalvik

- Flash multi-disabler again? (it says in the LineageOS instructions to do it at this point)

11. Flash LineageOS

- Reboot into TWRP

- Download LineageOS on PC, copy to phone.

- "Install" LOS .zip

- Reboot into recovery.

Sometimes this process seems to work and I'll boot into LineageOS, but after rebooting the phone it gets stuck in aboot loop. Sometimes it just gets stuck in a bootloop and the Lineage install doesn't seem to have worked at all. I'm missing something or getting the order wrong somewhere. I've also seen mention of a vbmeta file, but I'm not sure if I need that since I'm using magisk to patch some files?

Any help would be appreciated, thanks in advance.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] git_gud:
Hello Ivan_Meler, thanks for your wonderful work.

I installed the latest TWRP and this unofficial build on my S10 with no major issues, except Trust is complaining that Selinux is not being enforced and I have no way of turning it back on / enforcing it.

I have been using Lineage OS / Cyanogenmod since Samsung Galaxy S3 and I have never encountered this problem.

My S10 is currently not rooted (rooting it is quite a hassle at this moment, if possible I would like to keep it unrooted).

I had been happily using lineage OS on multiple Xiaomi devices (boot loader unlocked, not rooted) without this issue.

I was also using an Oneplus device (boot loader unlocked, not rooted) without this issue.

Can you tell what is causing it? Do you think we can patch it for the next release?

Once again thanks for your work.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] mecaskey:
Happy New Year!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] therussellhome:
I tried the December build with microG and it mostly worked. I did not try gpay but I could not get signature spoofing working so I'm not sure how much success you will see using gpay.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] therussellhome:
I suspect this is just missing out of the 18.1 source but I had to revert back to 17.1 because this is missing the "Allow clients to use VPNs" hotspot option

@Ivan_Meler continues to impress me with how fast he gets builds out
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] drinks_rootbeer:
I eventually found this set of recommended instructions by PiCkLeS for installing Magisk / TWRP. I followed them exactly as written. Then I rebooted into TWRP recovery, and followed the instructions at the top of this thread:

I don't want gapps so I skipped that portion. I've tried rebooting into the recovery partition, but it is stuck in a boot loop.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
you probably tried to magisk patch twrp and boot to lineage that way which was mentioned multiple times including in post that mentions root that it wont work
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ichmyselfandi:
@Ivan_Meler

Would you please consider patching Sig Spoofing into this rom?

Otherwise it is such a hassle to set up microG correctly.

signature_spoofing_patches
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
Will probably do that son, Unfortunately had a lt fo other stuff t deal with in personal life s i didnt have to much time fr andrid but hpefully ill find time t add it in next build
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Frankdroid88:
Hi all, thanks to Ivan for the great work, the ROM is very smooth and fast. After flashing this ROM i have encountered couple of problems. I was able to connect the phone with my galaxy watch and set it up but the app keeps crushing and the phone disconnets from the watch. I' cant install bluetooth library patcher as this option is only available for stock rom. Miracast is also not woking, the device can't detect any tv. Do you guys have any advice on this ? Thanks everyone for your support
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] drinks_rootbeer:
I see, I misinterpreted the instructions in the top post. Since it says " flash twrp as per given instructions " right below " Download Q twrp from this thread " I took that to mean use the instructions from that thread to flash twrp / Magisk root. I see the third post now which discusses Magisk Canary, is that what you mean?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] :
@Ivan_Meler

I don't want to ask ETA but, Are there any plan to develope for S10 5G(G977X devices)?

I really want to use LineageOS instead of One UI..
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
New builds with january security update are out here is a brief changelog

- Merged January 2021. Security update

- Fixed OpenGapps installation from lineage recovery

- Fixed features that broke with initial 18.1 merge

- Misc performance and stability improvements

- Synced with LOS source

Unfortunately due to recent events i didnt have time to implement all features like signature spoofing as some requested but ill try to do that in a next few days hopefuly

Big thanks to everyone who supported this project as their donations help cover the build server cost
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ilviandante:
Hi! Now miracast works like samsung rom?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hornedfiend:
I'm really hoping someone will be able to find a workaround for recovery magisk soon. I need magisk for some networking apps and always booting from recovery is a bit troublesome atm. 🤞
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
well you can always activate advanced reboot menu and do it without holding a key combo that way, and lineage recovery does most stuff nowadays (except for backup and restore unfortunately), tho i also hope magisk bug causing it will be fixed
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] xdagee:
how about flashing a custom kernel?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] arcanandrei:
Do you experience lag issues with scrolling in Chome/Firefox/Opera on this ROM on Galaxy S10+? Those browsers are literally unusable and they make me feel like I have a phone from 2009. Using Samsung Internet Beta solves this issue, it's blazing fast

Edit: it's possible to get Android Auto working with this rom?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Stamzrat10:
Thanks a lot Ivan! I will be waiting for the implementation of signature spoofing! I found a thread on xda that teaches how to spoof on Android 11,but it's much more reliable to get it straight from you.

Till then, enjoying your 17.1 version
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Stamzrat10:
My Bluetooth works just fine..
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] shatteredsight:
Hi everybody and @Ivan_Meler,

first of all thanks for this rom, is really light and great and I've not had any serious problem so far.

I only have two issues: one with Magisk, and one with my mobile banking app (I think the two problems are related).

I have correctly patched the recovery image and I have root, but as you can see from my screenshot I'm missing

the whole "Advanced Settings" part with the SafetyNet check in it, did I do something wrong?

I also attached the Magisk log for you to check if needed.

The mobile banking app is throwing me the error in the other attached screenshot, I installed your ROM without any gapps so maybe that's the problem? If memory serves me right I thought that I didn't really need the gapps to make

those banking app to work.

I also attached two screenshots from SELinux which is giving me alerts, maybe that's another problem.

Any help is really appreaciated.

Thanks

Davo
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] drinks_rootbeer:
I'm still really confused on what the actual instructions are, and I'm still not seeing any clearly written instructions. In post #1 there are some vague instructions, and in post #3 are some even more vague instructions. Post #1 seems to imply that after following the provided instructions, you will have a twrp recovery with lineageOS installed there. In post #3 it says that if you want a rooted system (implying that instructions in post #1 do not provide root access, is that correct?) you need to use a special variant of magisk (is that what magisk canary is?), modify a special variant of the LOS recovery.img, then flash that modified LOS recovery.img. Is that process from post #3 supposed to happen after proceeding through the instructions in post #1? Does it happen somewhere in the middle of post #1's instructions instead of something else? Does it completely replace the process in post #1?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] ichmyselfandi:
@Ivan_Meler

Does the new Magisk stable release maybe address the current bug?
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Ivan_Meler:
Here are some big news You can finally have root without lineage recovery again check post 3 for instructions and to download boot images Enjoy
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] Valentino911:
Excellent! Thanks a lot @Ivan_Meler 😊
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] mecaskey:
Works like a charm w/TWRP 3.5!
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] WSC Productions:
That's the installation instructions. You first need to check if you're running Android Q. Then install Q TWRP from the thread above linked. Then follow the rest.

It's that easy.
[Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve] hornedfiend:
Awesome. Thanks Ivan.

Now we just need a proper camera for AOSP based roms, one that would allow us two use at least 2 cameras on our phones. That is truly almost the last barrier for me to be able to fully switch to a more aosp rom. I'm not a photographer or not even a camera user that much, but when I do need to take a photo of something, I'ld like it to work the way it's supposed to.

I guess this is the worst part about moving to aosp in general, not just for me. Plus banking or nfc payment solutions.
[Off-topic] srkraidu:
Redmi2 Prime

Not allowing to come to screen by giving intermittent error .
[Off-topic] anistaher:
what's that ?

192.168.100.1 192.168.1.1 jpg to pdf
[Samsung Galaxy Z Fold 2 Guides, News, & Discussion] Nonce01:
Hey

Just wondering if anyone has been able to locate the Thom Browne firmware for the unlocked international version. I’m assuming it should flash without any issues with Odin but happy to be corrected - have only recently shifted from the ‘appleverse’ :D

Thanks
[Samsung Galaxy Z Fold 2 Guides, News, & Discussion] lawtq:
It's on sammobile. Flashed it by mistake. Hated the theme though
[Samsung Galaxy Z Fold 2 Guides, News, & Discussion] Nonce01:
Thanks for the reply... if you don't mind can you send me the link please.
[Samsung Galaxy Z Fold 2 Guides, News, & Discussion] lawtq:
https://www.sammobile.com/samsung/g...e/SM-F916B/BTU/download/F916BTBU1BTIA/372308/
[Samsung Galaxy Z Fold 2 Guides, News, & Discussion] Nonce01:
Thanks. Is there any difference between Multi-CSC OXM and Multi-CSC OXT (I see the TB option at samfrew.com/model/SM-F916B/region/BTU shows Multi CSC OXT)? Would it be safe to flash the Multi-CSC OXT on my OXM phone? Thanks!
[Samsung Galaxy Z Fold 2 Guides, News, & Discussion] HazardsDE:
I would be very glad if someone shared the tbrowne theme with us. I had some problems unpacking. It must be under System/data/overlays/jsonfiles/usersjson there should be the theme located. hope somebody can help out :)
[MTCD Android Head Units General] orik13:
For Dasaita PX6

Updates on Dasaita website: https://www.dasaita.com/blogs/news/update-firmware

-----

Older versions:

Android 10:

HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q

HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ

MCU images - unzip and copy "img" file to flash (sd/usb):

v3.57: View attachment 5111231

v3.60: View attachment 5111233

v3.62: View attachment 5111235

DMCU - unzip and copy to flash (sd/usb) together with MCU image:

for 1280x720 units: View attachment 5111237 - use it if you got a wrong resolution after flashing MCU image and you need to restore your unit to 1280x720 resolution

All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
[MTCD Android Head Units General] halloj:
Before even considering this read in the other thread what happen to my unit. User name halloj,
[MTCD Android Head Units General] marchnz:
Anyone reading this

*** Do not flash the DMCU.ext listed here together with the MCU ***

OP please edit this post, there is NO reason to flash dmcu.ext when flashing the same vendor MCU.

Suggest expanding on the comment "no worries just reprogram", with clear examples if making this statement.
[MTCD Android Head Units General] orik13:
I edited it to make it more clear. Your comment is not absolutely correct: it is based on my own experience. Similar issues can be found by googling and even here at xda
[MTCD Android Head Units General] ToyotaJay:
Hi all I am a bit confused by how many different downloads please excuse me as a noob and first time flashing my PX6

My question is can I just jump from 3.5.8-1 to the latest 3.6.2 I believe and what files exactly do I need to load onto a flash drive.

Your help in advance is much appreciated. Cheers J

I am running a MTCE HA running 3.5.9
[MTCD Android Head Units General] marchnz:
Suggest NOT changing your MCU unless resolving a known issue. Same for Android. This is a head unit, constantly updating isn't necessary.
[MTCD Android Head Units General] gomoriz:
Update for mic issue

Hi Experts! If I want to update my Dasaita PX6 Max10 is there any preferred order which update to do first OTA or MCU? In case of OTA update at starting is it necessary to click on WIPE AND FORMAT FLASH option? Somebody is doing this, somebody is doing that... When is it suggested?

The reason why I planning to switch to latest update because during calls my mic is working strange, sometimes the others cannot hear me properly. They are complaining about low volume and faded voice. (If they are calling back they says it is better...) Have you experienced the same thing?
[MTCD Android Head Units General] orik13:
https://xdaforums.com/showpost.php?p=83671635&postcount=3655
[MTCD Android Head Units General] orik13:
Are you sure it is not a h/w issue? Did you try other mic?
[MTCD Android Head Units General] gomoriz:
I use the internal microphone, not yet tried an external one. I checked the mic with apps, basically it is working however its volume seems to be a little bit low, but it is not faded. I feel it is rather a noise suppression issue (coming from sw side), therefore I hope that an update could help.
[MTCD Android Head Units General] marchnz:
I respectfully disagree based on years of experience: there's no need to flash the MCU configuration file DMCU with an MCU that matches the manufacturer of your head unit. I.e. HA to HA, JY to JY etc.

Your well meaning advice resulted in a configuration not appropriate (which messed up the screen) for another members screen type/resolution.

The 'similar issues' stated are probably your misunderstanding of what the DMCU file is and possibly where others have installed a different vendor MCU. E.g. GS on HLA
[MTCD Android Head Units General] mikrocefal:
Hello, with dasaita px6 android 10 1024/600 firmware HA3, the update "HA3_rk3399_10.0_ota (20200915) 升级 包" and MCU "MTCE_HA_V3.62": all is ok , thank you
[MTCD Android Head Units General] h0va4life:
A few questions...

1) Anybody able to modify steering wheel controls? I open the app and it is blank.

2) Also, can you summon siri/google via the steering wheel when in carplay/android auto?

3) I have an OBD dongle but am unable to get the headunit to connect to it. I see it in the available devices but nothing happens after i select "yes" to connect.

I have the max10 600p resolution version for highlander. A canbus was included and I am able to change vol/toggle modes.
[MTCD Android Head Units General] xdamember2:
When you install a harness with a CAN adapter the steering wheel signals a routed for you to the CAN decoder box. It worked for me to reroute them to my own circuit. It should be equally fine to connect them to the KEY1 and KEY2 inputs, that is if your car has resistive buttons and only one or two. Then you can program them as desired.
[MTCD Android Head Units General] woggles:
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
[MTCD Android Head Units General] Al Ferro:
I noticed that the first time I installed that update, then I went back to the prior version I had, one more time I gave it a try and I started to try to remove that annoying notification, but then I thought why waste time on that, also I notice that saving a screenshot was giving me an error, so once again I went back to the prior version I had installed.
[MTCD Android Head Units General] exCat:
I can’t decide whether to put this up or Malayk’s ROM. I don't really need pre-installed programs, I know which launcher, music player, etc.. I want to use, but there may be settings in it that I can't solve on this ROM.
[MTCD Android Head Units General] thienthanty:
Try

https://xdaforums.com/showpost.php?p=83767241&postcount=3694
[MTCD Android Head Units General] mikrocefal:
bad for me

hello, with this firmware "HA3_rk3399_10.0_ota (20201016) 升级 包", I can no longer make a call with "google voice". :(
[MTCD Android Head Units General] woggles:
Thanks, the annoying pop up is gone but as another use mentioned using call x from Google Assistant doesn't work anymore!
[MTCD Android Head Units General] Alexandru.nae:
The seller ask me to check the cables from times to times, nothing near the issue. In the meantime i run a MUT3 diagnose on the car, I have U0245 error, canbus timeout. The idea is that rockford amplifier and rear camera are working well so the canbus it's working for few things. Only for the atached setting doesn't work. Any idea? Thanks
[MTCD Android Head Units General] marchnz:
On noes, not U0245. If reseller has no suggestions, fire could be answer.
[MTCD Android Head Units General] Alexandru.nae:
:)) I hope not, at least I will fight with the seller for a huge discount.
[MTCD Android Head Units General] jlbooth:
When you change settings in the Vehicle Settings app, that is a WRITE to Canbus operation. When the reverse camera works, it is a READ operation as the system is "reading" the reverse signal state. I would suggest looking at the Canbus settings in the Factory settings to make sure the correct vehicle is chosen and the correct revision for your particular car is chosen.

To get to the factory settings, go to Settings... Car Settings.... Factory Settings... enter 126, then choose the Canbus option at the top. Verify that the correct make/model/year car is chosen or the closest one to your particular vehicle. Hope this helps.
[MTCD Android Head Units General] Alexandru.nae:
Hi, thanks for your advice. I do it already, no luck. For sure it's a RX/TX issue but I cant figure out how to fix it. Also I run MUT3 diagnose on the car, I have 'audio can bus' time outs. I run also can bus line repair with MUT3, no luck. I am going crazy if I will not fix the issue. :)
[MTCD Android Head Units General] Alexandru.nae:
The canbus operation...
[MTCD Android Head Units General] chrisv4:
I have uploaded it for you: https://mega.nz/file/YE9iVaIY#Ul059lmg33l1QEEBbcD7INRJspaMtEDtsbayfAYJFIs
[MTCD Android Head Units General] Bob_Sanders:
You don't need a digital output for an external DSP if that's what you are needing it for. You can use the rca outputs to a dsp. I have the AXXESS dsp which works through rca. It is bluetooth so all your adjustments are done on your phone. It sounds really good

AXDSP-X | Axxess Integrate

Digital Signal Processor with Chime Control and Digital Amp Turn on

axxessinterfaces.com
[MTCD Android Head Units General] jlbooth:
Whether I "need" digital or not, I know I can get audio complete with all the electrical noise I could never want from the RCA output. I was thinking about getting something "reasonably" close to a pure digital output signal without throwing much extra hardware at it. Joying has toslink output which can be driven into an external DSP. Was wondering if similar could be obtained somehow from these that have HDMI output instead of a dedicated fiber optic output. Honestly I don't even know if digital audio is even being carried on the HDMI output. Knowing how cheaply made these are, the HDMI might carry the video signal only.

However I will consider using the suggested Axxess module.
[MTCD Android Head Units General] Apollon2:
IF there is audio output on the hdmi-port (which could be easily tested) you might want to consider this to extract the audio signal: https://www.amazon.de/AmazonBasics-Audio-Extractor-Konverter-Audio-SPDIF-Stereo/dp/B07KRWYN4R
[MTCD Android Head Units General] jlbooth:
@Apollon2 Thank you. That is the type device I had in mind and the one you suggest is quite inexpensive. I use a similar device on my home theater to extract audio from my Chromecast and other HDMI devices to feed into the fiber optic input of my audio amp/receiver.