Updated the Module.
Moved the new one to GitHub. https://github.com/Fabl0s/VolumeStepsExtender
Moved from the old Magisk-Template to the newer MMT-Ex Template and now contains 4 values for build.prop:
Code:
ro.config.vc_call_vol_steps=30
ro.config.media_vol_steps=30
ro.config.alarm_vol_steps=30
ro.config.system_vol_steps=30
Notification-Steps are still not changed by any build.prop value I can find, maybe you can find something helpful.
I won't create multiple Modules with own Setp-numbers again.
Just change those numbers mentioned above, 30, 60 and 100 were tested with the old Modules and should work with the new module too.
Tested on my Nokia 8 with Android 9 and my ASUS Zenfone 6 with Andoird 10 (Both Stock ROM, Magisk 20.3 Stable)
No support for OEM-Roms.
Lineage should work, can't test it yet tho.
Old Post:
Hi there,
A Simple Magisk Module to Increase the Volume Steps of any ROM with stock AudioService.jar by adding 3 entries to the build.prop!
Prop Entries:
ro.config.vc_call_vol_steps=XX
ro.config.media_vol_steps=XX
audio.safemedia.bypass=true
Depending on Zip, you get either 30, 60 or 100 Steps for MediaVol. InCallVol is set to 14 in all Zips, change it youself if you want another value. (common/system.prop in the Zip)
Bypass Safemedia should disable the Loud Volume Warning on European Devices (Don't Quote me on that tho)
IT WON'T WORK WITH ANY STOCK SAMSUNG DEVICE AND I CAN'T CHANGE THAT!
SAME GOES FOR ANY OEM WHO CHANGES ANDROIDS AudioFramework.jar!!!
Until now, it seems like Lineage 15.1 doesn't work either.
Maybe other versions too.
T17 is for Magisk 17 and 18
T19 is for Magisk 18 and 19+
If you need this for Magisk 16 or earlier, take a look at this: [url]https://forum.xda-developers.com/apps/magisk/module-volume-steps-increase-magisk-v10-t3554996[/URL]
I tested T17 on my Devices (Xperia Z4 with Android 7, Xperia XZ with Android 8 and Nokia 8 with Android 9)
## Changelog ##
T17: Release for Magisk 17+
T19: Release for Magisk 19+
This is not much work, but if you appreciate it anyway, hit Thanks or consider to gift me a drink.
Cheers
working on redmi note 5 AI with havoc os 8.1 thanks
working on Xperia Z3 D6603 with CarbonROM 8.1
Is there any chance to make it for v16?
working on mi max 2, miui 9 android 7.1.1.
thanks
gkornaks said:
Is there any chance to make it for v16?
Click to expand...
Click to collapse
Try this link.
https://forum.xda-developers.com/apps/magisk/module-volume-steps-increase-magisk-v10-t3554996
zerlkung said:
Try this link.
https://forum.xda-developers.com/apps/magisk/module-volume-steps-increase-magisk-v10-t3554996
Click to expand...
Click to collapse
Thanks! It's working.
Working on redmi note 5 witch android pie. Thanks you
Wow, this is absolutely perfect. The kernel I use with Franco Kernel manager doesn't support gain adjustment, the lowest volume was still a little to loud (on the toilet) now is all gravy (Whyred Los 15.1) Thanks dev
Possible to increase music to 60? Ty
Have any one Tried this on Redmi Note 4 mido???
If not then will it work on Redmi note 4 mido(Custom Roms)???
pokipokipxorn said:
Possible to increase music to 60? Ty
Click to expand...
Click to collapse
Sure. Gonna do it tomorrow if I remember!
@[email protected] said:
Have any one Tried this on Redmi Note 4 mido???
If not then will it work on Redmi note 4 mido(Custom Roms)???
Click to expand...
Click to collapse
If the custom Rom is LaOS Based it should work, else just try it. Won't break your phone
pokipokipxorn said:
Possible to increase music to 60? Ty
Click to expand...
Click to collapse
Uploaded 60 Steps Module to first Post! (Left the In-Call Steps at 14)
pokipokipxorn said:
Possible to increase music to 60? Ty
Click to expand...
Click to collapse
You can do it by yourself.
Unzip file, go to common/system.prop then change the values to your preference. Zip the file & then flash it.
I've set my volume steps to 100 and removed
Code:
ro.config.vc_call_vol_steps=14
as I don't need it.
Works perfect on pocophone f1 with miui 10 beta
Thanks
links
Links are deads and no more in official repo.....
Noru29 said:
Links are deads and no more in official repo.....
Click to expand...
Click to collapse
Yes that's unfortunate. But you can still download the module from the op.
op ?
Noru29 said:
op ?
Click to expand...
Click to collapse
Original post, the first post of this thread.
Related
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.
DREAM UX N8/S8 ROM- TAB S2 T819 BETA[Updated 8 August 2018]
The group includes all variants as I am now beginning to stem out my ROM to other variants.
Well well well! I never thought that this day would come...It's alive! After countless hours shouting at my ISP I've finally gotten this ROM onto drive. Now DISCLAIMER: I do not own this device. A beta tester from my telegram group has confirmed that it boots and seems fine.I have used elements of the T819 base to ensure better compatibility but this is still a port. Please remember that this is a beta and any bugs that may show themselves will be harder to fix. Join the telegram group if you need support or any possible fixes.
WHAT'S INSIDE?:
From The Top:
1. N8 Calculator
2. N8 Calendar
3. S8 Camera UI
4. S8 Clock
5. N8 Contacts
6. S8 Email
7. N8 Galaxy Apps
8. N8 Gallery
9. N8 Game Launcher
10. S8 Internet
11. S9 Messages
12. N8 My Files
13. S8 Dial UI (Phone)
14. Play Games Pre-installed
15. S8 Samsung Connect
16. N8 Samsung Music With Edge
17. N8 Samsung Notes
18. S8 Settings
19. Sidesync S2
20. S8 Video Library
21. S8 Voice Recorder
22. Customizable Edge Lighting
23. Bixby Home (No Voice [64 bit])
24. Touchwiz Home 2018
25. Samsung Themes (Placeholder)
26. Rounded Google Search
27. Lots of Other Stuff from the Port
EXTRAS
1. Fully Functional Dolby ATMOS
2. Fully Functional AOD (Note: Can cause a little more battery drain and also can bug out backlight keys. Extra app installed to unfreeze the buttons when this happens)
3. Build prop tweaks for improved performance
4. Magisk Compatible (Superuser installed by default)
5. Speaker and Headphone Values boosted.
6. Game Tuner Integrated into UI for GPU OC.
Best settings for me ATM:
I/O Scheduler: 2048 R/W and CFQ.
LMK Default ( No change).
Virtual Memory: Swappiness 0 (Slows down if on any higher value. Laptop Mode:1 ZSWAP: Memory Pool: 35% Maximum Compression Ratio: 75%
THATS ALL FOLKS! Install Instructions:
ITS FLASHABLE!
Wipe data (Optional but Recommended)System, Dalvik Cache and Cache
Then Flash THE ZIP!
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Link to the beta: https://drive.google.com/open?id=1ZltuUyQtx1nWK-E6l7IkytJO4ZrZBVHw
Also You may find some random Note 8 Stuff as i ported a Note 8 Floating feature.xml file but adjusted the battery settings to our Tab S2 configuration. Also PLEASE READ what i wrote below!
Enjoy! Special thanks to,
@McFy for development help
Leave a comment below! No screenshots for obvious reasons
Reserved for bug fixes, notices etc.
Hi! Thanks for the effort ! Is it flash-able for the T719? Since it’s just the difference screen size. But otherwise the internal or more or less the same.
Izachii said:
Hi! Thanks for the effort ! Is it flash-able for the T719? Since it’s just the difference screen size. But otherwise the internal or more or less the same.
Click to expand...
Click to collapse
Yes it should be. However you will have to edit the zip and remove the getprop line from installer script. Otherwise the zip will just stop.
Skulldron said:
Yes it should be. However you will have to edit the zip and remove the getprop line from installer script. Otherwise the zip will just stop.
Click to expand...
Click to collapse
Ok! I try to download and see how it goes. And have a feedback to you. Thanks for the effort !
Good
O
All good
Root not working
alkaabi55az said:
O
HTML:
All good
Root not working
Click to expand...
Click to collapse
So just magisk? I know that supersu comes bundled with it. To replace supersu is to flash magisk on top. It's a glitch process unfortunately and is based on lucky
Skulldron said:
So just magisk? I know that supersu comes bundled with it. To replace supersu is to flash magisk on top. It's a glitch process unfortunately and is based on lucky
Click to expand...
Click to collapse
Galaxy app not working
who can help me install the rom on t719?
Aweome - nice to see a new ROM for the T819...
Skulldron said:
Yes it should be. However you will have to edit the zip and remove the getprop line from installer script. Otherwise the zip will just stop.
Click to expand...
Click to collapse
could you help me in the installation on t719 what should be changed? how to do it thanks
Skulldron said:
Yes it should be. However you will have to edit the zip and remove the getprop line from installer script. Otherwise the zip will just stop.
Click to expand...
Click to collapse
It installs but have black screen. cant see nothing after samsumg logo.
Like I said it may not work considering them having different display sizes and also different size batteries
Anyone tried telephony?
In general works fine 4 me. T819 LTE.
Freezed AOD and EDGE light by myself. Just needed more battery life against features.
Issue with contacts sync from google.
Great sound fix.
---------- Post added at 01:26 PM ---------- Previous post was at 01:21 PM ----------
emuandco said:
Anyone tried telephony?
Click to expand...
Click to collapse
I did. And it works fine.
hello
I wanted to try the new rom, the tablet starts and everything works, however, I realized that I do not have root rights. Do you have any advice on how to install magisk? thank you
dantibes said:
hello
I wanted to try the new rom, the tablet starts and everything works, however, I realized that I do not have root rights. Do you have any advice on how to install magisk? thank you
Click to expand...
Click to collapse
find-search magisk thread here in XDA and follow the instruction
@jazzespresso
Thanks for the reply. in fact I had followed the guide that is in this forum and after flashato magisk last version the twrp refers me to the error 1
Not debloated?
Hi thanks for the rom. I can not sign in to my google account on it though. it just goes to a black screen
re flashed and it is now working
Android Version : MIUI 11 Pie 9 Ported From MM2 Easy recovery install.
You should be having proper knowledge of flashing Custom ROM and how to Restore a phone if anything goes wrong.
Take complete backup before taking any action based on this thread. I am not responsible for any action taken by you.
I am just compiling all the information / files available on different websites into this thread, I have patched together with cyber spit, bubblegum, and tape, for a pretty much fully working Miui 11 PIE running rom. I have removed what I believe to be all of the bloat. Worked to modify a working miui pie vendor. Magisk 19.5 installer is all ready included as well as the modified boot for root access. The playstore installer is also included for a fully functioning playstore.
All Credit goes to respective developer/s included in the install.txt within the zip file. I request XDA moderator and or Developer of Respective files to let me know if I have forgotten to mentioned (give credit) their name in this thread. The Download Links are given directly from respective Developer/s.
You need the following two files to Test MIUI 11 PIE on Mi Max 2 (Oxygen). This ROM recovery is ported from the Xiaomi RedMi with many patches and customized from various sources. This ROM maybe Stable enough for your daily use on Mi Max 2. I have access to two MM2 4/64 Global versions using a 1tb sd card one on At&t the other on Tmobile and all features I need are currently working.
1a. Treble Mi Max 2 Recovery 3.2.1 https://androidfilehost.com/?fid=5862345805528056270
1b. OrangeFox Recover 10
https://sourceforge.net/projects/ora...n.zip/download
2. MIUI 11 Pie ROM ported from MM2
https://drive.google.com/folderview?id=1KfWqQmi7bN_yXZfgVzxiifWuS2jDozCr
First step:
Start your phone into recovery and Flash a Treble recovery, if already not flashed. Restart into Recovery.
Click Wipe then Advance wipe and clear System, Vendor, Boot, Data, Cache, and Dalvick cache.
Second step:
Now Extract the Downloaded Rom files in Recovery backup folder. You should know where and how to Extract. (Use extract tool for android or pc then copy paste to recovery backup folder.)
Third step:
Click Restore and Select System, Boot, Vendor and Swipe to confirm. Wait for restore to complete. If any errors, Reboot recovery and try again. Or Mount the System, Vendor, Boot and try again. After Restore completes Reboot. Please allow 3-5 Minutes for first boot.
What works:
Cell Service, Wifi 5ghz/2.4ghz, Bluetooth, Torch, Camera, Sound, Auto Brightness, HW buttons.
What doesn't work:
Some people can't log in to Xiaomi account ( I do not use it, So I can not verify either or).
I do not have dual 4G sims so I can not verify if its working. There may be potential signal problems for some user but I didn't faced in USA with Tmobile, Or AT&T operators.
Eye protection mode/ reading mode 100% does not work, But similar apps available within the play store.
Playstore Installer Included & Now Working. (Due to the chinese base)
Guys, this is a nearly perfect MIUI 11 PIE package for our lovely Xiaomi Mi Max 2 (Oxygen) Although MIUI 11 is still beta.
If I missed anything in the above, kindly let me know to include. If you make any further updates / patches that makes this ROM more stable / perfect or enables new features, please don't hesitate to message me to include in this thread.
I have an old PC running windows with 8gb max at any one given time, So if you would like to make the recovery image into a flashable zip, I'd be happy to update/add it.
If you can afford it, Im trying to save for a computer from this decade, any help is appreciated
https://www.paypal.me/LiamMcGinnisIv
If you would like to use the boot, vendor, system, or any other files, All I ask is pass on the proper credits. With this we should be able to have a fully functioning android Q in the near future (Currently toying around with fair progress in the free time).
Credits : liammc83 HR83 beingtejas letolover77
lekhraj.gupta WhatsNew Any Others Who May Have Been Missed
Best of Luck and Happy Flashing )
reserved
Download, tks
I will try today. Thanks!
Famous pie inCall volume bug solved ??or is still there ??thanks to developer for the hard work bro u rock...
faraaz3 said:
Famous pie inCall volume bug solved ??or is still there ??thanks to developer for the hard work bro u rock...
Click to expand...
Click to collapse
In all miui based rom, In call volume is much louder than other custom roms. and also no echo issue in miui roms.
Outstanding!
Only wish there was a way to install this for use with dual boot patcher in order to test it out.
Does camera app works? I have crashes with message: "Could not find tag for key xiaomi.ai.asd.enabled".
why MIUI 11 PIE 9.9.9 from Connor when there is 9.9.24 available, here is the link for MIUI 11 PIE 9.9.24 for Mi Max 2 from Connor https://c-t.work/s/2147a4b6b1c34e
cheers
maheshkondraju said:
why MIUI 11 PIE 9.9.9 from Connor when there is 9.9.24 available, here is the link for MIUI 11 PIE 9.9.24 for Mi Max 2 from Connor https://c-t.work/s/2147a4b6b1c34e
cheers
Click to expand...
Click to collapse
Basically the same gsi source. But older patched boot, older magisk, and play store installer will not work with conner, yet its labeled *.24
But hey either or, flash what y'all want. If I knew someone was going to keep this updated, and work out the bugs as Xiaomi releases 11 tomorrow, I would just go back to playing with A10.
After all I don't even use these mi max 2s any longer. Was just trying to contribute to the old gang.
Lol , reason why I left.. they insult the older devs who use there time for them
liammc83 said:
Basically the same gsi source. But older patched boot, older magisk, and play store installer will not work with conner, yet its labeled *.24
But hey either or, flash what y'all want. If I knew someone was going to keep this updated, and work out the bugs as Xiaomi releases 11 tomorrow, I would just go back to playing with A10.
After all I don't even use these mi max 2s any longer. Was just trying to contribute to the old gang.
Click to expand...
Click to collapse
By the way.. gapps aroma is directly flashable on your built.. my friend asked me to do that on his max 2 and I did many other changes ,
Fingerprint issues remains their.. but everything else is great and working perfectly.. all gapps are working without bugs and also i removed several apps inbult like mi ai, keyboard , etc etc..
Well good luck guys here.. we won't disturb you guys here..
Liammc83 great work bro.m
beingtejas said:
By the way.. gapps aroma is directly flashable on your built.. my friend asked me to do that on his max 2 and I did many other changes ,
Fingerprint issues remains their.. but everything else is great and working perfectly.. all gapps are working without bugs and also i removed several apps inbult like mi ai, keyboard , etc etc..
Well good luck guys here.. we won't disturb you guys here..
Liammc83 great work bro.m
Click to expand...
Click to collapse
Every time I flashed on my end kept crashing system (black screen sticks), odd. Its why I dumped in the chinese play store installer v3.
But nice to know its working
None of any of this could have been accomplished without you or hardrock 83.
Can we flash pietreble kernel on it?
What about stock camera app? Does it work? Mine is crashing.
zavorotnii said:
What about stock camera app? Does it work? Mine is crashing.
Click to expand...
Click to collapse
It force closes, yes, crashes....Working on fixes.
liammc83 said:
It force closes, yes, crashes....Working on fixes.
Click to expand...
Click to collapse
Ah, thanks! I thought that I did something wrong.
@shivanshgoel said:
Can we flash pietreble kernel on it?
Click to expand...
Click to collapse
Hardrocks V5 kernel tweaked from beingtejas works, yes.
zavorotnii said:
Ah, thanks! I thought that I did something wrong.
Click to expand...
Click to collapse
Please give the camera fix
Manjubailur said:
Please give the camera fix
Click to expand...
Click to collapse
Nope didn't notice..
Fixed now (On My End), working on a few adjustments, ect.
Will be uploaded today with some tweaks.
Is there a way to remove the on-screen navbar without having to enable full screen gesture? I prefer hardware buttons. And one more thing, how to disable the rounded corners? Apart from these two probs and known bugs, this ROM has been decent so far. Thanks!
deleted
deleted
Reserved #1
Reserved #2
Finally, a LineageOS 19.1 without Gapps pre-installed. Kinda sad that the other los has gms built-in while the other one stopped development. But this one looks promising as it sticks to the original Lineage experience.
Some questions that I would like to have clarification before testing this ROM:
1. ROM is using Aryan Tress right? Means it does also support ANX v204?
2. Signature spoofing present in the ROM?
3. Is OTA available?
4. Will it support erofs and f2fs compression in future build?
5. Is NTFS file format for OTG and SD Card readable? (Some roms can't read my ntfs SD card which I use for backups/ROM changing)
agree with @BigChungus321 , finally a vanilla build.
Can you please tell me the difference between vantom kernel and the default?
Also are you planning to make this official?
Edit: Is this using oss vendor?
Thank you!
Stan m said:
agree with @BigChungus321 , finally a vanilla build.
Can you please tell me the difference between vantom kernel and the default?
Also are you planning to make this official?
Edit: Is this using oss vendor?
Thank you!
Click to expand...
Click to collapse
This is an oss vendor rom since the flashing instruction only says latest miui 13 firmware plus the download size for the file is 1GB+. If it is miui vendor then it should be less.
BigChungus321 said:
This is an oss vendor rom since the flashing instruction only says latest miui 13 firmware plus the download size for the file is 1GB+. If it is miui vendor then it should be less.
Click to expand...
Click to collapse
Okay thanks! Why the miui firmware though? I moved from arrow os 11 to 12 without flashing any firmware or anything else...
BigChungus321 said:
Finally, a LineageOS 19.1 without Gapps pre-installed. Kinda sad that the other los has gms built-in while the other one stopped development. But this one looks promising as it sticks to the original Lineage experience.
Some questions that I would like to have clarification before testing this ROM:
1. ROM is using Aryan Tress right? Means it does also support ANX v204?
2. Signature spoofing present in the ROM?
3. Is OTA available?
4. Will it support erofs and f2fs compression in future build?
5. Is NTFS file format for OTG and SD Card readable? (Some roms can't read my ntfs SD card which I use for backups/ROM changing)
Click to expand...
Click to collapse
to
1. its Aryan Tress yes anx should work i dont use it i use gcam
2. no since this is no linage feature like i said its a clean los build i dont modify anything
3. not yet i can add it if needed
4. erofs no since los trees if they add support for it i can switch to it f2fs is already look at github i only revertet erofs related changes
5. should work but im not really sure dont have sdcard in ntfs
Stan m said:
Okay thanks! Why the miui firmware though? I moved from arrow os 11 to 12 without flashing any firmware or anything else...
Click to expand...
Click to collapse
its oss yes you can flash firmware its not a must its just to keep everything up2date if you already on last firmware its not needed (comming from miui or already flashed from other oss rom)
_JaSoN_ said:
to
1. its Aryan Tress yes anx should work i dont use it i use gcam
2. no since this is no linage feature like i said its a clean los build i dont modify anything
3. not yet i can add it if needed
4. erofs no since los trees if they add support for it i can switch to it f2fs is already look at github i only revertet erofs related changes
5. should work but im not really sure dont have sdcard in ntfs
Click to expand...
Click to collapse
Tysm!
Signature spoof is not really a big problem since there's a workaround for microg without signature spoof. Also thank goodness no erofs, I kinda like having system as r/w. OTA not a problem as well, would be cool though for a TG channel as a way to get notified on updates in the meantime. For anx and ntfs, welp I hope it works since I personally prefer stock camera images and use my SD card to restore backups.
I'm definitely going to give this rom a shot when I get bored of my current ROM.
_JaSoN_ said:
its oss yes you can flash firmware its not a must its just to keep everything up2date if you already on last firmware its not needed (comming from miui or already flashed from other oss rom)
Click to expand...
Click to collapse
Stan m said:
Can you please tell me the difference between vantom kernel and the default?
Also are you planning to make this official?
Click to expand...
Click to collapse
What about this?
Thank you.
Stan m said:
What about this?
Thank you.
Click to expand...
Click to collapse
are you talking about stock miui kernel ? look here https://forum.xda-developers.com/t/...leepy-yuki-delta-and-doraemon-kernel.4398423/ basicly is just upstreamed and added a few features look github or look the linked thread for changes i cant write them all
_JaSoN_ said:
are you talking about stock miui kernel ? look here https://forum.xda-developers.com/t/...leepy-yuki-delta-and-doraemon-kernel.4398423/ basicly is just upstreamed and added a few features look github or look the linked thread for changes i cant write them all
Click to expand...
Click to collapse
So that means this build will never be official? Because i think lineage requires stock kernel
Stan m said:
So that means this build will never be official? Because i think lineage requires stock kernel
Click to expand...
Click to collapse
LineageOS doesn't require the stock kernel. You can't go official with the current device sources (as they are right now anyway) as LineageOS already has a different sm6150-common tree.
Aryannn999 said:
LineageOS doesn't require the stock kernel. You can't go official with the current device sources (as they are right now anyway) as LineageOS already has a different sm6150-common tree.
Click to expand...
Click to collapse
so why not use that?
Anyone using this rom want to share their opinion?
Stan m said:
Anyone using this rom want to share their opinion?
Click to expand...
Click to collapse
I'm using it for about 2 weeks... very good in my opinion, battery friendly no draining, charging fast... the alarm can wakeup phone from power off state...
Hellera said:
I'm using it for about 2 weeks... very good in my opinion, battery friendly no draining, charging fast... the alarm can wakeup phone from power off state...
Click to expand...
Click to collapse
Thanks for the reply! Btw how are you using it since 2 weeks? this was released just 5 days ago
...maybe I was confused because I'm using lineage too on another phone, Oneplus-6T... sorry about this!
ANOMALY-KERNEL
Features:
.Built with clang 14.0.6
. Disabled some Debugging stuff
. Based on Latest OnePlus Kernel Sources
.General improvments to sched
.Full -o2 Build with a few improvements
.Usb Fastcharge
.Vibration control
.Adrenoboost changes for more performance
.fsync toggle
.added GPU overclock to 865Mhz
.implement Dynamic SchedTune Boost v3
And much more.
Description:
This Kernel was Built mainly For Evolution-X so compatibility with other roms is unknown. (Please let me know if it does so I can mention it)
it has some goodies and is more performance based but should offer good battery life,
more features to come.
im not responsible for blown up devices or bootloader problems... FLASH AT YOUR OWN RISK!!!
Downloads:
Downloads for : OnePlus OnePlus 8 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Kernel Source:
https://github.com/linux-beast/Evolution_kernel_oneplus_sm8250.git
Possible to remove write protection and make able mount remount
Oneplus 8 pro/ Evo-X rom. Flashed using ex kernel manager. But, I'm not sure if it took. Kernel name hasn't changed at all so I can't say if it worked out. Thanks, though. Glad to see development on kernels.
DrDominate said:
Oneplus 8 pro/ Evo-X rom. Flashed using ex kernel manager. But, I'm not sure if it took. Kernel name hasn't changed at all so I can't say if it worked out. Thanks, though. Glad to see development on kernels.
Click to expand...
Click to collapse
Today I will add my name to kernel so you can tell which version your on. Another way is to check the build date. Should say oct 7
beany23 said:
Today I will add my name to kernel so you can tell which version your on. Another way is to check the build date. Should say oct 7
Click to expand...
Click to collapse
Build date says oct 6th for me. Something might have gone wrong with the flash. I'll try the next build you post when it arrives.
DrDominate said:
Build date says oct 6th for me. Something might have gone wrong with the flash. I'll try the next build you post when it arrives.
Click to expand...
Click to collapse
That actually is correct. Yesterday I just got sources ready for the xda thread
Mr Hassan said:
Possible to remove write protection and make able mount remount
Click to expand...
Click to collapse
Possibly but atm I will not mess with it.
Let me get some builds out and I'll take a look
beany23 said:
Possibly but atm I will not mess with it.
Let me get some builds out and I'll take a look
Click to expand...
Click to collapse
Not regular kernel will do it but can u make it one for me?
Mr Hassan said:
Not regular kernel will do it but can u make it one for me?
Click to expand...
Click to collapse
not yet . ill let you know when i decide to look at it
Mr Hassan said:
Possible to remove write protection and make able mount remount
Click to expand...
Click to collapse
You can't remount as rw on my ROM as I ship with erofs instead of ext4.
AnierinB said:
You can't remount as rw on my ROM as I ship with erofs instead of ext4.
Click to expand...
Click to collapse
I said the same thing to him in DM...
Hi and nice to see a kernel for Evo X A13.
Just to be clear, this is fully compatible with Evo X OnePlus Extras app?
MasonJames1988 said:
Hi and nice to see a kernel for Evo X A13.
Just to be clear, this is fully compatible with Evo X OnePlus Extras app?
Click to expand...
Click to collapse
should be. its built using the evolution rom and device files.
New build uploaded.
Changelog:
Added GPU overclock
Fixed issue with wifi disconnects
Disabled some more debugging stuff
Looks good, I haven't gotten a chance to check it out yet, is it possible to optionally increase the OC to 920mhz? This was the OC on my old kernel and it worked great. Thanks for the interest in the evo rom, best rom out for this phone. https://github.com/mrslezak/Radioactive_kernel_oneplus8/releases/tag/untagged-82015065e6e64c806a7b
Looks like the kernel isn't actually installing. Tried FK manager and OrangeFox and this is what I see.
gforceriders said:
Looks like the kernel isn't actually installing. Tried FK manager and OrangeFox and this is what I see.
Click to expand...
Click to collapse
+1 on this, tried installing on Ex kernel manager. I know for sure it hasn't installed because it hasn't touched my konabless undervolt
I can also confirm the kernel doesnt install correctly. There was a Evo X update early this morning with a kernel date of the 12th.
This kernel date should of been the 11th or the 10th
That's interesting. I had the issue at first but the latest build installed just fine? Hmm did you guys use the latest download?
Even shows the correct name now..