I need to disable the scroll cache, but I lose a lot of performance on android, I did some research and they said that this can cause performance delay due to GC, is there any way to solve this? or is there another method to disable without losing performance?
Obs: I do the deactivation with the following command "persist.sys.scrollingcache=4 ( or 3, the 2 lose performance )
Wondering what sense it makes to disable Android's scroll cache ( basically a drawing cache - a bitmap ) because using a drawing cache makes an animation smooth compared to redrawing the view at every frame?
BTW:
persist.sys.scrollingcache=1 -> cache on always
persist.sys.scrollingcache=2 -> cache on certain times
persist.sys.scrollingcache=3 -> cache off certain times
persist.sys.scrollingcache=4 -> cache off always
Related
How do I change To dexopt in data/dalvik-cache instead of cache/dalvik-cache. I'm porting a rom and it chooses cache/dalvik-cache to dexopt so it won't boot. Also if I add cache dalvic . Internal memory becomes full and cannot write anymore.
Hi guys, For those who feel there x8 is slow and laggy please try my script... Thank you
Features:
-Boost Your Phone...
-Renice Apps
-Saves a lot of Battery life
-Boosted 3g/4g/wifi/hspa/edge/etc
-Tweaks for sysctl
-Reduce Lag
-Drop Caches(for better ram)
-Wipe dalvik cache
-Block Ads
-Tweaked TouchScreen
For more details click the link below
http://forum.xda-developers.com/showthread.php?t=2242861
[APP] [SHARE] [2.2+] ★ Sense 5 UI ★ Quick settings v2.2 ★ All brands ★
Root version benefits..
- Power options; Normal reboot, Hot reboot. Reboot recovery, Reboot bootloader, Shutdown
- Wipe options; Wipe cache, Wipe dalvik-cache, Wipe battery statistics, Wipe all app data
- Mount options; mount System parition RW/RO, mount Data partition RW/RO
- Convert app to System app, revert conversion
- Instant screen off option, locks device into sleep mode
Downloads : 1.Root Version : http://d-h.st/oEG
2.Stock Version : http://d-h.st/xXh
Original Thread : http://forum.xda-developers.com/showthread.php?t=2183614
Credits :
laehmic
Click to expand...
Click to collapse
First cool
Sent from my GT-S5830i using xda app-developers app
Good :thumbup:
Instruction:
1. Go to TWRP
2. Wipe > Advance Wipe > Dalvik / ART Cache & System & Cache & Data (For fresh Install, ignore if updating from any previous MIUI rom to keep ur data)
3. Install Zip package
4. Clear Dalvik Cache (If updating from any previous MIUI rom)
5. After start keep airplane mode on by presing power key & salect aeroplane mode on ( this need to be done only while startup wizard, after complete start wizard you can off aeroplane mode)
6. Enable "Documents" app by going Setting > Install apps > go to end of apps there is "Documents" app & enable it.
For NVRAM Error:
Download NVRAM File & replace the both file Wifi & Wifi custom to Root or (/Device) > data > nvram > APCFG > APRDEB
& reboot.
IF INTERNET SPEED IS LOW:
Download K3 Note Modem Patch.zip & flash via TWRP. After flashing reboot.
IF FACING APP SLEEP IN BACKGROUND OR NOT AUTOSTART THEN PLEASE FOLLOW BELOW INSTRUCTION:
1. Go to Security app > Permissions > Autostart > Enable the perticular app which you want to be autostart.
2. Go to Security app > Battery > App battery saver > (click on pertucular app which u don't him to be sleep & keep running in background) > choose "No restrictions"
Changelog in 6.7.14
Very smooth comparing with 6.7.12
Fixed heating problem which was in 6.7.12 while playing game
Battery improved alot & not heating even playing clash of clan with connected charger….. Very surprising!!!
DOWNLOAD MIUI8
Is the ROM is stable one?
We already know there are many MIUI custom ROMS available for Lenovo k3 note but none of them is stable.:crying:
Good day , I have a general question about these and hope someone could explain me what exactly happens there:
So , I played around with some props values ( also looked a bit into the aosp code / dev docu ) and set these values with magisk as system.prop
dalvik.vm.isa.arm64.features=Default
dalvik.vm.isa.arm.variant=cortex-a76
dalvik.vm.isa.arm.features=Default
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.5
dalvik.vm.heapminfree=8m
dalvik.vm.heapmaxfree=32m
dalvik.vm.dex2oat64.enabled=True
dalvik.vm.dex2oat-flags=--debuggable
dalvik.vm.dex2oat-filter=everything
dalvik.vm.image-dex2oat-flags=--debuggable
dalvik.vm.image-dex2oat-filter=everything
dalvik.vm.dex2oat-Xms=16m
dalvik.vm.dex2oat-Xmx=512m
persist.dalvik.vm.dex2oat-threads=8
dalvik.vm.dex2oat-threads=8
dalvik.vm.image-dex2oat-threads=8
dalvik.vm.boot-dex2oat-threads=8
dalvik.vm.jitmaxsize=128m
#extrem values ! Default would be 10000
dalvik.vm.jitthreshold=2500
dalvik.vm.jittransitionweight=333
dalvik.vm.jitprithreadweight=333
pm.dexopt.install=speed
pm.dexopt.bg-dexopt=speed
Note here that I used first dalvik.vm.dex2oat-Xmx=256m instead of 512m , after a Dalvik clean up and rebuild I had 248m of Dalvik cache , no noticable performance impacts etc , I though It would be better to raise the value. In the same reboot process to enable the changes I also did an update , now my Dalvik cache is empty and can't be rebuilt , the interesting part is that my system is now quicker ? Especially in games I can notice a significant boost in startup time and menu transitions , but firefox (the only app atm) doesn't like this but can be used normaly after 3 "crashes-to-launcher"
Side Note: I don't need answers how to repair anything , I'm curious what's going on
So my questions is first how can it be faster if it presumably uses the default java JiT in memory instead of creating Dalvik cache + odex files
And what happend that Dalvik etc can't be normaly initiated ? Does it not like the settings and simply crash , or is this the right behavior for my settings and I have simply no idea what I'm doing ?
Thank you for reading and any helpfull response
Both the Dalvik ( uses Just-In-time compiler, JIT ) and the ART ( what uses Ahead-Of-Time compiler, AOT ) are a Android runtime. ART is the default runtime since Android Lollipop. Knowing this you have to clarify what Android OS you are trying to hack.
jwoegerbauer said:
Both the Dalvik ( uses Just-In-time compiler, JIT ) and the ART ( what uses Ahead-Of-Time compiler, AOT ) are a Android runtime. ART is the default runtime since Android Lollipop. Knowing this you have to clarify what Android OS you are trying to hack.
Click to expand...
Click to collapse
Right it would probably good to know my setup , I use the Mi 9T with Miui 12.3 on android 11 , ram is 6gb , cpu/gpu is SDM730
Thank you for the first clarification , so does this mean the JiT is on newer OSs ineffektiv ? Or just a backup technique