yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 2] Khaon:
I need to check informations and or look at the source code but the few I have read suggest ocing the ram is a bad idea.
[Xiaomi Mi 2] T3sla:
Well i saw boosting moto e's ram from 333 to 400 which is a nice 20% speed gain and they call that small overclock...! What is the speed of our ram and what type? DDR DDR2 etc.
[Xiaomi Mi 2] Alecsandru90:
the ram is Elpida BA164B1PF Dual‐channel 16Gb LPDDR2

but if nexus4 can do 333MHZ/400MHZ/466MHZ on RAM

and 116MHz on L3

why our mi2s can't do that?
[Xiaomi Mi 2] Khaon:
Hm unless I am wrong there is no L3 cache atm. I already however clocked some freq from 533 to 600 mhz on the bus.

However I have no idea yet if we ans how can oc ram. But I am not sure it would really be worth but we can still try anyway.

Hm I am running now the latest cm build I provided. I am kinda impressed by the fluidity and smoothness oO.

I have lollipop on my tablet but the performance difference between kikkzt and lollipop was less than in this phone.

Battery life seems to be better as well. I will try to have a deeper look hoping to solve mic problem until then you can use the zip archive someone posted on cm 12 thread

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Alecsandru90:
my bad , there was a level 3 overclock , no l3 cache , how about dsp? can we achive 24 bit playback with our dsp? and maybe overclock-it?

and about rom , will you sync with the latest cm12 patches?
[Xiaomi Mi 2] Khaon:
I need to look into dsp I don't know. Can you be more specific with level three overclock? I have built a new ROM but I forgot to upaload it and I am gone until thuesday. I will release thuesday nightly as soon i am back

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Alecsandru90:
awaiting your second cm12 ROM:):D
[Xiaomi Mi 2] Khaon:
It's been built

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Alecsandru90:
it has been built sucesfully? can you upload-it?

thanks
[Xiaomi Mi 2] Khaon:
Being sorry I tried some other things and they failed badly. So I choose to build with regular.

As soon done uploading it

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Khaon:
lollipop 22/10 online

Hello everyon, I am uploading a new nightly and the kernel was updated to f2fs
[Xiaomi Mi 2] Khaon:
rom and kernel being uploaded on drive.

i did not add the time to include audio patched libs.
[Xiaomi Mi 2] Alecsandru90:
still no f2fs support rom-side , thanks for your work
[Xiaomi Mi 2] Khaon:
If you want I ll make one for next release but we want feedback :P

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Alecsandru90:
the /data error is still here with latest twrp
[Xiaomi Mi 2] Khaon:
Let's try to summarize quickly; has I have userdata working with f2fs.

