LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos

[netra3441]

Thank you very much for the test! But it leaves me a bit perplexed. The sd-card that lineage 19.1 cannot read is read in TWRP with no problems and was also read with no problems on lineage 17.1 and on Windows. And it is formatted exFAT. So obviously there are technical differences between exFAT formatted with lineage 19.1 and exFAT formatted with other systems.

You are welcome. I understand that forum here so, that we all here help eachother.

Actually I run two Samsung Galaxy S7. One is my dailer driver, installed LineageOS 19.1 with all updates (great thanks always to @Ivan_Meler and all others, who are working on this) and in ths S7 I run a 128 GB Scandisk SDcard, formatted als internal space. Runs properly.

My other Samsung Galaxy S7 is my test system, I use for testing matters, because I am a handicaped person, and need the first S7 (the dailer driver) always, it must work properly all the time. In my testing S7, actually installed with LineageOS 19.1 and all updates too, I use a 64 GB Sandisk SDcard, and this I can also format with the S7 either as mobile, or as internal space, both works properly.

But, fipsy, you are right with assuming, that formatting SDcards is not trivial. So, f.e., mostly the Windows operating systems does not format standard exfat on SDcards, so its better, to do this always and only within the Samsung Galaxy S7, never using the Windows OS for that. The exfat, the S7 produces, can be read and written in Windows to.

And yes, there are differences, but also between the version of LineageOS. Actually I am waiting for the next update of @Ivan_Meler's LOS 20.0 in the hope, that this next update then will work with SDcards also properly as same as in 19.1, actually there are problems with the 20.0 on my testing S7 with that.

 

[arpcpro]

... in ths S7 I run a 128 GB Scandisk SDcard, formatted als internal space. Runs properly.

.. with LineageOS 19.1 and all updates too, I use a 64 GB Sandisk SDcard, and this I can also format with the S7 either as mobile, or as internal space, both works properly.
...

You mean that the "adoptable storage" is finally working fine? Did you partition the SD card manually or automatically on the phone? I have a 512Gb SD card and would like to adopt 256Gb as internal space and leave the rest as portable storage.

 

[netra3441]

You mean that the "adoptable storage" is finally working fine? Did you partition the SD card manually or automatically on the phone? I have a 512Gb SD card and would like to adopt 256Gb as internal space and leave the rest as portable storage.

As far, as I know, the Samsung Galaxy S7 can only handle SDcards with maximum 128 GB.

Such an 128-GB SDcard I have in my first S7 (daily use) and with LOS 19.1 this works fine formatted as (additional) internal memory.

In my second S7 (for test purposes) I have a 64 GB SDcard. Under LOS 19.1 this works also properly formatted as internal memory.

Both SDcards were formatted inside LOS 19.1, means in the smartphones, not manualy f.e. on a PC or so.

But I do not know, if any SDcard can be split-formatted, as you want to do. As far as I know, Android itself, and so LOS 19.1 has no split formatting function.

Maybe other users here have more or better information.

 

[arpcpro]

I have the Exynos S7 and a ´Samsung Evo 512Gb UHS-I class 10, A2 V30 130Mb/s´ works fine. It still has around 300 Gb free, but so far all good in daily use with stock Nougat 8.0.
Yes, the split formatted method worked via adb shell in the stock android 7.0. I think that it was never possible to split via the android menus.

 

[netra3441]

I have the Exynos S7 and a ´Samsung Evo 512Gb UHS-I class 10, A2 V30 130Mb/s´ works fine. It still has around 300 Gb free, but so far all good in daily use with stock Nougat 8.0.
Yes, the split formatted method worked via adb shell in the stock android 7.0. I think that it was never possible to split via the android menus.

Thank you for the information about SDcard sizes. Interesting, that this works inside the S7.

For my needs a 128 GB is enough. I use it just for information and social media.

Serious things I do only on my Linux PC.

 

[fipsy]

