yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] Vartom:
I am with my version of the kernel does not have a delay until the processor warms up to 50-55 degrees temperature. At a temperature of about 40 degrees, he simply flies! I can not really understand this processor is so sensitive to heat. Whenever taking a tablet after prolonged inactivity (cooling) it flies, once loaded it does not matter what the response and ease of the flight departs. I would not call it hard but they are noticeable delays.
[Nexus 9 Original Android Development] jolinnard:
I'm on stage3 today (stage4 was bad as you said), no freezes during all day. I've been playing my regular hour of Real Racing 3 without freezes or lag.
[Nexus 9 Original Android Development] USBhost:
New post where ill be posting builds

stage 3 failed uptime unknown but under 18h

going to stage 2 to retest.

Edit: stage 2 failed...

going to stage 1.

i'm so close now i can taste it!!

this is a good testing tool

"stress -m 1 --vm-bytes 500M --vm-keep --vm-hang 1"

Edit: trying something

https://github.com/USBhost/FIRE-ICE/commit/9084f39892465509885994f7c1db2c9d9b9847ad
[Nexus 9 Original Android Development] liang512:
What are all the stages? I don't know which one.
[Nexus 9 Original Android Development] USBhost:
dont worry what i said earlier they both failed.

what i mean about stages are https://github.com/USBhost/FIRE-ICE/commits/TMP1

im trying to find what is making the freezes
[Nexus 9 Original Android Development] liang512:
I just flashed stage2.zip and will report back tomorrow. Thanks for your hard work! :good:
[Nexus 9 Original Android Development] liang512:
Yes. Stage2 had a freeze. Flashed stage1, and will see how it goes.
[Nexus 9 Original Android Development] USBhost:
dont worry about testing stage one... it failed

______________________________________

well guys i have some good and bad news

The good news pretty much all my commits and cheery-picks 99% of them are cleared.

but the bad news.

the problem lies somewhere around here down https://github.com/USBhost/FIRE-ICE/commits/e23562722d1ef9a4f7c4a618fcf67dc20917d9c8

there's not much more i can do to test....

but i wonder if this is it..... https://github.com/USBhost/FIRE-ICE/commit/67f95ce62825ab634f353d27ca7feae88d2838c2 because that was a bad hack i did a long time ago....
[Nexus 9 Original Android Development] jolinnard:
Yeah... stage3 fails to me a few minutes ago...

Let's try then with that revert... Back to start.
[Nexus 9 Original Android Development] Vartom:
I do not understand what you are testing. I launched this stress with different parameters it works all the tests were successful.

In addition to the tests in that cause memory overflow, for example " stress --vm 32 --vm-bytes 64M --timeout 60s ".

log

[ 6818.593381] binder: undelivered transaction 708955

[ 6818.610047] binder: undelivered transaction 708953

[ 6818.614496] binder: 648:648 transaction failed 29189, size 100-0

[ 6818.787420] binder: 648:648 transaction failed 29189, size 100-0

if I run the test with the following parameters " stress --vm 20 --vm-bytes 64M --timeout 60s " will be successful.

" stress -m 1 --vm-bytes 500M --vm-keep --vm-hang 1 " With these parameters, the tablet works as though it has very little free memory. Chrome browser tabs are reloaded from the second - the third. and it's clear why.
[Nexus 9 Original Android Development] USBhost:
Im testing what's making the freeze....

if it was runned for like 4h or more then use like normal then it will freeze..

stress just helps it happen sooner

ps binder stuff that's normal to happen.

and i think this is the reason why the freezes happen

Watchdog unhandled level 2 translation fault (11) at 0x00000000, esr 0x92000046

im testing this now https://github.com/USBhost/FIRE-ICE/commits/TMP2

only f2fs and using the stock defconfig.

Edit:

nice log!! http://pastebin.com/6yHxNgTC

Edit hmm... https://github.com/USBhost/FIRE-ICE/commit/84906535bc2fb479cb31155b11f682ef538b007b

i missed that update, it was pushed 5 days ago

