yashsingh1/xdaforums huggingface dataset:
[Redmi Note 2 General] jajk:
[MENTION=7123834]H0Odini[/MENTION] Yes, I need sufficient information to help anyone or a working telepathy connection if insufficient information provided;)

See attached.
[Redmi Note 2 General] DarthJabba9:
New appearances in 7.3.23 (xiaomi.eu):

/system/priv-app/MiuiVideo (moved from /system/app/)

/system/priv-app/QuickSearchBox (moved from /system/app/)

/system/app/HybridPlatform

This is also /system/priv-app/CloudServiceSysbase, which appeared sometime after 6.11.10
[Redmi Note 2 General] gdeliana:
Hello everyone,

I am trying to make my own skinny, but when the system boots up it does not show the welcome screen and home button and recents button do not work. I remember that these buttons are somehow related to lockscreen and security, but i have security and miuikeyguard apk. What is missing here??
[Redmi Note 2 General] abs0lut3z33r0:
Anyone tried this on Mi5 Miui8 Global ROM . I have freezed a lot of apps and uptil now most core functionality is working correctly like spaces , dual apps , permissions. I don't want to get over ambitious with optimizations because it always end up breaking something on android. Could anyone share their experiences with Mi5?
[Redmi Note 2 General] Iliyena:
You could tell which app and then go look at the threads "Best SOT by far!" (Skinnied ROMs to start over from): https://xdaforums.com/redmi-note-2/development/best-sot-t3434915/page142 and then the thread by jajk, OP in this thread "Skinny Pro Custom Boot images" https://xdaforums.com/redmi-note-2/development/b-skinny-pro-t3347906/page179

To what use do you need all apps gone? This is an "old thread"
[Redmi Note 2 General] Iliyena:
Very special case here ;) Sorry for assuming you had a RN2. Weird issues with that RN4 :(
[Redmi Note 2 General] DarthJabba9:
This is not correct. There are MM-based custom ROMs for RN4 (Mido). IDK about Nikel.
[Redmi Note 2 General] DarthJabba9:
There are at least three:

https://xdaforums.com/redmi-note-4/...pment/quarkos-v3-0-stable-unofficial-t3636040

https://xdaforums.com/redmi-note-4/...ent/rom-flyme6-7-6-23r-weekly-update-t3629247

https://xdaforums.com/redmi-note-4/...elopment/rom-unofficial-lineageos-13-t3607847
[Redmi Note 2 General] DarthJabba9:
Those statements are meaningless. These ROMs are based on LOS, as are most custom ROMs, regardless of which project/company/group/person is developing/releasing them. And they

are

ROMs for RN4. You did say: "

all roms for redmi note 4 are nougat ones

". That statement is patently not correct. If you wish to qualify it now, that is perfectly fine. However, contrary to your initial statement,

there actually are

MM-based ROMs for the Snapdragon RN4. It is immaterial who is right or wrong - but facts are facts.
[Redmi Note 2 General] DarthJabba9:
100% to 0% battery drain overnight is quite abnormal on

any

ROM, and I wouldn't have thought that stock miui app bloat was the real problem. So I think you first need to ascertain what exactly is responsible for your battery drain. GSAM Battery Monitor should show where the real problem lies. Removing non-essential apps should not cause a bootloop - unless there is another problem. But you have not explained how exactly you have been trying to remove the apps. Such details might reveal why you are getting a bootloop.
[Redmi Note 2 General] jajk:
[MENTION=6023270]mali_[/MENTION] Clear cache and dalvik cache in TWRP after deleting each group of a few apps or use SDMaid to delete what it calls corpses. That might solve your problem if it is not caused by deleting something needed. TWRP backups after each proven successful boot take the hard work out of the process;)
[Redmi Note 2 General] DarthJabba9:
[MENTION=5952980]jajk[/MENTION] has given the best tip. It is possible that "skynet" has now bound things very tightly together, such that removing one thing will break everything - and this may be deliberate. I had issues with MM-based miui ROMs on the RN4, involving bootloops everytime I tried to flash a boot image with a modified ramdisk. Restoring a TWRP backup of the boot partition always resolved that problem. At that point, it was quite clear to me that miui would have to go.

