Database Info

[RS988][ROM][UNOFFICIAL] LineageOS 14.1 [06/15]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your warranty is now void.
I am neither responsible for bricked devices, dead SD cards,
thermonuclear war, nor you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! You alone are choosing to make these modifications.
If you point the finger at me for messing up your device, I won't laugh at you, but I'll try to work with you to fix it.
Thank you Rashed97 for your RS988 device tree!​
This is an unofficial LineageOS 14.1 ROM for the LG G5 RS988 . This is my first ROM, so things may go awry, but I haven't seen much evidence for that yet.
Working:
Brightness
Cameras
Fingerprint reader
Flashlight
Microphone (calling w/ Google Voice/Hangouts seems to work--that's what I use)
LED
Wi-Fi
Wi-Fi Hotspot
Quick Charge (users are reporting faster-than-stock speeds. I have experienced this as well)
Video recording (thanks @T3MPEST)
Not Working:
NFC, which includes Google Pay, etc. (thanks @-lukin-)
Loud static noise when using BT devices in calls (thanks @goast)
GPS — issues locking location while using Google Maps, etc.
Buggy media codecs preventing proper music playback; use third-party music players instead (thanks @LucklessCebu)
Audio recording (both pre-installed and third-party app) Working as of 3/10
Battery charging animation missing; "loops" LG logo (thanks @mattintoronto) Working as of 3/10
In The Works:
FM Radio Radio is apparently not included in any of the U.S. variants
Magisk Working w/ flashable .zip
Substratum Theme Engine Development on LineageOMS is currently inactive
Downloads:
I make direct links whenever possible for those of you with download managers.
20180615: MD5: db6f5cae64311f74425de7dff4f13dda
Updates: 5 June security patch, upstream Lineage updates
Android File Host
20180415: MD5: 1315911cb5c4bb875c2d1ab1b9eaa8ac
Updates: Security patch updates, upstream Lineage updates
Android File Host
20180327: MD5: e492de44bb789121916b22353a436dcc
Updated Lineage sources. Fixes double-tap to wake, screen tearing, etc.
Android File Host
20180310: MD5: 10b5c19def693e83203d5d8e07358ba6
Updates: Switched to current Lineage sources, which should fix a lot of things. Clean install will be necessary.
Android File Host
20180204: MD5: da2b6a9cd9265177566470aab2bc3aa0
I have been developer-approved! I have removed the Google Drive links in favor of Android File Host.
Android File Host
XDA:DevDB Information
[RS988][ROM][UNOFFICIAL] LineageOS 14.1, ROM for the LG G5
Contributors
NextDroid, Rashed97
Source Code: https://github.com/imasaru/android_device_lge_rs988
ROM OS Version: 7.x Nougat
ROM Firmware Required: Bootloader Unlocked, Latest TWRP installed
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-02-04
Last Updated 2018-06-18

Reserved.

NextDroid said:
Reserved.
Click to expand...
Click to collapse
Do you own Bluetooth devices? Specifically Android Wear and headphones? Just wanted to see if the Android Wear connected and worked and to see what Bluetooth calls were like. I'll back up and flash

Darn it @goast! I was just about to make another "reserved" post! Haha, just kidding. It's fine
I'll test my headphones right now and report back.
EDIT: It seems to work. Playback and the microphone on my BT headphones work.

NextDroid said:
Darn it @goast! I was just about to make another "reserved" post! Haha.
I'll test my headphones right now and report back.
EDIT: It seems to work. Playback and the microphone on my BT headphones work.
Click to expand...
Click to collapse
I'm sorry bro so everything I tested works. Bluetooth during call didn't. I have to use for work. So I restored my stock backup. I know this is a long standing upstream issue. Caller complained of loud scratching sounds during call.
If you need anymore info or anything for testing pm me and I'll respond

goast said:
I'm sorry bro so everything I tested works. Bluetooth during call didn't. I have to use for work. So I restored my stock backup. I know this is a long standing upstream issue. Caller complained of loud scratching sounds during call.
If you need anymore info or anything for testing pm me and I'll respond
Click to expand...
Click to collapse
Alright! Thanks.

Wy Wi-Fi is not woking
After flashing this Rom, my wi-fi is not working any longer. It turns on, but it won't connect.
Any Ideas?
edit: I am in Europe so I guess that's the deal... I'll flash another one

SuperQvas said:
After flashing this Rom, my wi-fi is not working any longer. It turns on, but it won't connect.
Any Ideas?
edit: I am in Europe so I guess that's the deal... I'll flash another one
Click to expand...
Click to collapse
Hm. I assume they use different frequencies 2.4/5GHz band for their wireless networks along? I'm not too sure.
Here in the U.S., WiFi works for me on the 5GHz band.
goast said:
I'm sorry bro so everything I tested works. Bluetooth during call didn't. I have to use for work. So I restored my stock backup. I know this is a long standing upstream issue. Caller complained of loud scratching sounds during call.
Click to expand...
Click to collapse
Adding to main post.

NextDroid said:
Hm. I assume they use different frequencies 2.4/5GHz band for their wireless networks along? I'm not too sure.
Here in the U.S., WiFi works for me on the 5GHz band.
Adding to main post.
Click to expand...
Click to collapse
I say I know I didn't look but all the other cm or aosp rooms had it too
Probably could be fixed but I know nothing about how to do it.
Edit: pmed u

Finally some light for RS988
NextDroid said:
Darn it @goast! I was just about to make another "reserved" post! Haha, just kidding. It's fine
I'll test my headphones right now and report back.
EDIT: It seems to work. Playback and the microphone on my BT headphones work.
Click to expand...
Click to collapse
Finally, someone is taking efforts to port ROM to this device.
Thanks @NextDroid
Will try out this rom coming weekend.
More keen on the battery performance.

rahuldg said:
Finally, someone is taking efforts to port ROM to this device.
Thanks @NextDroid
Will try out this rom coming weekend.
More keen on the battery performance.
Click to expand...
Click to collapse
Thank you!
Speaking of battery performance, I made this observation about an hour ago and was just about to post on it.
So I tried @waau 's Typhon kernel (M5 RC1) for RS988 earlier today to see whether it would work with this build of LOS. I found that Bluetooth would not work properly (as I wrote in the main post).
Thus I decided to return back to the 3.18 kernel that was built with LOS. I didn't have a .zip or an .img handy, so I reflashed the ROM to get the kernel and my Bluetooth back.
My phone was on low battery a while ago at 13%, and so I connected the charger and did something else for five minutes or so. When I got back, it was at 22%! I opened up Ampere to find something interesting... (attached photo)
Is this a feature of the stock kernel or did my reflashing "overlay" Typhon and keep Quick Charge from it? It would be nice to retest pure stock and see what happens (@goast?)
Either way, this is definitely a win-win.

Also, there weren't any camera issues on the stock kernel (before I flashed Typhon). Zoom worked and everything.

NextDroid said:
Thank you!
Speaking of battery performance, I made this observation about an hour ago and was just about to post on it.
So I tried @waau 's Typhon kernel (M5 RC1) for RS988 earlier today to see whether it would work with this build of LOS. I found that Bluetooth would not work properly (as I wrote in the main post).
Thus I decided to return back to the 3.18 kernel that was built with LOS. I didn't have a .zip or an .img handy, so I reflashed the ROM to get the kernel and my Bluetooth back.
My phone was on low battery a while ago at 13%, and so I connected the charger and did something else for five minutes or so. When I got back, it was at 22%! I opened up Ampere to find something interesting... (attached photo)
Is this a feature of the stock kernel or did my reflashing "overlay" Typhon and keep Quick Charge from it? It would be nice to retest pure stock and see what happens (@goast?)
Either way, this is definitely a win-win.
Click to expand...
Click to collapse
Those two things were broken on other devices before Typhon was made. I'd be willing to guess it some artifacts left over from Typhon. Maybe someone else can elaborate

I had no camera focus issue with stock kernel on this rom. I'm not sure about the quick charge though. I have 5 batteries so I rarely plug it in.

first custom rom i've tried on my RS988 that has worked so far. i am very impressed at the results. it just feels a lot quicker than stock nougat. sure as hell helps to not have 345830 pre-installed bloatware garbage apps.
also, my charging speed is a lot faster than stock nougat as well! normally accubattery shows my charge speed capping out at 2,480mA and right now on LineageOS i am capping out at 3,010 mA ! at that speed I could go from a dead battery to 100 percent in one hour. incredibly impressive. i don't use NFC at all and barely use bluetooth so i haven't bothered to test those things yet. so far everything else works for me. FANTASTIC WORK!

jungle35 said:
first custom rom i've tried on my RS988 that has worked so far. i am very impressed at the results. it just feels a lot quicker than stock nougat. sure as hell helps to not have 345830 pre-installed bloatware garbage apps.
also, my charging speed is a lot faster than stock nougat as well! normally accubattery shows my charge speed capping out at 2,480mA and right now on LineageOS i am capping out at 3,010 mA ! at that speed I could go from a dead battery to 100 percent in one hour. incredibly impressive. i don't use NFC at all and barely use bluetooth so i haven't bothered to test those things yet. so far everything else works for me. FANTASTIC WORK!
Click to expand...
Click to collapse
Well this is great news! Thank you for trying this out I'm glad it's working out!
@goast Maybe this is an indication that this is the Lineage kernel and not Typhon. Now that I think about it, the kernel is compiled at buildtime into a single file, which is stored in the boot partition. I doubt that it is a system of directories that could have some files overwritten.
Also, I think I see the BT calling problem you were talking about. I attempted to make a recording with both the preinstalled Recorder and a third-party app and I got static. When I made a call over Wi-Fi using Hangouts, though, I had no issues.
Also, final thing: have any of you tried to flash a Magisk .zip or SuperSU? I have tried countless times but have not had any success :/

NextDroid said:
Well this is great news! Thank you for trying this out I'm glad it's working out!
@goast Maybe this is an indication that this is the Lineage kernel and not Typhon. Now that I think about it, the kernel is compiled at buildtime into a single file, which is stored in the boot partition. I doubt that it is a system of directories that could have some files overwritten.
Also, I think I see the BT calling problem you were talking about. I attempted to make a recording with both the preinstalled Recorder and a third-party app and I got static. When I made a call over Wi-Fi using Hangouts, though, I had no issues.
Also, final thing: have any of you tried to flash a Magisk .zip or SuperSU? I have tried countless times but have not had any success :/
Click to expand...
Click to collapse
I think it is LineageOS itself in regards to the quick charge. I went from stock Nougat -> flashed the stock Nougat 21c build for RS988's via TWRP -> flashed LineageOS and from the first time booting up into LineageOS the quick charge was working already. It won't tell you it's quick charging in the notifications the same way stock Android does, but if you monitor it with Accubattery or a similar app you will see the charge rate is definitely quick charge.
In regards to Magisk, that is how I am rooted right now. Using the patched bootloader method caused me to boot loop so I just flashed Magisk 15.3 via TWRP then installed Magisk Manager and it worked perfectly. No problems with root at all and all the apps I've tried so far that required root access have worked. I am really really liking this setup a lot. Overall this is much faster for me than stock Android was due to how many bloatware apps LG included by default.
Will continue to test it out during my day to day use and see if I come across any problems. Once again, great work @NextDroid !!

NextDroid said:
Well this is great news! Thank you for trying this out I'm glad it's working out!
@goast Maybe this is an indication that this is the Lineage kernel and not Typhon. Now that I think about it, the kernel is compiled at buildtime into a single file, which is stored in the boot partition. I doubt that it is a system of directories that could have some files overwritten.
Also, I think I see the BT calling problem you were talking about. I attempted to make a recording with both the preinstalled Recorder and a third-party app and I got static. When I made a call over Wi-Fi using Hangouts, though, I had no issues.
Also, final thing: have any of you tried to flash a Magisk .zip or SuperSU? I have tried countless times but have not had any success :/
Click to expand...
Click to collapse
Cool. If you can get me a log of the issue I can pass it along if you can't figure out a solution
If you think you have one and run a test build let me know too lol

First off all, thanks for your work, this is a big step in having more roms developed since a couple of them follow the lineage branch.
I'm not a dev so probably this is just a stupid idea, but seeing that the main problems for the bugs appears to be the base kernel, maybe something can be ported from the LG V20 kernel in order to fix those problems since both phones share mainly the same specifications and the V20 has official lineage branch.
Also maybe check the wifi/bluetooh drivers in custom V20 kernels for lineage.
My previous phone was a motorola verizon droid turbo, and a lot of its development was thanks to the nexus 6, and moto x repository.
Just a thought.

SuperQvas said:
After flashing this Rom, my wi-fi is not working any longer. It turns on, but it won't connect.
Any Ideas?
edit: I am in Europe so I guess that's the deal... I'll flash another one
Click to expand...
Click to collapse
I know i had trouble connecting to my 5GHz wifi at home until I set my router to only use one channel. Currently its using channel 36, and its been working just fine ever since i changed that.

[ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy Note 3 (hlte*)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Device source code:
msm8974-common (shared by all Samsung msm8974 devices): LineageOS/android_device_samsung_msm8974-common
hlte-common (shared by all hlte* devices): LineageOS/android_device_samsung_hlte-common
hlte: LineageOS/android_device_samsung_hlte
hltechn: LineageOS/android_device_samsung_hltechn
hltekor: LineageOS/android_device_samsung_hltekor
hltetmo: LineageOS/android_device_samsung_hltetmo
Kernel source code:
LineageOS/android_kernel_samsung_msm8974
Build Compatibility:
The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
BuildModelhlteSM-N9005, SM-N900PhltechnSM-N9008VhltekorSM-N900K, SM-N900L, SM-N900ShltetmoSM-N900R4, SM-N900T, SM-N900V, SM-N900W8
Downloads:
https://download.lineageos.org/
Installation Instructions:
https://wiki.lineageos.org/devices/
Reporting Bugs:
https://gitlab.com/LineageOS/issues/android
Compatibility Notes:
External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
The latest TWRP does work, but if someone has issues then perhaps try using the actual supported recovery.
If you are encrypted, even with insecure boot, you absolutely must format userdata on upgrade, as noted in upgrade instructions in wiki.
If you are not encrypted then disable lockscreen before upgrading and it *should* work without wiping userdata.
If you didn't disable lockscreen before upgrading then delete the lockscreen files and it *should* work. Use the power of search, I'm not going to help out with this one -- it's an unsupported path.
If you get terribly stuck then wipe userdata as our official upgrade guide notes.
Donations:
I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.

[Reserved]

I have install this new 18.1 + MindTheGapps + magisk (before that i used 17.1) and after 2 days using i want to say that os works normal and suitable for everyday use. Camera, bt, calls, battery life - all is that works like 17.1. All call logs, sms, 120 apps was success restored by google backup. But some bugs detected:
some apps cant get login via google account. When i select my account nothing is happen.
other man after install 18.1 got internal storage wrong free space - only 2gb free and total space is ~22 but correct is 32. Once i got similar problem: it was 20gb free, but new app from play market cant be installed because no free space. After reboot that was fixed. I have dump if someone needs.
in system settings when i choice sound for notifications there is no sound on selection.
sometimes ui got freezes but very rarely, probably 2 times a day
no other problems detected.

kisilmike said:
some apps cant get login via google account. When i select my account nothing is happen.
Click to expand...
Click to collapse
this is a gapps-related issue, use a different gapps package
works fine here on microg or opengapps beta
kisilmike said:
in system settings when i choice sound for notifications there is no sound on selection.
Click to expand...
Click to collapse
lineage has it's own sounds(soundpicker) app for you to select its default ringtones. if your gapps package has google sounds bundled in, that may be the cause as it always has issues on 32bit systems and will replace lineage's own soundpicker
kisilmike said:
sometimes ui got freezes but very rarely, probably 2 times a day
Click to expand...
Click to collapse
did you clean flash? are you previously from official 17.1 build?

r0mushii said:
this is a gapps-related issue, use a different gapps package
works fine here on microg or opengapps beta
lineage has it's own sounds(soundpicker) app for you to select its default ringtones. if your gapps package has google sounds bundled in, that may be the cause as it always has issues on 32bit systems and will replace lineage's own soundpicker
did you clean flash? are you previously from official 17.1 build?
Click to expand...
Click to collapse
thank you for answer.
"in system settings when i choice sound for notifications there is no sound on selection. "
- now its work correct. May be reboot fixed it.
r0mushii said:
did you clean flash? are you previously from official 17.1 build?
Click to expand...
Click to collapse
yes, it was official 17.1 with latest updates but new 18.1 i have install on blank phone with all wipes available: internal memory, caches, ... . I Said wrong, it wasn't a freeze: just when i go to settings to modify somethings some times ui stopped for response and just kill window and getting new solve that. but it doesn't matter, because it happened only 3-4 times, maybe there was a synchronization or some.
But the problem with the internal memory size is quite real for my friend, he could not fix it and getting back for 17.1 for a while.

on clean flash, had a strange issue...got my music folder on ext sd replaced by a file with 0 byte, same if I look on computer, but can still read music....but after 2 days, the folder with music come back....don't know why but everything is ok now.

Running well so far.
Only issue or a feature request would be miracast support.

faheem200 said:
Running well so far.
Only issue or a feature request would be miracast support.
Click to expand...
Click to collapse
I can't say this for sure cause I don't know for sure but I think miracast support is left out because it's proprietary.

faheem200 said:
Running well so far.
Only issue or a feature request would be miracast support.
Click to expand...
Click to collapse
Lahpyrcopa said:
I can't say this for sure cause I don't know for sure but I think miracast support is left out because it's proprietary.
Click to expand...
Click to collapse
it's because miracast has been nuked by google since android 8.x (blame chromecast). most roms still have it but it's not a bulletproof fix and more of a hack and less likely that lineage will add these in the future(people complained about this since los15)

Amazing work yet again by all mighty haggertk
Will most definitely install and test new official build pretty soon. Btw one question I have for all, did anyone ever noticed sudden drop in speed via WiFi? Ever since I got new router and default WIFI is 5g and not 2.4 my note 3 (n9005) constantly lose how should I say speed.
Example im watching YouTube in 1080 or 720 and after maybe 1 to 2 hours and it stops buffering and just spinning circle is shown then I need to lower it to 360p to resume. Then I go to download file or browser and it's soon slow. Sometimes reboot fix it sometime don't. I've flashed few latest modems for our device but still the same.
Edit: when I'm on 2,4ghz wifi all is good and even going back to 5ghz after been connected to 2.4 works fine but looses is strength later on.

With my SIM card in my phone I notice that texts don't seem to be received unless the screen is on and if the screen is off they are delayed. I don't know if this is a bug or just my phone.

Lahpyrcopa said:
With my SIM card in my phone I notice that texts don't seem to be received unless the screen is on and if the screen is off they are delayed. I don't know if this is a bug or just my phone.
Click to expand...
Click to collapse
do you mean SMS? I have no problem with that.

Scorpionea said:
Amazing work yet again by all mighty haggertk
Will most definitely install and test new official build pretty soon. Btw one question I have for all, did anyone ever noticed sudden drop in speed via WiFi? Ever since I got new router and default WIFI is 5g and not 2.4 my note 3 (n9005) constantly lose how should I say speed.
Example im watching YouTube in 1080 or 720 and after maybe 1 to 2 hours and it stops buffering and just spinning circle is shown then I need to lower it to 360p to resume. Then I go to download file or browser and it's soon slow. Sometimes reboot fix it sometime don't. I've flashed few latest modems for our device but still the same.
Edit: when I'm on 2,4ghz wifi all is good and even going back to 5ghz after been connected to 2.4 works fine but looses is strength later on.
Click to expand...
Click to collapse
My wifi 5ghz always on and sometimes i transmit big data form/to PC, for example 5GB photo or more and speed is always 7-20 megabyte/s, no any disconnects or low speed detected. It is on 17.1 and 18.1 too.
I suspect that the problem is in the router, some routers are overheating or their memory is full. Try restarting your router when you got low speed

kisilmike said:
do you mean SMS? I have no problem with that.
Click to expand...
Click to collapse
I do and it's a hit or miss on my device.

kisilmike said:
My wifi 5ghz always on and sometimes i transmit big data form/to PC, for example 5GB photo or more and speed is always 7-20 megabyte/s, no any disconnects or low speed detected. It is on 17.1 and 18.1 too.
I suspect that the problem is in the router, some routers are overheating or their memory is full. Try restarting your router when you got low speed
Click to expand...
Click to collapse
You could also disable unnecessary settings in the router that just slow it down.

I have a problem with screen orientation. Previously, at 17 everything worked well, but last 3 updates came and next time sometimes the screen began to display the wrong orientation. Then I setup 18 in the hope of solve the problem and first 4 days everything worked well. But today it suddenly stopped working. Rebooting didn't help. I have attached 2 screenshots from other app. Acceleromer always show action but phone is not moving. Magnetic is changes depending on device position correctly.

kisilmike said:
My wifi 5ghz always on and sometimes i transmit big data form/to PC, for example 5GB photo or more and speed is always 7-20 megabyte/s, no any disconnects or low speed detected. It is on 17.1 and 18.1 too.
I suspect that the problem is in the router, some routers are overheating or their memory is full. Try restarting your router when you got low speed
Click to expand...
Click to collapse
Thx for replay
My router is fine,all other phones works just fine on 5ghz. Since im the only one who have ever reported something like this on 17.1 or 18.1 thread it must be router that has difficult time with my note 3. I could disable 5ghz and stick with 2.4ghz as for a phone its no big problem.
btw can u tell my your bootloader and modem version? cheera

Scorpionea said:
Thx for replay
My router is fine,all other phones works just fine on 5ghz. Since im the only one who have ever reported something like this on 17.1 or 18.1 thread it must be router that has difficult time with my note 3. I could disable 5ghz and stick with 2.4ghz as for a phone its no big problem.
btw can u tell my your bootloader and modem version? cheera
Click to expand...
Click to collapse
there is routers with dual band transmitter simultaneously: 2.4 and 5 it is very comfortably.
bootloader N9005XXUGBOK6
radio N9005XXUGPQB1
latest TWRP

Does QC working on hlte?

picco911 said:
Does QC working on hlte?
Click to expand...
Click to collapse
in short: yes
in long: all aosp-based roms can charge up to 1800mA max (compared to 1200mA on stock iirc). you can check the input current using battery monitoring apps like amplify or batteryguru
if it doesn't go 1800 max, check your wall adapter(charger) if it's capable of at least 5V-2A output and/or your cable/charging port if it's damaged or not(or in the case of the cable, if it can deliver that amount of current or not)
p.s. i've also read your reply on the abandoned havoc thread so i decided to explain it here instead

[ROM][UNOFFICIAL][11.0][ I9305 ][ LineageOS 18.1 ][BETA][TREBLELIZED]

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version of LineageOS 18.1 for our Samsung Galaxy S3 (I9305).
At first I want to thank @rINanDO, @ChronoMonochrome for all your work.
This Rom is based on I9300 LOS 18.1 .
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
GSI flash
NFC
BT headset call
Tethering
much more...
Spoiler: Whats not working
Screen Cast, Chromecast did work, Samsung TV not
Random reboots
SD-Card can't be formatted as a storage expansion, your device will crash
Maybe more
Spoiler: Links
TWRP
I9305 ROM
Magisk zip file
Spoiler: Changelog
26.10.2021
09.11.2021
10.12.2021
06.01.2022
19.01.2022
22.02.2022
20.04.2022
If you are going to use Gapps,
here you can download them:
Open Gapps
For the others, you can use microG.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][11.x][I9305][BETA] LineageOS 18.1, ROM for the Samsung Galaxy S3 LTE
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 11.x R
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2021-10-08
Last Updated 2022-04-20

If you're interested in flashing your first GSI, follow this thread (also alpha):
[GSI][11][ EXYNOS4 SMDK4412 ][N8000, N801X, N8020, I9300, N5100, N51XX, N7100, ...][ALPHA] [EOL]
Here you will find my exynos4 compatible GSI's. This work is based on the magic of @phhusson, so thank you very much for this. Don't forget, that you need an treblelized ROM to support this. Do you like my work? Than you can simply hit...
forum.xda-developers.com

First test build is online, have fun .

html6405 said:
First test build is online, have fun .
Click to expand...
Click to collapse
Thank you!
Clean-installed lineage-18.1-20211008-HTML6405-i9305 and it's looking really good.
I've installed LOS and the same apps as when trying out the 19300 build. No Gapps or Magisk.
All of the things I observed as not working with the i9300 build on this device are now working:
Hardware buttons are now working
Home button now wakes device
Wifi connects automatically to dual-band network and seems stable
GPS is working. I haven't tested thoroughly, but it does see satellites, which it couldn't before
Camera works and photos are right-side up
Screen rotation is working correctly (once I turned on 270 degrees in rotation settings - other angles were already on).
Audio volume is still low on internal speakers, but fine on Bluetooth.
I haven't yet tested telephony (which didn't work on the i9300 build). Going to leave the device on for a while to see if it's stable.

