yashsingh1/xdaforums huggingface dataset:
[Redmi Note 2 Android Development] Gyovany96:
[MENTION=5952980]jajk[/MENTION] Script works ! But I have some questions :

1. I set my CPU to 1183000 and limit cores to 4. As I know interactive governor it's good for octa-core , right ? Since now I got only 4 cores , it's good to keep interactive governor or change it ?

2. I don't know what num_limit_power_serv mean into following line. By the way , this configuration with 3332 that I've done it's good for my 4 cores CPU ? What do you think ?

3. I set ZRAM to 1GB due to my Prime phone version and this line echo 100 > /proc/sys/vm/swappiness. It's that good ? Thanks !

BTW the Busybox 1.25.0 .zip did not updated my busybox :/ , so I had to replace it manually and it's good now.

EDIT: Battery draining surprising fast so I stick to just CPU downgrade to 1183000 and 4 cores limit
[Redmi Note 2 Android Development] jajk:
[MENTION=5216574]Gyovany96[/MENTION] Ahh! Typo in the uploaded version of bb1.2.50 - I will fix shortly.

I would be running at least 4 cores and at least 1482MHz (for Prime) - each A53 core is fairly weak at 26MIPS rating. 4 cores @ max freq gives you very close to 50% max power usage by cpu. Remember: the lower the processing power, the longer it takes so battery savings are not what you expect them to be;)

num_limit_power_serv is the number of cores available to performance server .

Size of zram rule of thumb: set it to half of your normal free RAM. So 1GB for Prime is good, 512MB for us poorer folk;)

[MENTION=4351699]redbird88[/MENTION] Unzip the attached file, copy it to /etc/init.d folder and reboot. Edit to suit yourself after you know it is working. You did have an init.d folder without having to create it yourself?

[MENTION=5850987]DarthJabba9[/MENTION] Yes, Xiaomi are masters of leading people around in circles without giving them anything.

My vote for best ROM so far is also MR7.2.30 ported from RN3 originally from Indonesian forum (not the straight MR7.2.30 for RN2). I have a backup of it somewhere that I might reinstall and update to current apps, scripts and boot.img.

I have far less occurrences of the ColorDrawable lines in my logcats - nothing to be worried about but I will keep looking into why MIUI8 is spitting out so many. Having Xposed installed seems to aggravate the situation.

Anyone posting logcats, can you please clear the log first then do a reboot and immediately take a log after that and limit to last 1000 events? This makes it clearer what might be going on.

