[ROM] [Q-S] LineageOS With MicroG for Samsung S7 Flat/Edge

Search This thread
LineageOS microG 19.1 update available

important:
the update must be installed manually because the check of the updater of the rom fails. because i rebuilt everything and forgot to save the user-keys .

Important!
Make a backup before updating to make sure you revert to your current ROM.

Changelog
- Synchronized with LOS source
- bromite system web view to 100.0.4896.92
- bromite browser on 100.0.4896.92
- Permission manager still says "loading".
I can't fix this must do the dev. bananer.
permissions can be accessed from the app itself or from the privacy dashboard

"we had this problem under 18.1 as well, this has been fixed"

Changelog from ivan_meler
- 18.04.2022.
- Fixed bug wehre vibrations were too low on some devices due to inintensity being set to 0
- Fixed bug where apps would show square popup "animation" when launching from icon instead of roudned one
15.04.2022.
- Updated sepolicy and merged updated common samsung_slsi sepolicy
- Increased microphone gain while recording media (Camcorder, voice recording etc.)
- Added option to disable vibration feedback on fingerprint auth

Download Rom
https://www.los-legacy.de/19.1/herolte ...
lineage-19.1-20220419-microG-signed-herolte

The Rom was tested by me all main functions work properly!!
 
here are some screenshots after a clean install with magisk v23.x

New updated Rom for LineageOS 17.1 microG

Changelog
- Synced LOS Sources
- Merged April. 2022. security update
- Chromium Bromite browser back in version 100.0.4896.135
- updated Bromite WebView to version 100.0.4896.135
- WebView provider updated
- removed all Google WebView and AOSP WebView providers
- added Bromite WebView provider
vendor_lineage update common_mobile.mk
- added Chromium Bromite Browser

changelist microG

- update from lineageos4microg/android_prebuilts_prebuiltapks
to lineageos4microg/android_vendor_partners_gms
- vendor_lineage update common_mobile.mk
Add GmsCore \GsfProxy \ FakeStore \LocalGsmNlpBackend
\ NominatimGeocoderBackend \ PdfViewer \ AuroraServices
\ AuroraStore \ AuroraDroid \ F-Droid


lineage-17.1-20220424-microG-signed-herolte.zip

It has no effect on your current version, only the sources have chan
 

Attachments

  • Screenshot_20220424-131610_Magisk.png
    Screenshot_20220424-131610_Magisk.png
    109.6 KB · Views: 35
  • Screenshot_20220424-131537_Magisk.png
    Screenshot_20220424-131537_Magisk.png
    178.2 KB · Views: 30
  • Screenshot_20220424-131531_Magisk.png
    Screenshot_20220424-131531_Magisk.png
    82.2 KB · Views: 27
  • Screenshot_20220424-131501_Einstellungen.png
    Screenshot_20220424-131501_Einstellungen.png
    188.2 KB · Views: 26
  • Screenshot_20220424-131434_microG_Services_Core.png
    Screenshot_20220424-131434_microG_Services_Core.png
    172 KB · Views: 27
  • Screenshot_20220424-131426_microG_Services_Core.png
    Screenshot_20220424-131426_microG_Services_Core.png
    249.7 KB · Views: 27
  • Screenshot_20220424-131417_Trebuchet.png
    Screenshot_20220424-131417_Trebuchet.png
    458.6 KB · Views: 34
LineageOS microG 19.1 update available via OTA

Changelog by ivan_meler
27.04.2022.
- libbfqio dependency on hwc removed, as it was removed from Lineageos 19.1
- Various performance and stability improvements
- Synchronized with LineageOS sources (same base as official builds + some extras)
- bromite system web view to 100.04896.135
- bromite browser to 100.04896.135

download Samsung Flat
lineage-19.1-20220427-microG-signed-herolte.zip
+ recovery.img
+ prop

these extras were automatically created with and belong to.

Support for german users

Dashboard - LOS-Legacy®

Deine Android Community
 
LineageOS microG 19.1 update available via OTA

Changelog