todays build is all stock but for f2fs

Edit: Good new! all my commits are cleared :laugh::laugh: now im investigating what happened in the NDP5 merge

this build is testing cma
[Nexus 9 Original Android Development] Vartom:
I recently came across the following bug.

http://pastebin.com/G6RZXy2V
[Nexus 9 Original Android Development] USBhost:
I get that too but that has been there since beginning of time :good:

It's most likely a Hardware problem. So don't worry about it :fingers-crossed:
[Nexus 9 Original Android Development] liang512:
Use the latest test 10-18.zip. No freeze over 2 days.
[Nexus 9 Original Android Development] USBhost:
Same 1 day 18 hours uptime

Only 48% of that was sleep :good:

I think I found the problem!

I will declare it solved when my uptime is 2 days

Edit: Declared fixed 10:58PM

flounder:/ $ uptime

22:58:33 up 2 days, 0 min, 0 users, load average: 1.71, 2.17, 2.16

flounder:/ $

"How often have I said to you that when you have eliminated the impossible, whatever remains, however improbable, must be the truth?" --- Sherlock Holmes

Well Google you messed up :cool:

War is won! all cheers!!! :D:p;):):laugh::fingers-crossed::good::highfive:

thanks everyone for your help!

Be ready for the official update this Friday or Sunday

[MENTION=2489052]NYCHitman1[/MENTION] try this, it will theoretically fix your recovery problem.

https://github.com/USBhost/FIRE-ICE/commit/f30ed1f1634856fb8e32113c346b9bec5eb18b48
[Nexus 9 Original Android Development] NYCHitman1:
I'll check it out. Thanks for sharing!

EDIT: Didn't work, but that's OK. I'll keep on trucking through.
[Nexus 9 Original Android Development] Vartom:
It looks like a game with the following directions

https://github.com/USBhost/FIRE-ICE/commit/ac3d4a629b47f52f26a56a341ca9158637100054

https://github.com/USBhost/FIRE-ICE/commit/f51933d5bc53905c23ef3f86852508d0d209193e

But where is the truth?

Maybe it all started from here for this?

https://github.com/USBhost/FIRE-ICE/commit/951b641e00c9975deea3f625c652b0ca0bfa3e3a

The kernel nvidia Shield does not have anything like this and it works

https://github.com/CyanogenMod/android_kernel_nvidia_shield/commits/cm-13.0/mm/page_alloc.c
[Nexus 9 Original Android Development] USBhost:
are you sure???

i just built AOSP bootimage (android-7.0.0_r14)

and flashed SuperSU and all is well

even stock recovery flashed it fine

[MENTION=2489052]NYCHitman1[/MENTION]

can you send me your boot.img
[Nexus 9 Original Android Development] USBhost:
K10.5 is up

K10.5

-| linux: 3.10.104

-| latest: f2fs

-| latest: from google

-| dropped: the gpu updates from K10.4 :: they will come again

-| fix: Magisk usage with this kernel

-| fix: a full system freeze :: it may seem its not fixed... but it could just be me.. anyone else still get it?

-| fix: SuperSU failing to install on a custom ROM:: i no longer get it so i think its fixed....

-| Most likely a lot more i dont remember its been like 2 months without updates haha sorry...

well guys it's been a long 2 months.... and that bug is finally fixed....

but a lot of good things came from this bug... like they say problems bring innovation!

it made me go though a lot and make fixes/cleanups in my install script/kernel code...

i can say now it looks a lot more pretty than before :good::good:

Note's:

i was working on low memory killer to try to make it more friendly/even to all but i did not have enough time to test.

here are some things to expect: some lag after some time because swap gets full, apps can stay in ram when they

should really be killed, in some time when starting a big app it will really lag for a short bit until things are killed.

there should be an update soon to fix it :laugh: so just F.Y.I.

P.S. if it turns out if that system freeze is still here dont worry i won't pause the updates :fingers-crossed:
[Nexus 9 Original Android Development] NYCHitman1:
Build a stock AOSP boot.img and that's my boot.img.
[Nexus 9 Original Android Development] Bastlwastl2010:
Install 10.5 on CM13

