• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[CLOSED][LOS 18.1] Real System Optimization

Status
Not open for further replies.
Search This thread

gringo80

Senior Member
Jun 8, 2018
661
618
Hello there,
It's me again ... :D


What's New ?

Well ... I have made a full package for LineageOS 18.1 to take you in the next level !



Features

- Full ramdisk optimization : reworked from scratch (of course)
=>
. improve CPU/GPU & Memory management
. no lags, no freeze & no random reboot
. super smooth UX
. thermal protection : no throttling & no more overheating ... unless if you are a heavy gamer !
. ultra powersaving mode in deep-sleep

- improve also :
. Wi-Fi connectvity (screen-off playback)
. Camera in low-light
. Sound/Video recording

- Faster FP scanner
- Stock offline charging animation
- SafetyNet Fix included



F.A.Q :

Q/ using this mod the first time ?
A/ you format /data partition ... unless if you have flashed the SafetyNet fix already !

Q/ do i have to reinstall everytime i update my LOS ?
A/ yes, because it's not a Magisk module, otherwise the build fingerprint in /data will have a conflict with your LOS one , and the system will crash !





THIS IS A MOD THREAD
A.K.A
SYSTEM MODIFICATION

THE MAIN GOAL
IS
PERFECTION

THIS IS AN ADVANCED MOD LIKE YOU HAVE NEVER SEEN BEFORE
DON'T TRY TO CHANGE SOMETHING BY YOURSELF :
EACH PARAMETER IS RELATED TO ANOTHER ONE

" TAKE IT OR LEAVE IT "
&
DON'T COPY WITHOUT PERMISSION


***

TROLLS & NOOBS
STAY AWAY PLEASE

{Mod edit}
 
Last edited by a moderator:

gringo80

Senior Member
Jun 8, 2018
661
618
Reserved

2021-10-17 Highly Recommended

- let cleanup some trash = remove "XiaomiParts" :
. heavy battery eater in the background even if it is disabled [Proximity Sensor = always ON !!!]
. framework badly implemented by LineageOS : the handwave gesture was dropped a long time ago by many OEMs (Google included) ... and it's not working here after a deep-sleep ! (check by yourself)

- msm_irqbalance.conf : tiny update / huge effect
- disable scoped storage aka "fuse" = bring back sdcardfs alive !
Your phone will restart itself once, due to the virtualization switch from fuse to sdcardfs ... so don't worry ! Enjoy

2021-10-16
- initial release
 
Last edited:
  • Like
Reactions: f3r.and0

Funk Wizard

Forum Moderator
Staff member
Nov 8, 2014
4,750
17,294
New Delhi
OnePlus 8 Pro
OnePlus 9 Pro
Moderator Information | Thread Locked for Clean-up

MODERATOR NOTICE | THREAD RE-OPENED


I have cleaned the thread. Please take a moment to review the forum rules especially section 2 about language and respecting other forum members. Don't forget that you agreed to keep these rules when you signed up.

This back and forth between a couple of users in this thread is childish & this kind of conversation has no place on XDA. Some of the recent posts here are users blaming each other and some defending them. This is not a playground.


This is a Courtesy Warning !!

Please do not engage in this type of activity & keep the thread solely for the purpose of topic discussion, not for off-topic chit chat, or exchanging insults and personal jabs at other users. Should this disregard for the forum rules continue, further action against the involved will be taken which may lead to the account being reviewed for restriction or removal.

Let's keep the discussion clean on any issues moving forward.

Thank you for your consideration,


Funk Wizard
Forum Moderator
 
Last edited:

gringo80

Senior Member
Jun 8, 2018
661
618
Does this means full read/write access to externalSD/USB-OTG? Cause it doesn't fully work on a different Xiaomi device I own (also on LOS)...
Yes ... and i have made also a Magisk module for this, not limited to POCO X3 [NFC] but all devices with A11 !

Check the specific thread for more information !
 
Last edited:
  • Like
Reactions: stephtban

gardiol

Senior Member
Feb 23, 2011
821
1,063
San Carlo Canavese
photos.gardiol.org
** WARNING LONG POST **