How to do this? In terminal, type su to get SU rights. Type logcat -c to clear the log. Reboot, then back to terminal and type logcat -t 1000 -d /storage/emulated/0/logcat.txt
[MENTION=4666525]Adam Hui[/MENTION] will probably dumb the process down for me:p (I already know it can be done through adb so don't go there) Perhaps we can install an app?

Notice the perfserver related commands through logcats? The following is when perfserver sets the 1183MHz, 2 core boost:

D/PerfServiceManager( 710): [PerfService] notifyFrameUpdate - bDuringTouchBoost:true D/PerfServiceManager( 710): [PerfService] MESSAGE_BOOST_ENABLE_TIMEOUT_MS [SCN_SW_FRAME_UPDATE] bDuringTouchBoost:true
I/libPerfService( 710): 7: set freq: 1000000
I/libPerfService( 710): 7: set: 2
[Redmi Note 2 Android Development] jajk:
Fixed Busybox 1.2.5.0 installer script, download from here:

https://drive.google.com/open?id=0BwdRTuyj12_yd0s1QmNLRzdveFk
[Redmi Note 2 Android Development] jajk:
7550v2 and 8010v2 images posted.

Changes to hopefully fix ColorDrawable spam in logcats. (Re-add init.aee.rc and init.xlog.rc)

Let me know how this goes;)
[Redmi Note 2 Android Development] DarthJabba9:
If you are referring to this one, I agree.
[Redmi Note 2 Android Development] Sleepy_Augie:
[MENTION=5952980]jajk[/MENTION] I uninstalled Xposed framework, rebooted system, booted into recovery, flashed 8010 boot image, and it gave me the same bootloop as when I was restoring from a scatter file (this time I wasn't dumb and on low battery). It bootloops before I am able to access recovery, but I can get to fastboot. Flashing a stock boot image from fastboot fixed the issue immediately. I attempted this twice. I don't know what I'm doing wrong, and I've always had bootloops that still allowed access to the recovery, so something's fishy. I'm using eu 6.7.7 beta.
[Redmi Note 2 Android Development] jajk:
[MENTION=7150090]Sleepy_Augie[/MENTION] My guess on your predicament: To get to Recovery, the preloader and uboot partition must be intact as well as having a good recovery partition. I suspect that somewhere along the way, you have ended up with partitions at the wrong addresses or dodgy content in the preloader partition. When you flash a new ROM using TWRP, it only writes to the partitions by name, not physical address so any underlying problem is not corrected.

To fix the problem you would generally have to reflash an entire factory ROM using SP Flash tools and a correct scatter file. I have seen 2 variations of scatter files addresses - different MTK6795 phones reverse a couple of partition addresses to spoil initial attempts a porting to other devices. The one I gave you is absolutely correct for our phone. There is a way of getting a report out of your phone on where all the partitions are but it escapes me at the moment - someone will chime in and let you know;)

The other issue may be the origin of the TWRP you have. I hope you are using my 3.02-2 version and not some of the dodgy ones from Rusky sites?

And....the other, other issue might be a corrupt data partition - do you repair filesystem in TWRP to be sure. It seems to be common when flashing these latest version ROMs to end up with an error on /data.

[MENTION=5850987]DarthJabba9[/MENTION] Indeed:) I do have 7550 running nicely now but it is a bit harder on resources than 7230 was so it is tempting..... I might just fish out the backup and remind myself how good it was:)
[Redmi Note 2 Android Development] Brkge:
Doesn't work for me. Everytime I install your boot.img my phone stops frequently for a second even sometimes more than 10 seconds. While I am trying to use any root browser (Es, Solid, Root Browser) when they try to use root access from SuperSu phones free ram downs to 300MB even 20MB sometimes. This is my 4. Clean flash with;

*Flash EU Rom -> Flash SuperSu Stable -> Wipe Data, Dalvik, Cache -> Boot until get home screen -> flash boot.img

But still my phone gets lagging with the image.

