LineageOS 16.0 for S7 Edge build 30
- Thread starter Ivan_Meler
- Start date
Thany you, Sir!
Can I also have the data from vendor tree, manifest.xml, etc. for the Samsung Galaxy S Edge SM-G935F (hero2lte)? That would be fantastic!
expressluke
Senior Member
Dear Sir, I thank you for your prompt responses.
The XDA forum is still very foreign to me, so I move around in it a little uncertainly. It can only get better - with time.
For every further tip concerning S7 S 7 Edge I'm grateful to you.
F2fs is not supported with any los. Maybe moro kernel supports f2fs for los16. Los17 with f2fs works with morokernel
multiwirth
Senior Member
Hi there,
a short question:
In terms of rom compatibility is there any difference for s7 and s7 edge as they should be the same except the screen?
a short question:
In terms of rom compatibility is there any difference for s7 and s7 edge as they should be the same except the screen?
June security update builds are up, Nothing major in this build since I was focusing on los 17.1 builds and their rebase which is still in progress
Here is a brief changelog
- Merged June security update
- Synced with LOS source
Big thanks to everyone who supported this project so far as it helped offset build sevrer cost and this wouldnt be possible without them, Also ill try to post 15.1 builds with june patch soon (I have to test their stability and update few things in them)
Here is a brief changelog
- Merged June security update
- Synced with LOS source
Big thanks to everyone who supported this project so far as it helped offset build sevrer cost and this wouldnt be possible without them, Also ill try to post 15.1 builds with june patch soon (I have to test their stability and update few things in them)
This ROM works nicely. I have 1 problem though. The call audio is way too loud when putting it on the lowest. I noticed this problem with all AOSP ROMS. Samsung based ROMS are fine. Could you please find out how to fix this? Overall, enjoying this ROM but minus with this issue.
Thanks!
Thanks!
Builds with July 2020 security updates are out, There are not a lot of changes just some misc performance improvements along with security updates
17.1 builds with rebase are on their way (There are 2 small issues that have to be sorted one being 32bit versions of chrome refusing to load sites, and other is camera fdsan crash in rare cases), Once again big thanks to everyone who supported this project as it wouldnt be possible without them and work on android q wouldnt be possible either as donations help cover build server cost
17.1 builds with rebase are on their way (There are 2 small issues that have to be sorted one being 32bit versions of chrome refusing to load sites, and other is camera fdsan crash in rare cases), Once again big thanks to everyone who supported this project as it wouldnt be possible without them and work on android q wouldnt be possible either as donations help cover build server cost
Builds with July 2020 security updates are out, There are not a lot of changes just some misc performance improvements along with security updates
17.1 builds with rebase are on their way (There are 2 small issues that have to be sorted one being 32bit versions of chrome refusing to load sites, and other is camera fdsan crash in rare cases), Once again big thanks to everyone who supported this project as it wouldnt be possible without them and work on android q wouldnt be possible either as donations help cover build server cost
17.1 builds with rebase are on their way (There are 2 small issues that have to be sorted one being 32bit versions of chrome refusing to load sites, and other is camera fdsan crash in rare cases), Once again big thanks to everyone who supported this project as it wouldnt be possible without them and work on android q wouldnt be possible either as donations help cover build server cost
Extended Length Problem with AusweisApp2
Hi there,
first many thanks for this great work. :good: I have a SM-G930F. I use the AusweisApp2 for my identification card. With Stock ROM all was ok.
After flashing this custom ROM i have a extended length failure.
Quote FAQ AusweissApp2:
The challenge of extended length for smartphones
It is necessary that "Extended Length" is supported for communication by both the NFC chip and the firmware used by the respective device manufacturer so that the data and certificates can be successfully transferred. The current generation of commercially available NFC chips in Europe already supports Extended Length as standard. In fact, the version of the firmware / Android operating system used is often the stumbling block in this context. There is a field (-variable) that is read out by AusweisApp2 to check whether your smartphone supports Extended Length or not. This variable contains the packet length and is hard-coded in the operating system of the mobile device up to Android 8.0. Many mobile devices therefore only pretend to be able to transmit 261 bytes. In order for the reading process to work, the device must report that it can transmit a packet length of at least 500 bytes. This packet length is mainly used by AusweisApp2 or the online ID to implement the security protocols, e.g. PACE (encryption) required.
With the Android 9 operating system, Extended Length is enabled by default (see issuetracker.google.com/issues/37005118 - In detail, this change means that the smartphone manufacturers can / must now configure how many bytes at a time when using Android can be transferred.).
Apple released the NFC interface in autumn 2019. Since iOS 13.1 and from an iPhone 7, you can use the online ID function with the AusweisApp2.
Is it possible to fix this problem?
Thanks.
Hi there,
first many thanks for this great work. :good: I have a SM-G930F. I use the AusweisApp2 for my identification card. With Stock ROM all was ok.
After flashing this custom ROM i have a extended length failure.
Quote FAQ AusweissApp2:
The challenge of extended length for smartphones
It is necessary that "Extended Length" is supported for communication by both the NFC chip and the firmware used by the respective device manufacturer so that the data and certificates can be successfully transferred. The current generation of commercially available NFC chips in Europe already supports Extended Length as standard. In fact, the version of the firmware / Android operating system used is often the stumbling block in this context. There is a field (-variable) that is read out by AusweisApp2 to check whether your smartphone supports Extended Length or not. This variable contains the packet length and is hard-coded in the operating system of the mobile device up to Android 8.0. Many mobile devices therefore only pretend to be able to transmit 261 bytes. In order for the reading process to work, the device must report that it can transmit a packet length of at least 500 bytes. This packet length is mainly used by AusweisApp2 or the online ID to implement the security protocols, e.g. PACE (encryption) required.
With the Android 9 operating system, Extended Length is enabled by default (see issuetracker.google.com/issues/37005118 - In detail, this change means that the smartphone manufacturers can / must now configure how many bytes at a time when using Android can be transferred.).
Apple released the NFC interface in autumn 2019. Since iOS 13.1 and from an iPhone 7, you can use the online ID function with the AusweisApp2.
Is it possible to fix this problem?
Thanks.
Any info relating security update builds of LOS 16.0? Still prefer it, due to included Privacy Guard.
After testing out the ROM I foubd 2 problems
1 . fix for pictures saved from camera are corrupted on SD card after saving (open camera)
2. All audio isn't directed through headphones when connected as I can hear keyboard notes playing from main speaker of the phone
---------- Post added at 04:21 PM ---------- Previous post was at 04:21 PM ----------
After testing out the ROM I foubd 2 problems
1 . fix for pictures saved from camera are corrupted on SD card after saving (open camera)
2. All audio isn't directed through headphones when connected as I can hear keyboard notes playing from main speaker of the phone
1 . fix for pictures saved from camera are corrupted on SD card after saving (open camera)
2. All audio isn't directed through headphones when connected as I can hear keyboard notes playing from main speaker of the phone
---------- Post added at 04:21 PM ---------- Previous post was at 04:21 PM ----------
After testing out the ROM I foubd 2 problems
1 . fix for pictures saved from camera are corrupted on SD card after saving (open camera)
2. All audio isn't directed through headphones when connected as I can hear keyboard notes playing from main speaker of the phone
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
193
LineageOS 16.0 for hero2lte
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:
- 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
- HW encoding/decoding
- Charging with device powered off
- GPS
- Camera
- HWcomposer (HWC)
Not Working
-
Take a note that a lot of LineageOS features have not been completed yet this is not a device bug and please do not report those
in this rom thread as you will be reported to moderator also do not post bug reports for known issues or bug reports without proper
a) Logcat
b) proc/last_kmsg (or proc/kmsg)
c) data/tombstones
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Install gapps right after installing the rom itself dont try to boot to system before that
Downloads:
Google Drive
Mega.nz
MD5: 6cca47e757fd6ff6f48cbf51bc62d626
OpenGapps
Root
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 9 Pie
Changelog
XDA:DevDB Information
LineageOS 16.0 for S7 Edge, ROM for the Samsung Galaxy S7 Edge
Contributors
Ivan_Meler
Source Code: https://github.com/ivanmeler/android_kernel_samsung_herolte
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 1.2.5
Stable Release Date: 2020-07-12
Created 2018-09-14
Last Updated 2020-07-1257New build is up, making this a first exynos device to have working hwc on aosp pie. build has been tested against previous hwc issues which were present last time it was enabled and such issues werent present in this build,
Also gotta say im really dissapointed at this comunity at this point, Some of you clearly dont understand i do this in my free time which i might not have sometimes due to work and other stuff i have to deal with in personal life and i do this for free just to help comunity (Hell i even cover server cost), so you cant demand anything i said i would post build when i get time which is right now, and worst of all im only person working on this device so if i wasnt working there wouldnt be aosp pie or oreo for that matter so if any of you feel like complaining again you can just go and use any other rom from here
anyway here is an short changelog
12.05.2019.
- Fixed HWC
- Updated kernel to 3.18.139
- Updated vendor security patch to match (Latest at the moment samsung decided to drop support for monthly patches on s7 so they update it every 3 months now, we dont use a lot of blobs from stock anyway so this is non issue)
- Updated system security patch to may
- Enabled quota support on /data (Make sure you are on latest twrp)
- Misc performance and stability improvements
- Synced with LOS source47So a progress update on Q, I have booting build i got done earlier today but i want to finish up few things before posting it, as for lack updates i got sick of this comunity as some group of users are really disrespectful and well being only person that worked on aosp while others just take work and do it for profit while i spend time and money on build server expensses and reverse engineering stuff and stuff just didnt sit fine for me (I cant really build on other peoples servers either as i have parts of bsp source that is private and i dont want to leak as i could get in legal trouble, and thats the reason why rom has fully working hwc amongst other things) As for surprise i decided to postpone it until i release q because it would be picked by others minute i post it anyway
And well thanks to everyone who donated earlier as i do this non profit (Unlike some projects on these forums) in my free time and those donations help offset server cost a bit, ill try to post q builds in a coming week46Here is another progress update
I've updated graphics stack to use samsungs mali drivers provided with oreo (R22P0)
This means device is now fully using oreo blobs which should improve stability performance battery life and security in general
this should also help resolve some issues on pie builds (Like that black screen and camera issues)
While device does perform better with new blosb it managed to break camera and Hardware encoding/decoding so i need to look into that before
next release, as im doing this in my free time im not sure how long will it take till i have enough time to figure this out completely
but hopefully shouldnt be too long, also on a positive note HWC is working even with new blobs so there shouldnt be any degradation once camera and hw encoding/decoding are working with new blobs
this could also mean camera quality could improve a bit but that is yet to be seen43New build is up, making this a first exynos device to have working hwc on aosp pie. build has been tested against previous hwc issues which were present last time it was enabled and such issues werent present in this build,
Also gotta say im really dissapointed at this comunity at this point, Some of you clearly dont understand i do this in my free time which i might not have sometimes due to work and other stuff i have to deal with in personal life and i do this for free just to help comunity (Hell i even cover server cost), so you cant demand anything i said i would post build when i get time which is right now, and worst of all im only person working on this device so if i wasnt working there wouldnt be aosp pie or oreo for that matter so if any of you feel like complaining again you can just go and use any other rom from here
anyway here is an short changelog
12.05.2019.
- Fixed HWC
- Updated kernel to 3.18.139
- Updated vendor security patch to match (Latest at the moment samsung decided to drop support for monthly patches on s7 so they update it every 3 months now, we dont use a lot of blobs from stock anyway so this is non issue)
- Updated system security patch to may
- Enabled quota support on /data (Make sure you are on latest twrp)
- Misc performance and stability improvements
- Synced with LOS source