I spent some time to review this.

There are two replaced executables:
- charger
- init

The charger binary is replaced for the offline charging animation, i believe. But i didn't diffed with official charger bin as author do not disclose which MIUI it comes from. So it might be original or it might be modified i don't know.

The init replacement is more critical, probably related to the safetynet fix, but i would be personally concerned to run such binary on my phone unless full source to it is released by author.

All the main props files have been modified and a few things come to my attention.

The build is still abused as "official lineageOS build" by buildkite and such, which it is not at this point, so this would be a concern, even if more an ethical one, since people could report issues as "official" build while it's not an official build anymore.

Also, quite a few graphical props are changed / enabled when they have been not enabled on purpose on official build for stability concerns. So YMMV, but you could get crashes.

All build fingerprints have been changed with respect to official, which is probably related to the safetynet fix. This might lead to problems when Google will change things again, and users of this mod will probably have troubles using magisk or any other safetynet fix unless clean flash again. This patch does also change your crypto keys and make your data lost. But this has been advertised by the author, so you know.

There are a lot of modified init rc files, going trough them all is difficult here, but a few things come to my attention.
In a few files security permissions have been relaxed. Some additional permissions have been granted to camera, audio and other subsystems, the reason for this should be explained.
Also quite some /sys and /dev nodes permissions have been changed to make them less secure.

Systemwide stats collection and tuning have been altered in various places, again i see no direct reason for this.

It is my overall impression that the author took some init file from a different device and/or BSP and kind of copied it on the official ones. Not clear to what purpose.

There are massive changes to the mount schema and procedures, probably linked to the removal of "scoped storage", which is there for a reason so YMMV to accepting this change, specially if it is so widespread in the system.

There are lots of small tuning to CPU and governor, there is messing up with the nice levels and file descriptors, something which should not taken lightly and probably would need deep testing on some benchmark to prove that they actually work beside the placebo effect.

Moving on.

The media profiles, audio codecs and settings, have been modified with at least a couple of changes that are known for having caused issues with various apps in the past.

This is more or less the most of it. I have spent way too much time on this analysis at this point, but i did it as this might impact directly the support i give to the community on official LineageOS 18.1 for surya if anybody flashes it and then report issues.

I can see some improvements which would be good for official build too like some cleanup of probably useless init stuff (leftovers from davinci or generic sm6150) and such.

Unfortunately, providing one mega-patch like this with no underlying github repository to track changes and meaningful commit history to justify each one of them make this entire work useless, which is a pity. I strongly suggest the author to read up how to contribute to the android development community so that the good in his work can actually be of benefit for everybody, as he benefitted from the work of many like we all have.

I have also seen various lines that are actually authorship by somebody else, i suggest the author to spend some time identifying them and, after creating a repository for the patch, repo-pick those patches with the correct metadata. This is a time consuming activity, but a necessary one, as you all can understand, so that a real community can function. Just to be clear: it's the duty of who publish stuff to ensure it does not infringe others authorship's, not the other way around.

I suggest the author (i mean the real person behind his many accounts) to understand how the open source android development community works so that the good in his work can be actually benefit the community. There is good in his doing, it's only the ways that make it difficult to be actually used.

(note: i crossposted this on the official LOS for surya thread as well, because this is also related to that thread and might cause issues for users there)
 
Last edited:

Vulnerability

Senior Member
Sep 14, 2017
69
38
STAY AWAY FROM THIS MOD!! I just flashed it in my LOS install and my phone was instantly bricked! I couldn't reboot back into LOS after the official update today! All my data is lost, i have to do a full restore via miflash then install LOS again. I'll never use this mod again!
 

gringo80

Senior Member
Jun 8, 2018
661
618
@gringo80

What the Hell is wrong with you? Calm down.
Read OP in RED COLOR !

I don't understand, people don't like this work and keep coming from everywhere.


WHAT'S WRONG WITH YOU ALL ... NOT WITH ME. I DIDN'T INVITE ANYONE.
THIS IS NOT A MANDATORY VACCINE !