After 12 ours with my "normal" gaming and surfing:

Battery life ist significant better then last 10.4 (1 our)

Tablet is not so warm...(i dont say "hot")

It feels smoother then last 10.4

Hm is this the reason:

* dropped: the gpu updates from K10.4 :: they will come again
[Nexus 9 Original Android Development] CerB:
Is there any rom with nougat for the N9 ? cant find anyone, and if not, why ?
[Nexus 9 Original Android Development] Choochter:
Is DTTW broken in K10.5 or is it just me? Kernel Adiutor says its enabled, definitely isn't. Running Pure Nexus, Marshmallow
[Nexus 9 Original Android Development] USBhost:
i pulled it because of an installer bug(nougat) but it's fixed now

it's up on the GNU side. upload where im at is slow

sorry

hmm it should work... make sure it enabled in settings
[Nexus 9 Original Android Development] Choochter:
It's set on in the settings and, as I mentioned previously, also in KA. Was OK in 10.4.2
[Nexus 9 Original Android Development] USBhost:
its working fine here....

try rebooting. i did nothing to DTW on K10.5
[Nexus 9 Original Android Development] jlokos:
Yes; just look in Android development section.
[Nexus 9 Original Android Development] USBhost:
So that's what he meant....

Hah my bad I thought he said my kernel downloads was no where to be found

Because they where down when he posted. haha :laugh:

I read his post to fast...
[Nexus 9 Original Android Development] USBhost:
Idk but I'm glad it's working better for you :victory:
[Nexus 9 Original Android Development] Vartom:
I believe that there something wrong with NvMap MemFree.

Kernel FIRE-ICE N K10.5 10-22-2016.zip
[Nexus 9 Original Android Development] dictionary:
Have to grab a log when I'm free, but double tap to wake stopped working after flashing the latest MM kernel
[Nexus 9 Original Android Development] Bryanx86:
It has also stopped working for me as well
[Nexus 9 Original Android Development] dumdum2:
I've installed FIRE-ICE K10.5 10-22-2016 and now the device won't wake with double tap on de screen have to use the power button. Any solutions?
[Nexus 9 Original Android Development] Choochter:
So, not just me then, I reported this yesterday. What's worse, I went back to 10.4.2 which was previously OK but DTTW is still broken
[Nexus 9 Original Android Development] USBhost:
is the problem with only the MM version?
[Nexus 9 Original Android Development] dumdum2:
I also tried to reverse and install 10.4.2. and 10.4 when doing it my nexus crashes and reboots seconds after starting. I had to reinstall 10.5.

I'm using MM
[Nexus 9 Original Android Development] Choochter:
Got DTTW back by dirty flashing my OS and 10.4.2 - also on MM
[Nexus 9 Original Android Development] Bryanx86:
Also on pure nexus mm [MENTION=5501864]USBhost[/MENTION]
[Nexus 9 Original Android Development] buttie:
I'm on AICP nightlies with Android 7.0 and have the same problem. After flashing 10.5 I cannot flash any other kernel. Flashing ROM (with provided kernel) - bootloop, flashing ElementalX - bootloop, flashing 10.4.2 - bootloop. Only after re-flashing 10.5 system starts again.

BTW: I still have freezes on 10.5 but not so often like on stock or AICP kernel.
[Nexus 9 Original Android Development] tamjan:
SELinux is disabled on 10.5. Maybe that's why?
[Nexus 9 Original Android Development] dumdum2:
Not disabled, it's Permisive
[Nexus 9 Original Android Development] Bryanx86:
I have mine on enforcing and still no dt2w
[Nexus 9 Original Android Development] tamjan:
Mine says disabled...
[Nexus 9 Original Android Development] USBhost:
DT2W i may know why....

it's not because of SELinux.

i think it's because of https://github.com/USBhost/FIRE-ICE/commit/d042dd6db92cd82088ce1b8e0d8278be774a5d3e

try this build....

