Forwarded from Exynos7885 Bot
❤23🔥6👍4👎3😱3🎉3🤩2
Bug tracker
- Internal system error: ok. I did a simple misunderstanding and will be fixed on next beta
- Install zip not working on A30s: WIP
- Internal system error: ok. I did a simple misunderstanding and will be fixed on next beta
- Install zip not working on A30s: WIP
👍18❤1👎1
If after the aroma zip the kernel is not updated, try extracting the aroma zip and from kernel/ get the zip of your varient and flash with twrp. Let me know if this works
👍7👎1
Beta 2 coming today
fixing internal system error on aosp varient
maybe fixing install aroma not working
Note: UI3 doesn't have sLMK
Compiler is Neutron clang 16
fixing internal system error on aosp varient
maybe fixing install aroma not working
Note: UI3 doesn't have sLMK
Compiler is Neutron clang 16
❤14👍5👎1🔥1
Forwarded from Exynos7885 Bot
❤24🔥7👎3👍2🤩2🎉1
What score you will give to beta02. I'm checking the user's rating for this one.
Higher score means better.
Higher score means better.
Anonymous Poll
13%
1~3
13%
4~7
33%
7~10
42%
100
🔥19👎7❤5😁2👍1
❤17👍6🔥4👎3🤩2
Beta 3
For OneUI varients cpu input boost was removed as requested
For aosp varients, made some changes to lmk
On boot, lmk is the default android (not slmk) and it continues like that unless the user chooses to use slmk.
The slmk is good at free memory but kills too much, it's just because the kernel cannot know what app (or PID) is on foreground or background. The kernel has to guess it like oom_score_adj, task_prio which may be incorrect. So the slmk has been changed to have a userspace client.
Before: kernel { get running pids -> guess -> kill -> loop }
now I intend to: kernel { get running pids } -> userspace { get exact fg/bg app database from Android am and sort out pids to kill -> write pids to be killed } -> kernelspace { kill the received pids -> loop }.
This lmk method will be activated when the user app opens and ioctl to the /dev node. Before it will be android default lmk implementation. I'm still coding the app so this may be changed.
For OneUI varients cpu input boost was removed as requested
For aosp varients, made some changes to lmk
On boot, lmk is the default android (not slmk) and it continues like that unless the user chooses to use slmk.
The slmk is good at free memory but kills too much, it's just because the kernel cannot know what app (or PID) is on foreground or background. The kernel has to guess it like oom_score_adj, task_prio which may be incorrect. So the slmk has been changed to have a userspace client.
Before: kernel { get running pids -> guess -> kill -> loop }
now I intend to: kernel { get running pids } -> userspace { get exact fg/bg app database from Android am and sort out pids to kill -> write pids to be killed } -> kernelspace { kill the received pids -> loop }.
This lmk method will be activated when the user app opens and ioctl to the /dev node. Before it will be android default lmk implementation. I'm still coding the app so this may be changed.
❤45👍4🔥3😱2🤩2👎1