To any troll here,
Any fake issue ... your comment will be reported. So don't waste your time with me.

Thanks
 
Last edited:

gardiol

Senior Member
Feb 23, 2011
821
1,063
San Carlo Canavese
photos.gardiol.org
Read OP in RED COLOR !

I don't understand, people don't like this work and keep coming from everywhere.


WHAT'S WRONG WITH YOU ALL ... NOT WITH ME. I DIDN'T INVITE ANYONE.
THIS IS NOT A MANDATORY VACCINE !

To any troll here,
Any fake issue ... your comment will be reported. So don't waste your time with me.

Thanks


by gringo80,
THE GOD OF CREATION
All rights reserved © 2021

You made my day, ROTFL

And i am still waiting for a technical reply to my questions.
 

gardiol

Senior Member
Feb 23, 2011
821
1,063
San Carlo Canavese
photos.gardiol.org
i don't see question marked.
you are not welcome in this thread ... you should see a doctor

1. Can you share the source code for your modified init binary?
2. Can you detail the reason for the various relax of security and permissions in your patch?
3. Why are you forcing "official" build status in the props within the mod, if this will not be an "official" build after your mod is applied?
4. Why did you changed the build fingerprints?
5. To what end did you changed stats collection stuff in your patch?
6. Which is the source from you took the various init scripts modifications? Is it stock? BSP? A different device? Or they all your work?
7. Why did you removed the "scoped storage"?
8. Do you have benchmarks and/or screenshots proving actual improvements with your patch applied?
9. why don't you organize your work so that it can be of benefit to the community?
10. Have you checked if any of this work has previous authorship?

There you go, these are more or less all the questione for you.
 
Moderator Announcement

It's a pity that this thread required cleaning again after it was already conducted by a moderator just 3 days ago. And even an administrator engaged before I provisionally closed the thread above. First, at no point language and behaviour that violate the standards for member conduct as stipulated in rule no. 2 of the XDA Forum Rules is accepted and acceptable. Nobody is granted permission to violate the rules, doesn't matter if long time member or just joined, just user of the gratefully provided development or developer, doesn't matter if visitor to a thread or author of a thread.

While we love and encourage vivid discussions, exchange of arguments, knowledge, experience and technical information we can't and won't except if this derails into rants and fights. And certainly everybody is able to support us on this way. For example, if somebody believes or even knows for sure that other's work has been re-released don't post this "accusation" in the thread but follow our request from rule no. 12, contact the Developer Relation Team (DRT; refer to the team members here) with evidence and let the DRT do its job. Especially if it's obvious by moderator announcements in a thread that the thread has been or is under observation, please refrain from further posts that add fuel to the fire but simply report, contact a moderator of your desire or directly the DRT.

But back to the vivid discussions: We expect that especially development threads are professionally handled. And this not only means that the author of the thread provides support in the thread and doesn't point the XDA members to whatever social media but more important that brick reports are immediately taken very seriously, that every effort is shown to support restoration of a device and that future bricks are avoided to the maximum extend. And if a devlopment or development solution is questioned by reasonable information and questions, it can not only it must be expected that these information and questions are seriously and professionally discussed and answered with mutual respect. Why shouldn't we execute on XDA what we do in real life, in our businesses and professions?

@gringo80 I've removed the attachment from the OP and keep the thread closed. Please advise the moderators team to re-open the thread when you are ready to seriously deal with the asked questions, the reports of bricked devices and to discuss the information challenging your product. Thanks for your cooperation.