It is also possible that the specific ROM that you are using is compromised. Who supplied it? Did it come with the phone? Who did you buy the phone from?

FWIW, when I was still using miui, the best MM-based ROM I found was MultiPro. It was already slim, had a very decent battery performance, and was silky smooth. My issue was that the identity of the developer was difficult to ascertain. If that is not a problem for you, then perhaps you might want to try it

PS: GSAM should reveal what is causing the biggest drain.
[Redmi Note 2 General] DarthJabba9:
Sorry, but I don't get it. What are you trying on the Nexus 5?
[Redmi Note 2 General] DarthJabba9:
Perhaps stock miui on Snapdragon doesn't take too kindly to tinkering. I can't see why this should be the case, but that was my experience with boot images. Perhaps there are some checksums being verified somewhere, or some hidden dependencies? If so, your only option would seem to be going for a custom firmware.
[Redmi Note 2 General] DarthJabba9:
[MENTION=6023270]mali_[/MENTION] For the RN4, MultiPro is already a bit slim. It can perhaps be made even slimmer, since the developer has already started the process. IDK about miui on Nexus 5 - you may be chasing after the impossible on that one. Perhaps the removable security apps/service should be the first things to be removed/frozen (you can't remove the SecurityCenter). Good luck!

---------- Post added at 05:58 AM ---------- Previous post was at 05:57 AM ----------

[MENTION=6023270]mali_[/MENTION] For the RN4, MultiPro is already a bit slim. It can perhaps be made even slimmer, since the developer has already started the process. IDK about miui on Nexus 5 - you may be chasing after the impossible on that one. Perhaps the removable security apps/service should be the first things to be removed/frozen (you can't remove the SecurityCenter). Good luck!
[Redmi Note 2 General] DarthJabba9:
That may well be the case. It may require patching some apks.
[Redmi Note 2 General] DarthJabba9:
[MENTION=6023270]mali_[/MENTION] You might want to ask the poster in this thread.
[Redmi Note 2 General] Kukouri:
This being updated anymore?
[Redmi Note 2 General] Derickee Medvedev:
THANKS, WORKED ON MY SONY XPERIA Z3c with ported rom MIUI V7.

XMPush solved with step3
[Redmi Note 2 General] emmayazid:
How to enable dual apps setting? I can't enter it. I love to flash back to miupro from aosp rom because i love to use dual apps setting from miui. Pls help me
[Redmi Note 2 General] brasscupcakes:
Does this list still work as of Android Pie and later? Many app names changed...

Wondering because not only do those platforms break more easily but Xiaomi constantly updates its app and package names whenever one of them gets tagged as bloatware. Many thanks!
[Redmi Note 2 General] Al765436:
Does this still work now on miui 12,is it good/safe to delete powersaver and powerkeeper now?
[Redmi Note 2 General] jajk:
[MENTION=399136]anguslaw[/MENTION] I am out of ideas. You did change the locale in build prop?

Maybe someone else who has had this happen to them and figured out why can offer some help?
[Redmi Note 2 General] exiacruzalta:
Well I use the pre-made boot.img too but did not remove the listed apps from my rom yet, only do the init.d tweak. I tried syncing just now and it works so i think maybe some apps removed cause something cause only that part i dont do yet. last time my synce fail because i remove soma apps with google and transport in its name
[Redmi Note 2 General] DarthJabba9:
Actually, I have just discovered that it doesn't work here either! :(
[Redmi Note 2 General] exiacruzalta:
This is the code I use, if it could help you in any way

#Init.d support
service run-parts /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
busybox run-parts /system/etc/init.d
class main
user root
group shell
oneshot
#end
[Redmi Note 2 General] anguslaw:
Hi may I know How To change the locales in buildprop? And change from what to what? Thanks.
[Redmi Note 2 General] anguslaw:
Hi, Jajk, I started to think it might be the problem of the gapps, then I go to open gapps and download and install the mini version instead. Then the sync problem is solved. Sorry for the inconvenience caused. The sync problem is not related to your tutorial , it's related to the gapps.

However, on the other hand, I still cannot use the xda premium app, it just force closes once opened. Anyway, I can live with it.

Thanks again!
[Redmi Note 2 General] jajk:
[MENTION=7287632]exiacruzalta[/MENTION] and [MENTION=5850987]DarthJabba9[/MENTION] init.d support works fine with the command as it is written providing you have busybox installed in the xbin folder which is the case in the premade boot.img.

You have just repeated the command a second time and there is no need to rename the service to run-parts - that is not the command - just a label for the service.

The basic script should be as follows:

#Add init.d support

service runparts /system/xbin/busybox run-parts /system/etc/init.d

class main

user root

group shell

oneshot

[MENTION=399136]anguslaw[/MENTION] Glad you solved the sync issue, maybe not all open Gapps work since they are rebuilt regularly. In /system/build.prop change these lines to suit:

ro.product.locale.language=zh

ro.product.locale.region=CN
[Redmi Note 2 General] cafezeenuts:
I'm about to make my redmi note 2 skinny, i have 2GHz version. For stage 2 is this how i type it in for 01_tweaks?

#!/system/bin/sh

# Tweak Interactive CPU Governor
echo 806000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
# echo 90 403000:75 806000:81 1183000:84 1326000:87 1469000:90 1625000:93 1781000:96 1950000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 40000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo 20000 > /sys/devices/system/cpu/cpufreq/interactive/above_highspeed_delay
echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
# echo 1781000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# echo 1781000 > /proc/cpufreq/cpufreq_limited_max_freq_by_user

# echo 1 > /proc/hps/num_limit_low_batt
# echo 8 > /proc/hps/num_limit_power_serv
# echo 4 > /proc/hps/num_limit_thermal
# echo 2 > /proc/hps/num_limit_ultra_power_saving

echo deadline > /sys/block/mmcblk0/queue/scheduler ## choose between cfq, bfq or deadline
# echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle ## Enable this line if using cfq or bfq scheduler only
echo 256 > /sys/block/mmcblk0/queue/read_ahead_kb

echo 300 > /proc/sys/vm/dirty_expire_centisecs
echo 500 > /proc/sys/vm/dirty_writeback_centisecs
echo 536870912 > /sys/block/zram0/disksize ### 536870912 = 512MB, 1073741824 = 1GB
# /system/bin/tiny_mkswap /dev/block/zram0
# /system/bin/tiny_swapon /dev/block/zram0

echo 512 > /proc/sys/kernel/random/read_wakeup_threshold
echo 1024 > /proc/sys/kernel/random/write_wakeup_threshold

#echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6 ## Enable if you have connection issues with wifi routers

# fstrim /data
# fstrim /data
# fstrim /system

Cheers
[Redmi Note 2 General] exiacruzalta:
I know, and i do install busybox into xbin many times and many types, but i dont know why i doesnt work until i did what i did. Magic perhaps? ;)
[Redmi Note 2 General] jajk:
[MENTION=2771703]cafezeenuts[/MENTION] Delete the # that I have shown in bold. Anything after a # is not processed on that line and this line needs to happen.

That script will work with that one change and needs nothing else until after the skinny process.

Uncomment (remove the # character) on the fstrim lines once your install is stable. Run the script and then recomment those lines. It is not necessary to run fstrim more than once a month.

#!/system/bin/sh

# Tweak Interactive CPU Governor

echo 806000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo 85 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

# echo 90 403000:75 806000:81 1183000:84 1326000:87 1469000:90 1625000:93 1781000:96 1950000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads

echo 40000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

echo 20000 > /sys/devices/system/cpu/cpufreq/interactive/above_highspeed_delay

echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack

# echo 1781000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# echo 1781000 > /proc/cpufreq/cpufreq_limited_max_freq_by_user

# echo 1 > /proc/hps/num_limit_low_batt

# echo 8 > /proc/hps/num_limit_power_serv

# echo 4 > /proc/hps/num_limit_thermal

# echo 2 > /proc/hps/num_limit_ultra_power_saving

echo deadline > /sys/block/mmcblk0/queue/scheduler ## choose between cfq, bfq or deadline

# echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle ## Enable this line if using cfq or bfq scheduler only

echo 256 > /sys/block/mmcblk0/queue/read_ahead_kb

echo 300 > /proc/sys/vm/dirty_expire_centisecs

echo 500 > /proc/sys/vm/dirty_writeback_centisecs

echo 536870912 > /sys/block/zram0/disksize ### 536870912 = 512MB, 1073741824 = 1GB

# /system/bin/tiny_mkswap /dev/block/zram0

# /system/bin/tiny_swapon /dev/block/zram0

echo 512 > /proc/sys/kernel/random/read_wakeup_threshold

echo 1024 > /proc/sys/kernel/random/write_wakeup_threshold

#echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6 ## Enable if you have connection issues with wifi routers

# fstrim /data

# fstrim /data

# fstrim /system

[MENTION=7287632]exiacruzalta[/MENTION] Yes magic. I know I have problems with the sysinit way of providing init.d support and I can sort of see why this is when looking at a logcat. It is all about the sequence things get done during the boot process. It may be more reliable to delay the start for this service. I will dig up the syntax for that and try it.

Success invariably depends on the system partition provided by you so the magic is all yours;)
[Redmi Note 2 General] DarthJabba9:
Ha! A repeat of the command! I will try it tonight. Thanks.
[Redmi Note 2 General] DarthJabba9:
[MENTION=5952980]jajk[/MENTION] I have busybox installed in /system/xbin - exactly the same place as it has always been!
[Redmi Note 2 General] jajk:
Repeating the command is pointless. Do you think Android just ignores it the first time like a naughty child:confused:

Everyone should have no init.d support if the original script is wrong - that is not the case so there is something about your installation upsetting it.

You could elevate the importance of the script by doing something like this if you really feel it necessary?

service runparts /system/xbin/busybox run-parts /system/etc/init.d

class core

critical

user root

group shell

oneshot
[Redmi Note 2 General] DarthJabba9:
You are right that repeating the command is pointless. From my prior experience, using run-parts is not always reliable, although it should be. I have changed that part of the mod to one that I had working last December. It is slightly more involved than your mod, because it involves creating a couple of scripts to carry out what run-parts should do - and manually running the scripts in init.d, with a small delay before each

for FILE in /system/etc/init.d/*; do
sleep 1
sh $FILE >/dev/null
done;

This seems to work all the time, and is not dependent on the busybox version.
[Redmi Note 2 General] jajk:
[MENTION=5850987]DarthJabba9[/MENTION] Now you're on the right track - that is a straight replacement for run-parts but not using busybox.

If you look at a logcat, you will notice that things are not always executing in the same order which is why, in my view, we get some strange events like init.d support not being initiated or some random tweaks being reverted to stock settings. Example: There are around 3 scripts in the boot.img that all mess with the Interactive governor files - for your tweaks to take hold, your scripts really need to run last.

There is a late_start syntax but even then, there are other late starters so who is going to be the latest to start?
[Redmi Note 2 General] cafezeenuts:
[MENTION=5952980]jajk[/MENTION] Thanks for the reply, everything seems to be working except each time i reboot i have "Unfortunately, NetworkLocation has stopped" working message. And also in google play store when i touch the "read more" on apps page it crash and "Unfortunately, Google Play Store has stopped." message. But i still can install apps like normal.

Cheers
[Redmi Note 2 General] jajk:
[MENTION=2771703]cafezeenuts[/MENTION] Wipe dalvik and cache in recovery before doing anything else.

Have you used something like SD Maid to delete corpses (orphaned files) left behind by the skinny process?

Check that apps haven't reappeared - if so, delete again, reboot and delete corpses.

You should not suffer any FCs once the process is complete but you will get Settings spit you out if you go to a menu for something that no longer exists.
[Redmi Note 2 General] cafezeenuts:
[MENTION=5952980]jajk[/MENTION]

Yes I have deleted.

Try that didnt work for play store "read more" on apps page it crash and "Unfortunately, Google Play Store has stopped." message.

But i did manage to get rid of "Unfortunately, NetworkLocation has stopped" working message. by freezing it in SD Maid.

I'm using open_gapps-arm64-5.0-pico-20160219.

Cheers
[Redmi Note 2 General] DarthJabba9:
initd is set to run "on property:sys.boot_completed=1". I am not sure whether this means that it runs last, but it seems to work ok, and it was the only way in which I could get initd to work reliably when I was working on it last year.
[Redmi Note 2 General] jajk:
[MENTION=2771703]cafezeenuts[/MENTION] Someone else had a problem with open gapps pico that was solved by installing open gapps mini. I run pico without problem but the build predates your version. I think that some builds may be dodgy.

The removal of (Baidu) Network location is difficult as it keeps trying to re-assert itself. Chinese Government, oops, sorry Xiaomi is obsessed with knowing your every move:(

You have to hunt down and delete baidu files and folders from several places to fully kill it. I should have recorded that process but gotta leave a bit of frustration for everyone else;)

[MENTION=5850987]DarthJabba9[/MENTION] on property:sys.boot_completed=1 may be a useful improvement to the script. class late_start could also improve the reliability. I am pondering on the best approach as there is potential for the current init.d script to be executed too early.

A bit of useful reading here:

https://github.com/android/platform_system_core/blob/master/init/readme.txt

Suggestion welcome.
[Redmi Note 2 General] DarthJabba9:
In one of my scripts in /etc/init.d, I introduced a ten second delay at the start of the script. It still did not work. That is when I gave up and returned to my old hack. It has yet to fail, so I suspect that the sys.boot_completed property might be the one to target (nothing else uses it in the ramdisk)- perhaps coupled with late_start, just to be doubly sure.
[Redmi Note 2 General] jajk:
Found this description that tends to indicate class late_start is better than class main and class core is out of the question.

Service classes of Init:

class core – Always started first and cannot be shut down without serious consequences in most cases

class main – Responsible for services like telephony, radios, critical sensors. Many can be restarted or paused at certain times, but only if absolutely required

class late_start – Happens right before the full system boots and starts becoming available to the user. Stuff that relies on /data will usually have to start here to avoid issues on encryption

This change may be all that is needed. I am testing now but it will be hard to tell if it fixes anything on my phone as I already had a reliable init.d.

Anyone having init.d problems want to test if changing the class main line to class late_start cures their problems???
[Redmi Note 2 General] DarthJabba9:
I will test it. I am just re-downloading your original custom image now ...

Edit: unfortunately, it does not cure the problem.

---------- Post added at 01:14 PM ---------- Previous post was at 12:48 PM ----------

This is the diff for my manual mod (not original - I found the details on the net sometime last year):

diff -U3 -d -w -rN ramdisk.org/init.initd.rc ramdisk/init.initd.rc
--- ramdisk.org/init.initd.rc	1970-01-01 01:00:00.000000000 +0100
+++ ramdisk/init.initd.rc	2015-12-26 22:20:30.246122807 +0000
@@ -0,0 +1,17 @@
+# darthjabba - init.d support #
+# chmod 0750 init.initd.rc
+
+chown root root /sbin/sysinit.sh
+chmod 777 /sbin/sysinit.sh
+
+service sysinit_d /sbin/sysinit.sh
+class main
+user root
+disabled
+oneshot
+
+on property:sys.boot_completed=1
+ start sysinit_d
+
+# end - darthjabba #
+
diff -U3 -d -w -rN ramdisk.org/init.rc ramdisk/init.rc
--- ramdisk.org/init.rc	2015-12-26 22:09:43.258126591 +0000
+++ ramdisk/init.rc	2015-12-26 22:17:45.346123771 +0000
@@ -9,6 +9,9 @@
import /init.${ro.hardware}.rc
import /init.${ro.zygote}.rc
import /init.trace.rc
+# darthjabba - initd #
+import /init.initd.rc
+# darthjabba
import /init.miui.rc
import /init.storage.rc

@@ -478,7 +481,6 @@
chown system root /sys/class/input/input9/mag_hard_offset
chmod 0660 /sys/class/input/input9/mag_hard_offset

-
# Define default initial receive window size in segments.
setprop net.tcp.default_init_rwnd 60

@@ -761,3 +763,4 @@
class main
oneshot
# add by GOODIX for finger print end
+
diff -U3 -d -w -rN ramdisk.org/sbin/sysinit.sh ramdisk/sbin/sysinit.sh
--- ramdisk.org/sbin/sysinit.sh	1970-01-01 01:00:00.000000000 +0100
+++ ramdisk/sbin/sysinit.sh	2015-12-26 22:26:14.318120794 +0000
@@ -0,0 +1,9 @@
+#!/system/bin/sh
+# darthjabba; init.d support #
+export PATH=${PATH}:/system/bin:/system/xbin
+cd /data/local/tmp/
+for FILE in /system/etc/init.d/*; do
+ sleep 1
+ sh $FILE >/dev/null
+done;
+
[Redmi Note 2 General] jajk:
[MENTION=5850987]DarthJabba9[/MENTION] I can't fault the original, using late_start or on property:sys.boot_completed=1 on my phone so I am leaning towards the following as a way of postponing init.d scripts running till the very latest.

#Add init.d support

service runparts /system/xbin/busybox run-parts /system/etc/init.d

class main

user root

group shell

disabled

oneshot

on property:sys.boot_completed=1

start runparts

Since you seem to have a repeatable problem using run-parts, can you try this version out and report back? It is interesting that including a mkdir /system/etc/init.d in init.rc does not work. I'll try putting it after a on property:sys.boot_completed=1 to see if that makes a difference.
[Redmi Note 2 General] cafezeenuts:
[MENTION=5952980]jajk[/MENTION] Haha no worries. I think i can live with that small bug on play store. I will use it for a week and try the mini gapps next week. Cheers
[Redmi Note 2 General] jajk:
I have posted an updated boot.img. SELinux is set to permissive in this one. If you don't want to be permissive, unpack boot.img, delete the line in init.rc setenforce 0 or change it to setenforce 1 and repack. Not working in init.rc but works putting setenforce 0 in init.d script:confused:

There is talk around of this fixing some Google Apps FCs when based on a Chinese Kernel. I don't have the problem so someone will hopefully tell me if this is the case or not.

Other changes: Updated init.d support method to make it more reliable and further weight loss included.

http://xdaforums.com/showpost.php?p=65262314&postcount=18

[MENTION=2771703]cafezeenuts[/MENTION] Glad to hear you are getting it sorted. Did you go into SD Maid Settings/CorpseFinder and tick the extra boxes? The above may apply to you.
[Redmi Note 2 General] cafezeenuts:
[MENTION=5952980]jajk[/MENTION] Yes i have gone into SD Maid Settings/CorpseFinder and tick all the boxes. It didnt help my play store fc bug. I'll try your new boot img and in stall mini gapps instead of pico new week. Cheers