lpedia said:
Thank you!
Clean-installed lineage-18.1-20211008-HTML6405-i9305 and it's looking really good.
I've installed LOS and the same apps as when trying out the 19300 build. No Gapps or Magisk.
All of the things I observed as not working with the i9300 build on this device are now working:
Hardware buttons are now working
Home button now wakes device
Wifi connects automatically to dual-band network and seems stable
GPS is working. I haven't tested thoroughly, but it does see satellites, which it couldn't before
Camera works and photos are right-side up
Screen rotation is working correctly (once I turned on 270 degrees in rotation settings - other angles were already on).
Audio volume is still low on internal speakers, but fine on Bluetooth.
I haven't yet tested telephony (which didn't work on the i9300 build). Going to leave the device on for a while to see if it's stable.
Click to expand...
Click to collapse
Update: saw a random reboot after ~4 hours during which the device was continuously playing music via a Bluetooth speaker.

lpedia said:
Update: saw a random reboot after ~4 hours during which the device was continuously playing music via a Bluetooth speaker.
Click to expand...
Click to collapse
Thanks for testing, but you can't compare these two builds because of different hardware .
If you're facing a random reboot, it would be great to create a last_kmsg file and send it to me,
otherwise I can't debug anything.
lpedia said:
Audio volume is still low on internal speakers, but fine on Bluetooth.
Click to expand...
Click to collapse
You could change the Speaker Boost Volume level from 6 to 7 in the /vendor/etc/sound/i9305 file,
this will increase the audio volume.
I will include this in the next build.