by ivan meler
07.05.2022.
- Improved battery usage logging for the display.
- QR code reader added to camera app (long hold icon and launch from context menu)
- Various performance and stability improvements
10.05.2022.
- Switch to the new libperfmgr power hal, which can be configured via /system/vendor/etc/powerhints.json
- DT2W adapted to the new power grid
- Muted gps notification for phone services (thanks Google for solving so many things for everyone)
- Improved battery life and performance
- Cleanup of all leftover patches that was used by the old PowerHal
------------------

14.05.2022
- Merged security update from May 2022.
- Synchronized with LineageOS source
- fixed permissions manager

lineage-19.1-20220513-microG-signed-herolte.zip
 

Attachments

  • photo_2022-05-14_08-44-15.jpg
    photo_2022-05-14_08-44-15.jpg
    52.7 KB · Views: 9
  • Like
Reactions: daywalk3r666
Last edited:

nutzfreelance

Senior Member
Mar 6, 2022
155
45
i flashed 19.1 with twrp 3310 and it booted fine but when i rebooted to recovery it hangs and i cannot get it to boot , i can get to download mode

what is the minimum twrp?
 
Last edited:

nutzfreelance

Senior Member
Mar 6, 2022
155
45
@nutzfreelance
twrp-3.6.1_9-0
there is also an issue with magisk and Zygisk

Device: Samsung Android version: N/A Magisk version name: N/A Magisk version code: 24102
For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it does not exist for the old kernel. Users with those devices should use a custom kernel bypassing such a restriction or a newer version.