Edit: I will disable zram and try again.
[Redmi Note 2 Android Development] Sleepy_Augie:
[MENTION=5952980]jajk[/MENTION] I'm using that recovery, and I repaired data just in case. I'll try a sp flash of a full stock rom (maybe there's a factory issue clean slate one somewhere, idk) in the next few days. I might have done a spotty job last time, so I'll make sure to flash all of the partitions this next time around.
[Redmi Note 2 Android Development] Deic:
[MENTION=5952980]jajk[/MENTION] may create a Github project with the stock boot.img unpacked & a bash script with the lines to do it skinny. ex. of project directory:

---------------------------

/miui7/ <- unpacked stock miui 7 boot.img

/miui8/

build_miui7.sh <- script to modify stock miui 7 boot.img & build it

build_miui8.sh

----------------------------

Then

git clone https://github.com/owner/project.git
cd project
./build_miui*.sh

It would be helpful to colaborations
[Redmi Note 2 Android Development] acestars:
I am using xposed v86 by solarwarez since it released. I have really weird behavior woth my phone.

Before upgrade i have miui global 7.0.12 with xposed v86 by solarwarez and some modules that working flawlessly.

I upgraded to miui 8.0.10 and installed xposed v86, skinny pro, etc. With same modules like before upgraded i got random reboot so i flash miui 7.0.12 back and restore same applications like before upgraded but strangely i still got random reboot because some xposed modules. Really weird this miui, smh.
[Redmi Note 2 Android Development] jajk:
Skinny_Pro_MIUI7_7140_boot.img uploaded which replaces all previous versions of 7140. It has been updated to be inline with all other current variants.
[MENTION=5850987]DarthJabba9[/MENTION] Just finished loading MR 7230 from backup and updating apps & scripts etc. Give it another month or so and I might release it as the new and improved MIUI9:laugh::laugh::laugh:

[MENTION=4476591]Deic[/MENTION] Why? We are just editing a bunch of scripts here, not rewriting code so complexity doesn't really warrant Github.

[MENTION=7260255]Brkge[/MENTION] I wish I knew what is going on with the few reports of this type of behavior. Maybe it is what ROM you are coming from rather than what ROM you are loading since only a factory ROM installed through SP Flash will create all partitions correctly. You can TWRP away to your hearts content but never fix the multitude of supporting partitions if they are wrong for the ROM you are moving to. Maybe you have had a CM or AOSP ROM installed and not since then reinstalled a full factory ROM? I can only guess at this so if you solve it, please let us know what the deal is so others can help themselves.

[MENTION=3885679]acestars[/MENTION] Same deal, you have got to look at the logic of the situation and ask what is being left behind? It will be one of the lower level partitions like preloader, uboot or even logo that is updated but not down-dated when you go back to a previous ROM. Later MIUIs have really been stuffing around with these partitions that have no reason to change.
[Redmi Note 2 Android Development] DarthJabba9:
[MENTION=5952980]jajk[/MENTION] Looking forward to your MIUI9! ;)
[Redmi Note 2 Android Development] Deic:
[MENTION=5952980]jajk[/MENTION] idk what exact changes there are between stock boot.img & your skinny one and is hard to can colaborate here, so a Github repo would amazing to have for this. If not, I will create a repo with my concept, but it wouldn't the best option...
[Redmi Note 2 Android Development] Brkge:
[MENTION=5952980]jajk[/MENTION] Actually I flashed 8.0.1.0 global stable fastboot fastboot rom with Sp Flash Tool and wiped Data+System+Cache before flashing EU rom which is disaponting to have a problem. Then I tried your boot image but the problem with SuperSu which It does not give root access Screen was there even on the first boot. Then I flashed 6.8.18 global dev fastboot (I tought maybe stable rom isn't compatible with root) with Sp Flash Tool before flashing 8.0.1.0 EU and had same problems. Tried flashing It with lots of different combinations (It killed me becouse It took my 6pm to 7am. I slept 3 hours after that.) but every time had different problems :D. At last I had the most stable combination which is Free ram is 1 gb ram and supersu is stable. The problems I had/have:

•Music and videos stops playing for 2 seconds in every 30-60 seconds.

•Sometimes phone lags and If I am typing It types after 3 seconds of waiting. If I am deleting... (Still facing this)

•If I am downloading something from Play Store It downloads to the %100 then wait there (If I am lucky). But I don't have the problem now.

•If I am unlucky even if I am signed in to my google account. Play store says authentication required please sign in to your google account and doesn't let me download. I got rid of It with Deleting my google account several times. I was lucky..

I will do several tests this night and see If I can fix the lagging or Media stops.

Edit: Phone lags and media kills are related when phone continues responding music stops.
[Redmi Note 2 Android Development] DarthJabba9:
This is straightforward. Unpack the stock boot image to one directory, and unpack the skinny boot image to another directory, and run "diff" on them - e.g.,

diff -U3 -d -w -rN stock-boot-ramdisk/ skinny-boot-ramdisk/

This will tell you all the differences between the stock ramdisk and the skinny ramdisk.
[Redmi Note 2 Android Development] jajk:
[MENTION=4476591]Deic[/MENTION] Edits are in plain view and [MENTION=5850987]DarthJabba9[/MENTION] suggestion is an easy way to see what has changed. Many have already contributed to developing the skinny images and even more have taken parts of it and applied it to their own projects. It is all open and free for the taking - participate here or create your own platform - I don't really care. I take plagiarism as a compliment and derive some amusement from it otherwise I would shut down my threads:)

[MENTION=7260255]Brkge[/MENTION] Your report is so similar to what a minority of others report but the majority do not have these problems. I can only conclude it is something that a small group is doing differently to everyone else.

Tell me that

Xposed has not gone anywhere near the phone

at this stage, that you have

updated busybox

, you are running the example init.d script

exactly as provided

, you have not reinstated apps using

Titanium Backup

and that you have installed Gapps

separately

and after the ROM install? It will be a seemingly minor difference in what you do that is causing the problem.

[MENTION=5850987]DarthJabba9[/MENTION] Experiment over, back to 7550 but I now have a fresh and updated 7230 backup to fall back on when I spit the dummy with what I have;)
[Redmi Note 2 Android Development] DarthJabba9:
My freshly installed 7230 (clean install) is performing wonders so far - with 100 apps restored with Titanium, I've had 98% deep sleep overnight (and I haven't even skinnyfied it yet). The 8.0.1.0 ROM could never come anywhere near this, even after the most intense skinnying. Will skinnify 7230 and run for a few days, and then make up my mind. Perhaps the secret is to start with a clean install, which I haven't done with 8.0.1.0.
[Redmi Note 2 Android Development] jajk:
[MENTION=5850987]DarthJabba9[/MENTION] Heretic! You must praise Xiaomi and feel like something wonderful is about to happen. MIUI8 is everything to everyone including those with split personalities and remember - your phone may contain traces of Samsung parts (or not):eek:
[Redmi Note 2 Android Development] redbird88:
Yes, i had the folder without having to create it.
[Redmi Note 2 Android Development] DarthJabba9:
:p TBH, I am now convinced that each new release just increases the resource overheads, therefore reducing battery life and free memory, while not giving much back in return. The eye opener was applying the latest 714 skinny pro boot image to the wife's phone, and finding myself wondering why I ever "upgraded" from 7230. My conclusion: let us find out we can skinnify 7230 even more, coupled with whatever benefits can be obtained from newer kernel releases (e.g., can we add the kernel of 7550 to the ramdisk of 7230 - assuming that the newer kernels actually improve anything)
[Redmi Note 2 Android Development] redbird88:
The file was created as expected.
[Redmi Note 2 Android Development] panzerpig:
Im thinking the same. I have skinnified 6.8.4 and its good, get 4+ hours SOT. But i remember that MIUI 7 was better, the roms I used a year ago. (MIUI 7-7.1?). Seems MIUI 8 is more bloated than 7.
[Redmi Note 2 Android Development] acestars:
I stuck at miui global 7.0.12. So which miui version is better of all?
[Redmi Note 2 Android Development] DarthJabba9:
I can only remember back to 7.2.30 ID, which seems perfectly fine to me, compared with all the later ones. IF your 7.0.12 serves your purposes and gives you good battery life, you might as well stay with it. The issue for us retros, though, is that Skinny Pro Boot development has ceased on anything earlier than 7.5.x - but if we ask [MENTION=5952980]jajk[/MENTION] very nicely, he might continue! :highfive:
[Redmi Note 2 Android Development] Brkge:
[MENTION=5952980]jajk[/MENTION] I made so many flashes and I did and didn't install xposed before boot.img, I did and didn't install the busybox you provided before boot.img, I never used Titanium Backup and I never Installed Gapps after the EU rom (I once did months ago on to MIUI8 Beta and It didn't even let me choose language. It stuck there every time. I tought It wasn't compatible with Gapps on to It already owns.) But I can't promise which combinations gave which results. I gave up for now and I will Install sMIUI for a little time untill I have free time to test these. I need to use Whatsapp and I have to listen music :D

