yashsingh1/xdaforums huggingface dataset:
[Redmi Note 2 Android Development] Iliyena:
Thats... low multicore actually, 3000 is more like it for me. I have downloaded Geekbench 3 separately and made a clone to install. I like GB3 better, quicker results to small changes and then I do a Geekbench 4 run now and then to confirm the results ;)
[Redmi Note 2 Android Development] acestars:
I cant find Geekbench 3 in gplay so wanna share it to me?
[Redmi Note 2 Android Development] Iliyena:
Apk mirror^^
[Redmi Note 2 Android Development] jajk:
[MENTION=3885679]acestars[/MENTION] I think the different core handling is more about multitasking than outright performance. Cpu control is separated into background non-interactive (hidden), foreground and foreground limited categories now (foreground limited being a completely new category). Make sure you are not limiting cpu core number or freq in your init.d script when doing a benchmark as ~3000 is typical in Geekbench 3 as [MENTION=7442305]Iliyena[/MENTION] mentioned.

I am forcing myself to use 8.5.20 to see if I can beat it into submission with some recompiling of framework and system apps. The holy grail is to reinstate the ability to stop undesirable services - any revelations to this effect are welcome;)
[Redmi Note 2 Android Development] acestars:
[MENTION=5952980]jajk[/MENTION] I already set to max freq and max core in init.d maybe the lower value caused by too many background apps i have :D

Maybe to defeat the unstoppable services of miui through decompile it but i really lack of knowledge of smali language.
[Redmi Note 2 Android Development] BlayDee:
I'm using skinny Russian one. So I've tried to flash skinny boot before first start and it worked but just for one day... I'm not that advanced to delete gaps myself (did that earlier and got errors everywhere) so I can't check that. Tempted to go back to old boot for a while untill i get some working fix. I've also flashed over with open gaps and force clean, but that didn't help either
[Redmi Note 2 Android Development] jajk:
[MENTION=6280308]BlayDee[/MENTION] They are all Russian ones:laugh: Have you turned off Xunlei download accelerator (china spyware) in Download Manager? That may have an effect on downloading apps.
[Redmi Note 2 Android Development] BlayDee:
Turned that off, and nothing changed, also I started to get a lot of lags where I couldn't even click anything and only option was to hard reset. I've noticed also that some programs are having hard times with getting root access with SuperSU(root explorer, logcats), no popups with accept feature. Now I switched to original boot and everything seems to be "fine", SuperSU an Google play are working as intended. Also I'm using multirom
[Redmi Note 2 Android Development] jajk:
[MENTION=6280308]BlayDee[/MENTION] You have these problems but does anyone else using MR 8520 have similar issues? I installed MR and run skinny boot on it without such issues but I run Gappless.

On an unrelated matter - do you have a working magnetic sensor (compass) with MR ROM? I lost that function on this ROM.
[Redmi Note 2 Android Development] BlayDee:
Nope, doesn't work. Do you think that switching to xiaomi.eu rom would help with those issues? I can give it try but don't really want to go through that whole process again without results. Also can you provide me maybe with gappless rom in any chance?
[Redmi Note 2 Android Development] jajk:
[MENTION=6280308]BlayDee[/MENTION] Maybe mag sensor is also faulty on other ROMs too??? Anyone on EU or other variant having same problem?

Gappless ROM is relatively easy to create if you look in an open gapps zip file you will find a file called gapps-remove.txt. You can manually remove everything you can find in that list or turn it into a script to automate the process. Before you ask.... it has been done before so either search for a pre-made gapps removal script or build it yourself;)

Because of mag sensor not working, I have gone back to trusty old 7550 (again)

P.S. I have (hopefully) ordered a new genuine battery (3rd time lucky) so the RN2 can be promoted back to daily driver in readiness for MIUI9 / Android 7.1.2 release. I so want to believe that something wonderful is about to happen :laugh::laugh::laugh:
[Redmi Note 2 Android Development] vaselor:
[MENTION=5952980]jajk[/MENTION] I've read that Xiaomi doesn't sell genuine replacements, so the best option is buying a Nohon
[Redmi Note 2 Android Development] Reicherd25:
I face this issue also in stable 8.5.2.0 skinny v2 xiaomi.eu version, apps stuck at 100% download but no installing. But its working fine when i revert to stock boot img
[Redmi Note 2 Android Development] dsjiffry:
[MENTION=5952980]jajk[/MENTION]

