yashsingh1/xdaforums huggingface dataset:
[Redmi Note 2 Android Development] jajk:
714-13 for MIUI is up.

Changelog:

disable sn service (TWRP still finds the serial number for backup folder without it)

disable console service (if ro.debuggable=1 as found in some ROMs build.prop for reasons unknown)

This will be the final version for MIUI 7.x.x - that is as skinny as it can possibly get.

[MENTION=4460588]MOVZX[/MENTION] I think your settings for interactive governor are a bit weird unless that is because of the way CM works? The guide from Nexus 5 forum is not applicable to our special MTK based phone besides Nexus 5 owners being a bit strange;)

Are you going to try disabling more stuff in the boot.img to get closer to 714-13?

Edit: Since you have a 2.2GHz cpu, you might want to edit init.hermes.power.rc to give it valid frequencies for your cpu. The file assumes everyone has the poverty model like me:(

A classic example as to why tweaks belong outside the boot.img;)
[Redmi Note 2 Android Development] MOVZX:
I believe our device has only 1 CPU in big.LITTLE configuration, unlike any other device which uses 2 CPU combined into big.LITTLE. Maybe that's driving me crazy with 2.2GHz power.

Anyway, I am really satisfied with this Skinny Edits, 5 hours+ of SOT with 20% screen brightness (I am sure it's 20%, I checked it on /sys/class/leds/blahblahblah-screen/brightness). I'm not gaming on a phone (prefer it on my PC, PC Master Race LOL).

I disabled auditd & sn service as you suggested, booted it up and checked logcat no weird things, no critical error, no nothing. But the init.trace still there.

And, in stock MIUI, RAM score for Antutu is above 6000+, in CM it's maxed out to 5000+ only, can't achieve higher or at least closer to stock MIUI. I wish for your enlightenment...
[Redmi Note 2 Android Development] DarthJabba9:
That is the question. The report does not seem to confine the problem to Qualcomm SOCs, even though it says that it originated from Qualcomm-supplied source code (netd, etc). For all we know, this code might be in use by anybody, and anywhere.
[Redmi Note 2 Android Development] jajk:
[MENTION=4460588]MOVZX[/MENTION] The MTK6795 chip has 8 cores of equal power - it is not a big-little configuration at all even though most kernel tweakers will display it as 4 big, 4 little cores.

You still have all the logging / debugging that you can disable to unleash a bit more speed and battery saving.

If you look at init.hermes.power.rc you will see it is trying to set 1950000 and 606000 frequencies for performance mode. 1950000 does not exist for your cpu and 606000 does not exist for either cpu version. Who knows what your max and min freqs will end up being set to with these 2 invalid values. That is where you will be loosing some performance. I think it is also limiting to 4 cores on line out of a potential of 8. I hate to say it but CM and AOSP ROMs all suffer from the lack of high level drivers due to the non-release of MTK and Xiaomi source code. Hotplugging, thermal throttling and Perfserver features are all compromised. As usual, all the CM and AOSP development effort abandons the previous version every time a shiny new version of Android appears so we never quite get a mature, stable version. Watch what happens when N comes out. Customized stock is always best;)

[MENTION=5850987]DarthJabba9[/MENTION] I expect the potential exploit is across all manufacturers.

If you follow the Skinny ethos closely, there is potential to enable performance mode all of the time since the cores will scale from nothing to full on as demand dictates - no need to mess around switching profiles etc.

The downside is the notifications that nag you about being in performance mode.

Solution: copy and then rename \system\etc\.tp\thermal.off.conf to thermal.conf

Performance mode simply turns off aggressive thermal throttling by switching from thermal.conf to thermal.off.conf settings. Thermal protection is still functional with this trick so no damage will occur. The cpus will be allowed to run a bit hotter before throttling back or unplugging.
[Redmi Note 2 Android Development] acestars:
So when on performance mode which conf will be used thermal.off.conf or thermal.conf? Sorry i just a bit confused.
[Redmi Note 2 Android Development] jerryshaw12:
I think thermal.off.conf
[Redmi Note 2 Android Development] jajk:
[MENTION=7442305]Iliyena[/MENTION] There should be a support group for people "like us" but then we would all sit in a circle denying there is a problem.

[MENTION=5850987]DarthJabba9[/MENTION] Are you able to stop unwanted services in 7316 or does it know better than mere humans?
[Redmi Note 2 Android Development] cukierkas:
If you guys so smart, why aren't you making your own OS, like Jolla sailfish or chromium, etc.