DT2W works just fine for me on Android N
[Nexus 9 Original Android Development] Choochter:
Sorry, didn't fix it for me - Pure Nexus
[Nexus 9 Original Android Development] USBhost:
k looks like im going on an adventure to Android 6 :fingers-crossed::fingers-crossed: wish me luck

Edit haha found it !!! K10.5.1 will be up soon
[Nexus 9 Original Android Development] USBhost:
K10.5.1 is up

K10.5.1

-| FI.d: v53.2

-| fixed: DT2W

-| fixed: battery label if it was bad on all naught custom ROMs :: let me know how it goes

Note's:

Low Memory Killer now has a 30MB between levels starting from 100MB to help with the lag.

That DT2W problem was because of power.flounder.so not being loaded on MM.

P.S. remember guys if you have a bad battery label just let me know
[Nexus 9 Original Android Development] dumdum2:
10.5.1 - Solved DT2W. I'm on MM Pure Nexus.

Thx
[Nexus 9 Original Android Development] enriquejones666:
Would you recommend this ROM over shiznits Noougies ROM? I know he's been busy and hasn't had time to get up to 7.0_r14 yet.
[Nexus 9 Original Android Development] jlokos:
I wasn't able to get Noougies rom running on my device. AICP and F&I kernel working great for me.
[Nexus 9 Original Android Development] liang512:
It fixed battery label on Noougies ROM. Thanks so much!
[Nexus 9 Original Android Development] buttie:
I would recommend, but remember that those are still early age nightlies. There are builds which are almost unusable and builds (like last one 20161024) which in pair with 10.5.1 didn't freeze on me even once yet.

Sorry for off-top [MENTION=5501864]USBhost[/MENTION]
[Nexus 9 Original Android Development] fleischbanane:
[MENTION=5501864]USBhost[/MENTION]: Can you please add the new builds to your release-postst? I can't find a way to enter the download-section with the XDA-App and have to open the thread in chrome everytime I want to download an update. And if you want to use the download-counter in the download-section, can you please add a link to the download in the release-posts?

Thanks for your great work especially regarding the freeze-bug! :good:
[Nexus 9 Original Android Development] dictionary:
Why not just go to the op, and click Download Here? That's what I do, then click on whichever one I want, and download. It opens up in a browser. It's seriously not that much work for us to do considering how much work he's doing for free. Just something to think about.
[Nexus 9 Original Android Development] fleischbanane:
Sorry if I'm blind, but I only see the download link to the GCC. :(
[Nexus 9 Original Android Development] jolinnard:
In the OP there is a link like this:
[Nexus 9 Original Android Development] fleischbanane:
Ohhhh I'm so sorry, I thougt it's the toolchain... :eek:
[Nexus 9 Original Android Development] buttie:
That's my uptime on 10.5.1 (with last AICP 12 nightly) without single freeze:

flounder:/ $ uptime
12:17:03 up 2 days, 13:41, 0 users, load average: 4.83, 4.23, 3.07

Now I'm testing FIRE-ICE on new build of AICP with Android 7.1 merged, will report back after few days.
[Nexus 9 Original Android Development] USBhost:
Awesome!
[Nexus 9 Original Android Development] damngood98:
Are you using the Google or GCC version?
[Nexus 9 Original Android Development] buttie:
I'm using GCC and on AICP 12.1 (Android 7.1) I'm almost up to 48 hours without freeze.
[Nexus 9 Original Android Development] chancex:
i don't why lose the wifi? any idea?
[Nexus 9 Original Android Development] USBhost:
If I understood you

you are saying that you have no wifi?

If so update your vendor
[Nexus 9 Original Android Development] chancex:
Thanks support

let me list the software version

OS: cm-13.0-20161030-NIGHTLY-flounder.zip

Kernel: FIRE-ICE K10.5.1 10-24-2016.zip (2 type GCC most try it)

Xposed: xposed-v86-sdk23-arm64.zip

Other: vendor-build-prop-fix-signed.zip

Flashtool: TWRP 3.0.2