html6405 said:
Thanks for testing, but you can't compare these two builds because of different hardware .
Click to expand...
Click to collapse
Yes, I wasn't intending to suggest that they are directly comparable - just confirming that everything that's supposed to be working is working.
Telephony is working, I can now confirm. The SIM was visible but not active on reboot after inserting the SIM, and after a second reboot it became active.
html6405 said:
If you're facing a random reboot, it would be great to create a last_kmsg file and send it to me,
otherwise I can't debug anything.
Click to expand...
Click to collapse
Good - I was going to ask just what logs you'd like me to collect re the reboots. I'll grab last_kmsg next time it random reboots.
There've been two random reboots since install, both while it'd been playing music over bluetooth continuously. The first was after ~4 hours and the second ~2 hours. I will just leave the device idle now and see if it happens when it's in deep sleep. There are no tombstone files, by the way.
html6405 said:
You could change the Speaker Boost Volume level from 6 to 7 in the /vendor/etc/sound/i9305 file,
this will increase the audio volume.
I will include this in the next build.
Click to expand...
Click to collapse
Thanks! That does help (after a reboot). Still not loud, but it is more audible.

@html6405 - I have a logcat and last_kmsg from a strange half-hung event this morning. Should I upload here, or would you prefer a PM?
The device had stayed up without a random reboot overnight (and ~75% deep sleep). I connected the Bluetooth speaker and started the VLC media player. For a while, all seemed well. Then I pressed Home to send the player to the background, and instead, bootanimation started. Very briefly - didn't complete half a loop - then the screen went blank, hardware buttons were lit, and no response to buttons or quick press of power button.
adb could still connect to it, so I grabbed the logcat and last_kmsg before trying anything else. htop worked, but none of the running processes seemed to be using an unusual amount of memory or processor, so I didn't try killing any.
I had to force-restart (Power and Volume Down) to get it to respond.
Now it tells me there are new updates. Is that expected?

