LineageOS 15.1 (Android 8.1.0) for S7 herolte build 53 18.20.2020.
- Thread starter Ivan_Meler
- Start date
Exodusnick
Senior Member
You do know that there will be no more security lease for lineageos 15.1 Google has discontinued it.Resurrection!
After a long period of deep sleep, I did it:
I created a new LineageOS 15.1 build for the Galaxy S7:
https://www.androidfilehost.com/?w=files&flid=331142
October (Security) patches are included:
https://review.lineageos.org/q/topic:"O_asb_2021-10"
.. and I would like to provide monthly builds for both S7 devices.
Testers very welcome!
I'm looking forward to your feedback...
Note:
My builds won't be signed for now!
Be careful when updating or upgrading from an earlier signed build!
Instructions can be found here:
https://wiki.lineageos.org/signing_builds.html#test-keys-to-your-own-release-keys-or-vice-versa
So there is no point in publishing monthly builds if nothing changes
There should be backports, 4.4.4 got backports all the way up to December 2019.
Exodusnick
Senior Member
Exodusnick
Senior Member
Exodusnick
Senior Member
One has already asked here and it was rejected https://review.lineageos.org/c/Line...sage-71a156679496134917bfc5121cda3d67d339a7be
See comments patchset.
Last edited:
Exodusnick
Senior Member
As I said it is unfortunately no longer worth it .
Next will drop lineageos16.0 no one knows when.
And I give support for lineageos 16.0 normal + lineageos 16.0 microg as long as it is possible.
Next will drop lineageos16.0 no one knows when.
And I give support for lineageos 16.0 normal + lineageos 16.0 microg as long as it is possible.
@Exodusnick , I absolutely agree with you!
I am currently building for several devices and using the backported Android 9 patches,
which are maintained into the sources of LineageOS 15.1.
And when I find the time, I'll switch to LineageOS 16.0, of course except for the Galaxy S7 devices ...
LineageOS 15.1 December build is available now:
I created a new LineageOS 15.1 build for the Galaxy S7:
https://www.androidfilehost.com/?w=files&flid=331142
December patches are included:
https://review.lineageos.org/q/topic:"O_asb_2021-12"
Please note!
Google has discontinued support for Android 8.1 in October 2021!
Hopefully, the Android 9 (security) patches will be backported to LineageOS 15.1 for a while ...
I will be offering such future builds when they become available.
But use them at your own risk!
I created a new LineageOS 15.1 build for the Galaxy S7:
https://www.androidfilehost.com/?w=files&flid=331142
December patches are included:
https://review.lineageos.org/q/topic:"O_asb_2021-12"
Please note!
Google has discontinued support for Android 8.1 in October 2021!
Hopefully, the Android 9 (security) patches will be backported to LineageOS 15.1 for a while ...
I will be offering such future builds when they become available.
But use them at your own risk!
Exodusnick
Senior Member
For lineageos 16.0 I already give support was around do you want to give then also still support on it ?
See here
LineageOS 16.0 for S7 build 30
LineageOS 16.0 for herolte /* * 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...
forum.xda-developers.com
I don't want to do that at all.
I wrote: "... of course except for the Galaxy S7 devices ..." ;-)
Exodusnick
Senior Member
So, everything seems to work just fine on this Rom. Amazing Work! 
The only thing I've found which is not working is this echo problem when using the speaker phone
Ppl say in here that it is because of missing noise cancellation code that is Samsung proprietary. So my question is, is it technically possible to add the samsung code by flashing a zip or something?
I get that you wouldn't want to implement it in a LOS build ofc but, could it be done for those of us who want it? Or is that code just simply not compatible with for example LOS?
Alternately, is there a way to reroute the audio from the internal speaker to the external speaker without reproducing this effect?
Seeing as internal speaker is without echo no matter volume and external speaker is with echo no matter volume it doesn't really feel like its the microphone thats the problem
The only thing I've found which is not working is this echo problem when using the speaker phone
Ppl say in here that it is because of missing noise cancellation code that is Samsung proprietary. So my question is, is it technically possible to add the samsung code by flashing a zip or something?
I get that you wouldn't want to implement it in a LOS build ofc but, could it be done for those of us who want it? Or is that code just simply not compatible with for example LOS?
Alternately, is there a way to reroute the audio from the internal speaker to the external speaker without reproducing this effect?
Seeing as internal speaker is without echo no matter volume and external speaker is with echo no matter volume it doesn't really feel like its the microphone thats the problem
Last edited:
So, about the speaker phone echo problem. I've been googling for hours and trying different things out and it seems to be unsolvable without remaking the Rom itself
But.. What you can do is raise the normal in call speaker volume enough so that you can use that as your loud speaker
I've tried it by editing mixer_paths_0.xml in /system/etc
So what I did was copy the file to a writable location (for example /sdcard) then i edited all of these values to 50 instead of the original 32
After that I used TWRP to mount /system and replace the file and voila, now you have a working loud speaker. Sort of..
50 might be a bit high value but if people start hearing themselves you can always just turn the volume down using the buttons
Its much better than the more or less useless loud speaker at least!
<path name="gain-incall_nb-handset">
<ctl name="HPOUT3L Input 1 Volume" value="50" />
<ctl name="HPOUT3R Input 1 Volume" value="50" />
<ctl name="HPOUT3L Input 2 Volume" value="50" />
<ctl name="HPOUT3R Input 2 Volume" value="50" />
<param name="DSP4 XM f010:0" value="0 0 0 1 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 5 0 0 0 7 0 0 0 9 0 0 0 11 0 0 0 13 0 0 0 6 0 0 0 3 0 0 0 22 0 0 0 3 0 0 0 0 0 0 1 50 0 0 0 240 0 255 255 118 0 255 254 74 0 255 254 239 0 0 0 223 0 0 65 238 0 0 0 3 0 0 0 3 0 0 0 0 0 0 0 0 0 0 82 8 0 0 39 16 0 0 0 12 0 0 5 220 0 0 7 208 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 12" />
<param name="DSP4 XM f010:1" value="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3" />
</path>
<path name="gain-incall_wb-handset">
<ctl name="HPOUT3L Input 1 Volume" value="50" />
<ctl name="HPOUT3R Input 1 Volume" value="50" />
<ctl name="HPOUT3L Input 2 Volume" value="50" />
<ctl name="HPOUT3R Input 2 Volume" value="50" />
<param name="DSP4 XM f010:0" value="0 0 0 1 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 5 0 0 0 7 0 0 0 9 0 0 0 11 0 0 0 13 0 0 0 6 0 0 0 3 0 0 0 22 0 0 0 3 0 0 0 0 0 0 1 50 0 0 0 240 0 255 255 118 0 255 254 74 0 255 254 239 0 0 0 223 0 0 65 238 0 0 0 3 0 0 0 3 0 0 0 0 0 0 0 0 0 0 82 8 0 0 39 16 0 0 0 12 0 0 5 220 0 0 7 208 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 2 0 0 0 0 0 0 1 12" />
<param name="DSP4 XM f010:1" value="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3" />
</path>
But.. What you can do is raise the normal in call speaker volume enough so that you can use that as your loud speaker
I've tried it by editing mixer_paths_0.xml in /system/etc
So what I did was copy the file to a writable location (for example /sdcard) then i edited all of these values to 50 instead of the original 32
After that I used TWRP to mount /system and replace the file and voila, now you have a working loud speaker. Sort of..
50 might be a bit high value but if people start hearing themselves you can always just turn the volume down using the buttons
Its much better than the more or less useless loud speaker at least!
<path name="gain-incall_nb-handset">
<ctl name="HPOUT3L Input 1 Volume" value="50" />
<ctl name="HPOUT3R Input 1 Volume" value="50" />
<ctl name="HPOUT3L Input 2 Volume" value="50" />
<ctl name="HPOUT3R Input 2 Volume" value="50" />
<param name="DSP4 XM f010:0" value="0 0 0 1 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 5 0 0 0 7 0 0 0 9 0 0 0 11 0 0 0 13 0 0 0 6 0 0 0 3 0 0 0 22 0 0 0 3 0 0 0 0 0 0 1 50 0 0 0 240 0 255 255 118 0 255 254 74 0 255 254 239 0 0 0 223 0 0 65 238 0 0 0 3 0 0 0 3 0 0 0 0 0 0 0 0 0 0 82 8 0 0 39 16 0 0 0 12 0 0 5 220 0 0 7 208 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 12" />
<param name="DSP4 XM f010:1" value="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3" />
</path>
<path name="gain-incall_wb-handset">
<ctl name="HPOUT3L Input 1 Volume" value="50" />
<ctl name="HPOUT3R Input 1 Volume" value="50" />
<ctl name="HPOUT3L Input 2 Volume" value="50" />
<ctl name="HPOUT3R Input 2 Volume" value="50" />
<param name="DSP4 XM f010:0" value="0 0 0 1 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 0 0 0 5 0 0 0 7 0 0 0 9 0 0 0 11 0 0 0 13 0 0 0 6 0 0 0 3 0 0 0 22 0 0 0 3 0 0 0 0 0 0 1 50 0 0 0 240 0 255 255 118 0 255 254 74 0 255 254 239 0 0 0 223 0 0 65 238 0 0 0 3 0 0 0 3 0 0 0 0 0 0 0 0 0 0 82 8 0 0 39 16 0 0 0 12 0 0 5 220 0 0 7 208 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 2 0 0 0 0 0 0 1 12" />
<param name="DSP4 XM f010:1" value="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3" />
</path>
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
235
LineageOS 15.1 for herolte
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. */
Working:
- Camera
- Camcorder
- Wifi
- Sound
- mali drivers
- USB tethering
- Video Playback
- Fingerprint Sensor
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Buttons and their backlight
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- Stuff I didn't test yet
- HW encoding/decoding
- Charging with device powered off
- HWcomposer (HWC)
- GPS
- Screen cast
- Bluetooth in call audio
Not working
-
DO NOT POST BUG REPORTS WITHOUT LOGCAT OR STEPS TO REPRODUCE BUG
(some bugs also require dmesg and/or (last_)kmsg and/or /data/tombstones/*)
Install gapps right after installing the rom itself dont try to boot to system before that
Downloads:
Google Drive
Mega.nz
MD5: ff9c8d53bb0a94649761e181c6e49b71
OpenGapps
MindTheGapps
Root
15.0 Build and gapps
I do this in my free time so bear that in mind when you notice I didn't fix known bug in next available build, Currently i work on this alone and i am not one of those kangers that just copy source and claim it as their own work,
if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler
Feel free to join telegram group with early builds progress updates and some off topic stuff Join
Based On Android 8.1.0 Oreo
Changelog
XDA:DevDB Information
LineageOS 15.1 for herolte, ROM for the Samsung Galaxy S7
Contributors
Ivan_Meler
Source Code: https://github.com/ivanmeler/android_kernel_samsung_herolte
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 1.0.R
Stable Release Date: 2020-02-18
Created 2017-11-25
Last Updated 2020-02-1863New build is up, go get it in op
Changelog
01.08.2018.
- Completely swapped kernel to a new base (ERF4) and upstreamed to 3.18.91
- No more random reboots (No matter which gapps you use either)
- general stability improvements
- performance improvements
- battery life improvements
- Added new mac ranges to macloader algiorithm
- This will ensure people that had weak wifi signal will have better reception as their chip
will get properly detected (If you are still having issues with wifi range feel free to reach me
in PM ill need first half of phones mac address)
- Switched to oreo ril blobs
- This will improve signal strenght
- Battery life
- General ril stack stability (voice/data/sms)
- Fixed Drm content
- New version of netflix app will work so will apps that depend on it
- Added nfc wrapper (this should help with nfc stability)
- Removed kernel is not seandroid enforcing warning
- Fixed GPS
- Updated all of the gps and sensor blobs to ones from oreo ERF4
- This wont help you locate nearby seals tho, they dont want to be seen and will keep hidding from gps
- Synced with LOS source
58Yet another quick progress update, Rebase on top of samsungs oreo drop is almost done, Kernel is ready I also updated BSP source, I just need to figure out few things about new blobs as samsungs implementation is kinda weird and i dont want to publis build that might be less stable than last one58New build is up , Quite big changes in this one, HWC has been fixed and thats just one of things that makes this build smoothest so far for that matter it should be as smooth as TW if not smoother as ui elements are finally rendered by gpu and not cpu, This should also make battery last longer as we dont push cpu with tasks like rendering ui and gpu was intended for that anyway
Also I am proud to announce I'm now a part of LineageOS team and once I resolve issues with GPS official LOS 15.1 builds will start to roll, That doesnt mean ill stop unofficial builds on xda as ill use xda as test ground for latest new features and improvements, Also this build is based on new BSP, and this is just first on the list of surprises comming for this, anyway enjoy new build, Also I still do this in my free time and dont get paid for this so dont ask for eta's52More progress updates from Pie
Mobile data is working now
Gps is working
All of the sensors are working
Mobile calls dont drop randomly anymore
MTP (and usb in general) is working
OMX is working
Camera is still broken and ill focus on fixing it before release everything else i tested so far
was working
Also note that im doing this in my free time and i dont get paid for this so please try not to rush me and message
me asking me about ETAs its quite irritating and i dont care if X or Y device got aosp, As s7 is only device with this cpu
and you cant compare it with devices that used same cpu as countless other devices, Thanks for understanding
Also ill probbaly be releasing few more 15.1 builds before it goes official with minor bug fixes
I would also like to thank everyone who donated in past as it helps with covering build server hosting