Hey jajk, I managed to unpack my boot.img and was wondering how to add the core limitations (limit cores to 5) to it???

Do I need to create a new file or add those lines to an exsisting file??
[Redmi Note 2 Android Development] jajk:
[MENTION=5997739]dsjiffry[/MENTION] Find the similar sections in init.rc and / or init.mt6795.rc and modify as shown. Careful there are not conflicting settings in both files;)

# HMP CPU hotplug strategy
chown system system /proc/hps/rush_boost_enabled
chmod 0664 /proc/hps/rush_boost_enabled
write /proc/hps/rush_boost_enabled 0
chown system system /proc/hps/rush_boost_threshold
chmod 0664 /proc/hps/rush_boost_threshold
chown system system /proc/hps/input_boost_enabled
chmod 0664 /proc/hps/input_boost_enabled
write /proc/hps/input_boost_enabled 0
chown system system /proc/hps/input_boost_cpu_num
chmod 0664 /proc/hps/input_boost_cpu_num
chown system system /proc/hps/num_base_perf_serv
chmod 0664 /proc/hps/num_base_perf_serv
chown system system /proc/hps/num_limit_power_serv
chmod 0664 /proc/hps/num_limit_power_serv
write /proc/hps/num_limit_power_serv 5 #<-----set between 2 and 8
chown system system /proc/hps/num_limit_ultra_power_saving
chmod 0664 /proc/hps/num_limit_ultra_power_saving
write /proc/hps/num_limit_ultra_power_saving 5 #<-----set between 2 and 8
chown system system /proc/hps/num_limit_low_battery
chmod 0664 /proc/hps/num_limit_low_battery
write /proc/hps/num_limit_low_battery 5 #<-----set between 2 and 8
chown system system /proc/hps/num_limit_thermal
chmod 0664 /proc/hps/num_limit_thermal
write /proc/hps/num_limit_thermal 5 #<-----set between 2 and 8
chown system system /proc/hps/down_threshold
chmod 0664 /proc/hps/down_threshold
write /proc/hps/down_threshold 90
chown system system /proc/hps/up_threshold
chmod 0664 /proc/hps/up_threshold
write /proc/hps/up_threshold 99
# and.......maybe in init.mt6795.rc
write /dev/cpuset/foreground/cpus 0-4 #<-----set range from 0 to 7 (5 cpus shown)

[MENTION=7117356]vaselor[/MENTION] I have ordered what looks to be a brand new old stock genuine Xiaomi battery but that is not to say that is what will arrive:eek:

[MENTION=7182578]Reicherd25[/MENTION] [MENTION=6280308]BlayDee[/MENTION] I have uploaded v34 image which might fix your problem revert selinux files to stock). This version also has improved scheduler settings;)
[Redmi Note 2 Android Development] Iliyena:
Time to update the OP of the current settings set by boot.img/init.d example? :) (Curious to try whats improved with the Sheduler though I am on CM 12.1)
[Redmi Note 2 Android Development] BlayDee:
[MENTION=5952980]jajk[/MENTION] Found out what was the cause. After I've flashed your new boot.img problem was still the re but I've found out that app named find device kept interfering with play store. After deleting that everything works fine. Thanks for help!
[Redmi Note 2 Android Development] Reicherd25:
It works now, thanks :good:
[Redmi Note 2 Android Development] jajk:
[MENTION=7442305]Iliyena[/MENTION] Here are the improved settings just for you. Rotational is turned off on zram and loops for improved speed.

I set the rq_affinity to 2 to try and reduce the overly liberal use of cores and preserve some battery - this is not for performance.

Note that rotational is still set to 1 for zram and loops even in Android 7.1.2!!! Maybe some people are using hard drives in their phones?

