yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] kraatus90:
Update 4.1

Update: new build v4.1 is up.

Changelog:-

69126cb (HEAD, origin/v4, v4) update defconfig

d3ea5e9 Revert "lib/int_sqrt.c: optimize square root algorithm"

dcf2339 Revert "lower GPU volt constraints a bit"

be11060 Revert "ARM: move VFP init to an earlier boot stage"

008dc57 Revert "ARM: add support for kernel mode NEON"

95d03ca Revert "ARM: crypto: add NEON accelerated XOR implementation"

834dddbf Revert "ARM: 7835/2: fix modular build of xor_blocks() with NEON enabled"

1eb14bd Revert "arm: vfpmodule: Fix warning procfs vfp_bounce reporting failed"

edd8370 Revert "vfp: remove double entries"

6490e34 Revert "ARM: pull in <asm/simd.h> from asm-generic"

d8e46cc Revert "crypto: create generic version of ablk_helper"

9e846b6 init:disable debug

fd295a7 Revert "Add /dev/frandom support"

beeb0a0f Revert "netfilter: x_tables: Silence some debug info"

9d6e18c Revert "Optimized ARM RWSEM algorithm"

8ddf33d Revert "Makefile: sort list of defconfig targets in make help output"

d86bd11 Revert "arm:lib: Correct Neon Flags"

9ade7aa Revert "fs/namei.c: fix potential memory leak in path_lookupat"

a446773 Revert "msm: kgsl: set the correct max_state"

1e33304 Revert "ASoC: msm: qdsp6v2: Silence some noise"

d23e35b Revert "wlan: Address buffer overflow due to invalid length"

i have reverted some commits so its essentially same as v3 now ( with more tcp options). also i got reboots with su2.52 too today(on v4) so as people already pointed out it wasn't because of su2.67. hopefully this will solve reboots, i am using it from last 1 hour. and haven't faced any problems so far. :)
[X 2014 Original Android Development] Vinnom:
I just downloaded, gonna test it. Have you fixed simple_ondemand on gpu haha?

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] kraatus90:
yep , but cpubw_hwmon still crashes , although i don't really use anything else thn msm_adreno, i'll see what i can do for it.
[X 2014 Original Android Development] Junior Passos:
2.65 installed and not solved. Keeps restarting.

And 2.65 has become stable recently because until some days ago was beta.

As I said earlier, the root version is not the problem here, always I used 2.52 and always worked very well.

This problem of getting restarting only started after krait kernel v4.

But as 2.65 is now stable, I will use this version.

Great. \o/ Installed here.

I'll be watching to see if the problem has solved (I hope so).

Thank you man. :fingers-crossed:
[X 2014 Original Android Development] thomstrack:
I was with v4 for 2~3 days and I have no reboots. (SuperSu 2.52).

Installed v4.1 and until now, working fine.

Thanks man.
[X 2014 Original Android Development] iron maiden:
Good morning minimum frequency 268 does not work right? very thanks kraatus90