after flash and boot, login system can't connect the wifi and can't find any wifi ap(just scan).

need help!
[Nexus 9 Original Android Development] USBhost:
Flash the latest vendor.img for your device

That should fix it.

Latest Marshmallow one
[Nexus 9 Original Android Development] chancex:
Same...

maybe try other way

thanks a lot
[Nexus 9 Original Android Development] buttie:
Are you sure you've installed latest vendor for MM (version MOB30W)?

Pro-tip: don't use vendor-build-prop-fix then you'll always know if you have correct vendor version for your current ROM.
[Nexus 9 Original Android Development] chancex:
Im use the CM ROM.
[Nexus 9 Original Android Development] buttie:
Doesn't matter, CM 13 is a Marshmallow ROM, you need latest vendor from Marshmallow, that means version MOB30W.

If you unpack your ROM zip directory system you can find file build.prop, if you open this file in Notepad those two lines will always show you correct vendor for your ROM:

ro.build.description=volantis-user 6.0.1 MOB30W 3031100 release-keys
ro.build.fingerprint=google/volantis/flounder:6.0.1/MOB30W/3031100:user/release-k

Anyway, we are way off-topic, further help you should seek in CM thread.
[Nexus 9 Original Android Development] chancex:
thanks

but i flash to factory image, thanks again
[Nexus 9 Original Android Development] cunningstunts_1:
At the weekend, I installed the last available version of Purenexus with the latest FireIce kernel. I have to say, this is the best my Nexus 9 has ever been. I've been using Purenexus and FireIce since the start of the year and have always suffered with freezes. It seems like this is now resolved, so congratulations dev, you seem to perfected the kernel. Thanks for your work.
[Nexus 9 Original Android Development] USBhost:
K10.5.2 is up

K10.5.2

-| FI.d: v54

-| latest: from google

-| some: swap updates

-| some: ksm updates

-| fixed: some lag because of zram

not a big update.....

i will work on fixing substratum in the next update!

thanks [MENTION=4118860]davall[/MENTION]

Today is my 2 year anniversary of this kernel!!! :fingers-crossed::cool::victory::highfive::p:D:o:):cowboy:

Thank you all for the support!

it's amazing how much i have learned in just the past two years...

I was a noob back then... well im still one now lol...

but hey i know so much more now than what i did back then! :cool:

I could not have done it without you guys!

Thank you!
[Nexus 9 Original Android Development] Bryanx86:
I was curious your input on what might happen were I to flash your kernel after having already applied a substratum overlay that I'm going to stay with? Do you think it would cause a bootloop? [MENTION=5501864]USBhost[/MENTION]
[Nexus 9 Original Android Development] USBhost:
off hand i dont know much about substratum.

someone told me of if it was already applied it would work.

but if it was not the overlay won't apply.
[Nexus 9 Original Android Development] wantowan2:
Hi!

I don't use it much but I think all you have to do is open the them you used in "overlays", then " rebuild"?? At worst you would select all/uninstall selected. Reboot then do it over again the way you like it.

DEV!!! I don't know if I should call you USB or Mr. Host....

Well, well, well. I have been distracted but now I have N on my N9 I came back looking for a kernel. It seems this horrible lag has followed us into N. It was even in Slim. As I know the device maintainer for slim personally and was surprised.

I wish I had the time to really dig into this device again to see what is going on.. . I just wanted to say that I can see how much work you have put into this kernel. Original functionality has definitely started coming back! Haha I can multitask, open multiple web based apps and everything.

As it is still early for N its a bit hard to know where any of the remaining little items are (front or back end). Keep it up man, its really working out.

Thanks!
[Nexus 9 Original Android Development] USBhost:
News Update....

I'm getting some progress with substratum

I think i found the problem...

It seems aapt is not being copied to /system/bin/

Edit: one workaround is to do

adb root

adb remount

Then apply

Edit 2: it seems to be more there problem than mine....

substratum does not like busybox's mount....

Edit 3: i seem to have fixed it. substratum is working fine in my testing