@html6405 - the 9 October OTA update dowloaded and installed via TWRP, and the system booted OK. I connected the bluetooth speaker and started playing music via VLC media player. The system rebooted almost immediately. The attached zipfile contains last_kmsg (called last_kmsg-2) taken after that reboot, plus the last_kmsg and logcat from the 8 October build, mentioned in my previous post.

lpedia said:
Now it tells me there are new updates. Is that expected?
Click to expand...
Click to collapse
Sure, I've set the audio volume to the maximum.
lpedia said:
The system rebooted almost immediately
Click to expand...
Click to collapse
Ok, this was a modem crash, thanks for your log, I will take a deeper look into it.
I'm not sure why the crash happened.

html6405 said:
Sure, I've set the audio volume to the maximum.
Ok, this was a modem crash, thanks for your log, I will take a deeper look into it.
I'm not sure why the crash happened.
Click to expand...
Click to collapse
@html6405 - the device got another OTA update today. Thank you - and I like the fact that they install automatically via TWRP!
It has had quite a few random reboots now, and ALL have been while it's playing music files continuously. It does this with LOS's music player and with the VLC app, and it doesn't matter whether the audio files are local or on a network fileserver, or whether the output is bluetooth speaker, wired headset, device speakers, or muted. After a variable length of time playing - usually 15-30 minutes - the device will suddenly reboot.
But it doesn't seem to do it when playing video continuously. I haven't tested this thoroughly, but yesterday VLC played video files from a network fileserver for over four hours without any reboot. I'll try it again today to see if that's consistent.
Do you need any more last_kmsg files - or only if it reboots under different conditions?