regards..
[X 2014 Original Android Development] kraatus90:
use kernel auditor to change minimum freq.
[X 2014 Original Android Development] colourfuldays:
i have flash v4.1 ,there are no reboots still now.but i found gpu max frequency couldn`t boost to 578MHz. the max frequency it can approched was 200MHz not 578MHz.when i set min frequency was 578MHz ,everything was smoothly especially playing games. i am using msm_adreno.
[X 2014 Original Android Development] Flipz77:
I think it's just the adreno-tz governor trolling us; even on stock kernel I never saw it run faster than 330 MHz.
[X 2014 Original Android Development] kraatus90:
try some heavy games and use a monitoring app to see frequencies. it works perfectly fine.
[X 2014 Original Android Development] Vinnom:
Hey, man. I just booted the phone, and here, using my script, the phone is mainly at 268 MHz, ae you can see in the pic :)

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] iron maiden:
Hello Vinnom auditor kernel've always used to put the frequency 268 and so is your script works such frequency version of krait you bring your? thank you

Hello forget to put thanks: good:
[X 2014 Original Android Development] Junior Passos:
[MENTION=4825505]kraatus90[/MENTION] Today restarted again. :(

I noticed that this always happens when I'm not using WiFi and mobile data are turned on.

It may be coincidence or not.
[X 2014 Original Android Development] kraatus90:
thn go back to v3 , i'll try to fix it in meantime. im kinda busy this week :)
[X 2014 Original Android Development] Junior Passos:
Okay. Thank you.
[X 2014 Original Android Development] Vinnom:
I'm running krait v4.1 :)

And yes, my script uses 268 MHz as minimum value

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] iron maiden:
Hello ok very thanks for you and developer kraatus90

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] Jostian:
Using SU 2.67 and all is fine with V4, with V4.1 I get random reboots [emoji30]
[X 2014 Original Android Development] kraatus90:
to everyone,

please use version v3 even if v4/v4.1 is running fine for you. because i want to make sure i have a solid base as v3. i'll update to v5 in 3-4 days. also please post dsmsg/kernel logs after you face a reboot. thanks
[X 2014 Original Android Development] Vinnom:
Ok, I'll go back to v3 ^^

I faced just one random reboot, then I grabbed a last_kmsg, a logcat with errors and a full verbose logcat with the last 2000 lines.

You can find it here^^

Enviado de meu XT1097 usando Tapatalk

---------- Post added at 01:50 AM ---------- Previous post was at 01:45 AM ----------

Also, just for comparison, I tested v4.1 with stock settings and with my script in PCmark. The results are as follow

Stock settings

My settings

I'll test battery too, later

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] iron maiden:
hello ok volvere to version 3.0 thank you very much

regards
[X 2014 Original Android Development] rufik:
last_kmesg says something like that:

CPU0: TZ: Non-secure watchdog bite. NS WDT

It looks like MSM Watchdog:

[B]* Qualcomm MSM Watchdog[/B]
Watchdog timer is configured with a bark and a bite time.
if the watchdog is not "pet" at regular intervals, the system
is assumed to have become non responsive and needs to be reset.
A warning in the form of a bark timeout leads to a bark interrupt
and a kernel panic. if the watchdog timer is still not reset,
a bite timeout occurs, which is an interrupt in the secure mode,
which leads to a reset of the SOC via the secure watchdog. The
driver needs the petting time, and the bark timeout to be programmed
into the watchdog, as well as the bark and bite irqs.

source: https://github.com/gokulnatha/GT-I9505/blob/master/Documentation/devicetree/bindings/arm/msm/msm_watchdog.txt
[X 2014 Original Android Development] BootloopedMillennials:
That is extremely close to new phones. Great tweaks to the interactive governor!

Could you post a better picture of the graph from My Settings results? Would like to compare it to mine below. My scores hover around 4100-4300.
[X 2014 Original Android Development] thomstrack:
Not Any reboots here with v4.1.

Only for share, my results with battery life is really great. With moderate use.

The kernel is rock stable, fast and with good battery life.

Really thanks for this amazing kernel. :)

PS: I did little changes on governor settings.
[X 2014 Original Android Development] albatros_1994:
Great kernel and battery life. I've tweaked interactive a bit(see screeshot for settings + input interval 250ms + Naptime app). 4,5sot yesterday, with stock kernel ~3.

I've noticed that scrolling multiple times with chrome or play news(play edicola in italian) sometime there is a delay. With performance governor same problem. I think the problem is the gpu idle/adreno idle. When the gpu goes to 27mhz and in the same time the user move something , the gpu need some time to return in "performace" state. A short gpu touch boost would be great.

I apologize for my raw english
[X 2014 Original Android Development] Vinnom:
Oh sure, man!

Here it is:

Hmm, maybe there is something about your config. Maybe you could take a look at my script and see the part of above_hispeed_delay and target loads. Maybe your migration load threshold is to high, too?

Take a look here

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] Jostian:
Hi Vinnom how does one use yr script, yr settings look great, would like to use the script but not sure how, thanks
[X 2014 Original Android Development] Vinnom:
Save it in your sdcard and type in your terminal emulator:

su

sh /sdcard/profile

If you are using v4.1, some errors messages will be echoed, but don't worry.

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] Jostian:
and on reboot it will be applied automatically?
[X 2014 Original Android Development] BootloopedMillennials:
Thank you!

My scores suffer at writing portion of test. Other scores are in range of stock ratings, which is great my phone is not reaching 25 degrees or losing battery during test.

Went back to Ghostpepper based governor setting and same result. Overall score dropped lower at 39xx.

Is Writing toughest part of test?
[X 2014 Original Android Development] Vinnom:
Hmm, Idk.

For me, the worst part is video playback, not sure why. But, as the script have room for improvement yet (and I'm testing fine tunes here), soon I'll balance even more this settings.

My best score was 5152 and I noticed that our device gets higher scores with 1728 MHz as max freq than 2457 MHz. Maybe because of temperature. As I'm getting good daily experience with 1728 MHz and better scores, I'll stay with it and try to improve other settings.

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] pjssilva:
Reboots with V3

Hi,

I am getting reboots with V3 too. I downgraded from 4.1 by simply flassing the zip using TWM. Did I do somtheing wrong?
[X 2014 Original Android Development] Jostian:
I flashed the new TWRP v3 and now my memory structure has changed and apps cannot find their info????
[X 2014 Original Android Development] kraatus90:
not related to the kernel. post on twrp thread.

yes , follow instructions in the op. and please ,never dirty flash a kernel like that otherwise you will get problems.

ps:- i can't seem to find any solution for reboots. only thing i know is, its a kernel panic related to wcnss. im still working on it though.
[X 2014 Original Android Development] BootloopedMillennials:
Cannot solve writing benchmark issues ran battery life test anyway.

Procedure- 50percent brightness brightness. I turned off cell (kept WiFi) to remove discrepancies. On for everything else.

6:45 is goal. Hardest is improving performance benchmarks.
[X 2014 Original Android Development] pjssilva:
I tried to follow the OP. If I understood correctly I am supposed only to flash the boot.img using fastboot. After that I can go to TWRP and flash the v3 kernel, right? No need to reboot in between.

I tried that and my cellphone is still rebooting. It rebooted one hour and a half ago. I will try to figure out how to get the syslog to see if I can discover what happened.
[X 2014 Original Android Development] Vinnom:
WOW, this is great man! The one I ran gave me 4 h 54 min. I think it is because my settings are too agressive. Like yours, I let everything on and 50 percent of brightness.

I'll try to have things here less agressive (not too much, although I like battery life, smooth performance is essential to me).

[MENTION=4825505]kraatus90[/MENTION] I had three random reboots so far, since I switched back to v3 (of course I did a clean flash). Two of them, yesterday and the third, today.

Here are the logs (I always grab last_kmsg, errors logcat and verbose logcat last 2000 lines. If another is needed, just tell me):

First reboot

Second reboot

Third reboot
[X 2014 Original Android Development] BootloopedMillennials:
Expected battery to be better than mine. Average CPU percentage was greatly lower on your graph. Took as your CPU is doing less work?

A middle ground between our settings would be nice. Would be tough since polar opposites comparing. Only share timer rate in common. lol

PCMark stock values

http://www.futuremark.com/hardware/mobile/Motorola+Moto+X+%282nd+Gen%29/review
[X 2014 Original Android Development] Vinnom:
Oh, forgot to look at my battery graph. In fact, it seems my battery is not so healthy anymore, look

Suddenly, after 20% it just drops almost instantly to 0.

I had already noticed some awkwards behaviours like that here. But, it didn't occur all the time, so I never paid too much attention.

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] BootloopedMillennials:
Battery calibration, overheated and shut off, or bad battery. One of those.
[X 2014 Original Android Development] Vinnom:
I think that is bad battery, at least the first symptoms.

I do battery calibration almost every week and the graph doesn't point out overheat :(

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] BootloopedMillennials:
Graph showing CPU temperature? Can be battery temperature.

These batteries could survive years if kept between 20%-80% charge. Going below 20% every week to calibrate can be bad.
[X 2014 Original Android Development] Vinnom:
You are right. I'll try to keep an eye at battery temperature.

There was a time there I could calibrate once per month or 2 months. But now, every week, for some reason I full discharge it. Then I take the chance to calibrate.

Other problem is that Brazil is too hot and our humidity is too high. Our phones don't dissipate heat right. Everytime I'm gonna charge it, I have to put it on a ceramic or granite surface (principally using turbocharger).

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] kraatus90:
Update

Bad news guys, yesterday i bricked my phone while flashing a test kernel, now the bootloader seems to be f@#ked. pc can't detect the device nor it enters in twrp/bootloader mode. since the device is still under warranty, i've sent it for repair and they said the motherboard is gone and it will take 2-3 weeks + 100$. so im thinking of ditching the device unless i find a cheaper solution and probably gonna wait for sd820 phone because there's no point spending 100$ on a device which is going to be stuck at marshmallow (witth crap camera) anyway.

so the development of this kernel is stopped until i find a fix for my phone. if not, the development is stopped for ever. because i can't develop it without phone otherwise it will be not stable or work as it's supposed to. sorry for stopping this but i have no choice. :(

im still trying for free replacement from motorola but not sure if they will do that. thanks for your support :)
[X 2014 Original Android Development] pjssilva:
Kraatus,

I am so sorry for what happened. Anyhow thank you very much for your work. Hope you get a replacement.
[X 2014 Original Android Development] Xtremelyevil:
Is it just me or is the download for v4.1 missing?
[X 2014 Original Android Development] kraatus90:
you can find it here. but v4/4.1 are not stable so better use v3 or older.
[X 2014 Original Android Development] Xtremelyevil:
Oh okay, thank you.

Hope you can get back to developing asap (please Motorola be kind).
[X 2014 Original Android Development] Xtremelyevil:
I have been encountering a strange issue since flashing the kernel (not sure if it's kernel related).

After my phone has been idle for a little while , my screen just stays black after unlocking my device, I hear the phone unlock but the screen is stil black.

Could anyone help, because the issue persists after a few reboots.
[X 2014 Original Android Development] karanrajpal14:
Alright. I'll wait for it. Thanks!
[X 2014 Original Android Development] Jostian:
Which version are you on?
[X 2014 Original Android Development] Xtremelyevil:
I'm on v3 of the kernel
[X 2014 Original Android Development] Jostian:
I had problems with V3, but V4 is the best for me, maybe give it a try
[X 2014 Original Android Development] Ozonethegreat:
Will this work on the XT1096 with Nexus Experince Rom?
[X 2014 Original Android Development] Xtremelyevil:
I disabled Doze and I will see if the issue persists , if it does I will try v4.
[X 2014 Original Android Development] szymel00:
No, this is only for stock. ;)

Wysłane z Victara MM
[X 2014 Original Android Development] Jostian:
Hi, how did you disable doze? thanks
[X 2014 Original Android Development] Xtremelyevil:
When I say disabled I do mean "I think I maybe did disable Doze"[emoji14], but I used Doze Setting Editor to do so. And set Inactive Timeout to an absurdly high number.

So far the bug hasn't occurred to me so I might have fixed it , but I'll have to continue testing for a few days to see if it really did work.
[X 2014 Original Android Development] igor_anta:
So both v4 and v3 game me random reboots and some minor signal issues and I decided to get back to stock kernel.

The problem is I don't have WiFi now. Can someone please point me to a fix? Thanks in advance, cheers.
[X 2014 Original Android Development] piccit:
Try re-flashing system
[X 2014 Original Android Development] kraatus90:
https://www.androidfilehost.com/?fid=24399994186368326
[X 2014 Original Android Development] Jostian:
I found that using V3 and V4 with Kernel auditor and synapse gave me reboots but using V4 without synapse or auditor gave me o problems...
[X 2014 Original Android Development] igor_anta:
Thanks kraatus90, that did the trick.

I'll actually try that out and report. @ Jostian what about v4.1, did you try that one?
[X 2014 Original Android Development] Ozonethegreat:
Ok, thanks
[X 2014 Original Android Development] Jostian:
v4.1 gave me reboots with and without synapse/auditor.
[X 2014 Original Android Development] Vinnom:
I had no problems when I flashed v4.1. I just flashed back v3, because kraatus90 asked to, so he could have a solid base to continue the development. As he can't continue developing, I'll try v4.1, at least for a few days. If I have no problems with, I'll stay at it, as I want to use other tcp congestion controle and use simple ondemand as gpu governor

Enviado de meu XT1097 usando Tapatalk

EDIT: [MENTION=4825505]kraatus90[/MENTION] do you have v4.1 yet? I forgot that I deleted it from my storage and it can't be seem anymore to download.
[X 2014 Original Android Development] kraatus90:
here :)
[X 2014 Original Android Development] Vinnom:
Works flawlessly for me :)

Have you news for us, about your device?

I noticed that my battery isn't healthy anymore :( sadly is too soon for me, I wanted to wait until Nexus 5X to come to Brazil :/

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] kraatus90:
yea, they sent me a new phone for free lol. im working on new build. but i'm thinking of selling it for nexus 5x or wait for s7 , not sure really.

i don't really want to use those hot 6-8 core inefficient phones.
[X 2014 Original Android Development] LeoS2016:
Please don't leave us ahah ;) this project is really interesting, I'm anxiously waiting for a stable build. Your kernel seems promising, I appreciate it. However, if you decided to sell your Moto, I suggest you to wait for next gen. N5X is not a big jump...
[X 2014 Original Android Development] Tinchoska:
Can I use trickster to modded the kernel? I've have it pay so... and any advice to tweak? I want to have more than 5 hrs.... I missed that ; (

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] Tinchoska:
I can't find the v4 download link... Can someone tell where I can get it?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] kraatus90:
i removed v4 because it's very unstable. and i don't have a copy of it.
[X 2014 Original Android Development] Tinchoska:
Oh, perfect, didn't know that, so v3 is the one?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] Vinnom:
v3 is the most stable one, at least the most stable that was reported.

For me, v4.1 works fine (just a few posts before yours, the link is there)

Just don't you forget to always flash over stock boot.img.

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] Tinchoska:
I've already flash root so I have flash the modify boot from super Su, I need to flash stock boot and then this?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] kraatus90:
no offense, but have you read the op ?
[X 2014 Original Android Development] Tinchoska:
LOL I've read the OP, didn't get what to do, maybe because ive read it very fast.... Yesterday I've read it and did it. So, v3 is the one stable enough to be as a daily use right?

Enviado desde mi XT1097 mediante Tapatalk

---------- Post added at 10:05 AM ---------- Previous post was at 09:39 AM ----------

I know you write to use kernel auditor or Synapse, but if I prefer to use trickster MOD? Is it going to work anyway?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] Vinnom:
My steps are always:

- Flash stock boot.img

- reboot bootloader

- Flash root boot.img

- reboot bootloader

- Boot into recovery

- Flash krait kernel (whatever version, stable one is v3) and superSU

- Reboot system

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] Tinchoska:
Thanks for that my friend, I've already done it after reading it with attention.

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] Vinnom:
For some reason, I'm getting strange behaviour.

Last week I had a problem with my SIM: it wasn't being recognized. So, as it was probably a issue regarding xposed framework (which I was testing how worked for me) I knew what I had to do: install factory img (the retail for my device).

I tried other workarounds before, as I always get lazy when I have to fresh my phone like this. As they didn't work, I had to do what I had to do.

After this, after restoring my apps, restoring my accounts etcetera, I went to reflash krait kernel. The strange behaviour enters here: the phone is rebooting everytime, stuck at minimal actions... I just don't know what to do =/ for now, I'll have to stop using krait, until I figure things out here.

I'll try other things, flash ealier versions (already tried v3 and v4, the issues are the same) and try over and over. I'll grab some logcats too, as it can help in future development.

Cheers

EDIT:

Well, I could solve it quicker than I expected!

STEPS:

- Flashed stock system.img + boot.img. Used it a bit, without any reboots or stucks.

- Flashed root boot.img, then superSU. Used it a bit, without any reboot or stucks.

- Flashed krait v1. Used it a bit, without any reboot or stucks.

- Flashed krait v1.1 (over krait v1). Used it a bit, without any reboot or stucks.

- Flashed krait v2 (over krait v1.1). Used it a bit, without any reboot or stucks.

- Flashed krait v3 (over krait v2). Used it a bit, without any reboot or stucks.

- Flashed krait v4.1 (over krait v3). So rebooted the phone and in bootlogo screen, it rebooted. Then, after this little reboot, it booted normally and didn't reboot so far.

Everything now is working normally.
[X 2014 Original Android Development] LeoS2016:
Do you suggest try it now or just wait for v5.0 (wich might be the stable one)? I want to calibrate the display and a better control... I don't mind fc, but can't stand random reboots ahah
[X 2014 Original Android Development] Vinnom:
Well, you can try the steps that I described and report the results.

After doing this, I had no more reboot so far. Seriously, v4.1 is very stable for me.

[MENTION=4825505]kraatus90[/MENTION] the only issue is that I can't use init.d with my scripts yet :(

Enviado de meu XT1097 usando Tapatalk
[X 2014 Original Android Development] kraatus90:
its working fine for my friend. i don't use it so no idea :p. im using test version since 3 days. so far no reboots or fcs. once i sortout some stuff i'll release it. just want to make sure its rock solid stable cuz it weill be last update as im selling this phone. gonna get that G5 :good:as i dont think samsung will release sd820 version of s7 here .
[X 2014 Original Android Development] rickk182440:
hey, this possible for cm13?