yashsingh1/xdaforums huggingface dataset:
[ZenFone 2 Android Development] Dan_Jacques:
The v80 version is compatible with the last (.63) stock rom version?

I`ve facing problems installing this kernel on Barebone V4 (a .63 rom based). After flashing the kernel, the system doesnt boot and stop at a "opened" android and a single mensage: "error". Any solutions?
[ZenFone 2 Android Development] ck007:
With the latest stock version (.63) it's all ok, no problems. You could leave the custom version and use the stock one.
[ZenFone 2 Android Development] Emblema:
I'm using it, from the V77OC since the last V80 and it's works fine.
[ZenFone 2 Android Development] Xda909:
Hey guys, I'm happy :) The screen protector is destroyed but saved my display and the baking oven drying was sucessfull. I guess, the red dot on the battery is a fluid indicator? Then my warranty is over and the hesitation to unlock the bootloader was unessential ;)

Back to topic: for me, the brightness is to low too. I need to set the automatic near to max to achieve sufficiant brightness in the dark.

99% DS and -2% Battery tonight. This is awesom! thessjactive 1333 touchboost / 1866 hispeed ond 551ML.
[ZenFone 2 Android Development] TheSSJ:
Read the feedback regarding BLX just now. I can confirm that the phone does not stop charging even if BLX limit is reached. Next version will hopefully fix this.

Cheers
[ZenFone 2 Android Development] corrsea:
Minimum brightness is perfect for me. :)
[ZenFone 2 Android Development] Emblema:
Step by step this kernel is growing..

But it works in CM??
[ZenFone 2 Android Development] S#@DY:
Nope... Though i have requested him to work on other roms too :D

---------- Post added at 05:37 PM ---------- Previous post was at 05:36 PM ----------

I was also in the same doubt... I set blx to 99, still the phone gets to 100...
[ZenFone 2 Android Development] TheSSJ:
V81 is out, BLX is now fixed

Also knoneNull1 has implemented my mods into the ResurrectionRemix ROM,maybe it works for CM also now :)
[ZenFone 2 Android Development] glock24:
And I just updated to v80...
[ZenFone 2 Android Development] TheSSJ:
Sometimes development is a rolling train ;)
[ZenFone 2 Android Development] S#@DY:
Does v81 contain all the fixes for ze550ml too..?

Cant use RR now. As it is only for 551 and gives frequent reboots on my device.. Please clarify the question above..

Still waiting to try as [MENTION=2085303]cieffe54[/MENTION] is yet to upload the latest
[ZenFone 2 Android Development] TheSSJ:
Well, brightness should be fixed on 550 and BLX, too. As I don't know if you use another battery type than 551 (and I don't think so) I can't say if BLX will work on yours, but I am 99% sure that it will
[ZenFone 2 Android Development] ibo1996:
How to install the KVM?

https://drive.google.com/file/d/0B3sOydQ8aL7Ja2FHdHo1ZHJjZ00/view?usp=sharing

https://drive.google.com/file/d/0B3sOydQ8aL7JMEZfeEdaaUNTbVU/view?usp=sharing
[ZenFone 2 Android Development] S#@DY:
Waiting :D when [MENTION=2085303]cieffe54[/MENTION] will upload it
[ZenFone 2 Android Development] TheSSJ:
Read the OP:
[ZenFone 2 Android Development] Jonno12345:
Is it possible at some stage to build a newer revision with KVM support so people have the option? You've come a long way since v51 and it would be a shame to lose those features for KVM. Of course, I'm not sure how much work it is for you, but just if possible once we have some stable major revisions?
[ZenFone 2 Android Development] TheSSJ:
As KVM impacts performance a lot actually, I decided to remove it from the kernel features. Of course it can be added back in a special version,but first I want to check the sound part in the hope I can influence that a little...
[ZenFone 2 Android Development] Dan_Jacques:
Thanks. I found the problem: my bootloader is locked :silly:

Sorry for the dumb question. :p

Well, byebye warranty, I'll flash this kernel :good:

A little question: the stock kernel (not yours) has hotplugging support? I see 4 cores active, even the CPU usage is low.
[ZenFone 2 Android Development] jeffrey roy:
blx working since 1st released

i dont know why blx is not working for them, but for me its working fine since the first time you add blx!!!
[ZenFone 2 Android Development] S#@DY:
May be, just may be because we use 551ml.
[ZenFone 2 Android Development] rohit297:
Can anybody tell me, what blx actually do
[ZenFone 2 Android Development] TheSSJ:
Hi,

glad to see another person joined the unlocked crew :highfive:

The stock kernel has hotplugging support, but only when the phone goes to deep sleep 3 of the 4 cores are turned off. When something wakes the phone up again, then all cores are turned on again.

So on screen on all of the cores are always turned on, but our Intel SoCs have a very good idling mechanisms, so battery consumption is really low therefore.

Honestly I've read a lot now about hotplugging and its advantages. Disabling cores during screen on can consume even more power compared to the phone using all of its cores. The only case where this COULD be beneficial is when the screen turns off, but you are listening to the radio or normal music from your phone, then it is normally not necessary to use all cores as the load should be low. Also phone calls shouldn't be affected by this.

It would be sufficient to just enter blx into the search box on the top right :p

See this:

http://xdaforums.com/nexus-s/development/mod-battery-life-extender-blx-t1257497

Could extend your battery life by a lot
[ZenFone 2 Android Development] Dan_Jacques:
Yeah, I prefer the freedom. My last phone (Moto E) had the bootloader unlocked 3 hours after bought lol

But in the .63 firmware, the usual unlocking method isnt working. I did the adb commands, but after the "reboot bootloader" nothing happens, only a bootloader idle screen. I'm thinking to downgrade to 2.19.40.20 version, but I've to research if downgrade is possible or, like in Moto G/E, there is a risk for hardbricking.

[MENTION=2388665]TheSSJ[/MENTION] Well, in modified (or build from scratch) hotpluggers for Qualcomm like Intelliplug (from faux123 to qualcomm SoCs) ou MSM_Hotplug, even the screen is on, two cores are active (in certain situations, only one core is active). They are enought to run UI very well, w/o lags. And consider: in a quad-core Cortex A7 (like Moto G), with much less power than Z3580 or Z3560, only two cores can run UI and light apps very well (the major issue of Moto G was ever the 1GB RAM). I know, 2 or 3 cores @2.33GHz consumes more power than 4 cores [MENTION=2670407]500mhz[/MENTION], its a fact. But in the most time, only two cores are enought (The is a profile to do it in IntelliPlug for eg.: Eco Performance). I think try to unplug one or two cores when screen is on could improve the battery juice a lot, without sacrifice performance.

Thanks for the great work on Project T. I'm here to help :laugh:

Sorry my really bad english.
[ZenFone 2 Android Development] ck007:
I confirm that blx works with v. 80. Thanks! ?
[ZenFone 2 Android Development] knoneNull:
bro [MENTION=2388665]TheSSJ[/MENTION] can we request for Breath led effect on notification its cool feature in replace on stock boring notification led
[ZenFone 2 Android Development] TheSSJ:
If you link me a kernel where this was done I can check - I can imagine it's just changing the voltages gradually in order to have the LED breathing, though
[ZenFone 2 Android Development] knoneNull:
i believe asus fugu use breathing led wait i will search :) :o :o :o
[ZenFone 2 Android Development] Dan_Jacques:
Well, Project T v80 OC/UC installed. There is some BLX adjust to do?
[ZenFone 2 Android Development] knoneNull:
here bro [MENTION=2388665]TheSSJ[/MENTION] https://github.com/CyanogenMod/andr...3/arch/x86/platform/intel-mid/fugu/fugu_led.c

here the one commint from fugu [MENTION=2388665]TheSSJ[/MENTION] https://github.com/CyanogenMod/andr...mmit/42df119c6912ffde81cb763122feac03a8ea0522

https://github.com/CyanogenMod/android_kernel_asus_fugu/commits/cm-12.1?page=11
[ZenFone 2 Android Development] ImjuzCY:
I'm not sure about hotplugging when screen on to save battery (at least for me). You see, if you disable two cores, the CPU workload will be around 30% or more when doing nothing but just screen on. If all four cores are running, CPU workload is less than 15%. That's for screen on and no touch no process running. Although they are both just at minimum frequency, but higher workload means higher battery drain right?

Another example, if you set two cores disabled, in normal usage, phone will get hot quickly, because of high CPU workload. If you set four cores online, phone will not getting hot so easily, because low workload. Heat=Battery loss.

Maybe arm is different than x86

These are my findings, I may be wrong, so correct me if I'm.
[ZenFone 2 Android Development] Dan_Jacques:
I understand.

Yep, ARM are different to x86. and you can be right. But, if there is a hotplug to test, I think this could be tested. In all ARM phones (I know, x86 are different to ARM) the hotplug works good.

I'll do some tests with four and two cores (kernel adiutor + ssjactive) to see battery backup and performance. I'll report the results. But... There is some hotplug that stop cores when the screen is on?
[ZenFone 2 Android Development] ImjuzCY:
AFAIK, there is no governor for our device with hotplugging when screen on
[ZenFone 2 Android Development] Dan_Jacques:
I spoke some "ugly" words here :silly:
[ZenFone 2 Android Development] Zelota91:
Is this Kernel compatible with Prism Barebone or other rom based on Asus stock rom?

Inviato dal mio Zenfone 2 ZE551ML
[ZenFone 2 Android Development] ImjuzCY:
Yes as long as its stock based
[ZenFone 2 Android Development] Xda909:
Hm, we should test the battery los in screen-on & light load with all cores enabled and only 1 core enabled. Maybe I can manage to do that. Problematic is, to ensure exactly the same light (20-40% core usage) load.

In theory, even an 99% loaded core should use less power than 2 49% loaded cores when the same voltage is used. The power drain is caused by static leakage (only depending on the voltage) and dynamic leakage / switching current (dependend on clock frequency and load). The dynamic usage scales usually lineary with the switching, so by clock frequency and load (at a given voltage). The static part is static but can be avoided by switching off (power gating) the core. So when we have 10mA static and 10mA dynamic @ 500 Mhz / 40% load, we would end up at 20mA for the workload. Do we use 2 cores, we have 2x 10 mA static and 2x 5mA dynamic (20% load) = 30mA.

This implies, that the active core doesn't need to scale up voltage (if it uses the same voltage @ 800 Mhz, whats possible, clock scaling wouldn't be a problem). AND it implies, that intel power gates cores.

If only modules can be power gated (likely), than we need to disable two cores of the same module to achieve an effect.

If the power gating has very fine granulairty (function units, scheduler etc..) and can be applied even on active cores, than disabling should realy have a minimal effect.

Thats for the theory ;) I'll try to test it. There are other factors (cache hitrate / trashing; activation/deactivation-losses etc.) that could affect the "theory" ;)

Unfortunattely, I can not find a documentation about the C-States and how they work exactly.
[ZenFone 2 Android Development] jeffrey roy:
blx works fine since 1st released

well, i am also a ze551ml, 16gb 2gb ram, 1.8mghz user!!! i dont know what [MENTION=2388665]TheSSJ[/MENTION] does exactly mean on v .81 that the blx is already fixed...sinced 1st released of blx is already working fine,, i dont know what is exactly fixed!! i dont know if the battery limit can now go lower beyond 80% or what? i am confused, can you make it more specific!! [MENTION=2388665]TheSSJ[/MENTION] THanks in advanced, and thank you for the awesome kernnel...been using it for a while now and its great!!!
[ZenFone 2 Android Development] TheSSJ:
The issue with BLX was that the phone kept charging, even if the limit was reached (the phone showed 100% all the time, but in the background the capacity kept growing even if the BLX limit was reached. So as an example:

You set 80% as limit for BLX and put your phone to charge. Until 79% everything looks normal, then when the phone hits 80% Android shows a full battery and a green LED lights up. But if you keep your phone charging the capacity is still going over the set limit. Plugging the USB cable out would show you then 86% instead of the 80% you have set.

That's all basically. I still have set the minimum allowed value to 80% (values below simply won't work) as I think some ranges are a little too much (like setting your phone to 1% or so :silly: )
[ZenFone 2 Android Development] Dan_Jacques:
Well, uninstalling Energy Saver, Task Manager and Autostart Manager the battery juice is better (WTF).

Apparently the performance didnt change between 2.33, 2.4 and 2.5GHz, even in CPU based benchmarks (like HWBOT Prime, Superpi, Geekbench). I'll continue the tests.
[ZenFone 2 Android Development] S#@DY:
I dont know why, but the phone just freezes at the boot.. Happened many times..
[ZenFone 2 Android Development] Dan_Jacques:
try to erase cache
[ZenFone 2 Android Development] Justere:
Thank you for all your hard work.

How do you think about unlocking LTE frequencies for not WW regions (CN,TW)?

According to my information it is possible to change settings in kernel sources.
[ZenFone 2 Android Development] TheSSJ:
I know there was some work involved which needed to manipulate just SFI entries somewhere. If you tell me where to look, I would implement this feature of course.

Status about LED modding: Unfortunately the component of our led are so simple, that they are just able to be turned on and off :( No breathing effect possible unfortunately. Maybe I could try to make it at least a bit more colorful (like red, orange, green, again with red, orange, green, etc.), but this will be a to do point in the future.

Next step is to see what can be done to make the volume of our speaker and Headphones a little louder
[ZenFone 2 Android Development] knoneNull:
thanks for that try bro
[ZenFone 2 Android Development] S#@DY:
Always did
[ZenFone 2 Android Development] ansebovi:
No hotplug but you can disable cores using kernel auditor in screen on and screen off..

I tried at start and my result is 4cores gives better battery than 2cores
[ZenFone 2 Android Development] Dan_Jacques:
After some time, the four cores are active.
[ZenFone 2 Android Development] ImjuzCY:
Thessjactive will turn on all cores when screen turns on. Use yankactive if you want to disable cores
[ZenFone 2 Android Development] AL_IRAQI:
it seems that Asus know what users want, they changed lowest brightness level in 40.90
[ZenFone 2 Android Development] TheSSJ:
Glad to see that. The kernel restriction of enforcing 15% was one thing, but they also enforced it on Android System side, that's why the driver changes weren't enough to lower the brightness. At least they have now changed Android OS accordingly to scale down in a more linear fashion

Hopefully they will release the newest kernel src also

/EDIT: Big changes coming:

Quickwakeup (execute tasks by waking up only parts of the system and go directly to deep sleep again)

EXT4 optimizations

Block device optimizations

F2FS (just for sh*ts and giggles, as I don't use it, but having the driver implemented is a good learning exercise)

TCP congestion algorithms

More to come (and to be commited :D )
[ZenFone 2 Android Development] Dan_Jacques:
Two great news!

OMG! :D

Can you add westwood TCP congestion? It's faster :fingers-crossed:
[ZenFone 2 Android Development] adilsh:
looking forward to your masterpiece ;p thanks!
[ZenFone 2 Android Development] TheSSJ:
Sure, it's just a flag to activate. Will also activate:

CONFIG_TCP_CONG_BIC

CONFIG_TCP_CONG_CUBIC

CONFIG_TCP_CONG_WESTWOOD

CONFIG_TCP_CONG_HSTCP

CONFIG_TCP_CONG_HYBLA

CONFIG_TCP_CONG_HTCP

CONFIG_TCP_CONG_VEGAS

CONFIG_TCP_CONG_VENO

CONFIG_TCP_CONG_SCALABLE

CONFIG_TCP_CONG_LP

CONFIG_TCP_CONG_YEAH

CONFIG_TCP_CONG_ILLINOIS
[ZenFone 2 Android Development] allasca:
How about WESTWOOD+ ???
[ZenFone 2 Android Development] TheSSJ:
It is westwood+, there is no source code for plain westwood anymore
[ZenFone 2 Android Development] allasca:
Will you delete the 2%brightness for new latest update?
[ZenFone 2 Android Development] TheSSJ:
Why should I? Maybe if the newest source from Asus will come my brightness patch won't be needed anymore, but other than that the response to 2% brightness was quite positive.
[ZenFone 2 Android Development] Dan_Jacques:
I read that reduce brightness (at least in the last update .90) is only a filter, not a hardware command. It can be proven taking screenshots. When the brightness is low, the screenshot is darker.

Well, in the .59 firmware and your kernel, apparently the screenshots are identic, with the 2% brightness or 100% brightness.
[ZenFone 2 Android Development] ImjuzCY:
Noticed that too. So I suppose using a filter didn't reduce power consumption by the display right? If then kernel level low brightness is still needed
[ZenFone 2 Android Development] BorjaRRR:
Can i apply OTA update with this kernel or i need to flash stock before update?
[ZenFone 2 Android Development] Dan_Jacques:
Indirectly, yes. It's necessary less power to show a black pixel than a white pixel. But the difference is much less than effectively reduce the brightness by hardware.
[ZenFone 2 Android Development] eoghan2t7:
You still need the stock boot.img from your current rom as the ota will fail due the the md5sum not matching up.
[ZenFone 2 Android Development] Dan_Jacques:
You can download the stock boot.img from here: https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
[ZenFone 2 Android Development] S#@DY:
Did the kernel sources has changes in the latest build? Because the last updated kernel is still 2.20.40...

Waiting for new features.

*Also whenever I turn off the workqueues, it automated turnss on everytime. Please have a look here.*
[ZenFone 2 Android Development] TheSSJ:
That's normal,after a reboot it takes the default value which is set from source ....... BY ME :D
[ZenFone 2 Android Development] S#@DY:
Nah.. Not after a reboot.. If i set it off,

If i open kernel adiutor.. I find it is still on...
[ZenFone 2 Android Development] Dan_Jacques:
OMG, the memory management is much better in the last .90 firmware. Anyone tested Project T on this?
[ZenFone 2 Android Development] TheSSJ:
V82 is out:

F2FS support added

added several tcp congestion algorithms and defaulted to westwood (great speed increase)

Increased tcp window size (more performance)

Under the hood fixes (wifi now integrated into kernel, ramdisk fixed up, etc.)
[ZenFone 2 Android Development] Dan_Jacques:
WOOOOOOOW! I would like to buy a beer for you.

You've tested format /data under F2FS?

I'm trying to add this on my other phone (Moto E), and I have problems with fstab. So, after the formatting, /data becomes inacessible. It happens in Z2?
[ZenFone 2 Android Development] TheSSJ:
Don't know about f2fs details...as project T is just a kernel,i added just the f2fs support to it,nothing else ;)

So some ROM Chef needs to do this exercise now to try running his ROM with f2fs partitions
[ZenFone 2 Android Development] Dan_Jacques:
Thanks! Unafortunately there is no much documentation about it. The most related F2FS searches are about Nexus 4/5 conversion.

I sent to Asus a request for the last kernel sources (if has changes in the lastest update). I wish their response :fingers-crossed:
[ZenFone 2 Android Development] corrsea:
Just had 2 random reboots on v82. Going back to 81 for now to see if they stop.

Edit

Just happened in 81 as well do I guess it's something else causing them.
[ZenFone 2 Android Development] Dan_Jacques:
Great performance in v82. I'm benchmarking. It's perfect with the 2.20.40.90.

P.S.: SIOPLUS IO rules
[ZenFone 2 Android Development] eoghan2t7:
For f2fs to work edits will need to be done in the fstab in the ramdisk like this

http://review.cyanogenmod.org/#/c/93105/2/rootdir/etc/fstab.qcom

Also twrp will need to be modded to allow for reading the f2fs partitions for the likes of backups and restores etc..
[ZenFone 2 Android Development] Dan_Jacques:
Well, the new version is constantly better than stock:

Stock kernel 2.20.40.90 x Project T v82

Geekbench:

Single core: same

Multicore: Project T +35%

SuperPi 1M:

Stock: 11.835s

Project T: 11.470s

Antutu 5:

Stock: 46.566

Project T: 47.015

GTX 3.1:

Manhattan: equal

T-Rex: Project T +10%

Basemark OS:

System: Project T +15%

Memory: Project T +30%

Graphics: equal

Congrats, [MENTION=2388665]TheSSJ[/MENTION]!
[ZenFone 2 Android Development] Zetsubou Sensei:
What I/O schedulers do you guys recommend? I've been relying on fiops for the last 2 years but just read that it could lead to lag during heavy multitasking. I usually leave up hangouts, Reddit and chrome but will get near the 3-3.5 gb ram usage.

Any recommendations? Currently trying out Zen.
[ZenFone 2 Android Development] dam1974:
You can change low memory killer settings permanently to 1144,1220,1297? I apply this settings with Autokiller memory optmizer app and I have 1 GB ram free forever

Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
[ZenFone 2 Android Development] marcof93:
I don't know what you do with your phone, but I have always 1.7-2.3 GB of free RAM on stock values.
[ZenFone 2 Android Development] Zetsubou Sensei:
-Delete please-
[ZenFone 2 Android Development] marcof93:
It's not necessary to rewrite the same message every 10 minutes, search in the thread, it's a question already answered many times.
[ZenFone 2 Android Development] geertus:
you mean Stock kernel 2.20.40.90 in stead of Stock kernel 2.20.40.93 ?
[ZenFone 2 Android Development] Zetsubou Sensei:
Wow, totally didnt notice the first one was sent, my fault.

I'll do some digging. Sorry guys
[ZenFone 2 Android Development] ImjuzCY:
More free ram means slow multitasking. Apps are killed to get it off the ram and when relaunched from storage will be slower than from RAM. I like my apps to stay in ram than needing to be relaunched from storage
[ZenFone 2 Android Development] Dan_Jacques:
2.20.40.90

A little typing error. :o

I'm testing battery life now ;)
[ZenFone 2 Android Development] TheSSJ:
Little info: thanks to @knoneNull I discovered, that the power efficient work queue sysfs flag has the wrong permissions, which is the reason, why they can't be turned off at the moment.

Next release will fix this, along with many NASTY things (e.g. sioplus IO sched will be set as default) ;)

Cheers
[ZenFone 2 Android Development] Dan_Jacques:
TheSSJactive is the default cpu gov at the last version?
[ZenFone 2 Android Development] TheSSJ:
As not everyone is using thessjactive (and I also don't want to force people to boot with a battery focused gov, this could increase boot time :) ) I don't want set this as default...if it would be more focused on performance,then probably...
[ZenFone 2 Android Development] Okazakee:
So the row scheduler is impossible to use? I haven't read lastest posts...
[ZenFone 2 Android Development] TheSSJ:
Unfortunately troubleshooting is not as easy as I thought, but I still didn't lose hope :)

As things seem to be functioning pretty stable (and my next commits will hopefully,too)...ROW is the next scheduler on my list
[ZenFone 2 Android Development] ansebovi:
It know this is bit off topic but do you have any idea to create multirom for zenfone 2 at some point as we have lot of roms now, or can you discuss this about other debs who are working on roms of zf2
[ZenFone 2 Android Development] AkiroX:
Will you update the base to .90/3? Or will you keep it .40? Seems the .90 basse is giving everyone epic battery life.

I dunno if it's the rom or the blobs but if it's blob related I'd imagine this kernel would rule the world. lol
[ZenFone 2 Android Development] TheSSJ:
Well, to use .90 base Asus needs to release the source first :D

But my philosophy is to implement updates from Asus as soon as they become available
[ZenFone 2 Android Development] dahikino:
Can I use this kernel with aosp ROM 5.1.1 made by Niropa?