If you know how to make things better, why bother with this Chinese miracle?
[Redmi Note 2 Android Development] DarthJabba9:
Yes, I can stop them (autostarts).

By the way, I tend to stop only the BOOT_COMPLETED receiver stuff. Is that enough, or should I be stopping all the other receivers?

PS: are we talking about the same thing?
[Redmi Note 2 Android Development] jajk:
[MENTION=2606021]cukierkas[/MENTION] Big difference between making something and hacking it:) Nothing is safe from me whether it be a car or motorbike ecu, outboard motor, phone, PC, mother's hearing aids, lawnmower. Everything is built to under perform so I, and others (afflicted) like me, find purpose in life:)

[MENTION=5850987]DarthJabba9[/MENTION] Yes, that is what I am talking about. I spat the dummy on 61117 because suddenly there were unstoppable services (in MyAndroidTools). In the Security Centre, there where some retarded services like GameBooster and others that Xiaomi find essential to their harvesting program. Can you throw me a link to the 7316 boot.img and I will update skinny to it. I was waiting for a Yandex link to appear so I could take just the boot.img from the ROM but this time around, only Google Drive links which force me to take the whole ROM which I am not about to do.
[Redmi Note 2 Android Development] DarthJabba9:
[MENTION=5952980]jajk[/MENTION] Here is the 7316 boot image: https://mega.nz/#!7gkWCJZQ!tGXXtL6-SRs39Fahjy5n14IwNoTpXfojI4PT6tLd1rs
[Redmi Note 2 Android Development] nickzeptepi:
Can i flash the boot image while I'm using a Cyanogen based ROM?
[Redmi Note 2 Android Development] jajk:
Skinny_Pro_7316_Tweaked-v27.img uploaded

This is suitable for all 7.3.xx MIUI8 ROMS but, although it will run and do no harm on earlier ROMs, it is of no benefit so don't use it if you have a ROM earlier than 7.3.xx

Rebased on 7316.

Cpu core limit removed - this can still be done in init.d instead if you want less cores.

There has been some efforts to rearrange the cpuctrl and cpuset groups in recent ROMs. Part of this was for the amazing GameBooster function and the remainder may not be of any use to our RN2 device (ROMs are not specifically built for our phone since around 7140). I have kept support for these new configurations in this release just in case they actually do something useful - you tell me if you notice better core utilization, better performance or better battery:confused:

[MENTION=6871652]nickzeptepi[/MENTION] No. CM needs different bits in its ramdisk and no, I won't be supporting it.
[Redmi Note 2 Android Development] lukaks69:
As you saw I mentioned you many times in my topic about skinny.img.

I have a question, 7226 skinny.img worked well on 7.3.9 and 3.2, it is better for users to start using 7316 on 7316 rom or it is better that they use it also on 7.3.9 and 3.2 instead of 7226 ? thank you :D
[Redmi Note 2 Android Development] DarthJabba9:
I think you will spit the dummy on 7316 as well, because nothing can be stopped in the Security Centre. It has 5 BOOT_COMPLETED receivers, and none of them can be stopped.

By the way, my question still remains - when stopping services for an app, should I stop only the BOOT_COMPLETED receivers, or should I stop

all

receivers?
[Redmi Note 2 Android Development] acestars:
[MENTION=5952980]jajk[/MENTION] I am installing magisk on eu 7.3.9 and looks fine. But why your skinny boot image can't be patched with magisk?

When i tried to install systemless supersu it can't be patched as well.

Sent from MIUI 8.0.2.0 on Redmi Note 2 using Tapatalk
[Redmi Note 2 Android Development] jajk:
[MENTION=7361449]lukaks69[/MENTION] Read, try it and find out and don't mirror my boot images - it looks like they are someone elses work and you loose connection to the original thread which contains important information about their application.

[MENTION=5850987]DarthJabba9[/MENTION] Yes I would spit the dummy with 7316 and everything post 61110. The answer to your question is complex - each app needs to be able to start when truly required and not just because the network state or location has changed etc. I examine the cause of apps starting when I notice that they are running without my knowledge and seek to disable the offending receiver. This is not always possible and often I will replace the app if it refuses to comply.

[MENTION=3885679]acestars[/MENTION] I have no idea what magisk needs that it is not finding. Look at the install script to see what the process is. I don't intentionally do anything to stop it installing.

Why would you want force systemless root on a 5.0 ROM? SuperSU install script would need to be hacked to allow it.
[Redmi Note 2 Android Development] jajk:
SuperSkinnySU-v2.52-arm64.zip uploaded.

Install through TWRP and don't update app via playstore.