# Set IO Scheduler
# For internal eMMC memory (includes sdcard0)
write /sys/block/mmcblk0/queue/scheduler deadline ### default cfq
write /sys/block/mmcblk0/queue/add_random 0 ### default 1
write /sys/block/mmcblk0/queue/rq_affinity 2 ### default 1

# For ext sdcard (sdcard1)
write /sys/block/mmcblk1/queue/scheduler deadline ### default cfq
write /sys/block/mmcblk1/queue/read_ahead_kb 2048 ### default 128
write /sys/block/mmcblk1/queue/add_random 0 ### default 1
write /sys/block/mmcblk1/queue/rotational 0 ### default 1
write /sys/block/mmcblk0/queue/rq_affinity 2 ### default 1

write /sys/block/mmcblk0boot0/queue/scheduler deadline ### default cfq
write /sys/block/mmcblk0boot0/queue/add_random 0 ### default 1
write /sys/block/mmcblk0boot0/queue/rq_affinity 2 ### default 1

write /sys/block/mmcblk0boot1/queue/scheduler deadline ### default cfq
write /sys/block/mmcblk0boot1/queue/add_random 0 ### default 1
write /sys/block/mmcblk0boot1/queue/rq_affinity 2 ### default 1

write /sys/block/mmcblk0rpmb/queue/scheduler deadline ### default cfq
write /sys/block/mmcblk0rpmb/queue/add_random 0 ### default 1
write /sys/block/mmcblk0rpmb/queue/rq_affinity 2 ### default 1

write /sys/block/zram0/queue/rotational 0 ### default 1
write /sys/block/zram1/queue/rotational 0 ### default 1
write /sys/block/zram2/queue/rotational 0 ### default 1
write /sys/block/zram3/queue/rotational 0 ### default 1
write /sys/block/loop0/queue/rotational 0 ### default 1
write /sys/block/loop1/queue/rotational 0 ### default 1
write /sys/block/loop2/queue/rotational 0 ### default 1
write /sys/block/loop3/queue/rotational 0 ### default 1
write /sys/block/loop4/queue/rotational 0 ### default 1
write /sys/block/loop5/queue/rotational 0 ### default 1
write /sys/block/loop6/queue/rotational 0 ### default 1
write /sys/block/loop7/queue/rotational 0 ### default 1
[Redmi Note 2 Android Development] file015:
I have SKINNY-V2 - MIUI 8.6 Beta 7.6.8-SKINNY-V2 - Release Notes - Xiaomi.eu

Bulid propertry

Existing line in /system/build.prop from:

Ro.mtk_perfservice_support = 1 to ro.mtk_perfservice_support = 0

And Skinny_Pro_8520_Tweaked-v34 instead of boot.

Do I need to do some more scripts that you mention, or is this all that is enough?

Thank you for your help
[Redmi Note 2 Android Development] acestars:
[MENTION=5952980]jajk[/MENTION] did you already tried miui 9 beta? are there any significant changes?
[Redmi Note 2 Android Development] jajk:
[MENTION=3885679]acestars[/MENTION] Just monitoring the impressions across the forums at this stage. Conflicting experiences reported as always so it may have anything from no bugs at all to better off sticking with previous version.

RN2 is no longer my primary phone but I will update Skinny when there is something worthwhile to update. The kernel did not change with the intro of MIUI9, nor did the security update move from 2016 so nothing worthwhile has happened yet (or probably since MIUI 7.1.4)

[MENTION=5730746]file015[/MENTION] If you want to look like a noob, quote the entire O.P. Now read the 2nd line:mad:
[Redmi Note 2 Android Development] acestars:
[MENTION=5952980]jajk[/MENTION] congratulation, you already moved on from RN2 or maybe from xiaomi? so what's your primary phone now for my own reference if i wanna buy new phone or maybe you have some insight?
[Redmi Note 2 Android Development] jajk:
[MENTION=3885679]acestars[/MENTION] Primary phone = Moto G 2013 running AOSP Extended 7.1.2:laugh::laugh::laugh:

RN2 is configured as a tablet (no SIM) and is only used as my GPS Navigator so I don't get lost at sea or put holes in my boat.