lpedia said:
Do you need any more last_kmsg files - or only if it reboots under different conditions?
Click to expand...
Click to collapse
Sure, just send them to me via PM and then I will analyze them, maybe they will help me to find the root cause.

for the GSI there is no i9305 images
Where to find em,or they are avaiable at treble info?

Noobmaster20 said:
for the GSI there is no i9305 images
Where to find em,or they are avaiable at treble info?
Click to expand...
Click to collapse
The GSI from the linked thread and all coming GSI's should fit for all exynos4 devices.
But I had no time to test it on the I9305, there will come updated versions soon.

Update 26.10.2021:
Fixed modem crash issue in Kernel, the connection still get's lost sometimes and you still have to reset the APN settings after every boot, I'm working on this...

I'm testing this ROM right now, unfortunately I lost my SIM card day ago so can't say anything about mobile data etc. In 2 hours of listening music on youtube, using social media apps and browsing web there wasn't any reboot. I didnt encounter any major bugs, one thing that is happening to me is when i try to send photo (directly from camera, not gallery) in messenger app, when i click to send photo it is jest restarting messenger application, I will test how it is with other apps and edit this post. In overall this ROM is working really nice. Thank you for working on this ROM. Maybe it is now not the smoothest or fastest working ROM but it is usable and gave me "fresh feeling" of this old phone
EDIT: sending photos from camera works on instagram