This is standard SuperSU package skinnified to suit only arm64 and resolutions above hdmi.

This consumes less resources than later versions and is less problematic since it is pre systemless root complexities.

I recommend using this version unless you are on an Android 6.0 ROM in which case the SuperSkinnySU-v2.79-SR3-arm64.zip works perfectly.
[Redmi Note 2 Android Development] acestars:
[MENTION=5952980]jajk[/MENTION] I cant login to uber and i think because my rooted and xposed installed device so i try systemless su and xposed. But i found the real culprit is xposed imei changer module, LOL.

Sent from MIUI 8.0.2.0 on Redmi Note 2 using Tapatalk
[Redmi Note 2 Android Development] jajk:
[MENTION=3885679]acestars[/MENTION] I didn't post v2.52 because of your problem ;) I made the file after having issues on my moto G and realizing the SuperSU2.79SR3 was the culprit.

It would be interesting to alter the install script for SuperSU to force systemless on a 5.x ROM. Why? Because it is there. Someone other than me should try it:laugh:
[Redmi Note 2 Android Development] lukaks69:
Then will just give thread of this thread, thanks you, did not wanted to be ruse about posting your skinny, but understand. Could you told me what I asked about if it is better to use skinmy img for 7316 on 739 and 32. Again thank you
[Redmi Note 2 Android Development] Iliyena:
Oops. Read the comment I replied to wrong. Nvm
[Redmi Note 2 Android Development] Iliyena:
So, 2 zram activated with different size and prioritizing, what can I try to ever now how it affects me? ;P
[Redmi Note 2 Android Development] jajk:
[MENTION=7442305]Iliyena[/MENTION] It will be hard to see what is happening but in theory, it should allow lower priority tasks to be swapped out more readily than higher priority tasks. There may be more to do to make this happen:confused:

[MENTION=7361449]lukaks69[/MENTION] Try both and you decide which one is better. I am skeptical about the recent changes to core management but users may complain that the "power" booster novelty does not work without including the changes. Personally, I would stick with the older version and forego the useless bling.
[Redmi Note 2 Android Development] Iliyena:
Indeed it will... Guess I'll go with 2x384MB and make one p 2 and one p 3. ;)
[Redmi Note 2 Android Development] lukaks69:
On 7316 init is not supported? Some user flashed it and no changes in governor, than flashed 7223 and changes applied from init
[Redmi Note 2 Android Development] jajk:
[MENTION=7361449]lukaks69[/MENTION] Exactly the same init.d support in both versions. Look at the end few lines of init.rc file on both versions. Some user got something wrong.
[Redmi Note 2 Android Development] lukaks69:
Maybe he flashed wrong, thanks
[Redmi Note 2 Android Development] jajk:
Skinny_Pro_7323_Tweaked-v27.img uploaded

Suitable for 7.3.xx MIUI8 ROMs. Earlier ROMs, stick with v26.

Changes:

Rebased on 7.3.23

This has some change to kernel binary and healthd (charger binary) which is a fairly rare occurrence. Hopefully something has changed for the better.

Some values for cpuctrl have changed in stock so the skinny version has mirrored the changes.
[Redmi Note 2 Android Development] acestars:
So what will happen if earlier roms flashed this version?
[Redmi Note 2 Android Development] jajk:
[MENTION=3885679]acestars[/MENTION] Earlier ROMs can not utilize the new cpuctrl settings - they just get ignored since support in the boot.img is only half of the equation - MIUI must also support it at O.S level. Nothing bad will happen if you flash this on earlier versions (right back to MIUI7.5 but not MIUI7) except some settings will be left slightly less than optimal.

As I mentioned earlier, I am not overly convinced that the latest changes are for the better since I am not running the latest ROMs. There is a new performance app included in the latest ROMs (name eludes me at the moment) that I suspect is the reason for the changes. If it is anything like GameBooster, it will be a complete joke. It does seem to lock into mcd services which I remove. Somebody might tell me if there is anything worthy of redemption in this latest app????

Edit: PerfTurbo is the newly added app which is also linked in some way to Sysop app that requires GAPPS. In true Xiaomi style, we have all sorts of apps and services appearing or changing names. Mostly these are junk adware / spyware with important sounding names like Security Core so you don't delete them. Unless someone can do a catchup on what all the new apps and services actually do, I might have to load the latest ROM myself sometime next month and find out. I will then keep it secret unless you join my exclusive club:rolleyes:
[Redmi Note 2 Android Development] DarthJabba9:
perfturbo and sysopt are among the things that I removed in my skinny 7.3.16, so whatever they are supposed to be doing is not crucial to the smooth running of the phone.
[Redmi Note 2 Android Development] Adam Hui:
telegram or smthing?
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] Why not - xda isn't exclusive enough. Anyone on 6.0 is excluded from joining :rolleyes: = sarcastic