I had a Ulefone BT3 for the above purpose but that suffered a horrendous fate after plugging in to a 2.4A charger while the screen was on full brightness and the battery at 10%. The internal charging circuit didn't handle the condition too well and stopped working altogether so now it is a brick.

2017 has been a miserable year so far for new model phones in the tight-ass price bracket - mainly due to the squeeze on supply of 14 and 10nm SoCs hence higher prices charged for budget range. It will come good soon if manufacturers can stay out of court long enough to make something;)
[Redmi Note 2 Android Development] Sleepy_Augie:
[MENTION=3885679]acestars[/MENTION] As another person who moved on from the rn2, my tactic to buying a good phone on the cheap was to look at used top of the line models from around 2015. Better quality, cheap, and usually way better support (I'm on oem supported 7.0).
[Redmi Note 2 Android Development] vaselor:
[MENTION=7150090]Sleepy_Augie[/MENTION] Which phone did you get? Buying old flagships always seemed reasonable to me

Enviado desde mi Redmi Note 2 mediante Tapatalk
[Redmi Note 2 Android Development] Sleepy_Augie:
[MENTION=843780]vaseline[/MENTION] I got a lg v10. Great performance, bad battery life.
[Redmi Note 2 Android Development] vaselor:
[MENTION=7150090]Sleepy_Augie[/MENTION] Battery life is pretty much my only must have spec. But V10 is a nice phone, enjoy it!

Enviado desde mi Redmi Note 2 mediante Tapatalk
[Redmi Note 2 Android Development] Iliyena:
Using the Nexus 5X Interactive tweaks and modifying them a bit and perhaps lowering the used resolution to 1080p should get you a better results then we have with the Redmi Note 2 I'd hoped... Almost bought a used V10 beliving that. It's quite good looking at least ;)
[Redmi Note 2 Android Development] file015:
SKINNY-V2 -> MIUI 8.6 Beta 7.6.8-SKINNY-V2 - Release Notes - Xiaomi.eu is best.
[Redmi Note 2 Android Development] vaselor:
How can I lower my resolution?

Enviado desde mi Redmi Note 2 mediante Tapatalk
[Redmi Note 2 Android Development] Iliyena:
PM soon. Sorry for off topic [MENTION=5952980]jajk[/MENTION].
[Redmi Note 2 Android Development] DarthJabba9:
I got a Redmi Note 4X (SD625). I'm pretty happy with it. The battery life is absolutely awesome, and there are official skinny ROMs (eg SlimROM, which is

really

"Slim" - contains only the

bare

essentials).

Mrs DJ9 now uses my RN2, and I really feel for her (she has to charge the battery 3 times to my one charge). For her sake, I hope that Skinny Pro continues! :fingers-crossed:
[Redmi Note 2 Android Development] jajk:
[MENTION=7442305]Iliyena[/MENTION] Do tell how to lower resolution here. It is worthwhile for battery and memory saving if it is done properly. I have thought about it but not yet got round to looking at it.