Is it possible to get the GPS time fixed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ducks1 said:
Is it possible to get the GPS time fixed? View attachment 5443741
Click to expand...
Click to collapse
Where are you facing this issue?
I will check this!

html6405 said:
Where are you facing this issue?
I will check this!
Click to expand...
Click to collapse
The screenshot is from an app called GPSTest https://github.com/barbeau/gpstest

ducks1 said:
The screenshot is from an app called GPSTest https://github.com/barbeau/gpstest
Click to expand...
Click to collapse
Hmm ok,
I've downloaded the GPSTest app from the playstore and I didn't get this message,
do I have to do anything to see this?
For sure I've tried GPS outside.

[ROM][11.0] crDroidAndroid v7.x for s5neolte [UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:​
Pre-installation:​
Gapps (Download from here)
Magisk for root - (Download from here)
First time installation:​
Download Rom, Gapps & Magisk (If you want ROOT)
Reboot to recovery
Format data
Flash Rom, optional Gapps & Magisk
reboot and enjoy
Sources: https://gitlab.com/samsung_s5neolte
Known issues:
you tell me
Credits goes to:
LineageOS
Community

Download
july 2022

dummy2

Wow thanks

after flash im missing keyboard and messaging apps, flashed with and without gapps, same result, even after manual install of any keyboard app, system does not recognize them.

sanczooo said:
after flash im missing keyboard and messaging apps, flashed with and without gapps, same result, even after manual install of any keyboard app, system does not recognize them.
Click to expand...
Click to collapse
strange, here is all working, screenshot is seconds ago taken

Hello, great rom, congratulations on work, I have a problem with bluetooth, after pairing the device, after 1-2 seconds it disconnects the device.

jreneusz said:
Hello, great rom, congratulations on work, I have a problem with bluetooth, after pairing the device, after 1-2 seconds it disconnects the device.
Click to expand...
Click to collapse
confirmed, will take a look.
no bug, more a special thing with android 11, when you connect two phones enable "Settings > Network and Internet > Hotspot and tethering > Bluetooth tethering" on both phones.
my jabra speak 510 works instantly without anything special. see pictures.
dont know what you are do with bluetooth, but if you have wifi in your location its way faster to share files with kdeconnect(is in playstore/fdroid), directly from device to device or pc ;-)