Regards
Oswald Boelcke
Senior Moderator
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Moderator Announcement

    It's a pity that this thread required cleaning again after it was already conducted by a moderator just 3 days ago. And even an administrator engaged before I provisionally closed the thread above. First, at no point language and behaviour that violate the standards for member conduct as stipulated in rule no. 2 of the XDA Forum Rules is accepted and acceptable. Nobody is granted permission to violate the rules, doesn't matter if long time member or just joined, just user of the gratefully provided development or developer, doesn't matter if visitor to a thread or author of a thread.

    While we love and encourage vivid discussions, exchange of arguments, knowledge, experience and technical information we can't and won't except if this derails into rants and fights. And certainly everybody is able to support us on this way. For example, if somebody believes or even knows for sure that other's work has been re-released don't post this "accusation" in the thread but follow our request from rule no. 12, contact the Developer Relation Team (DRT; refer to the team members here) with evidence and let the DRT do its job. Especially if it's obvious by moderator announcements in a thread that the thread has been or is under observation, please refrain from further posts that add fuel to the fire but simply report, contact a moderator of your desire or directly the DRT.

    But back to the vivid discussions: We expect that especially development threads are professionally handled. And this not only means that the author of the thread provides support in the thread and doesn't point the XDA members to whatever social media but more important that brick reports are immediately taken very seriously, that every effort is shown to support restoration of a device and that future bricks are avoided to the maximum extend. And if a devlopment or development solution is questioned by reasonable information and questions, it can not only it must be expected that these information and questions are seriously and professionally discussed and answered with mutual respect. Why shouldn't we execute on XDA what we do in real life, in our businesses and professions?

    @gringo80 I've removed the attachment from the OP and keep the thread closed. Please advise the moderators team to re-open the thread when you are ready to seriously deal with the asked questions, the reports of bricked devices and to discuss the information challenging your product. Thanks for your cooperation.

    Regards
    Oswald Boelcke
    Senior Moderator
    5
    i don't see question marked.
    you are not welcome in this thread ... you should see a doctor

    1. Can you share the source code for your modified init binary?
    2. Can you detail the reason for the various relax of security and permissions in your patch?
    3. Why are you forcing "official" build status in the props within the mod, if this will not be an "official" build after your mod is applied?
    4. Why did you changed the build fingerprints?
    5. To what end did you changed stats collection stuff in your patch?
    6. Which is the source from you took the various init scripts modifications? Is it stock? BSP? A different device? Or they all your work?
    7. Why did you removed the "scoped storage"?
    8. Do you have benchmarks and/or screenshots proving actual improvements with your patch applied?
    9. why don't you organize your work so that it can be of benefit to the community?
    10. Have you checked if any of this work has previous authorship?

    There you go, these are more or less all the questione for you.
    5
    ** WARNING LONG POST **

    I spent some time to review this.

    There are two replaced executables:
    - charger
    - init

    The charger binary is replaced for the offline charging animation, i believe. But i didn't diffed with official charger bin as author do not disclose which MIUI it comes from. So it might be original or it might be modified i don't know.

    The init replacement is more critical, probably related to the safetynet fix, but i would be personally concerned to run such binary on my phone unless full source to it is released by author.

    All the main props files have been modified and a few things come to my attention.

    The build is still abused as "official lineageOS build" by buildkite and such, which it is not at this point, so this would be a concern, even if more an ethical one, since people could report issues as "official" build while it's not an official build anymore.

    Also, quite a few graphical props are changed / enabled when they have been not enabled on purpose on official build for stability concerns. So YMMV, but you could get crashes.

    All build fingerprints have been changed with respect to official, which is probably related to the safetynet fix. This might lead to problems when Google will change things again, and users of this mod will probably have troubles using magisk or any other safetynet fix unless clean flash again. This patch does also change your crypto keys and make your data lost. But this has been advertised by the author, so you know.

    There are a lot of modified init rc files, going trough them all is difficult here, but a few things come to my attention.
    In a few files security permissions have been relaxed. Some additional permissions have been granted to camera, audio and other subsystems, the reason for this should be explained.
    Also quite some /sys and /dev nodes permissions have been changed to make them less secure.

    Systemwide stats collection and tuning have been altered in various places, again i see no direct reason for this.

    It is my overall impression that the author took some init file from a different device and/or BSP and kind of copied it on the official ones. Not clear to what purpose.

    There are massive changes to the mount schema and procedures, probably linked to the removal of "scoped storage", which is there for a reason so YMMV to accepting this change, specially if it is so widespread in the system.

    There are lots of small tuning to CPU and governor, there is messing up with the nice levels and file descriptors, something which should not taken lightly and probably would need deep testing on some benchmark to prove that they actually work beside the placebo effect.

    Moving on.

    The media profiles, audio codecs and settings, have been modified with at least a couple of changes that are known for having caused issues with various apps in the past.

    This is more or less the most of it. I have spent way too much time on this analysis at this point, but i did it as this might impact directly the support i give to the community on official LineageOS 18.1 for surya if anybody flashes it and then report issues.

    I can see some improvements which would be good for official build too like some cleanup of probably useless init stuff (leftovers from davinci or generic sm6150) and such.

    Unfortunately, providing one mega-patch like this with no underlying github repository to track changes and meaningful commit history to justify each one of them make this entire work useless, which is a pity. I strongly suggest the author to read up how to contribute to the android development community so that the good in his work can actually be of benefit for everybody, as he benefitted from the work of many like we all have.

    I have also seen various lines that are actually authorship by somebody else, i suggest the author to spend some time identifying them and, after creating a repository for the patch, repo-pick those patches with the correct metadata. This is a time consuming activity, but a necessary one, as you all can understand, so that a real community can function. Just to be clear: it's the duty of who publish stuff to ensure it does not infringe others authorship's, not the other way around.

    I suggest the author (i mean the real person behind his many accounts) to understand how the open source android development community works so that the good in his work can be actually benefit the community. There is good in his doing, it's only the ways that make it difficult to be actually used.

    (note: i crossposted this on the official LOS for surya thread as well, because this is also related to that thread and might cause issues for users there)
    4
    Hello there,
    It's me again ... :D


    What's New ?

    Well ... I have made a full package for LineageOS 18.1 to take you in the next level !



    Features

    - Full ramdisk optimization : reworked from scratch (of course)
    =>
    . improve CPU/GPU & Memory management
    . no lags, no freeze & no random reboot
    . super smooth UX
    . thermal protection : no throttling & no more overheating ... unless if you are a heavy gamer !
    . ultra powersaving mode in deep-sleep

    - improve also :
    . Wi-Fi connectvity (screen-off playback)
    . Camera in low-light
    . Sound/Video recording

    - Faster FP scanner
    - Stock offline charging animation
    - SafetyNet Fix included



    F.A.Q :

    Q/ using this mod the first time ?
    A/ you format /data partition ... unless if you have flashed the SafetyNet fix already !

    Q/ do i have to reinstall everytime i update my LOS ?
    A/ yes, because it's not a Magisk module, otherwise the build fingerprint in /data will have a conflict with your LOS one , and the system will crash !





    THIS IS A MOD THREAD
    A.K.A
    SYSTEM MODIFICATION

    THE MAIN GOAL
    IS
    PERFECTION

    THIS IS AN ADVANCED MOD LIKE YOU HAVE NEVER SEEN BEFORE
    DON'T TRY TO CHANGE SOMETHING BY YOURSELF :
    EACH PARAMETER IS RELATED TO ANOTHER ONE

    " TAKE IT OR LEAVE IT "
    &
    DON'T COPY WITHOUT PERMISSION


    ***

    TROLLS & NOOBS
    STAY AWAY PLEASE

    {Mod edit}
    3
    Moderator Information | Thread Locked for Clean-up

    MODERATOR NOTICE | THREAD RE-OPENED


    I have cleaned the thread. Please take a moment to review the forum rules especially section 2 about language and respecting other forum members. Don't forget that you agreed to keep these rules when you signed up.

    This back and forth between a couple of users in this thread is childish & this kind of conversation has no place on XDA. Some of the recent posts here are users blaming each other and some defending them. This is not a playground.


    This is a Courtesy Warning !!

    Please do not engage in this type of activity & keep the thread solely for the purpose of topic discussion, not for off-topic chit chat, or exchanging insults and personal jabs at other users. Should this disregard for the forum rules continue, further action against the involved will be taken which may lead to the account being reviewed for restriction or removal.

    Let's keep the discussion clean on any issues moving forward.

    Thank you for your consideration,


    Funk Wizard
    Forum Moderator