[Magisk][Module] Xperia Z2 / Z3 / Z3c Torch Boost v1.2 - Magisk

Here I present you my first Magisk module.
Description:
It boosts the torch on SONY Xperia Z2 / Z3 / Z3c devices by replacing system/etc/flashled_calc_parameters.cfg with a file that sets if_torch_vr = 500000 instead of just 25000, which is the default value by SONY.
By doing this, the flash LED is operated at 500 mA instead of just 25 mA.
In my experiences, 500 mA is a sweet spot which provides good brightness, but at the same time doesn't heat the LED too much. Still, I would advice you to not use the torch for more than about 5 minutes at a time. You use this module at your own risk. If you want to set a lower brightness, then you can edit system/etc/flashled_calc_parameters.cfg in the zip and change if_torch_vr to a value lower than 500000 before installing the module. Of course you can also use a higher value, but I wouldn't exceed 1000000 (this is also the value that SONY set in the line # Max current for Torch (uA) i_batt_max_torch of the flashled_calc_parameters.cfg file.)
Background:
The method I used was first described in a thread by @olokos which you can find here. For comparison: The extreme version you can download there (which is a flashable zip and not a Magisk module obviously) sets if_torch_vr to 1000000, which corresponds to 1000 mA or 1 A. As users reported, even at this setting the torch can be used for 5 minutes before temperature increases significantly, but I want to keep it safe by using just half of that value. If you want to know more about the user experience with different settings, I recommend you to read the above mentioned thread, as well as @antkalaitzakis96's thread, who uses the same method, which you can find here.
Compatibility:
This module should work on any SONY Xperia Z2 / Z3 / Z3c device running on Android 5.0 - 8.1.0, rooted with Magisk. I'm quite sure about this since I compared the flashled_calc_parameters.cfg files from Android 4.4 (SONY stock KitKat ROM) with Android 6.0.1 (SONY stock Marshmallow ROM) and also with Android 7.1.2 (LineageOS and Carbon Nougat ROMs) and the files were always completely identical! If you still want to check if the module will be compatible with your system before installing it, grab system/etc/flashled_calc_parameters.cfg from your system by using a root file explorer and then compare it with the flashled_calc_parameters.cfg file from the module zip file. The only difference between the two files should be the if_torch_vr line.
Enjoy!
Please leave some feedback if the module works for you.
Thanks:
Many thanks to @topjohnwu for the ingenious Magisk universal systemless interface and to @olokos for the initial torch boost mod.
Changelog:
v1.0 - Initial release
v1.1 - Updated to Magisk Module Template 1500
v1.2 - On Oct 26, 2020 @t.Lancer published an updated version in post #25 which works on newer Magisk versions. Thanks a lot!

Needed this. Thank you so much.

I love this module, I always wondered why my light was dinner than everyone else's. My light cuts through the darkness now!

Hi okij, I've used your module a bit reduced. Good work! Now there is the stock camera and I believe that the flash light so not in the camera settings is considered?The images are over-exposed in the close range. Once the module has been deactivated. Perhaps the setting can be automated to take pictures?

bussi2010 said:
Now there is the stock camera and I believe that the flash light so not in the camera settings is considered?The images are over-exposed in the close range. Once the module has been deactivated. Perhaps the setting can be automated to take pictures?
Click to expand...
Click to collapse
The module only changes if_torch_vr (comment line: "# LED If setting for Torch or video recording (uA)"), so it just affects the brightness when using the torch or when using the flash LED as a lamp when doing a video recording (which is good, because you have a brighter video lamp).
On the other hand, flash brightness is controlled by max_if_flash (comment line: "# Flash LED_If max current (uA)") which is set to 1500000 by default and not altered by the module. Therefore the module doesn't change anything when taking pictures.

Anybody having problems to install this module on Magisk 13.3? When I go to MODULES, select it and install, Magisk app freezes and I have to restart my phone. After that, I cannot open Magisk app anymore. I have to completely uinstall it and install again to be able to open the app again. On Magisk 12 it was working perfectly.

@maecar: The Problem is not Magisk 13.3, but Magisk Manager 5.1.0. There are numerous reports on the last few pages of the Magisk Support thread about the freezing issue. Until @topjohnwu fixes it, reverting to Magisk Manager 5.0.6 helps.

Mind making modulesl universal for Xperias...
Thanks... I use Z5!

Thanks for proper credit mate, nice work

olokos said:
Thanks for proper credit mate, nice work
Click to expand...
Click to collapse
I have to thank you and @AndroPlus for the initial MOD! I've been happily using it since about 2 years, but of course always had to re-apply it when updating a ROM. Now with Magisk, we can just "set and forget".

Is 500,000 secure?

SALL666PL said:
Is 500,000 secure?
Click to expand...
Click to collapse
IMHO it is.
This mod is known for about 2 1/2 years by now (long before my Magisk implementation) and I haven't read of any user who damaged his phone by using it.
Anyway, as I wrote in the OP, I would advice to not use the torch for more than about 5 minutes at a time, just to go safe.

okij said:
IMHO it is.
This mod is known for about 2 1/2 years by now (long before my Magisk implementation) and I haven't read of any user who damaged his phone by using it.
Anyway, as I wrote in the OP, I would advice to not use the torch for more than about 5 minutes at a time, just to go safe.
Click to expand...
Click to collapse
Thanks for the answer

Hello. This module didn't work for me. I tried to install it via Magisk and TWRP, but I get '' installation failed'' in Magsik and two red ''ERROR'' in TWRP. Do you know how to fix it?

DARKBUB said:
Hello. This module didn't work for me. I tried to install it via Magisk and TWRP, but I get '' installation failed'' in Magsik and two red ''ERROR'' in TWRP. Do you know how to fix it?
Click to expand...
Click to collapse
Since you don't provide any logs (installation or recovery) it's impossible to know for sure.
But, a likely issue is that this module is old and hasn't been updated for later versions of Magisk. If you're on Magisk v14+, this module won't install...

DARKBUB said:
Hello. This module didn't work for me. I tried to install it via Magisk and TWRP, but I get '' installation failed'' in Magsik and two red ''ERROR'' in TWRP. Do you know how to fix it?
Click to expand...
Click to collapse
Didgeridoohan said:
Since you don't provide any logs (installation or recovery) it's impossible to know for sure.
But, a likely issue is that this module is old and hasn't been updated for later versions of Magisk. If you're on Magisk v14+, this module won't install...
Click to expand...
Click to collapse
Yes, @Didgeridoohan is right, the module used an old template. I didn't notice that it doesn't install correctly anymore on newer Magisk versions because I only installed it once and then just updated Magisk to each newer version, which always kept the module installed.
I now updated the module to v1.1 which uses the current Magisk Module Template 1500. You can find the download in the updated OP.
Xperia Z2 / Z3 / Z3c Torch Boost v1.1 installed well on my Z3 Compact, running on Magisk v16.
Please leave a note if it works for you too now.

okij said:
Here I present you my first Magisk module.
Description:
It boosts the torch on SONY Xperia Z2 / Z3 / Z3c devices by replacing system/etc/flashled_calc_parameters.cfg with a file that sets if_torch_vr = 500000 instead of just 25000, which is the default value by SONY.
By doing this, the flash LED is operated at 500 mA instead of just 25 mA.
In my experiences, 500 mA is a sweet spot which provides good brightness, but at the same time doesn't heat the LED too much. Still, I would advice you to not use the torch for more than about 5 minutes at a time. You use this module at your own risk. If you want to set a lower brightness, then you can edit system/etc/flashled_calc_parameters.cfg in the zip and change if_torch_vr to a value lower than 500000 before installing the module. Of course you can also use a higher value, but I wouldn't exceed 1000000 (this is also the value that SONY set in the line # Max current for Torch (uA) i_batt_max_torch of the flashled_calc_parameters.cfg file.)
Background:
The method I used was first described in a thread by @olokos which you can find here. For comparison: The extreme version you can download there (which is a flashable zip and not a Magisk module obviously) sets if_torch_vr to 1000000, which corresponds to 1000 mA or 1 A. As users reported, even at this setting the torch can be used for 5 minutes before temperature increases significantly, but I want to keep it safe by using just half of that value. If you want to know more about the user experience with different settings, I recommend you to read the above mentioned thread, as well as @antkalaitzakis96's thread, who uses the same method, which you can find here.
Compatibility:
This module should work on any SONY Xperia Z2 / Z3 / Z3c device running on Android 5.0 - 8.1.0, rooted with Magisk. I'm quite sure about this since I compared the flashled_calc_parameters.cfg files from Android 4.4 (SONY stock KitKat ROM) with Android 6.0.1 (SONY stock Marshmallow ROM) and also with Android 7.1.2 (LineageOS and Carbon Nougat ROMs) and the files were always completely identical! If you still want to check if the module will be compatible with your system before installing it, grab system/etc/flashled_calc_parameters.cfg from your system by using a root file explorer and then compare it with the flashled_calc_parameters.cfg file from the module zip file. The only difference between the two files should be the if_torch_vr line.
Enjoy!
Please leave some feedback if the module works for you.
Thanks:
Many thanks to @topjohnwu for the ingenious Magisk universal systemless interface and to @olokos for the initial torch boost mod.
Changelog:
v1.0 - Initial release
v1.1 - Updated to Magisk Module Template 1500
Click to expand...
Click to collapse
Hey there. I've just replaced values in flashled_calc_parameters.cfg as it's written (25000 changed to 500000) using root explorer and then rebooted my phone. It worked our too! Btw, I'm running CarbonROM 8.1 rooted with SuperSU.

@okij Hi, could u make it working with Magisk V18 and newest template + Android 9.0? But i tried searching that file and it isnt here?

Bartekreaper said:
@okij Hi, could u make it working with Magisk V18 and newest template + Android 9.0? But i tried searching that file and it isnt here?
Click to expand...
Click to collapse
I didn't try Android 9 CarbonROM yet and most likely won't use it for the next couple of weeks since I need my Z3c as my daily driver and the ROM must be reasonably stable and bug-free.
Are you saying that flashled_calc_parameters.cfg isn't in folder system/etc/ anymore on Android 9?
The Torch Boost Magisk Module v1.1 still works fine with Magisk v18.0 under Android 8.1, so currently there's no need to update to the newest template.

okij said:
I didn't try Android 9 CarbonROM yet and most likely won't use it for the next couple of weeks since I need my Z3c as my daily driver and the ROM must be reasonably stable and bug-free.
Click to expand...
Click to collapse
I'm using the latest version of CarbonROM on my Z3C and the module works fine.

Related

[EXP] LineageOS 13 ufoFFICIAL (CVE-2019 April)

moved back to cm11-KitKat (@Adam77Root) vendors and HEX-edited libnvos.​source = p880DEV/aosp6 kernel + originalLG vendors + @alfsamsungpatches + mourta widevine
cons: blurred video thumbnails & QR&barcode not working due to CM11vendors.
Code:
[SIZE="1"]<manifest>
<remote name="bitbucket"
fetch="https://bitbucket.org/" />
<project name="LineageOS/android_external_busybox" path="external/busybox" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
<project name="lenzwagner/android_device_lge_p880" path="device/lge/p880" remote="github" revision="marshmallow" />
<project name="oF2pks/cmp880devkernel" path="kernel/lge/x3" remote="bitbucket" revision="Los13" />
<project name="oF2pks/proprietary_vendor_widevine" path="vendor/widevine" remote="bitbucket" revision="Vanir-N" />
<project path="vendor/lge" name="lenzwagner/proprietary_vendor_lge" revision="marshmallow" />
<remove-project name="LineageOS/android_packages_apps_CMUpdater" />
<remove-project name="LineageOS/android_packages_apps_Gello" />
</manifest>
[/SIZE]
Rom features:
-ScreenRecorder
-Xposed-able https://forum.xda-developers.com/showthread.php?t=3034811 (checked , GravityBox, InstallerOpt )
-kexec-ed (MultiROM)
-ButtonBacklight
-Widevine L3 (drm broadcast)
-WakelockBlocker
-AlarmBlocker
-f2fs Ver1.6 (wip)
-Reboot to Recovery
-(NO more keyboard BugFix & NoOverlayWarning & WebView & CM12audioFX-music.zip needed)
-MicroG-ified
-Bromite latest webView v76 with ad-blocking
Installation : wipe and flash in order
a)ROM https://androidfilehost.com/?fid=4349826312261650905
z)Xposed
z)Gapps ( or PlaystoreONLY and Google CalendarSync addon)
z)SuperSU & reboot =>2x auto-boot
Nota: MicroG & CalendarSync need specific in-built permissions to be granted.
Recommended app : SuperSu attached 2.82 twrp/zip + app install), Deltadroid's GApps, Greenify, BetterBatteryStat;
Kernel (cm/aosp7): take time to check with Kernel Adiutor(0.9.9.4 attached post#3), that swap meet you desires, disable KSM + rise dirty_writeback&expire for better battery
echo "0" > /sys/kernel/mm/ksm/run;
sysctl -w vm.dirty_writeback_centisecs=2000;
sysctl -w vm.dirty_expire_centisecs=1000;
sysctl -w vm.vfs_cache_pressure=50;
sysctl -w vm.swappiness=50;
GPL* aosp7 SELinux permissive
-check attached image from @ csk1jw 's aosp7-2016-12-07 post#2
-multirom : http://forum.xda-developers.com/showpost.php?p=67882937&postcount=21
-livedisplay/bandwith : http://forum.xda-developers.com/showpost.php?p=68213357&postcount=670
-perl/timeconst : http://review.cyanogenmod.org/#/c/104105/
Kernel GPL
microG compatible PlaystoreONLY (including Google ContactsSyncAdapter), to flash simultaneously with rom : https://www.androidfilehost.com/?fid=889764386195912422 ; once rebooted it will auto-update to latest version and survive OTA (thx @Deltadroid ); same for GoogleCalendarSyncAdapter.
Bromite latest webView v76 with ad-blocking, upgradable via F-Droid repo https://fdroid.bromite.org/fdroid/repo (Bromite 76 returns a 74/SamsungS9 webclient https://github.com/bromite/bromite/issues/156#issuecomment-445449741: Mozilla/5.0 [Linux; Android 8.0.0; SM-G960F] AppleWebKit/537.36 [KHTML, like Gecko] Chrome/74.0.3729.157 Mobile Safari/537.36); if v76 seems too selective, upgrade to latest Bromite without ad-blocking (v78).
Otherwise switch to official com.google.android.webview via regular install + 1 reboot.
Latest custom MicroG edition can be found here : https://forum.xda-developers.com/pr...arm64aosp-9-0-0r21-microg-ufofficial-t3878115
News
With LineageOS 13 you can :
-answer phone call straight with home button, whatever busy is android M
-launch Camera on sleeping phone with 2x power button
-flash LineageOS' addonsu https://download.lineageos.org/extras
-manage Doze settings directly: https://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
-lightweight p880 with SuperSu Recently
...
Video Calling ??? Any update???
Salman Al-Badgail said:
Video Calling ??? Any update???
Click to expand...
Click to collapse
You tell me... Best will be to track Euphoria 5 to understand it: I tried once but didn't see any thing related; vendor in los13 are same origin (alfsamsung) than Euphoria 5 but they are hacked to fit Marshmallow new policies : http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper
To get all things better we could move to further modif like https://github.com/Unlegacy-Android/proprietary_vendor_nvidia/commits/aosp-6.0/grouper
I am kinda confused, is this ROM has aosp6 kernel or the newest in aosp7?
New build CVE-2017 June
New build : CVE-2017 June https://www.androidfilehost.com/?fid=817550096634778703
With @Deltadroid packages : no need to reflash Webview\Gapps\CalendarSync on upgrade, only [Rom+CM12audioFX-music.zip(+Xposed+su)].
b886b said:
I am kinda confused, is this ROM has aosp6 kernel or the newest in aosp7?
Click to expand...
Click to collapse
Kernel aosp7 2016-12-07 GPL* aosp7 SELinux permissive
-check attached image from @ csk1jw 's aosp7-2016-12-07 post#2
-multirom : http://forum.xda-developers.com/showpost.php?p=67882937&postcount=21
-livedisplay/bandwith : http://forum.xda-developers.com/showpost.php?p=68213357&postcount=670
-perl/timeconst : http://review.cyanogenmod.org/#/c/104105/
Thanks for the work she still invests into this device
Just to make sure I've read this right:
microG is already built-in?
It's MultiROM compatible, but MultiROM is not a requirement? (I rarely boot, so for me MultiROM would be overkill – no need keeping everything twice)
NO GApps are built-in (so one can keep it Google-free)?
As it's LOS based, no Superuser capabilities are built-in (but must be flashed afterwards if wanted)?
If I'm right with that, anyone tried it with Magisk? I'm considering to switch from "hard SU" to systemless root with Magisk (and what better time to do so then with a fresh install?), but if someone has experience with that (especially on this ROM), feedback would be very welcome!
oF2pks said:
Recommended app : SuperSu(2.79 twrp/flash + app install)
Click to expand...
Click to collapse
For me it's complicated.
You recommend the supers 2.79, and give the link that directs to version 2.82.
Did you mean recommendation supersu stable?
ze7zez said:
For me it's complicated.
You recommend the supers 2.79, and give the link that directs to version 2.82.
Did you mean recommendation supersu stable?
Click to expand...
Click to collapse
Stable 2.78 works fine on both primary and secondary rom, I'm not 100% sure but 2.8x focus on N and O new security stuff, so I didn't try them already, but some beta can bootloop on secondary install; anyway, once flashed, you can still upgrade app 2.7x live to latest and reboot.
Also you can patch LOS with su addons https://download.lineageos.org/extras .
( @svv3000 , Post #2 updated with minimal PlaystoreONLY.zip for microG + paid app.)
oF2pks said:
Stable 2.78 works fine on both primary and secondary rom, I'm not 100% sure but 2.8x focus on N and O new security stuff, so I didn't try them already, but some beta can bootloop on secondary install; anyway, once flashed, you can still upgrade app 2.7x live to latest and reboot.
Also you can patch LOS with su addons https://download.lineageos.org/extras .
( @svv3000 , Post #2 updated with minimal PlaystoreONLY.zip for microG + paid app.)
Click to expand...
Click to collapse
Thanks, @oF2pks! PlaystoreONLY is not necessary. I have tried a X-los13-201706-ufoHYBRID-p880.zip and fully satisfied. Many thanks for you one more time!
SuperSU 2.82 works fine and stable, by the way, on this ROM.
MicroG + patched Playstore also work. I had a some troubles with authorization in Google services (as result, MapsAPI was dead too). After success with authorization I had a problem with access to the Playstore content (and maps). But, a little bit of shamanistic dances with a tambourine... and all is fine.
GPS is OK. Camera (photo and video) is OK. Calls (except video calls - haven't try) is very good, but a small delay with the output to the screen is present. No freeze and reboot. Very good battery using (0.5-0.8% per hour with my very old battery, when I don't touch a phone)! Time to time a slight lethargy is happened, especially when using one of number opened apps and receive an incoming call.
But, in total - it's best ROM for P880 of all tested (original, Euphoria, AOSP, CM...)
Izzysoft said:
Thanks, @oF2pks! Flashing Gapps or Nougat is not an issue for me (I don't want either: I much more prefer microG and XPosed). So I'm waiting for your update of post #1 then to know whether to update TWRP and to what. If a special formatting is required (or another strongly discouraged), please point that out as well. Currently I'm running your LP build, with /system formatted as ext4.
What's also not clear to me is what you mean by "MicroG & CalendarSync need specific in-built permissions to be granted": CalendarSync (according to the list there) seems only relevant with Gapps, so I can ignore that. But what is expected to run for those "special grants" – or does your image already take care for that with regards to microG, as you list "MicroG-ified" with the "Rom features"? And by "MictoG-ified" you mean GmsCore incl. signature-spoofing and GsfProxy – so one would just need to add desired backends for UnifiedNlp?
And while you recommend SuperSu: Any hint on Magisk/MagiskSU? If that ROM comes without internal SU, I thought to give systemless-root a try (not that I had any issues with the other, no apps in use that could fail because of SafetyNet or the like – but AFAIK MagiskSU is completely open-source )
Oh: And does your TWRP build include MultiROM? Maybe I misunderstood what you wrote in this regard; did you mean: "Flash this TWRP with MultiROM, and then flash the MM ROM in parallel to your current LP to try it out"? I'm a bit confused now
Click to expand...
Click to collapse
-(Google)CalendarSync needs Calendar permission (check also native Calendar & CalendarStorage permissions)
-Spoof package Signature in all permissions section needs: on for microG services app. (this is the buit-in secure Marvin ROM patch).
-Latest microG app 2.4.9x needs registration activated in microG_app/menu for official Playstore (?) and could needs one reboot.
SuperSU works fine and always has real better efficient security checks (thx Chainfire).
Warning: on all MM &N, if you have wifi extender on same general router, switching from extender wep, to general router wep won't allow you to come back to extender connection (infinite waiting). I checked that on both p880 & Asus_tf700 and I'm 99% sure it's not kernel (works ok with same kernel on L with both p880 & tf700, or other modern devices with MM or N), neither rom or device tree: probable missing vendor location normalization (check post#5), since MM new policy. Also audio/music is not as cleared than my latest cm12.1
The working trick is to use multirom: forget wifi router on MM &N, reboot to L KK or even lgJB and switch twice, then reboot to MM and open wifi extender wep.
Latest multirom : https://www.androidfilehost.com/?w=files&flid=146943
One more question. I didn't find a "performance" option in "settings", like on CM13. And in statistics of BetterBattery I saw 1500 as maximum frequency of CPU. Is it possible to rise up a frequency to 1700 on this ROM and how (by system settings, not by App's)?
As this wasn't answered yet: If I got that right, other than CM, LOS does NOT ship with any superuser built-in. So did anyone try the ROM with Magisk and MagiskSU? For one, that'd be a FOSS solution, and then there are several nice features it offers. So my thoughts were whether it would be worth a try when "starting from the scratch" anyway.
oF2pks said:
Nota: MicroG & CalendarSync need specific in-built permissions to be granted.
Click to expand...
Click to collapse
Thanks for updating the initial post! Could you include some details on the quoted line, maybe in the "spoiler section"? Especially for the microG part. Again: I understand correctly that "MicroG-ified" just refers to the signature patch, but one would need to install the framework separately? Must be so as otherwise one couldn't flash Gapps, I guess
And one more question: When you finally update the first post with the TWRP stuff you've planned for it (especially which TWRP version [link] you recommend), I'm still confused on the MultiROM part. I've never used that. So: Does your TWRP build already include MultiROM? If not, in which step must MultiROM [link] be flashed? And if I have your LP build running before I start the procedure on MM, can I then simply install this LOS build as second ROM, keeping LP as first?
(Sorry for delay: broken computer os)
svv3000 said:
One more question. I didn't find a "performance" option in "settings", like on CM13. And in statistics of BetterBattery I saw 1500 as maximum frequency of CPU. Is it possible to rise up a frequency to 1700 on this ROM and how (by system settings, not by App's)?
Click to expand...
Click to collapse
No our aosp/cm kernel does not support, personally I even go for ondemand governor.
Everything can be set with KernelAdiutor or similar control/performance app.
Izzysoft said:
...Again: I understand correctly that "MicroG-ified" just refers to the signature patch, but one would need to install the framework separately? Must be so as otherwise one couldn't flash Gapps, I guess
And one more question: When you finally update the first post with the TWRP stuff you've planned for it (especially which TWRP version [link] you recommend), I'm still confused on the MultiROM part. I've never used that. So: Does your TWRP build already include MultiROM? If not, in which step must MultiROM [link] be flashed? And if I have your LP build running before I start the procedure on MM, can I then simply install this LOS build as second ROM, keeping LP as first?
Click to expand...
Click to collapse
I use microG+Playstore (Cal_sync)+embedded email and NO GoogleSearch or others; if you need Gmail.app, imho, it's better to use normal Gapp for battery and performance.
Concerning Multirom you can use latest
twrp for all flash operations : https://www.androidfilehost.com/?fid=529152257862714405
multirom.zip which patch first rom boot.img with menu selection (& all adb operations) https://www.androidfilehost.com/?fid=817550096634757304
All my kernels are kexeced https://en.wikipedia.org/wiki/Kexec
You can use Cyospak on top of aosp7 (but primary rom only) and get all your roms (KK L MM) on secondary or even use a boot.img only on primary . I usually use primary for rom testing because flashing via twrp is much faster on primary vs 2nd. Then when I need access to 2nd, I just flash multirom.zip ; once done you have 3 diff linux : twrp + multirom stand-by + rom (+all 2nd). It can be useful to keep secure f2fs/data (wip) on one rom only.
Try to flash rom with no more update on 2nd. I will update more explanation...
oF2pks said:
(Sorry for delay: broken computer os)
No our aosp/cm kernel does not support, personally I even go for ondemand governor.
Everything can be set with KernelAdiutor or similar control/performance app.
Click to expand...
Click to collapse
Thanks for your reply. I think your opinion about customization of the performance (and others too) is correct. Of course, KernelAdiutor is quite convenient to use and will satisfy most of the needs in the configuration. Never had problems with using it.
hi guys, noob here
just installed the rom, and now ive lost root access and dunno how to boot to my recovery (twrp 3)
i used third party apps to boot to twrp but now they request for root access which i dont have
i dunno the key combination for accessing the recovery
so now i want my root access back and a way to access my recovery
thx so much guys really need ur help
Izzysoft said:
As this wasn't answered yet: If I got that right, other than CM, LOS does NOT ship with any superuser built-in. So did anyone try the ROM with Magisk and MagiskSU? For one, that'd be a FOSS solution, and then there are several nice features it offers.
Click to expand...
Click to collapse
Magisk is really useful for modern devices to provide SafetyNet : using it with Oneplus5, Google always fight to broke it every week (AndroidPay) and when you loose Magisk, you loose all your setups; thus, imho ,SuperSu provides a much stable & secure with old p880 regular/system. But you should try installing csk1jw's ('pure') AOSP as primary rom, without Gapps, and with Magisk + MicroGNanomod https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Then flash kexeced Cyospak to access Multirom with los13 & others as secondary. I didn't have much time, but I will try this soon; for now I have los13 on primary due to fastest flash time (vs 2nd slots).
Will update los13 on next August Cve upgrade.
4xhd noob said:
hi guys, noob here
just installed the rom, and now ive lost root access and dunno how to boot to my recovery (twrp 3)
i used third party apps to boot to twrp but now they request for root access which i dont have
i dunno the key combination for accessing the recovery
so now i want my root access back and a way to access my recovery
thx so much guys really need ur help
Click to expand...
Click to collapse
Fist, if you were using SuperSu before, try easy install back SuperSu.apk only ( and check binaries).
Otherwise
-PowerOff : press [Volume Down & Power Button] until logo
or (check Developer Options)
-USB/adb : adb shell setup-recovery + adb reboot
BTW , reboot to recovery is included via AdvancedReboot option , (check Developer Options)
Izzysoft said:
What's also not clear to me is what you mean by "MicroG & CalendarSync need specific in-built permissions to be granted": CalendarSync (according to the list there) seems only relevant with Gapps, so I can ignore that. But what is expected to run for those "special grants" – or does your image already take care for that with regards to microG, as you list "MicroG-ified" with the "Rom features"? And by "MictoG-ified" you mean GmsCore incl. signature-spoofing and GsfProxy – so one would just need to add desired backends for UnifiedNlp?
Click to expand...
Click to collapse
Coming with MM (& N), are dynamic permissions, and so is build MicroG: if you don't grant permission explicitly, security won't allow signature faking; and CalendarSync needs Calendar permission. I will post attached screenshot very soon.
Concerning Multirom, I will update the dedicated thread with more info, but the whole thing is open source (from the beginning) : https://github.com/Tasssadar/multirom/wiki/Introduction
svv3000 said:
But, in total - it's best ROM for P880 of all tested (original, Euphoria, AOSP, CM...)
Click to expand...
Click to collapse
I agree, this ROM is by far the best one for this old but (theorically at least) still capable device.
Thanks a lot oF2pks
David

[Magisk Modules][A1]Prop Tweaks, Softkey Enabler, Lens[2.0.2][31/01/18]

Disclaimer: I am not responsible for ANY damage done to your phone
Now that we have that out of the way, I present to you my Magisk module for our device, what it does:
Magisk Night Light + Prop Mod:
* Enables Night light (Thanks to @jimmy123322 for the framework-res apk) (Only in 7.1.2, removed in 8.0)
* Adds EIS to prop file
* Enables slow motion in GCAM (Google Camera, thanks to @simonsmh) [Not working at the moment in oreo]
* Disables horrible noise cancellation during video cam recording
* Forces HAL 3
* Pixel Blue Accent (Removed for now until it can be added to our apk
* Pixel animations (when soft key enabler is installed and enabled) [Not yet available, working on it]
* Pixel (2016) Media sounds (ringtones, Notification and alarms)
Soft Key Enabler (Nougat ONLY!)
* Disables HW Keys
* Disables HW Key backlight
* Enables on screen soft keys
All this without breaking SafteyNet and without touching system partition (means OTA will work fine and you can always disable the module if you don't want it anymore without re-flashing system)
I made this because I was sick of restoring my system for OTA and for mess ups I did on the device.
I may add more tweaks, feel free to post suggestion such as useful prop tweaks or other similar things.
Enjoy!
Requirements:
Magisk 14.4+ for 1.4
Magisk 15.0+ for 2.0
Instructions:
Use magisk and add module in magisk
Download:
See Downloads Tab
XDA:DevDB Information
[Magisk Modules][A1]Prop Tweaks, Softkey Enabler, Lens[2.0.2][31/01/18], Tool/Utility for the Xiaomi Mi A1
Contributors
sooti, simonsmh, dr.bathman, Chris_Cheekyz
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2018-01-21
Created 2017-11-09
Last Updated 2018-08-22
Reserved
Change Log:
31/01/18:
* Fixed missing props
30/01/18:
* Fixed missing prop enabler from config file, all prop changes should work now
21/01/18:
* Update to Magisk template 1500
* Updated zip for oreo
* Removed night mode
* Removed pixel blue accent for now
* Added pixel stock audio sounds
26/11/17:
A1 Tweak Module V1.4 (both changes thanks to @Chris_Cheekyz)
* Added pixel blue accent
* Pixel animations (when softkey enabler is installed and enabled)
19/11/17:
A1 Tweak Module V1.3
* Removed Google Lens and unlimited photos tweak, since people don't want the unlimited photos and I have no way of sepperating the two. the seperate tweak is here
15/11/17:
A1 Tweak Module V1.2
* Added google photos unlimited storage in full resolution from Pixel
* Added Google Lens feature from Pixel
Thanks to @dr.bathman for the files
His original module Here
Reserved
RESERVED
Cool, will see
Btw, can i see the screenshot please
harizinside said:
Cool, will see
Btw, can i see the screenshot please
Click to expand...
Click to collapse
Screenshot of what? The night mode? I attached it
Just what we needed!
Do I need Magisk 14? Because when I try to flash it says migisk data not setup correctly please install Magisk 14. But I've heard that I shouldn't do that. So now what?
DaveCZ said:
Do I need Magisk 14? Because when I try to flash it says migisk data not setup correctly please install Magisk 14. But I've heard that I shouldn't do that. So now what?
Click to expand...
Click to collapse
Yes, magisk 14.4 and higher
sooti said:
Yes, magisk 14.4 and higher
Click to expand...
Click to collapse
Done, thanks. But is it normal that in the GCAM is the slow motion laggy?
DaveCZ said:
Done, thanks. But is it normal that in the GCAM is the slow motion laggy?
Click to expand...
Click to collapse
Not sure what you mean... I use GCamMod from oneplus 3 and no lag, just low resolution of 720p. But works great other then that
Good Job!! Can't wait to try it out.
I also suggest a version of this module that enables the nav bar. (Separate, since the HW keys still stay active without tweaks which is annoying)
JaadiBooti said:
Good Job!! Can't wait to try it out.
I also suggest a version of this module that enables the nav bar. (Separate, since the HW keys still stay active without tweaks which is annoying)
Click to expand...
Click to collapse
Ya i thought about that and will probably do that, i simply didn't do it because not everyone wants it, i'll make a separate one and upload it.
Nice one, I was using cf.lumen as a replacement for the night light until now.
Good idea to keep the nav bar out of this, as a lot of people would probably prefer using the dedicated hardware buttons in the chin (me inculded). I guess releasing it as a separate module would be the best idea.
Whats the best method to root without loosing OTA updates?
nitroax said:
Whats the best method to root without loosing OTA updates?
Click to expand...
Click to collapse
Use magisk 14.4 and don't touch anything in the system partition and you should be fine
sooti said:
Use magisk 14.4 and don't touch anything in the system partition and you should be fine
Click to expand...
Click to collapse
How to install magisk without touching system?
Fastboot boot twrp? Then flashing magisk? Is that right way? Thanks..
Vihru said:
How to install magisk without touching system?
Fastboot boot twrp? Then flashing magisk? Is that right way? Thanks..
Click to expand...
Click to collapse
First unlock bootloader
(Oem unlock trough setting and enable usb debug)
Reboot to bootloader and type
Fastboot oem unlock
Fastboot reboot
Reboot to bootloader again and type
Fastboot boot xxx.img (xxx is the name of the .img)
Install magisk and reboot
Uninstall magisk app and install magisk manager
Note: it can happen that you don't have any magisk app...then just install the manager, if into the manager it's all green you're fine; else if magisk isn't installed correctly, remove the manager, reflash magisk trough twrp and reinstall the manager.
Getting a installation error. Have magisk 14.5 installed with the latest manager app. I am able to install other modules. Strange.
sednafx said:
Getting a installation error. Have magisk 14.5 installed with the latest manager app. I am able to install other modules. Strange.
Click to expand...
Click to collapse
Installed fine on magisk 14.4, and the mods are working well. @sooti, thanks for this Magisk module.

Android P 9.0 for s6e+ BETA

To go into deeper detail on the ROM, I used Lineage 16.0 20180901 s6 build modified for the s6 found here:
https://forum.xda-developers.com/ga...20x-5x-nexusos-9-0-samsung-galaxy-s6-t3843199
It was also based on NexusOS kernel that has been modified, so a big shout out to Team Nexus for the kernel and rom, and to @lukasb06 for porting it to s6.
The original kernel was by Team Nexus for s6 and s6e
Kernel Features;
v2.0: first support Pie on s6e+ and n5
change log:
support N5-s6e+ (ready for daily usage)
bug: BT, GPS, NFC
deep sleep fixed, init.d support, dyninteractive and a lot of kernel code changed.
the kernel can be found at :
https://github.com/slaminger/android_kernel_samsung_exynos7420
**I have made some modifications, added a shim, added code to the init.rc to disable p2p wifi. Moving forward the modifications to the kernel will be done by myself.
Please read and follow the instructions :
New zip uploaded for November. Each month has its own folder
This is not fully functional yet but it is close, no Bluetooth, no NFC. the two buttons next to home don't work yet(a couple of temporary solutions below)
BACK UP YOUR CURRENT ROM! especially efs. Some people have ril issues, I noticed my imei changed. A quick efs restore fixed it and my sim worked again.
The home button can be set to double tap for recent apps and use opera browser for compensation of no back button as they have their own, or download back button from play store to add floating buttons to screen. Some versions have buttons pre installed.
I can get bluetooth not to crash, but it doesn't connect.
Wifi Hotspot not working.
Now that the bad is out of the way.
Install Instructions Below:
The call audio and WiFi works, camera works(lower res for video to 1080), magisk is working but apk requires manual apk install, audio works, headphones, video, gapps, everything I have tried besides the above is OK.
The install is a process, first flash the ROM, then the pie fix, then no NFC, and then flash the boot.
Img and start the ROM. set your WiFi and take a look around, give it a moment to run). After first boot, reboot to twrp and flash gapps. If you do it all at once gapps crash sometimes. Once you have this all set up and good to go then add magisk.
9.0SeptSecurity is a different version from the august security not just in the sense that the security patch is different, but also the august build is N920 where the September build is G920F. One is from a note one from s6. It is possible one might resolve a bug that is in the other for your device, i am honestly not sure. different people report different bugs on the same device. If bluetooth does happen to be in one of the zips it will likely crash a lot. remove it via twrp by mounting system and then going to system/app and delete the bluetooth and bluetoothmidi folders.
The reason for lowering rear camera to 1080p for video is that it gets buggy at the 4k default.
A big thank you to NexusOS and LineageOS for their 9.0 lineage 16.0 s6 ROM which I used as a base to port this to our device!
i would also like to thank @topjohnwu for Magisk.
And @MirzaAwais for the Pie fix zip
Link for zenltecan:
https://mega.nz/#F!vKZ2UIzZ!BRrSiAxmz2DOjGmnkl26uA
Link for zenlte:
https://mega.nz/#F!Peo0FAjL!_eknpYZl8Ih-x2Hr9vSysg
Link for common files to be flashed on every device:
https://mega.nz/#F!yewjES6B!71Yrg0zaIzAys0wjxvMOzA
Link for Noblelte:
https://mega.nz/#F!DH4HSS7I!0MusytbbTqTsnWB6XzR2Bg
Modified RIL fix to disable P2P WIFI (connect droid to droid without internet, this saves battery life)
https://mega.nz/#F!OOwBmCJb!n7zaoutCLw74vsVTmXUjvg
Link for zenltetmo:
https://mega.nz/#F!7D5xhQab!WgqIleQph7goPHVVSVo1lA
New Multirom for note 5 and s6e+
https://mega.nz/#F!es4wnQjI!sCZqFZiJbhQr1BtEKYKzYw
It's a bit slow for the first little bit while setting up and whatnot, but once you get everything running it works fine. You can use kernel auditor if you find your battery is dying a little too fast.
I am VERY open to suggestions and or help with this, as it is my goal to fix the bugs and have a fully working 9.0 for our device. The buttons are a priority for me.
To briefly summarize: you sacrifice the back button, pages button, and Bluetooth and get 9.0. Everything else works. I've got viper4android going via magisk, the audio fx work. The ROM has a LOUD volume. So if you like music, enjoy. The back button/page has a work around(most apps have a back button), and you can get an app from play store called back button which gives you the home, back and recent button as tiny floating screen icons also, in the meantime. so just bluetooth really. Use modified cam perm boot shim.img
Enjoy
I removed Bluetooth from the ROM intentionally because it crashed constantly and was hard to disable for people unfamiliar with twrp. No NFC.
The camera has been modified to address pipeline errors that caused it to not work in other builds, it is now fully functional up to 1080p video.
The advanced menu seems to be working fine.
Magisk successfully installed with the following modules tested: Viper4Android, Sony Framework, Sony Music, Audio Modification Library, Sys Config Patcher.
SUBSTRATUM DOES NOT WORK ON ANDROID PIE. This is because google does not want us using OMS for custom themes. they disabled it on purpose. i do not believe systemless substratum will be possible moving forward on any device running pie. atleast not at the time being.
**** Solved** see next post** Netflix not currently working, I googled and found many users on pie are having issues.
Superuser works also, but magisk has modules.
More details will be coming.
All gapps 9.0 working on sm-g928
W8, I used the full aroma package and installed everything. However pixel launcher with assistant in the search bar will not work if you install the new Google webview. The built in Google now launcher will work, and I have tried Nova launcher prime. Keep in mind the more gapps you install the slower your device can get. it is best to only install what you need. i installed everything just to see what worked. but i noticed my phone was slower after a while.
The camera is only confirmed working on g928w8 Canadian, g928g, g928f international/american, note 5 N 920variants. Others have reported bugs.
Netflix Netflix-6.13.0_build_29940.apk confirmed working, both cast and watching videos.
Congrats! Will this rom work on Note 5 N920C too ?
ThePscho said:
Congrats! Will this rom work on Note 5 N920C too ?
Click to expand...
Click to collapse
It could be made to work yes, there is an alpha note5 ROM already on xda
so i flashed the ROM. very stable i can say, but unfortunately the camera still does not work. i was able to install google camera mod via adb but still the same problem. it does not crash tho. it's just not starting
Dread2000 said:
so i flashed the ROM. very stable i can say, but unfortunately the camera still does not work. i was able to install google camera mod via adb but still the same problem. it does not crash tho. it's just not starting
Click to expand...
Click to collapse
Suggestion: if you un-compress the rom(s) and do a search for *camera or camera* does it return any results. I suggest you compare it to a working version and determine what is missing in the system/ system/app and system/priv-app folder(s) once you determine what is missing then just bring those changes over to your folders
AFFAFXP said:
Suggestion: if you un-compress the rom(s) and do a search for *camera or camera* does it return any results. I suggest you compare it to a working version and determine what is missing in the system/ system/app and system/priv-app folder(s) once you determine what is missing then just bring those changes over to your folders
Click to expand...
Click to collapse
i will give a try but i don't think i'm going to make it
AFFAFXP said:
Suggestion: if you un-compress the rom(s) and do a search for *camera or camera* does it return any results. I suggest you compare it to a working version and determine what is missing in the system/ system/app and system/priv-app folder(s) once you determine what is missing then just bring those changes over to your folders
Click to expand...
Click to collapse
My camera works on SM-G928W8
Dread2000 said:
so i flashed the ROM. very stable i can say, but unfortunately the camera still does not work. i was able to install google camera mod via adb but still the same problem. it does not crash tho. it's just not starting
Click to expand...
Click to collapse
Let me try n rebuild it real quick for your device, its the same phone mine is just zenltecan not zenlte
Its uploading now, I used the same zip from my phone and changed the updater script to zenlte
OK its done, I named it v2, same link as first post
@godkingofcanada Hi, I've got same problem with this rom as I had with Oreo rom before. My WiFi MAC Address is 02:00:00:00:00:00 and it doesn't turn on. Have I to do something more than installing rom and all fixes with it ? I can provide logcat if it would do. Also after clean installation there was no bootanimation and no wallpaper. Just black screen and that's all. Hope to see quick reply. Cheers
aerzjee said:
@godkingofcanada Hi, I've got same problem with this rom as I had with Oreo rom before. My WiFi MAC Address is 02:00:00:00:00:00 and it doesn't turn on. Have I to do something more than installing rom and all fixes with it ? I can provide logcat if it would do. Also after clean installation there was no bootanimation and no wallpaper. Just black screen and that's all. Hope to see quick reply. Cheers
Click to expand...
Click to collapse
What variant of s6e+ do you have? And sure let me peek at the logcat, I have never had it boot to black screen, normally the boot only fails if you did not flash the boot.img. the pie kl500.zip fixes the Wi-Fi, the other zip disables NFC, did you flash both ?
godkingofcanada said:
What variant of s6e+ do you have? And sure let me peek at the logcat, I have never had it boot to black screen, normally the boot only fails if you did not flash the boot.img
Click to expand...
Click to collapse
I did everything from first post apart from installing gapps. Let me grab it, and I will upload here. Thanks for fast reply
aerzjee said:
I did everything from first post apart from installing gapps. Let me grab it, and I will upload here. Thanks for fast reply
Click to expand...
Click to collapse
You are welcome. Also, what country is your phone manufactured in?
godkingofcanada said:
You are welcome. Also, what country is your phone manufactured in?
Click to expand...
Click to collapse
It's G928F variant, I don't have phone box with me, so can't check on it. I bought it here in Poland.
godkingofcanada said:
What variant of s6e+ do you have? And sure let me peek at the logcat, I have never had it boot to black screen, normally the boot only fails if you did not flash the boot.img. the pie kl500.zip fixes the Wi-Fi, the other zip disables NFC, did you flash both ?
Click to expand...
Click to collapse
Logcat took via built-in SysLog app. Hope there's something
aerzjee said:
It's G928F variant, I don't have phone box with me, so can't check on it. I bought it here in Poland.
Click to expand...
Click to collapse
Give me a moment to look, you have the international variant but I don't think there's any hardware differences. I need to verify
godkingofcanada said:
Give me a moment to look, you have the international variant but I don't think there's any hardware differences. I need to verify
Click to expand...
Click to collapse
Also, the phone is identifying itself as SM-N920X is settings, same this was happening with Oreo ROMs. I'll keep this page refreshed once in a while, I hope that you will find something. I've updated bootloader, but I'm not sure if it changes something. Thanks for fast replies

[DISCONTINUED][ROM][T715] Formula Performante [6/03/2019][CRH1]

Welcome to Formula Performante...
Hey there fellow Tab S2 user! So... your wondering what this ROM is huh? This ROM is the fruit of my labour, after many many hours of work, research etc. This ROM is genuinely the lightest stock based ROM, in all of the Tab S2 ROM era. The ROM weighs just 675 MB, its RAM usage only 1.0-1.1 GB and its fluidity and speed is unmatched, since any and all modifications have been directed towards only enhancing performance and battery life. So, what does this ROM pack? Here's a list:
Features:
1. Extraordinarily Light Operating System with a very deep debloat
2. Google Apps Removed while still maintaining SafetyNet
3. Latest @engine95 Kernel with Enforcing and far more superior RAM Management
4. Updated SoundAlive with slightly modified Volume Increases
5. Every App has been replaced by the lightest equivalent (For e.g, for the Music App, I checked RAM management of Google Play Music and Eleven Music (Cyangogenmod) and found that Eleven Music used 50 MB of RAM lesser than GPM, so I used that. This should give you an idea of how much research and time it took to find the lightest variant of most stock apps)
6. S8 Camera UI with FHD 60FPS,Tracking AF and Standard Improved Autofocus. Other than these improvements, the camera app was debloated as well, and any useless modes were terminated and rooted out.
7. Completely De-knoxed
8. Magisk Pre-Installed
9. Most Extra RAM and Battery Consuming features have been terminated
10. Device Maintenance switched out for Files GO and SystemUI Tuner (To view battery stats, pull down quick settings (notification panel), click on the top right corner (three dots),button order and place the battery icon and storage icon into the quick settings panel.
11. Mtweaks 13.0 Installed for better kernel control, including GPU control.
12. AOSP Sounds instead of Sammy Sounds.
13. Few build prop tweaks for minor performance gains.
Bugs:
Music will crash on first boot
Do not update Magisk, its 17.1 and has to stay that way to work! New versions of Magisk aren't compatible with out current kernel and will just kill boot!
INSTALL INSTRUCTIONS
1. Wipe DATA,SYSTEM,DALVIK CACHE and CACHE
2. Flash The ROM
3. Realize you enjoy the ROM and hit Thanks :good:
-- NOTE: This ROM is heavily debloated. It's weight alone should classify how much has been removed. Please check comments before installing to see if theres any problems.
Download Link: https://drive.google.com/open?id=1XedlWrDuaQGD48ercE-dWLWcFdCq41Cf
Kernel Source: https://github.com/engine95/Exynos-5433-S2-2DRG2
Screenshots will be uploaded later:
Thanks. Just installed it.
First impressions:
Starting with "Music has stopped". Oops.
Upgrading Magisk Manager results in error, because Magisk version lower than v18.0 not supported. You should mention this. So no updated version of Magisk possible here (from 17.1 to 18.1)? Oops
its fast, really fast. Wow
more to follow, will just reinstall everything to get Magisk to work.
...
ThaiDai said:
Thanks. Just installed it.
First impressions:
Starting with "Music has stopped". Oops.
Upgrading Magisk Manager results in error, because Magisk version lower than v18.0 not supported. You should mention this. So no updated version of Magisk possible here (from 17.1 to 18.1)? Oops
its fast, really fast. Wow
more to follow, will just reinstall everything to get Magisk to work.
...
Click to expand...
Click to collapse
Oh yeah, thanks for reminder. OP updated
You should explain why it isn't possible to update to the newest version of Magisk. It isn't so nice installing a new ROM with an old version of root and no chance to fix this.
Update:
Removed the ROM. Titanium Backup crashes immediately. So unusable for me.
ThaiDai said:
You should explain why it isn't possible to update to the newest version of Magisk. It isn't so nice installing a new ROM with an old version of root and no chance to fix this.
Update:
Removed the ROM. Titanium Backup crashes immediately. So unusable for me.
Click to expand...
Click to collapse
He explained why...upgraded versions of magisk are not compatible with the custom kernel he used inside the rom. Possibly if the kernel gets some updates we'll get magisk updated support too.
Btw idk why Titanium crashes...will test tonight if happens with me too. Dumb tought: maybe it uses some gapp related services to work and then it crashes because thei're missing? That sound stupid i know...
For the Dev:
It's possible to install gapps (bare minimum as play store and play services) or MicroGapps in this rom? Just in case i wont rely on Fdroid or other thirdy part stores. Thank you
Giuskiller said:
He explained why...upgraded versions of magisk are not compatible with the custom kernel he used inside the rom. Possibly if the kernel gets some updates we'll get magisk updated support too.
Btw idk why Titanium crashes...will test tonight if happens with me too. Dumb tought: maybe it uses some gapp related services to work and then it crashes because thei're missing? That sound stupid i know...
For the Dev:
It's possible to install gapps (bare minimum as play store and play services) or MicroGapps in this rom? Just in case i wont rely on Fdroid or other thirdy part stores. Thank you
Click to expand...
Click to collapse
Ok so Titanium backup, is related with the kernel being enforcing. Titanium require permissive which I didn't release due to the many security holes it usually poses. Oh and about Gapps, don't flash.
Updated Magisk 17.3 and up, (18.0, 18.1) compatible kernel is here https://forum.xda-developers.com/showpost.php?p=79164496&postcount=42
Enjoy
Can't enable any Accessibility Services telling that the text to speech language is not supported and when i tries to force itself to change it to english it restarts.
Thanks
core issue imo is that the calling app dialer does not show up during a call-no call ui (call received but no way to accept it) if there was a way to go back to stock dialer and messages this ROM would have been perfect. too bad all in the past now.
For me, after some finetuning, this is the best, fastest and most stable and compatible custom ROM ever for the SM-T715. Thank you Skulldron!
My finetuning after flashing the ROM (TWRP is clearly a requirement):
1) flash new Kernel v1.4
2) flash Magisk v.21.4 (the last one before Magisk (with v.22.0) became an "App", bundeled with the Magisk Manager )
3) install MagiskManager-v8.0.7.apk (The last separate Version of the Magisk Manager before it became a bundle with Magisk)
4) install newest Open Gapps for Arm 7.0 ("Micro" bundle in my case, because I need Exchange support that seems only to come with GMail) choose the one for your needs if you need: open gapps 7.0 arm
5) install Magisk Module "Google Dialer Framework" via Magisk Manager
6) install Google Phone (The offical Google dialer app shows a "device not supported" message but works fine with the Performante Rom. If you don´t like the error message, try another dialer app)
7) install Google contacts (The offical Google contacts app that works fine with the Performante Rom)
That´s the good and stable working basis installation for me. I do not need any google account and use sources like F-Droid, uptodown or the A**zon appstore for some charged applications i need (like Business Calendar, Mobile Doc Scanner...)
Based on you description I reinstalled this one because all other custom roms result in reboots, looping etc.
- Installed stock Gapps (Micro wasn't even available for 7.0)
- the newest kernel 1.6.1
- can use phone and contacts without warnings and problems
- upgraded to lastest magisk version, get warning about system app etc (seems a known problem right now, so I'll wait). But root works
- Netflix, Prime working, Disney with error 39
- fast!
-------------------------
Very good until now. Have to wait a few days and see if the reboots/boot loops etc are gone.
-------------------------
I'll use it only inhouse (since yesterday we have a Galaxy Tab S7+ as primary tablet, but: I can't use it because my daughert occupies it constantly!). Maybe this old and slim rom will give the S2 a new life.
@photona: Thanks for your post. Without it I never would have tried this one again. Sadly Skulldron was last online some months ago...
@engine95: Thanks for updating the kernel!
ThaiDai said:
Based on you description I reinstalled this one because all other custom roms result in reboots, looping etc.
- Installed stock Gapps (Micro wasn't even available for 7.0)
- the newest kernel 1.6.1
- can use phone and contacts without warnings and problems
- upgraded to lastest magisk version, get warning about system app etc (seems a known problem right now, so I'll wait). But root works
- Netflix, Prime working, Disney with error 39
- fast!
-------------------------
Very good until now. Have to wait a few days and see if the reboots/boot loops etc are gone.
-------------------------
I'll use it only inhouse (since yesterday we have a Galaxy Tab S7+ as primary tablet, but: I can't use it because my daughert occupies it constantly!). Maybe this old and slim rom will give the S2 a new life.
@photona: Thanks for your post. Without it I never would have tried this one again. Sadly Skulldron was last online some months ago...
@engine95: Thanks for updating the kernel!
Click to expand...
Click to collapse
Thank you for the tips, after installing opengapps, system webview will be missing, so I have to push a webview (v70.0.3538.80) into /system/app and install it again in the system. Didn't you encounter this issue?
laolang_cool said:
Thank you for the tips, after installing opengapps, system webview will be missing, so I have to push a webview (v70.0.3538.80) into /system/app and install it again in the system. Didn't you encounter this issue?
Click to expand...
Click to collapse
I don't use webview, so: no.
cant believe i haven't tried this before. made this ancient tablet very useable. I wish they still made tablets this size, this thin and light with such good screens. its perfect if you want to read the news or surf social media, want something bigger than your phone but not a monster tablet like most these days
Been using for a couple of days now and it is the best rom by far for everyhting, tried lineage android 10 and 11, both of them make the tab run very hot in games and after a few mins the graphics glitch so bad it is unplayable.
This rom however, the games run great and the tab only gets warm. Also battery usage is superior to all other roms ive tried.
Thank you for your hard work.
Glad to see the link still works, shame this was the last rom ive tried, the last happens to be the best

LineageOS 17.1 Magisk Garage !

Hi there,
This is a dedicated thread for LineageOS 17.1 where i will upload my Magisk modules !
Use Magisk Manager to install/remove the provided .zip modules (Recommended)
(You can install via TWRP too, but don't make any space if you change the .zip name, otherwise the installation will fail ...)
Enjoy !
Tell us a little about what each module is for!
veloz46 said:
Tell us a little about what each module is for!
Click to expand...
Click to collapse
it's inside the module itself !
veloz46 said:
Tell us a little about what each module is for!
Click to expand...
Click to collapse
Yes a small review, why not? Please!!!
here
Great contribution, @janhammer504
The following questions come to mind:
Call Recorder: I guess this module is device independent, as long as the LOS Dialer is used?
Google Sans: What difference does it make installing these fonts and where do you see them?
Notch Hide: So does this actually revert "has_notch" already set in the ROM and what's the purpose (I mean, having a punch hole may imply trying to prevent any content to be shown in that area)?
Master One said:
Great contribution, @janhammer504
The following questions come to mind:
Call Recorder: I guess this module is device independent, as long as the LOS Dialer is used?
Google Sans: What difference does it make installing these fonts and where do you see them?
Notch Hide: So does this actually revert "has_notch" already set in the ROM and what's the purpose (I mean, having a punch hole may imply trying to prevent any content to be shown in that area)?
Click to expand...
Click to collapse
1. Call Recorder is for LineageOS Dialer only (as mentioned in the module description)
2. Look to the screenshot to see the difference (these are the original fonts used in pixel devices)
3. This is an overlay to hide the notch (developer options : type cutout there to see where to apply) : useful for Netflix, YouTube, Gaming ... etc
Notch Hide / Update :
change the internal package name and use the official one !
How to enable :
developer Options > type display cutout
if not working : delete with TWRP or RootExplorer this folder ... and reboot !
/data/system/package_cache
Would be great to have more individual font modules. And system sounds. Preferably without loosing the default ones. Just sayin'...
Thank you for all your effort. This will be very usefull after official. Specially for some stuff... that will have to be removed
gardiol said:
Thank you for all your effort. This will be very usefull after official. Specially for some stuff... that will have to be removed
Click to expand...
Click to collapse
Which is?
Safetynet Fix added ... Enjoy !
All credits go to Didgeridoohan from Magisk Subforum !
janhammer504 said:
Safetynet Fix added ... Enjoy !
All credits go to tenow from Magisk Subforum !
Click to expand...
Click to collapse
Thanks! Is it possible to flash zip file via recovery or is it necessary to install magisk?
Shermo1208 said:
Thanks! Is it possible to flash zip file via recovery or is it necessary to install magisk?
Click to expand...
Click to collapse
yes you can copy-past the files in the system ... but how are you going to do that without ROOTING ???
janhammer504 said:
yes you can copy-past the files in the system ... but how are you going to do that without ROOTING ???
Click to expand...
Click to collapse
Flashing zip file with ofox recovery. Before ctsProfile problem I didn't have root and safety net passed without problem. Then, for the moment, I don't need root in my phone, therefore my question is if I can flash this zip file with ofox recovery. Thanks
Shermo1208 said:
Flashing zip file with ofox recovery. Before ctsProfile problem I didn't have root and safety net passed without problem. Then, for the moment, I don't need root in my phone, therefore my question is if I can flash this zip file with ofox recovery. Thanks
Click to expand...
Click to collapse
Magisk modules are stored to /data/adb/modules and mapped to /product/system/vendor/ ... without Magisk Root you can't load them !!!
janhammer504 said:
Magisk modules are stored to /data/adb/modules and mapped to /product/system/vendor/ ... without Magisk Root you can't load them !!!
Click to expand...
Click to collapse
Ok, thanks!!
any of you guys have tried installing ANX camera? because in my case I can't take any HDR pictures, wondering if it happens to anybody else.
FrameworkOverlay added :
. improve low brightness (new linear overlay) for more battery saving (works great)
. fix compatibility issue with chrome & webview (choose chrome as default system webiew in developer options to avoid yellow tint in chrome browser)
. add more color mode
. improve WiFi stability for both (2,4 & 5 GHz)
. update power_profile
. address some display glitches in some apps (related to the aspect ratio)
. many more things ....
I hope that @gardiol can merge this to the device three in the future !
edit : reuploaded here (XDA UI sucks again !!!)
update : fix some info in AndroidManifest
janhammer504 said:
FrameworkOverlay added :
. improve low brightness (new linear overlay) for more battery saving (works great)
. fix compatibility issue with chrome & webview (choose chrome as default system webiew in developer options to avoid yellow tint in chrome browser)
. add more color mode
. improve WiFi stability for both (2,4 & 5 GHz)
. update power_profile
. address some display glitches in some apps (related to the aspect ratio)
. many more things ....
I hope that @gardiol can merge this to the device three in the future !
edit : reuploaded here (XDA UI sucks again !!!)
update : fix some info in AndroidManifest
Click to expand...
Click to collapse
Already did... but you have to wait a few days before release.... because i want to test properly first.

Categories

Resources