[MENTION=5850987]DarthJabba9[/MENTION] Did you delete them before figuring out what they do? I decompiled the apps but it didn't help shed any light on what they actually do except that there is some cloud based action. I expect this is a further development of GameBooster which boosts the revenue for Xiaomi when it sells your data;)
[Redmi Note 2 Android Development] Adam Hui:
i'm dual boot, lemme in.
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] Wait for your invitation then.
[Redmi Note 2 Android Development] Adam Hui:
Hahaha...forever??
[Redmi Note 2 Android Development] dsjiffry:
When I access this file it says.

gpufreq debug enabled

Should I just overwrite all the text with 0??????
[Redmi Note 2 Android Development] DarthJabba9:
Indeed, I did. I figured that, whatever it was that they did, I was doing quite fine without it, and so I did not need it.
[Redmi Note 2 Android Development] jkd:
I use skinny_v2 7.2.24 ROM, Which boot img can i use ?
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] Must still be in the mail:laugh:

[MENTION=5997739]dsjiffry[/MENTION] Yes, then it will say gpufreq debug disabled indicating gpu touch boost is turned off which doesn't make a lot of sense but MIUI is full of nonsensical stuff:eek:

[MENTION=5850987]DarthJabba9[/MENTION] Thousands of man-hours went into coding those apps and you just delete them?

[MENTION=681627]jkd[/MENTION] Skinny_Pro_7223_Tweaked-v26.img
[Redmi Note 2 Android Development] DarthJabba9:
Yep. I am now

extremely

wary of anything new in miui ...
[Redmi Note 2 Android Development] dsjiffry:
What does debugging do exactly??????

And are the advantages and risks of disabling it??????
[Redmi Note 2 Android Development] jajk:
[MENTION=5997739]dsjiffry[/MENTION] Debugging is a form of logging things that occur during code execution. The logs that are created are then used by devs to fix up the code. Once the code is stable, all debugging code is normally removed or at least turned off before release because it is, in itself, an overhead. The notion that this debugging is left turned on and information is sent back to Xiaomi so the software can then be improved is stuff of fairytales so I turn it off to reduce the overheads;)

The risk of turning it off is that Xiaomi no longer has a valid sounding excuse to strip data from your phone and may lose revenue from selling your secrets and pushing ads to your phone when you decide to sever the connection altogether.
[Redmi Note 2 Android Development] DarthJabba9:
You're hilarious! :D
[Redmi Note 2 Android Development] Sleepy_Augie:
Would I be able to replace the security app I have with an older version who's services could be disabled? I'm on 7.2.24, and it would be nice to not have to switch, since I've worked a bit on skinnifying it.
[Redmi Note 2 Android Development] jajk:
[MENTION=5850987]DarthJabba9[/MENTION] Xiaomi provide the comic material - I just exploit it;)

[MENTION=7150090]Sleepy_Augie[/MENTION] Interesting proposition but a lot of stuff is intertwined with security center so you would have to transplant all the features you want to keep. I doubt it would be successful but please do try it and let us know if it maybe can be done. I have tried completely replacing security center with discrete apps before but it failed.
[Redmi Note 2 Android Development] Adam Hui:
Just fyi ot [MENTION=6296775]Dinolek[/MENTION] has boot up RR N, only camera & ir still dont work.
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] I have updated TWRP to support all Android 5.x and 6.0 just for you since I have been a little bit mean lately;)

Now we are truly ready for the release of MIUI8.2 for RN2 based on Android6.0 ...... I want to believe.
[Redmi Note 2 Android Development] Adam Hui:
Ive been being a thankful hats-off since first time beginning for ur efforts, just winked why u dont contribute at aosp development. Can we meet in Bali for beers?

Didnt u say it still in the mail? I felt so dirty on miui like jump to hold a swamp thing or press like for eagle-patriots posts.

I hope xiaomi doenst over act busy for just release one build forever for emergency revival & bends the rest of energy to release sources.

Yep, it's just a quick port test from wisniaPL build.
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] Actually I am playing on AOSP6.0 with Dinolek kernel ready to jump to LOS13.1 if the development doesn't get derailed like so many promising projects by loosing focus on the task at hand. 7.1 is a whole new set of problems at the hardware support level and for what? A good 6.0 has far more value than a buggy 7.1.

