I see that today's nightly update proposes the update to LineageOS 20, is there any official tread already?
[ROM][OFFICIAL] LineageOS 19 for Galaxy S10e/S10/S10+/S10 5G Exynos
- Thread starter Linux4
- Start date
According to the latest comment from the LOS 13 unofficial thread the release made it to the official status:
[ROM][UNOFFICIAL][13.0][OTA][Signature Spoofing][Open Source][Encryption] LineageOS 20 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
I don't think Wi-Fi calling works. I know for sure that VoLTE isn't implemented and I think both depend on Samsung's proprietary framework.
Attachments
Many thanks for your reply, @zpunout.
This is very disappointing. I had hoped to be able to fully "de-google" my phone, but I live in a rural area of the UK with very poor mobile reception, so WiFi calling is vital (VoLTE is not important to me). Maybe one day........!
Thank again for your advice.
This phone is virtually unusable as a phone. 40% of the time my call drops, always where I can't hear them but they can hear me. I see it drop from LTE to E randomly while on the phone and that's when I lose the ability to hear them or the call disconnects. I'm using the Global dual SIM S10e on T-Mobile in the USA. I assume this is due to the Samsung VoLTE driver issue. Anyone have a fix for this?
Also audio volume fluctuates seemingly at random during music playing over bluetooth, headphones, and speakers (has to be a software issue) and I can barely hear people over speaker or earpiece.
Had none of these issues on my dying Essential Phone.
Flashing to LineageOS 20 as a last ditch effort.
Also audio volume fluctuates seemingly at random during music playing over bluetooth, headphones, and speakers (has to be a software issue) and I can barely hear people over speaker or earpiece.
Had none of these issues on my dying Essential Phone.
Flashing to LineageOS 20 as a last ditch effort.
Maybe try setting the phone to not drop to E (2G) for calls and instead use 3G instead?
To access this hidden menu, go to the "Phone" dialer app and type *#*#4636#*#* .
Under "Phone information", take note of the current setting under "Set preferred network type" and write it down.
Then try changing that setting to "LTE/WCDMA" and then make a phone call. (It might take a couple of minutes and maybe even a reboot for the network to accept the change though.) The phone will try to use the 3G network (if available) to make and receive calls instead of the 2G network.
Well, it was worth a try. I only get a network busy with that setting. It'll try to call out and then fails, even after a reboot. I think the core issue is the T-Mobile 3G network got shut down and the bands auctioned off in the US.
These damn companies like Samsung and Google should be prosecuted for e-waste. They won't even unlock our bootloaders after their hardware goes EOL and they won't give us access to source code to be able to use them on common networks.
I went ahead and ordered a bootloader unlocked non-Verizon Pixel 4a. Don't like Google but it sounds like the safest bet. I can't answer or hold the connection on my clients' phone calls and it's becoming embarrassing.
Last edited:
I seem to have a similar problem noted. With LOS19 I see that HDMI is working, but the screen flashes, behaves odd, the phone then reboots within a few seconds. I had the same on the pixelexperience which was A13 as LOS20 would be. Leads me to believe it is an issue with the AOSP. I didn't yet upgrade to microg~LOS20 due to laziness, but it seems to be a good time.
The audio fluctuations are probably because you have dolby atmos turned on, try disabling it from the sound & vibration settings menu
I think this was the issue. Went away after I updated to LOS 20 and I believe it turned it off post-update. Thank you!!
Hello, recently I am having issues with Google Wallet, device passes safety net certification with Magisk 26.1 installed, also props are set and safety-net fix 24.0 mod 1.2 applied. It used to work well on LineageOS 19 but after upgrade to LineageOS20 the GWallet does not allow contactless payments anymore. Status in play store is certified, Does anyone know how to make GWallet work on los20? Please.
Hi
Ive found that Lineage 19.1 from Ivan is much more stable with regards to network drops. Lineage 20 seems to have to many bugs and seems to be unfinished as a daily driver. I've had more regular dropped calls and missing notification issues for apps like whatsapp, Signal and Telegram as the data function seems to randomly disconnect regardless of network or being on Wifi. It's like the network works fine after a reboot and then dies after a few days. Lineage 19.1 seems to be more stable.
I've gone back to 19.1 at this stage until the bugs are sorted which may take some time.
Please don't promote other projects in a developer's thread. It is rather rude. It's one thing to try to offer constructive criticism and feedback in an effort to help the developer improve this project; it's another entirely to use this thread to declare your preference for someone else's work.
As a reminder:
Developers on XDA work for free. These projects are their hobbies, and they are not compensated for their work. Nothing shared on XDA shall have any guarantee, express or implied, and you use the work at your own risk. Treat our developers with respect. They've helped make XDA what it is today.
Is anyone else having issues with the phone constantly pocket dialling people since the upgrade to LOS20? I'd guess it's something to do with the "long press fingerprint sensor to unlock phone" but there's no option in settings to control it, just the title with a blank screen
Thanks for that tip! I had tried so many different things and hacks to get rid of that problem, after all it was that simple!
(running LOS 20 though)
Hi
Sorry I cannot find the split screen option under settings > system > buttons (home button)...
Was the feature removed (very useful when you need to enter OTP code in some app: app on top split screen and OTP on bottom split screen)
Indeed I searched for split under the settings but nothing came up; probably obvious somewhere but as "search thread" doesn't work anymore on the forum...
Thanks a lot for your help
Sorry I cannot find the split screen option under settings > system > buttons (home button)...
Was the feature removed (very useful when you need to enter OTP code in some app: app on top split screen and OTP on bottom split screen)
Indeed I searched for split under the settings but nothing came up; probably obvious somewhere but as "search thread" doesn't work anymore on the forum...
Thanks a lot for your help
Split screen in LineageOS is in the menu where you switch between apps.
Tap on the app icon and the option will appear as shown in the screenshot.
Attachments
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
- Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
- Builds: https://download.lineageos.org
- Firmware:
- GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
- Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos98205How about maybe not updating firmware without explicitly being required to?
In upcoming LineageOS 20 releases a matching firmware version will be shipped with the ROM anyway (tho note that I cannot downgrade!)
Will see on the weekend if updating blobs is enough to make things work with this firmware version again.... meanwhile taking the firmware packages down3I'm seeing the same thing.
I've upgraded the firmware to G975FXXUFHVG4, and that "took". Confirmed using "adb shell getprop ro.boot.bootloader".
The instructions for the S10+ LOS Install say that Download Mode for that phone will give you a confirmation when
the download process(either in Heimdall or Odin) has completed, but despite waiting 10 minutes I never see it. The
blue progress bar does complete, and it obviously works since my prior firmware was a UG<something> as opposed to
the VG4 that it's on now.
I'm fairly confident that the Odin process I'm using works, despite the lack of a clear finalization message from the phone.
So, I am assuming that my Odin AP flashing of the LineageOS recovery is working(?)
However, like rik_w, I press Volume Down+Power to reboot, and then once the screen goes black, I immediately hold down the
Power+Volume Up+Bixby combo, but it never boots into recovery mode.
Is it possible that there needs to be a wait? Perhaps hold down the P+VU+B combo at some later point?
Now that the phone has the bootloader unlocked, I'm getting prompted at the powerup with a warning about the "Bootloader is unlocked, and bad things will happen to you, etc, etc", plus a "Press Power Key to Continue" prompt. If you don't hit the power button, it times out after 6-10 seconds and continues booting.
Is is possible that that prompting for the go-ahead, the "Press Power Key to Continue" is undermining the restart mode parameter so that it can't switch into recovery mode?
I've tried about 10 times, and I just can't get it to boot into the LOS recovery.
Anyways... does anybody have any ideas/insights? I bought this G975F specifically so I could put LineageOS on it. I couldn't use the G975U I'd received from AT&T, so ... do I now have -two- G975x's that I can't run LOS on?
EDIT: Would it be possible to remove the "Press Power Key to Continue" and warnings from the VG4 firmware distribution, or is that
blackbox code distributed by the manufacturer(Samsung), and no possibility of alteration/correction is possible?
Something in the firmware is blocking any attempt at going into recovery(LOS recovery or the factory recovery) with the bootlocker unloaded.
EDIT2: "bootblock unlocked", not bootlocker unloaded.
I've been able to get around this!
I went back to using heimdall, since Odin wasn't helping the issue anyways.
Apparently when using the Power + Volume Down buttons to force an exit/reboot from Download Mode, it would (for me) ignore/disable the Volume Up+Bixby+Power button sequence to go into recovery.
When using the heimdall command to flash the recovery, do NOT use the --no-reboot option. Allow heimdall to have the phone reboot after having flashed the recovery image.
The heimdall flash of the LOS recovery takes 3-4 seconds, which gives you enough time to get your fingers onto the Volume Up+Bixby+Power buttons before the phone reboots.
When the screen goes black, immediately hold down the VU+B+P buttons for a few seconds, and release them once the green Android logo shows on the screen. 2-3 seconds, perhaps.
Doing this, I was able to reboot into the LOS recovery the very first time. (As opposed to the other procedure that I'd tried 10-15 times without success). My phone is now running LOS 19.1. Joy!
tl;dr Let heimdall trigger the reboot for you before hitting the Power+Volume Up+Bixby buttons.3Copying my post from lineage 20 thread:
For everyone who upgraded to HVJ1 firmware, for all models there's a HVI4 build that has binary version 'G' too, at least for some CSCs, you should be able to downgrade to that and have it working again.
I'd recommend to use samfw.com over sammobile tho since that one has faster free download.
FYI that problem cannot be resolved without first getting new kernel sources from samsung... and next time: Don't update your firmware manually anymore, I will take care of it on 20.3
Could you please read my previous post? Don't update manually ever again (Compatible fw is shipped with the ROM on 20). And for new firmwares to work we first have to wait for Samsung to provide latest kernel sources.