So I have to Flash (Xiaomi.eu+OpenGapps+SuperSu+BusyBox) then Wipe (Data+Dalvik+Cache) then boot system before Installing the Boot image. Thanks will test but can't Promise :) already spent hours without my daily drive.

Edit: Also I need to know If I can use busybox from Play Store. Once heard that busybox is not for MIUI.
[Redmi Note 2 Android Development] DarthJabba9:
This is the process that I follow;

1. Boot to TWRP recovery

2. Wipe Data + Dalvik + Cache

3. Flash ROM (having first

edited the ROM's updater-script

to make sure that it

doesn't

install any of busybox, or gapps, or supersu, or preloader, or uboot/lk, or logo)

4. Reboot ROM (to make sure it boots) - don't allow TWRP to root

5. Boot to TWRP recovery

6. Flash opengapps + supersu + busybox

7. Reboot ROM (to make sure it still boots)

8. Reboot to TWRP recovery

9. Flash busybox
[Redmi Note 2 Android Development] Brkge:
[MENTION=5850987]DarthJabba9[/MENTION] It looks like the cleanest way but I don't know what files Gapps or SuperSU also BusyBox have so I can't delete them. EU rom might have them in /system/app so I can't clean them out. But have to check so thanks :D
[Redmi Note 2 Android Development] DarthJabba9:
You don't have to delete anything. You just need to edit updater-script before installing the ROM, and to comment out the lines installing gapps, supersu and busybox. The relevant lines are usually at the end of the updater-script - eg
[Redmi Note 2 Android Development] Brkge:
[MENTION=5850987]DarthJabba9[/MENTION] Thanks! This investigating Rom file taught me so many things. Now I can export Viper4Android which is the main reason why I use the sMIUI. I tried so many things to install Viper to my MIUI before. Now I can export the drivers :D
[Redmi Note 2 Android Development] DarthJabba9:
:good:
[Redmi Note 2 Android Development] Brkge:
[MENTION=5952980]jajk[/MENTION] Installing GApps after EU rom doesn't work. It changes the first boot setup's change language screen to a blueand I can't skip It. It says "Unfortunately, Settings has stopped."