I have no idea on where to start. You were the first who actually did an >android9 rom (all android 10 and 11 ones i've tried failed) to SM-G903M. But it doesn't stops right there.
-Performance is amazing. It feels even faster than CrDroid in galaxy S7 (my older, now screen-damaged, phone).
-Battery control levels (battery economy/balanced/performance) in battery settings keep true to what they promise. Battery economy keeps only 4 of the 8 cortex-a53 small cores on, to a 1ghz maximum, balanced delivers excellent performance and battery life, performance is excellent for compression and other tasks but with a higher power draw
-Memory management is excellent, something vital in a 2gb ram phone.
-Noop as default I/O
-ROM is so slim, even after gapps, trashing with all possible apps, custom whatsapp, and all kinds of addons, i still have 2GB of my 16GB space left, something IMPOSSIBLE on stock ROMs.
-Face unlock is smooth, fast, precise.
-No bugs as of now
I'm really asking myself if you don't actually use this phone daily, because the level of attention to details (geekbench even shows the phone in this ROM performance rivaling the j7 and exynos 7870 which is a faster chip) is amazing. Even the onscreen button toggle works (not using them btw), something which failed miserably for me in crdroid and dotOS from galaxy s7. I can't stress out how grateful i am, i thought i would never leave android 6 because my model (sm-g903m) was not compatible with other ROMs. I will update to android 12 if you make it happen for us again, sm-g903m, sm-g903f, sm-g903w, all included, as some developers (you an exception) seem to forget there are users worldwide who do not own american models
Thank you so much. If you need any actual help with anything, spreading the news about your ROM with a youtube video review in my native language and in clear english, i can do it. Just PM me.

Everything working great

Does this ROM have FM-radio?

evil-god said:
confirmed, will take a look.
no bug, more a special thing with android 11, when you connect two phones enable "Settings > Network and Internet > Hotspot and tethering > Bluetooth tethering" on both phones.
my jabra speak 510 works instantly without anything special. see pictures.
dont know what you are do with bluetooth, but if you have wifi in your location its way faster to share files with kdeconnect(is in playstore/fdroid), directly from device to device or pc ;-)
View attachment 5450975View attachment 5450977
Click to expand...
Click to collapse
Thanks for the answer, will try kdeconnect.

bluetooth works.

How's the mic working on this ROM, is it also very low in calls?
I might test after I play around with the LOS a bit more, see if I can get it to work there.

wvanstraalen said:
How's the mic working on this ROM, is it also very low in calls?
I might test after I play around with the LOS a bit more, see if I can get it to work there.
Click to expand...
Click to collapse
I just tested this ROM yesterday and unfortunately mic works in the same manner as in LOS 17.1 and LOS 18.1
I just don't get - how it is that some people here report that everything works perfectly and some can't have regular phone calls. MICGAIN patches do not work. S5 Neo lifevibes by danwood76 work only in v2 (still not close to stock quality). Speakerphone completely dead.
My device is SM-G903F (European distribution), maybe there is some difference in microphone hardware values between different devices distributions? It seems as if those custom ROMs mic programming has way too low values for mic input compared to mic hardware.
Hey devs, is there any chance to fix this problem? I volunteer to test any solutions and report them back here for future reference.
Thanks

Mike-san said:
I just tested this ROM yesterday and unfortunately mic works in the same manner as in LOS 17.1 and LOS 18.1
I just don't get - how it is that some people here report that everything works perfectly and some can't have regular phone calls. MICGAIN patches do not work. S5 Neo lifevibes by danwood76 work only in v2 (still not close to stock quality). Speakerphone completely dead.
My device is SM-G903F (European distribution), maybe there is some difference in microphone hardware values between different devices distributions? It seems as if those custom ROMs mic programming has way too low values for mic input compared to mic hardware.
Hey devs, is there any chance to fix this problem? I volunteer to test any solutions and report them back here for future reference.
Thanks
Click to expand...
Click to collapse
thx for reporting, i will take a look
edit: my device is a SM-G903F too, today my GF and me switch the phone, make several calls, then switch back, do some test calls, everything work for both sides normal, cant reproduce any issue.
anyone else with this problem?