[MENTION=5850987]DarthJabba9[/MENTION] SD62x is the only worthwhile low/mid budget SoC released so far this year so you are on a winner there. Shame it is in a Xiaomi branded phone though:(

Skinny Pro is not dead just waiting....
[Redmi Note 2 Android Development] DarthJabba9:
Indeed - but being a cheapskate, I chose this over the Lenovo P2. It is well served with brilliant custom ROMs (tons of them - based on AOSP/LOS/CAF) and custom kernels. As usual, it is pot luck with your camera sensor (there are 3 different ones, and you don't know which you will get until the device is in your hands. Fortunately, I got a good one (Samsung).

Good to hear that Skinny is not dead!:highfive:
[Redmi Note 2 Android Development] Iliyena:
Tried to make it work, some other people did too... The resolution is changed and DPI/density is just fine to change, but it renders the capacitive buttons unusable so gave it up...

Keep adb capabilities active do undo black screen/soft brick with a PC, these are powerful commands that will stick after a reboot! I'd use a script and keep a script for resetting to default to put into init.d in recovery mode...

wm size 1080x1920 #Mind the small X, not * or •, change resolution as you wish DOWN from physical resolution, not up.

wm density 480 #Changing the DPI to make UI usable...

Change numbers to 'reset' to restore default values, wm size reset, wm density reset.

I am lazy and usually use an app that is "still in development" Screen Resolution Changer, see pic, NOMone never worked right for me.. Used this with a Galaxy S6 running MM Stock ROM mostly, messes with some UI elements (camera app dies not scale correctly). Pluses in using the app is the restoring of values unless you accept the changes in.. 15 sec or so, and there is an option to let the app scale the DPI! A reboot is often needed to scale some UI though.

[

I feel them SD62x to be boooring as it is a to similar in performance/function with our little heater MT6795... Tried to see anyone checking multicore efficiency after 4-5 cores... It is great for battery life though... with it's own Skinny Pro it can go further ;)

SD660 seems interesting but is not widely used so far.
[Redmi Note 2 Android Development] jajk:
[MENTION=7442305]Iliyena[/MENTION] MIUI is multi-resolution but maybe our ROM has some resolutions removed. Have you tried 720P? That would be the only viable lower res for our display.

SD is boring but marketing is superior to MTK. In fact, so superior that it lands them in court for anti-competitioin. One should always compare offerings based on their nanometers which is the only thing that determines how power hungry they are per MHz. On a technical level, MTK is on par with Qualcom and maybe about to surpass it with new SoCs coming from a different foundry with a completely different process. If you are in the business or close to it, it is almost amusing that MTK moves production from its sister company TSMC to Global Foundries to free up TSMC production capacity for Qualcom and Apple since Qualcom has worn out its welcome with Samsung. Who's the smart one in all of this???
[Redmi Note 2 Android Development] Iliyena:
I started with 720p ofc, always 16:9 for first tries ;) Everything I've tried renders the capacitive buttons useless, had to a activate Quickball to try using it for checking how things looked. Could not find any real good soft-keys then. Wish there was an Xposez module for it, it is built into Android after all... Will try some soft keys I found today, but it's an app, always an extra app ;P

Addition:I think the screen is the problem, physically. :(
[Redmi Note 2 Android Development] DarthJabba9:
Any crummy old quad-core cpu running at 1.2ghz is more than sufficient for a smart phone (apart from gaming, which is of no interest to me). For me, battery life is absolutely crucial. On that score, the SD625 is a top performer. Release of full kernel (and hence custom ROM support) is also crucial. This is where Xiaomi+MTK is lacking IMHO. Since I got my RN4X and decided which custom ROM is right for me, battery life (between 11 hours to 16 hours SOT) has been a non-issue. I am sure that MTK can also achieve this if there is a properly optimised ROM. With no full sources, developers will always struggle. This is why I will never buy Xiaomi+MTK again (at least, not until they change their policy towards the GPL). I don't care whose fault it is (ie, Xiaomi or MTK or whoever else) that the sources are not released.
[Redmi Note 2 Android Development] jajk:
[MENTION=5850987]DarthJabba9[/MENTION] MTK does release sources for their SoCs but it is not their responsibility to release source for all the peripheral parts. The problem is the bottom feeder brands like Xiaomi use up all the cheap, end-of-life, faulty, fake cloned parts kicking around and it is that fact that prevents full source code being released. Harder marketing (social engineering) leads people to believe that Qualcomm is somehow saintly in all of this.

MTK source code for our MT6795 SoC has been released for a long time. Sony released the entire source code including their specific hardware peripherals some time ago so what does that tell you???

Why do people slag off MTK when the fault lies firmly with the crap phone manufacturers:confused:
[Redmi Note 2 Android Development] DarthJabba9:
[MENTION=5952980]jajk[/MENTION] Yes, I have read that MTK release their sources and that the problem is with Skynet. This is really no comfort to the purchaser, which is why I said I don't care about whose fault it is. Somehow, Xiaomi+SD seems to generate massive amounts of excellent custom ROMs, based on AOSP/LOS/CAF. But Xiaomi+MTK does not. Why? I am not sure that the other components in the SD versions of RN3 or RN4X are much better than any other Xiaomi product - yet they seem to be able to attract excellent custom ROMs. There are even functional betas of LOS 15 for Oreo for the RN4X - just a couple of weeks after Oreo was released. My conclusion is that it must have something to do with chipset compatibility that AOSP/LOS/CAF is easily ported to SD versions.

I wish I could be rid of miui on the RN2, but I can't. Skinny Pro is a life saver, and I am thankful for it. SlimROM on the RN4X is amazingly skinny, out of the box (and there is another ROM that is even skinnier). Why can't we get this for the RN2? :( So, my conclusion is still that Xiaomi+SD is fine, but Xiaomi+MTK will never attract my custom again.
[Redmi Note 2 Android Development] jajk:
[MENTION=5850987]DarthJabba9[/MENTION] It is because the mainboard used in your phone is not made by Xiaomi and is also used in many other phones so the only hurdle to getting ROMs ported to it is if there are any oddball peripheral parts used that don't have wide support. RN2 is a lesson in what happens when a phone is cobbled together out of junk parts with zero chance of firmware support for the peripherals used. Did Xiaomi learn anything from this? No, they are still a dishonest company that deceives their customers.
[Redmi Note 2 Android Development] DarthJabba9:
[MENTION=5952980]jajk[/MENTION] It seems that whoever made the mainboards being used in these SD devices must be thanked for doing such a fantastic job!

Perhaps Xiaomi should consider buying in mainboards for MTK devices as well.
[Redmi Note 2 Android Development] jajk:
[MENTION=5850987]DarthJabba9[/MENTION] I think it is a Qualcom reference board. Xiaomi doesn't really make phones - just brands them - LongCheer produced our RN2 as evidenced by the remnants of the factory acceptance testing files left behind. Who made yours:confused:
[Redmi Note 2 Android Development] DarthJabba9:
Who knows? Is there a reliable way of finding out (other than taking the device to pieces)?

Apparently, LongCheer is 20% owned by Xiaomi, so it's all the same IMO.
[Redmi Note 2 Android Development] firmaniac:
[MENTION=5952980]jajk[/MENTION] please upload Skinny Pro for MIUI 9.Thanks.
[Redmi Note 2 Android Development] Iliyena:
Tried the last one released? :) (Just wanna know if it works)
[Redmi Note 2 Android Development] jajk:
[MENTION=7750130]firmaniac[/MENTION] Throw me the boot.img from the latest and I will make one just for you;)
[Redmi Note 2 Android Development] firmaniac:
[MENTION=5952980]jajk[/MENTION] boot.img from MIUI 9 Beta 7.9.7-SKINNY-V2

https://www.mediafire.com/file/h25wvv5zqxreqg1/boot.img

Thanks
[Redmi Note 2 Android Development] jajk:
SkinnyPro_7914-v1.img uploaded.

Still not for NOOBs.

Suitable for all Miui9 based ROMs.

Same deal as before with most Xiaomi services disabled except now most Governor settings etc. are now be left to be done in init.d script by the end user.

I will post an updated reference init.d script soon;)

Edit Build.prop and disable perfserver to get the maximum benefit as before.

I am now running heavily skinnied MiuiPro 7.9.14 on my phone - so far so good and a definite improvement over recent Miui8 builds which were getting progressively worse. Will I go back to 7.5.50??? Possibly not this time:confused:
[Redmi Note 2 Android Development] firmaniac:
[MENTION=5952980]jajk[/MENTION] thanks
[Redmi Note 2 Android Development] jajk:
SkinnyPro_7914-v2.img is up.

Removed SecondSpace stuff plus a few bits missed on first version;)

This can actually be used on Miui8 as well as Miui9 ROMs so treat this as the latest version for both.
[Redmi Note 2 Android Development] Iliyena:
No more deadline shed for each and every block? ;)

See you changed the write xxx 'value' to echo 'value' xxx. Thx. Feels easier on the eyes. What busybox are you using? osm0sis?

I am using the XDA Labs app, that means I cannot copy the text in your init-script without going into a browser :P Glad I have it all already, and then some ;)