Nevermind, I will try finishing the setup then flash GApps then test It.
[Redmi Note 2 Android Development] jajk:
[MENTION=7260255]Brkge[/MENTION] The routine that [MENTION=5850987]DarthJabba9[/MENTION] is exactly what I recommend. Best of luck next time:)

Installing Busybox does not need a resident app unless you like consuming resources and downloading ads. MIUI already has busybox installed but it is very outdated and not the full set of commands hence my recommendation to update it to at least 1.24-1.

[MENTION=3885679]acestars[/MENTION] I note quite a few people sit on 7.0.12 and think it is the most stable - never tried it so can't comment on that but you are probably right. In the later ROMs up to 7.3.20, we get some nicer features but it is only sugar-coating. The down side is that overheads also increase.

7.1.4 is the best kernel for anything up to 7.2.30 - everything after it became noisier (more background processes) and started including all the RN3 junk for fingerprints and locked bootloaders which made them heavier.

Skinny 7140 is up to date with the rest and if there are any improvements discovered for later versions that still apply, I will add them back to this image;)
[Redmi Note 2 Android Development] jerryshaw12:
What Rom did you use? MR/EU/China/Global?
[Redmi Note 2 Android Development] DarthJabba9:
This: http://www.needrom.com/download/miui-7-2-3-0-redmi-note-2/