evil-god said:
thx for reporting, i will take a look
edit: my device is a SM-G903F too, today my GF and me switch the phone, make several calls, then switch back, do some test calls, everything work for both sides normal, cant reproduce any issue.
anyone else with this problem?
Click to expand...
Click to collapse
Hi,
Didn't know you replied by editing. Been too busy during whole week to take a closer look on this thread.
Thanks a lot for trying to figure out what's going on. This is really strange that you did not experience any issues during phone calls - what distribution your phone is? I've read that there may be some differences between different distributions around the world in hardware configuration. I discarded version of mic malfunction - before swithing to LOS 17.1 and 18.1 and CrDroid there were not problems with phone calls, audio recording and camera recording with stock ROM.
I am not exaggerating about this issue - wvanstraalen also reported this problem and there had been numerous reports in this thread https://forum.xda-developers.com/t/...c-gain-and-a-little-speaker-gain-too.3491483/ but they do not apply to Android 11.
Is there any way to compile a file/files which would contain insight info about how mic behaves in different circumstances and how mic values in mixer paths are fixed? I don't know if I am precise at the moment - I just write what my guts tell me what may be wrong with my and some people's devices. There must be some way to fix this. Or maybe there are people who have some practical knowledge about this issue. I do not expect miracles, but if you could point what could possibly done I'd be very grateful. If not - maybe there are some devs here who have dealt with this issue with different Samsung devices?
Kind regards,
Mike

evil-god said:
Download
december 2021
Click to expand...
Click to collapse
Thanks.

Some very significant performance improvements seem to have been achieved from the first version to the january 2022 update. Cores now seem to be able to turn off in heavy multitasking, such as with YouTube music, browser alongside facebook app as the first open app. This was impossible in the old ROM version. It may help with temperatures and prolong new third party batteries lifespan (not speaking about the more expensive ones but the ones below 10usd sold for the original galaxy s5 but compatible with the s5 neo, for those who ask themselves which ones i'm talking about. I highly distrust new batteries claiming higher capacity than the original as well)

After flash im missing data network, I have a G903M, anyone else with this problem?

[HTC U11] No Audio (both ways) during calls?!

I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.

I have that same problem.
I tried 5 different custom roms, I tried the kernel, it didn't work.
everything is working, only the sound on the phone call is neither going nor coming. same as normal earphone with bluetooth earphone.
audio recording in video recording, music working, microphone recording sound, but no sound in calls. There is an imei signal, but there is no solution.
Even emergency calls have the same problem.
why could it be?

Thank You for replying, OnlineBeyin!
And here I thought, I was completely alone in this. At least there's someone out there sharing the pain!
Well, here's to a strage new Problem.
In a funny way, I love this about digital technology; it never gets boring - as soon as you'd think you've got your stuff figured out, along comes a curious problem you've never heard of or even expected to be possible.
I havent found a solution yet but having someone with the same problem gives me hope, maybe together we can work it out.
I don't think it's about the custom ROMs since You tried five of them to no avail. What do You mean by "trying a kernel"?
I've come to terms with it since I kind of enjoy the silence that not being able to answer calls has provided, but there is some other strange behaviour that might hint at a possible solution I have not yet explored:
I've taken a look at the NikGApps package I was using (core) and I've realised that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I might need the basic version, since the core version does not provide an obvious dialer (What does "AOSP" stand for?) nor "Google Carrier Services", both of which seem quite important for phone calls.
Now me being a rather lazy fellow by nature, I thought I could just install the basic version over the the core version. In doing that, the clock app stopped working. I don't know why but opening it leads to the app crashing.
I've just seen Your post so I wanted to reply first rather then try a bunch of stuff and keep you waiting for an answer, but that's where I'm at.
So this strange behaviour (not being able to open the clock app) leads me to belive that...
<TL;DR>
Could there be an issue with different versions of programs running in the background?
(My point being Android is basically a customized version UNIX which has some similarities with Linux with which I have some modest experience with.
There I've experienced such issues around the OS telling me (paraphrasing) "the thing You want won't work like that because it is dependent on something that cannot be resolved automatically. You gotta have this version of that other thing to talk to that version of yet another thing and you have to solve that first. Then it'll work.")
So, long story short,
just to rule out this source of error, the next thing I'm going to try is to make a clean install with the full and original Version of GApps just to see if it'll work and go from there. If that won't help, I'll find out if there is something like the bash terminal from Linux just so I can see what the phone is doing exactly.
I hope this helps, if at least to spark an idea from somebody, anybody else!
I really want to get this phone working at some point, if only for sustainability's sake!

hi mate, still having the same problem...
Here's what I've tried and what I'm sure of
I tried turning off features such as google assistant voice listening and it didn't work.
I tested multiple microphones in the device with hardware test programs and the speaker that acts as a handset and it works fine.
The device is calling the other party, sending sms, just because there is a voice exchange problem, I have no doubts about imei etc.
It's purely a software issue. it's so clear
The first thing I would try would be to go back to the original rom. I haven't tested this before.
I also think that the device may have different criteria according to different countries, so there may be a conflict. But I don't think I made a lot of mistakes, to be honest.
It's very important to me that you share your every attempt.
I really want to operate this device. It's my favorite device.
In the meantime, I opened the device and tried to change the transmission films. I tried changing the bottom charging port. These are not solutions.

Hi
Cyberfreak1992 said:
I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.
Click to expand...
Click to collapse
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch

Happy new year, everyone!
System23 said:
Hi
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch
Click to expand...
Click to collapse
With great pleasure I'm here to announce:
Can confirm this works! Just tried it today, the patch straightforwadly fixes this issue.
I had to skip the integrity check in TWRP to be able install it, but that should be obvious.
I already lost hope.
All the thanks and all the glory definately go to System23!