Actually I run two Samsung Galaxy S7. One is my dailer driver, installed LineageOS 19.1 with all updates and in ths S7 I run a 128 GB Scandisk SDcard, formatted als internal space. Runs properly.

Exactly the same here! I run one S7 with LineageOS 17.1 as my daily phone with a 128 GB Windows NTFS formatted SanDisk SD-Card without any problems. I used exFAT before and had heavy problems with frequent spontaneous reboots (the card came exFAT preformatted and I didn't change the format). Now I'm just preparing the other phone with LineageOS 19.1 for migration. I also use NTFS in that phone and it works very well. Especially it's really fast. I always used the cards as mobile space.

Before you use the NTFS formatted card in a windows machine after using it in Lineage you have to delete the folder "System Volume Information" in the root of the SD-Card. Otherwise windows will not be able to read it.

But, fipsy, you are right with assuming, that formatting SDcards is not trivial. So, f.e., mostly the Windows operating systems does not format standard exfat on SDcards, so its better, to do this always and only within the Samsung Galaxy S7, never using the Windows OS for that. The exfat, the S7 produces, can be read and written in Windows to.

But it seems to be a special problem of lineage whereas TWRP is able to read the card without any problems.

Actually I am waiting for the next update of @Ivan_Meler's LOS 20.0 in the hope, that this next update then will work with SDcards also properly as same as in 19.1.

At first I also thought about using Lineage 20, but after seeing that there are neither OpenGapps nor NikGapps for it, I decided not to. The system is still too new and there are still too many problems with it.

 

[netra3441]

Exactly the same here! I run one S7 with LineageOS 17.1 as my dialy phone with a 128 GB Windows NTFS formatted SanDisk SD-Card without any problems. I used exFAT before and had heavy problems with frequent spontaneous reboots (the card came exFAT preformatted and I didn't change the format). Now I'm just preparing the other phone with LineageOS 19.1 for migration. I also use NTFS in that phone and it works very well. Especially it's really fast. I always used the cards as mobile space.

Before you use the NTFS formatted card in a windows machine after using it in Lineage you have to delete the folder "System Volume Information" in the root of the SD-Card. Otherwise windows will not be able to read it.


But it seems to be a special problem of lineage whereas TWRP is able to read the card without any problems.


At first I also thought about using Lineage 20, but after seeing that there are neither OpenGapps nor NikGapps for it, I decided not to. The system is still too new and there are still too many problems with it.

Well... never have heard, that NTFS works in a Smartphone - but ok. Myself I stay with exFAT all that years, thats original Android, no problems. I do not use Windows, I run Linux on my PCs and the notebook, just have one as a faxmachine under Win10, so therefore no need for me to use NTFS on an SDcard for my smartphone.

There are NikGAPPS for LineageOS 20.0. Works good. Read the first side of this thread, there you find a link.

But myself I tried Aurora store today, works nice, so I will install LineageOS 20.0 the next days on my daily driver - but only with Aurora, not with any GApps, because the testing S7 (my second one) runs much faster without that Google Framework.

Also I will arrange with formatting my 128Gb SDcard in my daily S7 as mobile memory, and try to organize files and apps in another way. I guess this will be the most serious problems with LineageOS 20.0, so I can do the upgrade from 19.1.

 

[fipsy]

Well... never have heard, that NTFS works in a Smartphone - but ok.

I had checked whether NTFS was supported and saw that it was. As far as I know the format was publicly released by Microsoft at some point. Therefore support is no longer a problem. The advantage of NTFS is that the cluster size is only 4 KB, making it very effective for many small files.

There are NikGAPPS for LineageOS 20.0. Works good. Read the first side of this thread, there you find a link.

Okay. Good to know. Migration to a new operating system is always relatively time-consuming for me because I have rooted the device and many scripts I wrote myself are running. It always takes quite a while before Magisk is set up again with all modules. And with working safetynet attestation. That's why I only do it every two to three years.

[..] not with any GApps, because the testing S7 (my second one) runs much faster without that Google Framework.

Absolutely! The Google Framework makes the device significantly slower. But I don't want to do without a lot of what Google offers. In that respect, I've adjusted a bit again.

Also I will arrange with formatting my 128Gb SDcard in my daily S7 as mobile memory, and try to organize files and apps in another way. I guess this will be the most serious problems with LineageOS 20.0, so I can do the upgrade from 19.1.

That was also one of the reasons why I gave it up. With Lineage 17.1 I put the largest directories of the internal memory on the SD card and linked them there with the help of Apps2SD. This works great. Let's see if this still works well with 19.1. It's on my agenda today.

 

[netra3441]

@fipsy

Thanks for your reply. Lot of information, very interesting, great, I appreciate that!

We learn every day something new.

I will give LOS 20.0 a try, but if this does not work, no problem to step back to 19.1.

A longer time I suspected the Google Framework, that it crimps more, than it helps.

 

[fipsy]

Thanks for your reply. Lot of information, very interesting, great, I appreciate that!

With pleasure! That's why I love this forum so much.

A longer time I suspected the Google Framework, that it crimps more, than it helps.

After all, the goal of this framekwork is not primarily to give users a good experience with the system, but to snoop on them.

 

[netra3441]

Well...

I have spended this Sunday to compare LOS 19.1 and LOS 20.0. It seems to be not such a good choice, to upgrade to 20.0 on a smartphone with low internal memory, like the Samsung Galaxy S7 is. With nowadays apps and userfile sizes a 32GB internal memory is too low.

19.1 not just allows SDcards to be formatted as internal memory, but also allows apps to save userfiles to the SDcard, when the apps have this function.

20.0 does not allow both. I really do not understand, why. I guess, this is, because the actual Pixel smartphones, from wich LineageOS has taken the Android, have no SDcard slot anymore...

External apps, wich help to move other apps to SDcard, only work, when the OS allows that, like 19.1 does, but not 20.0, or when a smartphone is rooted.

I do not root my smartphones, because this makes them unsafe.

Maybe I am wrong with that.

But it is very difficult, also here on XDA, to get proper and serious, ascertaining informations about f.e. rooting, if this is regarding the safeties of the smartphone, or not.

So, it seems, that I must stay with LOS 19.1, as long as my both Samsung Galaxy S7 work properly, and later, in a few years, buy a newer smartphone...

 

[araujo99]

LineageOS 19.1 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 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
- HW Backed video Playback
- Ril (Mobile data,calls, sms and stuff)
- Sensors
- Buttons
- Bluetooth
- Wifi HotSpot
- MTP
- 2D and 3D gpu acceleration
- HW encoding/decoding
- HWcomposer (HWC)
- Charging with device powered off
- Stuff I didn't test yet
- Camera
- GPS
- Fingerprint Sensor
- Mobicore
- SW codecs

Not Working
-


Keep in mind that some LineageOS features have not been completed yet this is not a device bug and please do not report those
in this rom thread, 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


Install gapps right after installing the rom itself don't try to boot to system before that if you want to use gapps (Or wipe data before installing them)

Make sure gapps you decide to use support android 12L/12.1/Are targetting api level 32
Also make sure you are using latest official TWRP before installing rom older versions do not have proper android 12 support

If you want to use Magisk use latest Magisk Beta (25.0) or Magisk 24.1, there is bug in 24.3 that was fixed after its release that prevents zygisk from working on some devices with 3.18 kernel

Downloads:
Google Drive
Mega.nz
GitHub Releases
MD5: f542ed3277e9abc559212931f4b49fd0


if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler

BTC: 1Q823BsSbEKP62JFM7BjXiRCgF84qgcFST
ETH(erc20): 0xc7272f851a692c679e85f18a62632c580ef3bdee
Donations help cover the build server cost and since I do this in my free time, and also cover the coffee for time spent debugging stuff



Feel free to join telegram group with early builds progress updates and some off topic stuff Join

Based On Android 12L/S
Changelog

05.01.2023.
- Merged January 2023. Security update
- Misc performance and stability improvements
- Synced with LineageOS source

07.12.2022.
- Merged December 2022. Security update
- Synced with LineageOS source

09.11.2022.
- Merged November 2022. Security update
- Cleaned up patches list
- Synced with LineageOS source

05.10.2022.
- Merged october 2022. Security update
- Fixed samsungs bug with gps where it would start acting up over time due to time rollover bug
- Synced with LineageOS source

07.09.2022.
- Merged September 2022. Security update
- Updated chromium webview to 105.0.5195.79
- Synced with LineageOS source

07.08.2022.
- Merged August 2022. Security update
- Synced with LineageOS source

07.07.2022.
- Merged July 2022. Security update
- Fixed more keystore issues
- Synced with LineageOS source

24.06.2022.
- Fixed issues with keystore present in a lot of bank/secure apps like binance
- Fixed issue where setupwizard would crash when adding fingerprint due to bug in keystore
- Cleaned up patches required for build and removed unneeded ones
- Synced with LineageOS source

07.06.2022.
- Merged June 2022. security update
- Merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
- Improved in-call audio quality drastically
- Addressed few more selinux denials
- Improved general stability and performance
- Cleaned up source
- Synced with LineageOS source

26.05.2022.
- Updated libexynosdisplay from BSP to comply with some android 12 changes
- Removed unused build.prop entries
- Fixed few selinux denials related to hwc props
- Improved UI performance and stability
- Cleaned up source
- Removed more unneeded patches for device support
- Synced with LineageOS source

18.05.2022.
- Added QR code reader quick settings toggle
- Improved device performance and stability
- Added Custom low power mode power profile for cpu
- Improved A-GNSS (A-GPS) Lock speed
- Exposed device hw revision to settings
- Improved fast/slow charger detection
- Synced with LineageOS source

10.05.2022.
- Switched to new libperfmgr power hal which can be configured from /system/vendor/etc/powerhints.json
- Adapted DT2W to new power hal
- Muted phone services gps notif (Thanks google really appreciate you breaking random things for everyone)
- Improved battery life and performance
- Cleaned up all of leftover patches that were used by legacy power hal
- Synced with LineageOS source

07.05.2022.
- Improved battery usage logging for display
- Added QR code reader to camera app (Long hold icon and launch it from context menu)
- Misc performance and stability improvements
- Merged May 2022. security update
- Synced with LineageOS source

27.04.2022.
- Removed libbfqio dependency from hwc since it was dropped from lineageos 19.1
- Misc performance and stability improvements
- Synced with LineageOS source (same base as official builds + some extras)

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
- Cleaned up build patches
- Synced with LineageOS source

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
- Synced with LineageOS source

08.04.2022.
- Fixed extended volume panel
- Updated icons for few more stock apps
- Cleaned up patches further
- Misc peroformance improvements
- Synced with LineageOS source

06.04.2022.
- Merged April 2022. Security update
- Enabled new LineageOS icons (you might have to clear launcher cache for them to show up)
- Fixed issue where galery app would show black text on black background
- Fixed issue where unlock sound would sometimes play twice
- Misc performance and stability improvements
- Synced with LineageOS source

29.03.2022.
- Drastically speed up app launch time (more info about that here)
- Imrpoved performance and battery life by disabling some unnecessary logging
- Switched to source built camera provider and removed samsung proprietary one
- Upreved camera provider to 2.5
- Fixed few selinux denials related to NFC trying to raad debug props
- Removed floating_feature.xml which is unused on aosp
- Disabled livedisplay by default
- Cleaned up extra dependencies used for compiling
- Synced with LOS source

22.03.2022.
- Added back configurable audio volume panel location
- Speed up unlock with fingerprint
- Updated a lot of apps to MaterialYou design language
- Fixed issue where touch screen area bellow home button would act as a gesture area even while gestures are disabled
- Improved stability of ADB connection
- Implemented new LineageOS setupwizard
- Cleaned up device tree and list of required patches
- Stability and performance improvements
- Pointed Changelog url in updater app to new page
- Synced with LineageOS source

14.03.2022.
- Fixed issue with keystore where apps would crash when invoking it (Security related apps mostly like signal and a lot of work apps)
- Officially rebranded as 19.1
- Updated changelog URL in updater app to point to a valid changelog
- Fixed battery icon styles (Again..)
- Removed invalid zram config.
- Cleaned up source
- Performance and stability improvements
- Updated some stock apps to math with new design
- Synced with LineageOS source

10.03.2022.
- Merged March 2022. security and feature updates (Android 12L)
- Fixed status bar network trafic monitor
- Improved zram performance and enabled zram writeback
- Cleaned up patches needed for build
- Fixed network usage monitoring
- Fixed per app network restrictions
- Removed AudioFX which was causing issues
- Decreased microphone and earpiece gain a bit to mitigate in-call issues
- Updated some device control apps like advanced display settings
- Improved vibrator intensity in new hal
- Imrpoved fp sensor response time
- A lot of 'under the hood' changes
- Performance improvements
- Merged more previously missing los features
- Implemented OTA updates

10.02.2022.
- Merged February 2022. security update
- Removed broken volume button location toggle
- Synced with LOS source

09.02.2022.
- Fixed issue where camera would stop working after prolonged use
- Misc performance and stability improvements
- Merged some more lineageos features that have been posted to gerrit
- Synced with LOS source

28.01.2022.
- Fixed developer options crashing on launch
- Added Bluetooth SBC Dual Channel HD audio mode
- Synced with LOS source

27.01.2022.
- Added back lineageos setup wizard present on clean installs
- Merged some of previously missing features that have been ported over to LineageOS 19
- Performance and stability improvements
- Synced with LOS source

18.01.2022.
- Enabled selinux (Its enforcing now)
- Moved audio hal to vendor
- Fixed confirmation dialog box for button backlight
- Fixed ok button which would go missing for button backlight
- Switched to source built secril_config_svc (used for ds detection)
- Removed obsolete debug.sf.disable_backpressure prop
- Merged latest security updates to kernel from aosp kernel/common
- Cleaned up source
- Cleaned up unused props
- Removed unused custom ld.config.txt that was overriding main one
- Misc performance and stability improvements
- Synced with LOS source

06.01.2022.
- Removed duplicate props in vendor and system
- Cleaned up device tree code
- Switched to source built camera provider lib
- Switched to few source built ril related libs
- Addressed more selinux denials
- Fixed volume panel location settings
- Added button backlight
- Added Advanced Reboot
- Added LiveDisplay entry into settings
- Added system side toggle for navigation bar
- Merged January 2022 Security Update
- Merged most of previously missing LineageOS features
- Misc performance and stability improvements
- Synced with LOS source


20.12.2021.
- Fixed wireless display
- Reduced logspam which should imrpove performance a bit
- Misc performance and stability improvements
- Synced with LOS source

16.12.2021.
- Merged r18 tag of Android 12 (SQ1D.211205.016.A1)
- Removed liboemcrypto which was preventing drm playback in some apps
- Synced with LOS source

13.12.2021.
- Updated Clearkey to 1.4
- Addressed most of selinux denials
- Switched to new AIDL Lights hal
- Upreved audio hal to 7.0
- Switched to new AIDL Vibrator hal
- Disabled configstore which got replaced with props
- Upreved fingerprint hal/service to 1.3
- Removido sinalizador de defconfig do kernel não utilizado
- Sincronizado com a fonte LOS

09.12.2021.
- Fundido em dezembro de 2021. Atualização de segurança
- Queda de recurso de pixel de dezembro de 2021 mesclada
- Adicionado suporte a falsificação de assinatura que pode ser usado para adicionar microg em vez de gapps
- Mesclado muitos recursos de lineageos que foram implementados
- Corrigida a taxa de amostragem do bluetooth durante uma chamada
- Regras ueventd específicas do dispositivo movidas para /system/vendor/etc
- Libertou algum carneiro
- melhorias de desempenho e estabilidade

30.11.2021.
- Lançamento inicial
[/esconder]


XDA:Informações DevDB
LineageOS 19.0 para S7, ROM para Samsung Galaxy S7

Contribuintes
Ivan_Meler
Código fonte: https://github.com/8890q/android_kernel_samsung_universal8890/tree/lineage-19.0

Versão do sistema operacional ROM: Android 12L
Kernel da ROM: Linux 3.18.x

Versão informação
Estado: EstávelI can use

Can I use twrp version 3.6.2_9-0 to install? Because the partition does not allow latest twrp instalat.

 

[ScanX]

Can I use twrp version 3.6.2_9-0 to install? Because the partition does not allow latest twrp instalat.

You can do without hesitation.

 

[fipsy]

There was a problem with the official download of TWRP for the S7. This problem is still not fixed. It cannot be flashed because the image is too big for the recovery partition. Ivan has therefore released another version for download that works: https://forum.xda-developers.com/t/...p-for-galaxy-s7-herolte.3333770/post-87570457

 

[sansei]

Hi, do I need to root my phone in order to have any app store available?

I installed TWRP 3.6.2 via Odin, left 'system unmodified' in TWRP and didn't root the phone, and installed LineageOS 19.1 + FlameGApps-12.1-basic through ADB sideload. Initial phone configuration was crashing and entering an endless loop. I tried few times, with wifi enabled, or offline mode, with entering google account details immediately, or not. It didn't matter. Wizard would loop screens. I think I've seen reports of other people succesfully installing FlameGApps with this LineageOS version, but apparently the fact I'm not rooting the phone somehow causes an issue.

With plethora of custom GApps variants I suppose it's not possible to expect them to be well tested like OpenGApps once was, so I thought maybe I can try a rom without GApps.

I wiped everything, and installed only LineageOS 19.1. It came without any app store. I think some years ago, it had some form of store installed. FDroid? I'm not sure. I tried installing Aurora Store via ADB but without success. It seems installing such apk requires root access which I technically don't need for any other purpose.

So now I'm puzzled, is root access needed in order to have either google apps or a custom app store?

 

[netra3441]

Hi, do I need to root my phone in order to have any app store available?

I installed TWRP 3.6.2 via Odin, left 'system unmodified' in TWRP and didn't root the phone, and installed LineageOS 19.1 + FlameGApps-12.1-basic through ADB sideload. Initial phone configuration was crashing and entering an endless loop. I tried few times, with wifi enabled, or offline mode, with entering google account details immediately, or not. It didn't matter. Wizard would loop screens. I think I've seen reports of other people succesfully installing FlameGApps with this LineageOS version, but apparently the fact I'm not rooting the phone somehow causes an issue.

With plethora of custom GApps variants I suppose it's not possible to expect them to be well tested like OpenGApps once was, so I thought maybe I can try a rom without GApps.

I wiped everything, and installed only LineageOS 19.1. It came without any app store. I think some years ago, it had some form of store installed. FDroid? I'm not sure. I tried installing Aurora Store via ADB but without success. It seems installing such apk requires root access which I technically don't need for any other purpose.

So now I'm puzzled, is root access needed in order to have either google apps or a custom app store?

Putting TWRP onto a smartphone actually does not work with Odin (Windows), it works actually only with Heimdall (Linux). But this is just my own experience. With Heimdall under Linux I was able to install TWRP on my Samsung S7, with Odin it did not worked at all.

Furthermore you dont need to root your smartphone to get access to apps stores.

You install first TWRP, use this one: https://forum.xda-developers.com/t/...p-for-galaxy-s7-herolte.3333770/post-87570457

Then, have started TWRP, wipe all storage, cache, Dalvik, and then install first the LineageOS 19.1, and after this (without reboot!!!) install GApps (I use NikGapps), wich fits LOS 19.1. Then reboot.

 

[sansei]

For me Odin on Windows installed TWRP just fine. TWRP 3.7 tar file is broken (too large) as some have already found, but it's not a big deal as 3.6.2 worked fine for me.

I also tried NikGApps from January with LOS 19.1 but it was continuously displaying App Store crash pop ups and ended up with the same loop in android config screens.

I began to think there may be some problem with latest LOS 19.1 package, and so I tried LOS 20.0 plus January omni package of NikGapps and finally initial configuration of Android went perfectly smooth. I even configured a Family Link protected account and it works as it should, so I'm extremely happy and would like to thank @Ivan_Meler for his hard work.

One last question to anyone who'd know the answer - how to install an app store (like Aurora Store) on top of pure LineageOS (no GApps) while not having root access? I found simple guides using adb commands how to do that, but they require root.

 

[netra3441]

@sansei

Thanks for your reply. Very interesting. I tried here everything to get Odin under Windows to work, and it does not, but Heimdall under Linux transmits the TWRP properly to the S7. Maybe the Windows 10 on my second PC feels, that I like Linux much more...

The actuall NikGApps (13) does not work good with LOS 19.1 on the S7. Myself I had taken NikGApps 12 for LOS 19.1, and this works together fine.

You dont need to root your smartphone for using Aurora Store.

I took the APK file for the Aurora store from Gitlab, see this link https://gitlab.com/AuroraOSS/AuroraStore

Same with Fdroid, that works also without rooting the smartphone.

Both, the Aurora and the Fdroid you can install within LOS 19.1 or 20.0 with their APK files, dont need to use ADB.

Both work properly for the moment. I am still testing, and will see, whether Aurora store works good with LOS 19.1, because if @Ivan_Meler cannot get to work the formatting of SDcards as internal memory in LOS 20.0, I will not use it.

But I also would like to say again a great thanks to @Ivan_Meler for his tremendous and fine work!!!

 

[Ivan_Meler]

February builds are out, nothing major just security updates are in them.
Do note that otas might show up in a few hours due to github caching of files so bear that in mind.

Huge thanks to everyone who supported this project, Donations help cover the build server cost and get me coffee.

18.1 and 17.1 will be out in a few days.

Enjoy new builds and stay safe.

 

[netra3441]

@fipsy

Because I am a very inquisitve person, today on my testing Samsung Galaxy S7 I installed Magisk (for rooting it) and then installed App2SD to try your hints.

On this testing S7 actually LOS 20.0 is installed.

App2SD crashes reproductable, when I try to format the SDcard as internal space for moving apps to it, it allows only to format one partition, and it fails always when try to format a second partition on this SDcard.

As I mentioned, on my daily S7 I run LOS 19.1. There it is no problem (and by its own, not with extra tool) to format the SDcard as internal and so enlarge the internal memory of the S7.

As a result, I assume very heavily, that in LOS 20.0 the complete technique with the SDcards is highly buggy.

I dont know and also cannot say, if this is a mistake of @Ivan_Meler - I assume, that it is a big bug inside Android 13 itsself, because I guess, that Ivan reads here, and if there would be a way to fix that Sdcard matter in LOS 20.0, he would have done so.

But, if you find the time, @Ivan_Meler please give us all a short response, if this is so or not.

So, also as an actual result, myself I must stay with LOS 19.1, because I need the SDcard be used as internal memory.

NOTE to the administration / moderation: please tell, if this discussion is unwanted in this thread, because I dont want to disturbe it. THX.