Beers in Bali sounds good but unfortunately I am stuck on the ground - unable to fly anywhere:(

[MENTION=6296775]Dinolek[/MENTION] It seems like the charging is still problematic in that it tapers off too early and never reaches the stock full voltage of 4.44V- have you looked at what the target battery voltage is set to? It might be set too low for our BM45 battery. Seems like it is still in the range for normal phone batteries. I would not advocate 4.44V because we get premature battery failures but 4.40V as a compromise.
[Redmi Note 2 Android Development] Adam Hui:
that was all persisted said for 5.0 when it comes 6.0 from scratch.

EDIT : Camera fixed in nougat, dont be ashamed to taste it ;)
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] I tasted 7.1 on my moto G and it was starting to step beyond hardware support so fell back to 5.1. In CM / LOS based ROMs you end up with too many shims to patch over the lack of hardware support so things don't quite function the way they are meant to if you look hard enough. Many users don't notice so fall in love with these ROMs more than they should.

Modified stock is always best:cool:
[Redmi Note 2 Android Development] Adam Hui:
I know.

My dealt it was a fair accepteable while it was suitable enough for daily use than a stucked chinese memory lame, as for me it's an over-act to use it as a remote controller, etc. & dinolek made bit-level detailed fix time by time, a perfectionist guy like u. Seriously, all ur code-quotes here were helpful works & being applied.

A freedom tiniest size & lightest weight modified custom was always an itchy obsession for me.
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] Move away from MIUI is inevitable now they are concentrating only on exploiting their users further. I am neither Chinese nor Communist so this exploitation does not sit well with me.

Very smooth results from heavily skinnied AOSP6.0 (ignoring known bugs) but charging is still wrong in dinolek 2.41 kernel. Maybe he will revisit the problem and adjust to the Xiaomi battery voltage instead of LeTV one? If the 6.0 threads were on XDA, it would be a lot easier to participate. I am not interested in joining fanboy clubs:eek:
[Redmi Note 2 Android Development] Adam Hui:
Forwarded to dino, le1s 'in 10 minutes created' quick port was just a quick poll test to directly submitting bugs & logs. Will rewrite from sources as it all collected.

Less a fanboy club :cool: all kids were grown up by xda, submitting quick reports, logs then deliver every partial fixes for another cycles till it clear enough. I think xda needs a fast enough in-app direct-chat to accomodate this.

Sorry for spamming ur thread, just realized my self to stop here :laugh:, will do it again later.
[Redmi Note 2 Android Development] jajk:
[MENTION=4666525]Adam Hui[/MENTION] It's not spam since the thread is not called "Only for MIUI Lovers". My intention is to provide the same skinny service for 6.0 once it is viable. The problem with going offsite is that we end up like 4pda where loads of misinformation is gathered because only snippets of information are brought back by the worker drones and all context is left behind. I get a kick out of it when I see snippets from here being jumbled in translation and context once they get back behind the iron curtain:laugh:

[MENTION=6296775]Dinolek[/MENTION] Currently the fully charged battery using your kernel is around 88% charged compared to stock 5.02 kernel. Or another way to look at it is a final voltage of 4.33V compared to 4.444V (which should actually be no more than 4.44V). If you are fully charged and plugged into USB or a charger and reboot from 5.02 to TWRP with your 2.41 kernel, the phone will panic and shutdown thinking it is overcharging. Unplugging the charging source will allow booting into recovery again.

The problem with xda is people get distracted feeding trolls and trying to please everyone. Ignore them, abuse them , mess with their puny minds... but stay on track is my message.
[Redmi Note 2 Android Development] rocco2023:
After installing Custom Boot Image at each start the following message appears: "the system process does not respond" wait or accept. Now I am with rom 8.1.3 of eu and the last custom boot image, but it has happened to me with all rom and custom boot image
[Redmi Note 2 Android Development] jajk:
Skinny_Pro_8210_Tweaked-v28.img uploaded

This is suitable for MIUI7.5.x and MIUI8.x.x ROMs.

[MENTION=1089478]rocco2023[/MENTION] Clean install your chosen ROM - do not connect to a Xiaomi account. Boot up once to get past all the setup screens, then reboot and install Skinny Boot. If you want themes or backups etc. from Xiaomi account, don't use Skinny Boot.
[Redmi Note 2 Android Development] Adam Hui:
A ressurection answer for skinny thread ? :laugh:

https://www.gizmochina.com/2016/12/22/users-will-able-delete-system-apps-miui-9/