but note you will have to flash your ROM again
[Nexus 9 Original Android Development] Bryanx86:
So need to reflash rom then kernel, what if substratum is already applied? I've not installed any busy box other than one in line with rom
[Nexus 9 Original Android Development] USBhost:
If it's already applied your fine. No need to reflash.

If it's not applied you will have to reflash.
[Nexus 9 Original Android Development] buffal0b1ll:
Not sure what the problem people are having with Substratum is. I'm having no issues enabling/disabling overlays with Substratum at all on:

FIREICE N 10.5.2 Google GCC (no tweaks)

phh superuser 259

Subs 490

Masq 15

Android 7.0 with 11/5 security updates

I should also disclose that I was originally on EX 5.05 on Substratum's first launch, grant Susbs/Masq root, complie enable overlays. Then I gave the 10.5.3 build a whirl and Substratum did enable/disable overlays OK. But I had weird SE Linux issues on 10.5.3 like Terminal Emulator not able to getenforce or setenforce, and AdAway not able to apply hosts file whether permissive or enforcing. I've since switched to FIREICE 10.5.2 and all is working as expected.
[Nexus 9 Original Android Development] USBhost:
Thanks for the report....

yea that way it would work. The problem was if FIRE-ICE was flashed first before "complie enable overlays".

The problem that I seen was that substratum could not mount system/could not push aapt.

I never touched getenforce/setenforce...
[Nexus 9 Original Android Development] buffal0b1ll:
Just to be clear, disabling/enabling overlays is working fine on 10.5.2 with phh259 now. The first go at enabling overlays was on EX 5.05 with phh259, then I flashed stock ROM boot.img, 10.5.3, and phh259 and booted and tested things, lastly flashed 10.5.2 and phh259 which is where I'm parked now.
[Nexus 9 Original Android Development] USBhost:
Last test

this is the last test.

If Substratum does not work then do this.

Note: make sure mount namespace is off in supersu.

/system/etc/FI.d/lib/busybox mount -o rw,remount /system
/system/etc/FI.d/lib/busybox mount -o rw,remount /vendor

Also Note: Substratum's way of checking systemless mode is bad!

i dont understand it.... it seems if mount is modified substratum would fail.

Good News! the regression from K10.5 is now fixed!!! cheers!

overall performance should be improved now.
[Nexus 9 Original Android Development] wantowan2:
Woot!

Haha, I just had too many apps opened and froze. So I came over to look for an update....perfect!
[Nexus 9 Original Android Development] USBhost:
Here's the late patch notes lol

K10.5.3

-| FI.d: v55

-| latest: from google

-| some: f2fs updates

-| some: cleanups from past merges

-| dropped: disabled selinux (it will stay permissive)

-| back to cortex a57 (a72 did not seem to help)

-| attempt to fix Substratum (it seemed to work for me)

Note's:

Substratum

In this update i stopped replacing stock mount with busybox's version.

In my attempt to fix substratum (im not happy with substratum btw).

SELinux

I decided to drop having selinux disabled it just became to problematic to keep,

and it made a lot of problems for users to switch kernels. so permissive it shall be...

goodbye clean kernel logs :crying:. i will find a way to make you clean again!

EDIT: i forgot to add i will be gone for the next 4 days on a cruise (NO INTERNET)

so i wish everyone safe journeys!
[Nexus 9 Original Android Development] wantowan2:
Hey cool, will give this a shot. Was having some freezing when going from one open web app to another with recents. Hard reset required. It would start there but would still get haptic feedback for a few taps before it would stop. During this time hardware buttons would still work. Could blank and unblank display, open power options but not be able to select anything. Synapse wouldn't be there. Work around was to keep recents simple and/or minimize everything before starting something new.

Oh ya it was the GNU version of the N version that I was using.

And you were right. The last update did do away with A LOT of the old MM lag issues, wicked!!!
[Nexus 9 Original Android Development] wantowan2:
Hey, pulled a driver log. It seems to have some interesting stuff in there. Maybe a good source for some fixes?

http://pastebin.com/RLrXSfbY

Hope this helps. ?