What is your twrp? Can you try providing logs? one is located at /tmp/*.log

1. format your userdata partition to f2fs.

1.1 reboot recovery

2. install cm12

3. install my lollipop kernel

4. wipe caches

5. reboot
[Xiaomi Mi 2] Alecsandru90:
your latest twrp

done all

can't acces logs via adb , my usb is dead
[Xiaomi Mi 2] Khaon:
data error happens in twrp not in the rom booting right? You dont get a prompt asking for a password.

you can copy logs anywhere else btw from file maanger they are located at /tmp and there is another i think.

Can you tell me your twrp version?
[Xiaomi Mi 2] Alecsandru90:
2.8.4.0

the rom boots fine

I get the first error when installing the rom(can't mount data , invalid argument)

the second one is after google is finished restoring apps and I go in recovery and try tor epair data partition
[Xiaomi Mi 2] Khaon:
Can you edit the update-script?

Seek line mounting any f2fs partition and replace its line (mount("blabl')) with

/sbin/busybox", "mount", "/data"[code]

This resolve your first error.

Can you be more expensive on your second one?
[Xiaomi Mi 2] Alecsandru90:
during the restore of apps /data gets corrupted , at least twrp sees that
[Xiaomi Mi 2] oile:
Can't wait for a new cm12 build xD
[Xiaomi Mi 2] Khaon:
I will try by tomorrow.

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Khaon:
Sorry what step? You mean restore twromp backup?

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] T3sla:
[MENTION=4577448]Khaon[/MENTION] does the 06/01 kernel for kitkat has the increased L2 cache speed?Cause when i set maximum speed @ 1242 i have reboots and i thought maybe because i applied the previous voltage settings.Which log will help to find out the cause?

Edit:it does even with stock speeds
[Xiaomi Mi 2] Alecsandru90:
no ,during restoration of apps from google market
[Xiaomi Mi 2] Khaon:
So your error happens when trying to install any application? Not upon first boot when you choice the application you want back or not.
[Xiaomi Mi 2] no_means_no:
I flashed the file but failed flashing Mokee ROM 4.4. Couldn't get it working even with full wipe etc.

How to get the old format back to install my Mokee ROM back?

edit:

I'm sorry for my noobish behaviour and questions: how to bring the right parts of the system back to the right format to reinstall my backup from mokee?
[Xiaomi Mi 2] T3sla:
[MENTION=4577448]Khaon[/MENTION] any thoughts?
[Xiaomi Mi 2] Khaon:
Install latest 23/01 and tell me if this still happens

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Khaon:
The kernel doesn't support mokee os.

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] no_means_no:
... but is there a way to get back to the system state where I can reinstall mokee?
[Xiaomi Mi 2] T3sla:
Does this kernel needs voltage increase compared to 06/01 ?Cause i'm quite heavily undervolted.
[Xiaomi Mi 2] Khaon:
Should not but can you refresh my memory please about features of 06 01

You can be sure to apply same for min to 1026 included. 1134 ++will requires more but less then 06 .

Sent from my nexus 10
[Xiaomi Mi 2] Khaon:
Just reinstall from recovery the flzshable zip

Sent from my nexus 10
[Xiaomi Mi 2] T3sla:
Well i'm not sure about the features but i think you started building oced L2 cache kernel after 08/01.That's what i'm asking actually, cause i'm not sure about the above speculation.Maybe 06 kernel is oced too and that's why i have reboots.

Another question, what are the default and what the oced 23/01 kernels speed and voltage you applied to L2 cache?Just want to calculate the increase in consumption approximately.
[Xiaomi Mi 2] Khaon:
You should take a look at the commits from github you will see which ppl etc I have increases to avieve a better stability on vcore

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] no_means_no:
That's what I tried, but the installation process has been aborted. I couldn't even restore my full backup I usually make when doing things I'm not 100% sure about :(
[Xiaomi Mi 2] Khaon:
Provide the recovery log at tmp partition

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] T3sla:
I more than willing to look but where exactly?Github it's like japanese language for me currently :P Can you provide a link of the specific commits?
[Xiaomi Mi 2] Khaon:
Those o are the commits related to the increase in cache speed:

https://github.com/Khaon/mi2_kernel/commit/7109ae049d4a33881a9cfb08b0031dec1c0f29e0

https://github.com/Khaon/mi2_kernel/commit/de52c4aa5ac4813ba9b12340ec58cbd9236e60f7

https://github.com/Khaon/mi2_kernel/commit/6c498522d6498bba94836c1b7f9ef4831b2d2bdb

https://github.com/Khaon/mi2_kernel/commit/9013eb209f218745fe00957300a3b28b626c2796

i think we can achievebetter.
[Xiaomi Mi 2] Khaon:
I will release by tomorrow or the day after tomorrow a new cm12 build.
[Xiaomi Mi 2] netweaver2009:
Including M1cha's custom audio HAL source tree? So with the mic fix built-in?
[Xiaomi Mi 2] no_means_no:
I'm really sorry, but there's no such thing in my cwm based recovery...
[Xiaomi Mi 2] Khaon:
and camerea yes.
[Xiaomi Mi 2] Khaon:
Honestly I dont see how comes you are having a problem.

So you have mi2 or mi2s. you were on pacman and everything was working, then you wa&nted to flash my kernel and ?
[Xiaomi Mi 2] no_means_no:
I was on mokee 4.4, flashed your kernel, couldn't restart, couldn't re-flash mokee and couldn't recover my full backup (last running mokee), even after wiping and formatting...

now running paman with your kernel. It was just a lot of work reinstalling everything step by step through titanium. I still can't flash mokee, but for now pacman is nice ;)
[Xiaomi Mi 2] T3sla:
I read somewhere that you shouldn't format system with TWRP version something...don't know if it's related just mentioning it.
[Xiaomi Mi 2] no_means_no:
I'm not using TWRP, it's CWM based recovery version 6.0.5.0. I formatted only after neither recovery from full backup nor reinstalling mokee worked. The formatting seemed to have no effect. Did install pacman then which worked fine.
[Xiaomi Mi 2] Alecsandru90:
could you take a look at philz touch recovery , that one worked flawless with f2fs in kit-kat
[Xiaomi Mi 2] T3sla:
[MENTION=4577448]Khaon[/MENTION] ok...many questions this time.

1)If i choose in trickster mod intelliplug does hotplug automatically gets disabled?Cause when i check last kmsg there is a lot hotplug pause and resume action.

2)How can i verify that only intelliplug is working?

3)Weirdest thing...i can't record logs!! I'm trying to get some live recording of logs to solve my random reboot problem and i tried 3 apps.They all start getting root permissions but not live logs just blank screen.I can only get logs with syslog but that way i'll never get a proper log cause it's after reboot.Any idea?

I'm using pacrom 4.4.4.
[Xiaomi Mi 2] Beyaz66:
1) No

because

2) when /sys/module/intelli_plug/parameters/intelli_plug_active is set to 1,

/sys/devices/virtual/misc/mako_hotplug_control/mako_hotplug_enabled stays enabled (1)

3) Same for me, no live logs in logging apps except from dmesg.

Edit: I'm also on pac, "maybe" it's rom related.
[Xiaomi Mi 2] T3sla:
So how do we disable for example mako?Editing manually the file?Does the change persist after reboot or we have to use init.d script?Or i guess using two kernel control apps as Khaon is doing which is a solution that i don't like much...

Yeah that's what i thought, seems it's pac related or at least pac+khaon kernel related.
[Xiaomi Mi 2] Khaon:
By defualt mako hotplug is enanbled so you have to disable it, you can do from an init.d script indeed;

I think the issue with your logs comes from pacman. I think I had similar issues back then, but no issue on cm.

Try logcat extreme

---------------------

EDIT: aero controls allows you to add custom sysfs entries... You couldd add the relevenant you want and save them.
[Xiaomi Mi 2] Alecsandru90:
BUG: if you use fauxsound control app, modify the settings and enable them on boot , you've lost the sound in calls , can't hear anything
[Xiaomi Mi 2] T3sla:
Since you're running pac let me ask you, do you have problems with notifications from apps like whatsapp viber skype etc.?Like not getting the msg immediately?If the screen is on everything is ok but from what i understood when enters deep sleep msgs can't be delivered.Until i turn the screen on or some other app wakes the phone.As far as i remember i didn't have that problem with CM.
[Xiaomi Mi 2] Beyaz66:
Already tried. Logcat extrem gives only kernel debug mesg. I will see if it works as it should without your kernel the next time an update come for your kk kernel.

I've had similar problems with fauxsound app. But even without it, my sound is lowered by something that I can't identify. In trickstermod's sound control: I set everything to '0': after a while L/R headphones, L/R headphones PowerAmp and speaker are repectivily decreased to -84, -6 and -84.

Sorry, I never use these kind of apps. I only have twinsee and twinmee which are comparable and I always get my calls, deepsleep doesn't affect them.
[Xiaomi Mi 2] T3sla:
After a lot searching seems that is a router problem, so for anyone having problems with some voip apps most probably it's not rom related.
[Xiaomi Mi 2] Khaon:
I think fauxsound code decreases by itself the volume to preserve your hardware but you can set a sysfs entry to disable this security
[Xiaomi Mi 2] Khaon:
I am uploading a cm12 new daily nightly build. It comes with M1cha's audio lib + default kernel.
[Xiaomi Mi 2] Beyaz66:
So, about live logs: once your kernel is installed, loggers from /dev/log/ disappear. Should the reason be this. Right?

I'm not sure to know how to do what your tlaking about. Aren't trickstermod, fauxsound app already doing this? More, even enabling gain lock in sound control from trickstermod doesn't preserve values from change.

Do you know what sound_reg_read from /sys/kernel/sound_ccontrol_3 does?

Edit: isn't something wrong about permissions for sound_reg_*read/sel/write in this same path?
[Xiaomi Mi 2] Khaon:
I have no idea just that logs are working with cm.

But if you say that it is working before applying than something interfere.

About the lock. As far as I remember it was always setting my speakers and mic volume on two.

About the sys entry I will look at the this by tomorrow or the day after tmr so you can have you answer. It's possible faux made a mistake. You have to declare the permission of your sysfs entries
[Xiaomi Mi 2] Alecsandru90:
how about the fixed recovery with reseize of the system?:)
[Xiaomi Mi 2] Beyaz66:
Does anybody else have an idea why dev/log is no more here when khaon's kernel is installed?

Yes, that is what the lock is suposed to do. But it doesn't lock anything. And when some of the settings are automatically lowered, it's unlocked again. A screenshot with permissions is in attachement. I would be grateful to you for the sys entry, it will save me from a lot of nervousness,thanks.
[Xiaomi Mi 2] T3sla:
That's a mystery i would like to solve too...

I wonder if you have the same issue with me, when i use voip like skype sound is extremelly loud even if i lower the volume completely and never gets turned off.
[Xiaomi Mi 2] Khaon:
The issue is related to the rom as logs are working on cm11. However no idea what makes the interference.

I will look deeper into the faux sound's code to see what make the lock to be removed, permissions and store/show function are not really standards.

I have no sound issue using voip(viber & whatsapp) but I am not using faux sound.

----------------------------- @Alecsandru90

I have uploaded latest twrp compatible with f2fs and it integrates natively resize2fs. You can resize your current partition issuing the following commands from the recovery :

e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system
resize2fs /dev/block/platform/msm_sdcc.1/by-name/system
e2fsck -fy /dev/block/platform/msm_sdcc.1/by-name/system

This will be added out of the box for the next releases.
[Xiaomi Mi 2] Alecsandru90:
i hope you add f2fs support in your next build, ROM-side , thank you for your work
[Xiaomi Mi 2] Beyaz66:
I've googled about the logger issue and how to activate/reinstall it, searched in pac's and your kernel github sources and nothing made me say "this is the culprit" and certainly nothing that you already don't know.

The most comon case is that logging is disabled kernel side but this doesn't apply to us 'cause you said that it works on CM.

Most people solve this with logger.ko. The bad is that the we can't make the module to mount dev/log because it isn't here.

Without any detail, I saw two cases (franco and I can't remember the second kernel) where something went wrong in the update process itself.

Is it possible for you to make an option to enable or disable logging? By this way you could lighten as much as possible loggers and we would be able to use them when needed.

Any changelog for the 13.02.2015 update? I have to repeat. Many thanks for the time you spend for/with us ;)
[Xiaomi Mi 2] Khaon:
I didn't take time to publish the changeling but I will in few days. You can build or without logs yeah. I mean the kernel. Well I can see lf something can be done

Sent from my Xiaomi MI2s
[Xiaomi Mi 2] Khaon:
I think this is what you are talking of. Didn't know of this mod, but yeah it is interessting! I will add this to the kernel in the afternoon or tomorrow. If anyone knows any kernel implementing this with our charger driver well let me know if not I port that myself:p.
[Xiaomi Mi 2] T3sla:
I'm a little confused... isn't the same link i posted?:confused: Yes this is it!! I'm glad that you liked it :) Is it gonna be an option under settings/performance which will let you choose the charge level?
[Xiaomi Mi 2] Khaon:
Nope sysfs interface variable, but, no worry, when it will be suported everything will be xlained in the f.a.Q. That's a nice first feature request :P. YOu righ will save useless charging hehe.
[Xiaomi Mi 2] Khaon:
Any kernel is live!

There is two zip in mediafire : one is for cyanogenmod rom && the other is all-kernel. This will be unified in the next update: i need to remove the write of tunnable at boot from init.rc's to a post-init script.
[Xiaomi Mi 2] paul89rulez:
Backupping and testing
[Xiaomi Mi 2] T3sla:
Doesn't work with AOSB rom.It seems to boot but i have black screen.I can see though that when i press power button screen light up and off.I'll try with other AOSP rom later.
[Xiaomi Mi 2] paul89rulez:
same with nexus 5 experience and Wiui v6. Device seems to start, charging led start, phone showed on windows for browsing, but screen is black. Here is some logs:
[Xiaomi Mi 2] oile:
Perfect on cm11! Very very smooth.

Please add gpu oc too! Thanks
[Xiaomi Mi 2] Khaon:
Miui v5 v6 wont work ramdis: needs To be adapted
[Xiaomi Mi 2] Khaon:
Your logs are wrong => last_kmsg is about xperian's kernel.

The best would be dmseg.
[Xiaomi Mi 2] paul89rulez:
so there are no generated logs.. i flashed your kernel anykernel version for shure, 4 times
[Xiaomi Mi 2] Khaon:
GPU OC is live !

Just to be sure did you try this?

adb shell su -c dmesg > dmesg.log

changelog :

gpu: overclocking: initial implementation

Thank to flar2 for his table and ppl adapter
[Xiaomi Mi 2] Fortinho:
Black screen on boot flashing penultimate allkernel version on Ivan's AOSP.

I guess should be the same with the last version, seems there aren't changes that could help for that.
[Xiaomi Mi 2] Khaon:
Little update !

Changelog

imported FauxSound 3.6
[Xiaomi Mi 2] dexxa05:
Khaon,

Thx for your work! The lastest release is compatible with MIUI 6?!

Et merci pour le travail :)
[Xiaomi Mi 2] paul89rulez:
w8ting for any kernel support.. running stable on -75mv with Codename Lungo cm11. The strange thing is that i can undervolt more with this kernel than Xperian Pro one. Will try with -100 soon

Edit:

Undervolted better:

There is my voltage table:

384mhz-750mv

486mhz-775mv

594mhz-775mv

702mhz-800mv

810mhz-825mv

918mhz-850mv

1026mhz-900mv

1134mhz-950mv

1242mhz-1012.5mv

1350mhz-1012.5mv

1458mhz-1025mv

1566mhz-1037.5mv

1674mhz-1050mv

1728mhz-1050mv

Running stable for now..

feel free to advice some changes!
[Xiaomi Mi 2] T3sla:
Is it stable with such low volrages?No random reboots?What speed bin pvs are you running?
[Xiaomi Mi 2] paul89rulez:
yes is stable, running times 20hs without random reboots\app crashing. I don't remember, maybe Fast bin. Will try to raise down -12.5 to high voltages, and -25 to 918>, but i think that this is the limit. Anyway, there will be not such improvments i think.
[Xiaomi Mi 2] Khaon:
Not much indeed since it is the display that consumes the most battery
[Xiaomi Mi 2] paul89rulez:
mmm is not that what i mean.. i mean that -75 and -100 have just the same. For me undervolt save alot of battery. With nexus 4 + undervolt at -150 (fastest chip) i had 6h screen on all the time :)
[Xiaomi Mi 2] Beyaz66:
I'd like to see if these two first points are related to anykernel. Does zImage = boot.img ?

_1_____

[MENTION=4577448]Khaon[/MENTION] I knew I'd already seen it somewhere in the thread. Rember [MENTION=2497001]paul89rulez[/MENTION] 's submitted logcat log on his post. The logger was already missing.

And I quote his next post:

So it's not a new thing if it can help you. And I can reproduce it on both sys0 & sys2, CM11 & PAC.

Personally, the fact that the logger was off suited and did'nt bother me for smoothness reason. But even if it's sometimes, it's needed and essential.

_2_____

All the last JAN/FEB kernels (and even lollipop version/ HOW is it possible?) works on sys0 on KK with both cm and pacrom. As soon as I flash on of FEB's version on sys1, the phone stucks at boot LOGO.

_3_____

For some time now, ONLY on sys1 partition, CWM gives me the root access missing message after I select "reboot the device" and ask if I want the su binary. No matter what I select, root works. Do someone know what can causing this or for what reason this "error" comes? That's just for curiosity, nothing alarming or related to this thread, but annoying.

_ ______

So for summerizing every request/wishes in last posts and make things clean:

- to save users from a poor handling; make the kernel turning off mako hotplug by itself when intelli plug is turned on.

- checking up fauxsound code and Fsystem because settings are automatically and too much lowered and couldn't be locked.

- taking the logger by the horns :cool:

- is there mounting error on last update?

Aside from that. The more I use the 13.01.15 v. the more the phone is smooth. Decreasing max CPU freq. to 1674 mHz gives the more an extra boost than at 1728 mhz. It sounds like the more is not alwas the best :)

Edit: strike
[Xiaomi Mi 2] Alecsandru90:
any news regarding f2fs ROM?

i've done-it manually :

moved /system files to /data

converted /system to f2fs and copied files back

flashed your kernel , wiped dalvik and cache

boots fine , but i can't get wi-fi working , sees acces point but get stucked at connecting and due to no logcat i can't see what isn't working
[Xiaomi Mi 2] Khaon:
There will be many simlinks missing doing so. I am not home I was not much lately into Aries dev busy in life and device still not very stable on lollipop. I will try building an f2fs image so you can try it out and give us dome feedbacks

Its very simple.

The boot IMG contains the kernel image zImage which is compressed, in our case with google's lz4, and the ramdisk.

The ramdisk is loaded first and into the ram and loads the zImage,thus the kernel, into the memory as well. The ramdisk contains among others the init binary and init.*.rc. The mount points and options are located in the fstab which is in the ramdisk.

A cm11 ramdisk won't be most likely boots or yield errors if used on a PAC man rom. They are different.

The init.aries.rc has changed as you could see from the device tree.on kk it was handling sys0 and sys1 mouting and also TDB. It is calling a special binary called dual_boot. TDB and current dual boot has been dropped during lollipop dev in favor of grub which is not released yet.

Lollipop script just mount the fstab instead of doing few checkings to handle TDB,etc.

I am using the same zImage for both kk and lollipop. But the any kernel script is not the same since there were drastic changes. If I forget to update kk when I did for lollipop. You can just inject latest zImage in the update archive. Kernel configs did not change a lot.

About logger there is indeed a config inside the kernel to enable android logs. It might be off erf. Will check. Also I will add a function disabling the other hotplugd when enabling a new one.

Sent from my nexus 10.
[Xiaomi Mi 2] Khaon:
.

Personally, the fact that the logger was off suited and did'nt bother me for smoothness reason. But even if it's sometimes, it's needed and essential.

As you said logger was indeed off.

https://github.com/Khaon/mi2_kernel/blob/lollipop/arch/arm/configs/khaon_aries_defconfig#L3037

A commit removed the logger. Someone talked about a loadable module if it can compiled as a module then I think it would be the best solution.

I assume setting to yes this would bring back logs.

I have sometimes this also on my nexus 10 with twrp

Sent from my nexus 10.
[Xiaomi Mi 2] Khaon:
I attached the android logger as a kernel module.

To load it two ways:

put the files in the folder located at

/system/lib/modules

or

put any where the logger

from console issue the following commands:

su

insmod where is the logger

google drive link