i will not push for a fix but i just wanted to let you know it exists
(ok i lied please please please please ( i have both a s7e and s7 and love your roms))
( is there a reason kernel is still on 3.XX when other android 12's is on 5.XX)
 
Last edited:
there is also an issue with magisk and Zygisk

Device: Samsung Android version: N/A Magisk version name: N/A Magisk version code: 24102
For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it does not exist for the old kernel. Users with those devices should use a custom kernel bypassing such a restriction or a newer version.

i will not push for a fix but i just wanted to let you know it exists
(ok i lied please please please please ( i have both a s7e and s7 and love your roms))
( is there a reason kernel is still on 3.XX when other android 12's is on 5.XX)
there is no problem with magisk and zygisk
you just have to install it correctly.
install the current twrp version download magisk.apk change the extension from apk to zip boot into twrp and flash magisk.zip restart follow the instructions of magisk
if magisk is not visible change magisk.zip back to magisk.apk and install it.
Magisk/releases
FoxMagiskModuleManager


regarding the kernel, please contact the main developer @Ivan_Meler he can tell you more about it.
 

Attachments

  • photo_2022-05-18_02-03-54 (3).jpg
    photo_2022-05-18_02-03-54 (3).jpg
    72.8 KB · Views: 7
  • photo_2022-05-18_02-03-54 (2).jpg
    photo_2022-05-18_02-03-54 (2).jpg
    46.3 KB · Views: 7
  • photo_2022-05-18_02-03-54.jpg
    photo_2022-05-18_02-03-54.jpg
    109.6 KB · Views: 6
  • photo_2022-05-18_02-04-55.jpg
    photo_2022-05-18_02-04-55.jpg
    69.3 KB · Views: 6
Last edited:

nutzfreelance

Senior Member
Mar 6, 2022
155
45
there is no problem with magisk and zygisk
you just have to install it correctly.



regarding the kernel, please contact the main developer @Ivan_Meler he can tell you more about it.
its not magisk root that fails.
its zygisk that fails to enable
in magisk under setting try enabling zygisk ( beta)

after reboot it does not enable
and since magisk says zygisk is the future that's an issue.

i have this rom booting one of my s7 and ivens rom booting my s7E
both fail zygisk, and i have posted this in Ivan_Meler rom discussion.
 

Attachments

  • zygisk.jpg
    zygisk.jpg
    31.5 KB · Views: 7
Last edited:

Ivan_Meler

Forum Moderator / Recognized Developer
Staff member
its not magisk root that fails.
its zygisk that fails to enable
in magisk under setting try enabling zygisk ( beta)

after reboot it does not enable
and since magisk says zygisk is the future that's an issue.

i have this rom booting one of my s7 and ivens rom booting my s7E
both fail zygisk, and i have posted this in Ivan_Meler rom discussion.
well instead of posting this again either do what i told you in my thread (install magisk 24.1 or latest canary) or go complain to magisk developers since they are ones that broke this.
 
  • Like
Reactions: Exodusnick

nutzfreelance

Senior Member
Mar 6, 2022
155
45
well instead of posting this again either do what i told you in my thread (install magisk 24.1 or latest canary) or go complain to magisk developers since they are ones that broke this.
i am on magisk 24.3 there is no working solution except a upgraded kernel.
it is a kernel issue and will never be addressed by the magisk team.
(they have labeled it as "wontfix" https://github.com/topjohnwu/Magisk/issues/5395 as its a mostly samsung old kernel issue)

if you never plan to fix it with a newer kernel then zygisk will never work.
amd magisk has stated that zygisk is the future of magisk

that is you the developers choice. if you don't care thats your prerogative
(i posted in two forums because they are listed as two separate developers.)
 
i am on magisk 24.3 there is no working solution except a upgraded kernel.
it is a kernel issue and will never be addressed by the magisk team.
(they have labeled it as "wontfix" https://github.com/topjohnwu/Magisk/issues/5395 as its a mostly samsung old kernel issue)

if you never plan to fix it with a newer kernel then zygisk will never work.
amd magisk has stated that zygisk is the future of magisk

that is you the developers choice. if you don't care thats your prerogative
(i posted in two forums because they are listed as two separate developers.)
And again use the canary build. Last canary works on j5 2016 with los 19.1. and the j5 has an old 3.18 kernel
 
  • Like
Reactions: Exodusnick

Ivan_Meler

Forum Moderator / Recognized Developer
Staff member
i am on magisk 24.3 there is no working solution except a upgraded kernel.
it is a kernel issue and will never be addressed by the magisk team.
(they have labeled it as "wontfix" https://github.com/topjohnwu/Magisk/issues/5395 as its a mostly samsung old kernel issue)

if you never plan to fix it with a newer kernel then zygisk will never work.
amd magisk has stated that zygisk is the future of magisk

that is you the developers choice. if you don't care thats your prerogative
(i posted in two forums because they are listed as two separate developers.)
you clearly have no idea what you are talking about so just.. stop it, i hate being rude to people and as i said this is fixed in magisk canary because magisk is what broke it to begin with, and no there was no kernel fix for this because even backporting patch from 3.19 wouldn't fix the issue magisk introduced.
so please explain how will new magisk version not work if canary which is base for next stable is already working.

You are clearly posting this in multiple places because you either want to piss people off or have no idea what you are talking about
 
Last edited:

V0latyle

Forum Moderator
Staff member
***Moderator Announcement***

I'd like to make a couple things clear:
  • The developers on XDA work for free; they are not compensated for the time and effort they put into their projects, and do so largely as a hobby. Therefore, they owe you absolutely nothing. Do not ask for updates or ETAs, and do not be rude if something doesn't get fixed. Disrespect will not be tolerated, especially towards our developers, contributors, and staff.
  • All members regardless of seniority or status are expected to conduct themselves according to the XDA Forum Rules. There are many users of many different backgrounds and very diverse technical experience on this site. Be patient and kind. If you don't have anything nice to say, say nothing at all.
  • If you ask for support, consider the potential solutions that are given you. We have many very knowledgeable people on this site who do everything they can to help users just like you. Listen to them and take their advice. If a solution doesn't work for you, have the decency to explain why. Regardless of whether you get the answer you want or not, do not forget that you don't deserve anything, that our members are helping you simply for the sake of helping, and you are ultimately responsible for finding a solution to your problems. Furthermore, if you refuse to accept advice, don't bother asking for help. The answer you get won't always be the one you want, but it might be the one you need.
I hope you'll consider these guidelines going forward. Be courteous, civil, and professional, and chive on.
 
  • Like
Reactions: Exodusnick

Top Liked Posts