I use open gapps pico, UPDATE-SuperSU-v2.76-20160630161323.zip, and my own build of busybox 1.2.50 (which also installs bash).
[Redmi Note 2 Android Development] DarthJabba9:
Skinny_Pro_MIUI7_7140_boot.img on MR-7230 ID: after streaming YouTube videos non-stop via wifi for 5 hours, with bright screen (50%) and bluetooth running, sending a few texts and emails, I have 30% battery left. That's what I call a result. I'll see how long it takes the battery to get down to 5%.
[Redmi Note 2 Android Development] vetriolo:
What about to create a flashable zip with your ROM? :angel::D:angel:
[Redmi Note 2 Android Development] DarthJabba9:
I always do that as a matter of course, in case I need a fresh install if TWRP backups fail. However, to make it freely available usually means having to support it - which I don't have the time for. If I get firm promises that I won't be asked any questions, about why this, or that, or the other, is happening (or not happening), then I might be persuaded to make it available.
[Redmi Note 2 Android Development] jajk:
On the theme of skinny things.....

I like to strip out support for non-arm64 devices wherever possible since I am not about to buy a MIPS, x86 or even Armv4,5 or 7 based phone anytime soon. Here is SuperSU2.78 in its Skinny form for anyone interested.

https://drive.google.com/open?id=0BwdRTuyj12_yQ1ozc0VYazRCQlU
[Redmi Note 2 Android Development] vetriolo:
For me it's ok.

I can skinnify my roms but I can't manage boot.img and scripts...
[Redmi Note 2 Android Development] DarthJabba9:
Ok, here it is: https://mega.nz/#!j48WjKDS!fK1fjftNwZvw4uvmYFFpSXq9ke72BL4Uz_a1d4sGIMk

Ask me no questions, and I won't have to ignore your questions. :cyclops:
[Redmi Note 2 Android Development] DarthJabba9:
And here is an installer of my version of the Skinny Pro 7140 boot image. This needs to be installed after the skinny ROM has booted successfully - then you can reboot to TWRP and install this one.
[Redmi Note 2 Android Development] vetriolo:
Thanks!! I will Download it and I 'll try it (after a nandroid backup). If I don't like I simply restore my nandroid....
[Redmi Note 2 Android Development] DarthJabba9:
Good idea. Just remember, before installation, to wipe data if you're not already on a global 7230 multirom (the installer will wipe cache + dalivk-cache; but there is no harm in wiping it yourself).
[Redmi Note 2 Android Development] jajk:
Anyone thinking they have lags in SuperSU and have installed the zip version of SuperSU via TWRP consider the following:

Skinny boot images disable the factory entry that starts the Su daemon from init.miui.rc. The reason for this is that when you install SuperSU, it puts a script in init.d called 99SuperSUDaemon which duplicates the setting found in init.miui.rc. Why do the same thing twice?

The functional difference is that Skinny's implementation of init.d support purposely delays init.d until boot is completed therefore the Su daemon is started very late in the grand scheme of things. Whether or not this can cause perceived lags in getting Su rights is a bit of an unknown and would only apply to the first few seconds after a boot completes. Starting the Su daemon from init.miui.rc will establish it much earlier in the boot process.

Anyone that wants to test if there is a difference,

delete

/etc/init.d/99SuperSUDaemon and then enable the following lines in /init.miui.rc (requires unpack/repack of boot.img)

service for su
service su_daemon /system/xbin/su --daemon
class main
oneshot

If there is a benefit in this change, I will re-enable this in future skinny images but the responsibility falls back on the user to delete 99SuperSUDaemon to prevent the re-assertion at a later point.

Report back please stating ROM and SuperSU version
[Redmi Note 2 Android Development] jerryshaw12:
Whoa thank you for explaining, i think you should re-enable it, also why sometimes downloading apps through play store stuck at 100% ?
[Redmi Note 2 Android Development] jajk:
[MENTION=6150156]jerryshaw12[/MENTION] I think I should not re-enable it unless I get confirmation that it causes a problem under certain circumstances. I am asking those that can do the change for themselves to do just that and report back. It will only ever effect the issuing of root rights by SuperSU immediately after boot - nothing else. I have never had a problem with it which is why I am casting this out to a wider group - maybe I don't have the apps or settings that trigger the problem (if there is one at all)