yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] USBhost:
11-15 18:54:36.078 1071 1171 E BrcmNfcJni: RoutingManager::nfaEeCallback: unknown event=2 ????
11-15 18:54:36.133 1071 1294 I OMXClient: Using client-side OMX mux.
11-15 18:54:36.186 1071 1298 I OMXClient: Using client-side OMX mux.
11-15 18:54:36.992 1071 1171 I BrcmNfcNfa: GKI TASK_DEAD received. exit thread 3...
11-15 18:54:37.295 654 1265 I ShutdownThread: NFC turned off.
11-15 18:54:37.295 654 1265 I ShutdownThread: NFC, Radio and Bluetooth shutdown complete.
11-15 18:54:37.298 654 1163 I ShutdownThread: Shutting down MountService
11-15 18:54:37.298 654 1163 I MountService: Shutting down
11-15 18:54:37.299 654 721 D VoldConnector: SND -> {7 volume shutdown}
11-15 18:54:37.299 654 722 D VoldConnector: RCV <- {651 emulated 5}
[B]11-15 18:54:37.301 151 195 W vold : Failed to unmount /mnt/runtime/default/emulated: Device or resource busy[/B]
11-15 18:54:42.449 654 722 D VoldConnector: RCV <- {651 emulated 0}
11-15 18:54:42.449 654 722 D VoldConnector: RCV <- {651 emulated 8}
11-15 18:54:42.450 654 722 D VoldConnector: RCV <- {659 emulated}
11-15 18:54:42.450 654 722 D VoldConnector: RCV <- {200 7 Command succeeded}
11-15 18:54:42.450 654 721 E VoldConnector: NDC Command {7 volume shutdown} took too long (5151ms)
11-15 18:54:42.450 654 721 W ShutdownThread: Result code 0 from MountService.shutdown
11-15 18:54:42.450 654 721 D MountService: Volume emulated broadcasting ejecting to UserHandle{0}
11-15 18:54:42.451 654 721 D MountService: Volume emulated broadcasting unmounted to UserHandle{0}
11-15 18:54:42.452 654 721 D MountService: Volume emulated broadcasting bad_removal to UserHandle{0}
11-15 18:54:42.455 654 824 W MountService: No primary storage defined yet; hacking together a stub
11-15 18:54:42.455 654 894 W MountService: No primary storage defined yet; hacking together a stub
11-15 18:54:42.457 795 795 D ExternalStorage: After updating volumes, found 0 active roots
11-15 18:54:42.458 795 795 D ExternalStorage: After updating volumes, found 0 active roots
11-15 18:54:42.466 654 670 W MountService: No primary storage defined yet; hacking together a stub
11-15 18:54:42.466 803 803 D MediaScannerReceiver: action: android.intent.action.MEDIA_UNMOUNTED path: /storage/emulated/0
11-15 18:54:42.468 795 795 D ExternalStorage: After updating volumes, found 0 active roots
11-15 18:54:42.952 654 1163 I ShutdownThread: Performing low-level shutdown...

i think thats the problem. now how to fix it...

edit: k9.8.4 is back up

also this bug i wont fix because it wants the old ramdisk from android 6.0.0.r2

not 6.0.0.r26 but i can support it for a little bet more.
[Nexus 9 Original Android Development] USBhost:
News update:

I will be taking the rest of this week off

Cough cough fallout 4, anime end cough...

But of course I will still be here just won't be working on my

Kernel this week.

Enjoy your week!
[Nexus 9 Original Android Development] tyvar1:
Great game go go go! :)

Any anime recommendation?
[Nexus 9 Original Android Development] USBhost:
Hmm... That's a hard question.

Steins;Gate

After all that was my inspiration for the internal name of my kernel.

Denver;Gate
[Nexus 9 Original Android Development] alegru:
I really like your kernel, made my tablet fly :good:

Would it be possible to include utf-8 support for cifs in your next release? Atm, only iocharset=iso8859-1 is possible, special characters won't work in cifs shares. The kernel I am using on my Nexus 5 has other charsets built in, it would be cool to have this feature.

Enjoy Fallout 4, great game!
[Nexus 9 Original Android Development] Kyuubi10:
Go ahead dev! Have some fun!

You deserve it :D

Your kernel rocks, sugoi desu!
[Nexus 9 Original Android Development] USBhost:
sure thing

also can you link me the kernel your using with your n5

so i can look into special characters stuff

thanks everyone! for all your support! :angel:
[Nexus 9 Original Android Development] alegru:
Ok, this is the kernel I use:

https://gitlab.com/engstk/hammerhead/blob/blu_spark/arch/arm/configs/hammerhead_defconfig#L590

I am no kernel developer, but this line comes to mind. Comparing it with your configuration:

https://github.com/USBhost/FIRE-ICE/blob/9.y/arch/arm64/configs/USBhost_defconfig#L3902

Seems to be relevant.

I am using Tasker to mount my cifs share, the command is:

su --mount-master -c mount -t cifs -o rw,username=xxx,password=xxx,iocharset=utf8,file_mode=0666,dir_mode=0777,noperm //ip/share /mnt/share

Thank you for looking into it!
[Nexus 9 Original Android Development] USBhost:
thanks that helped a lot

utf8 will be in the next update.
[Nexus 9 Original Android Development] USBhost:
K9.9

-| latest from google

-| memory improvements

-| bl: updated

-| utf-8 support for cifs

-| FI.d: v32

Notes:

Memory Improvements

i did some testing with lmk in trying to keep it low.

so more apps can stay in memory also trying to keep

performance while memory is low
[Nexus 9 Original Android Development] NicoGa:
Your week of rest was short, thanks!
[Nexus 9 Original Android Development] Nalorokk:
Critical kernel bug that don't gives this kernel to boot still exists. All kernels higher than AOSPM 9.8.4 is affected and works like on this video.

Returning to 9.8.4 fixes problem. Firmware is stock MRA58N with only kernel replaced to FIRE-ICE.
[Nexus 9 Original Android Development] Nikki1993:
Get the logs when issue occurs. Simply start the device and launch adb logcat, how to can be found on in the internet. Otherwise it's impossible to troubleshoot or tell if you are experiencing same issue as the others.
[Nexus 9 Original Android Development] Nalorokk:
Ok, did it
[Nexus 9 Original Android Development] jasonlai79:
I faced the same problem. AOSPM 9.8.5&9.9 can't work

我從使用 Tapatalk 的 Nexus 9 發送
[Nexus 9 Original Android Development] Nikki1993:
Same here, logs logs logs!
[Nexus 9 Original Android Development] b1g.p0ppa:
9.9 working fine here.
[Nexus 9 Original Android Development] USBhost:
hmm I was under the impression that k9.8.5 worked on MRA58N

thanks for the log

Edit: flash AOSPML should work now
[Nexus 9 Original Android Development] eded333:
Hello USBhost, there seems to be a problem with the kernel config for tegra devices as they haven't got the wiimote support enabled, nor the config, nor Hidraw. Could you enable it please? I'ts a feature I love to use on my other arm devices.

PS:

I know this isn't the place, but if you are also working on the Nexus Player kernel, if you can, check if those configs are enabled :p

Thanks for your awesome kernel!
[Nexus 9 Original Android Development] jasonlai79:
It works. Thanks!
[Nexus 9 Original Android Development] b1g.p0ppa:
Respect.
[Nexus 9 Original Android Development] Nalorokk:
Thanks, works for me too.

So next problem is that 2A charge patch actually ups charging rate from 1.3A to 1.6A which is not enough. Why don't do 2.5A? It should be safe for battery anyway.
[Nexus 9 Original Android Development] Nikki1993:
It's not about the 2A patch but the cable, outlet etc things. There is a lot of variables that influence the current output.
[Nexus 9 Original Android Development] NYCHitman1:
You can use a commit from my Shamu (also 3.10.y) kernel as a base, if you wish.

Wheatley CPU gov
[Nexus 9 Original Android Development] USBhost:
will look into it

thanks man!
[Nexus 9 Original Android Development] stonebear:
What is AOSPML?
[Nexus 9 Original Android Development] USBhost:
Android Open Source project marshmallow legacy
[Nexus 9 Original Android Development] stonebear:
Thanks man.

When would I use it instead of the AOSPM?
[Nexus 9 Original Android Development] USBhost:
Only if AOSPM does not boot
[Nexus 9 Original Android Development] stonebear:
Thanks. :)
[Nexus 9 Original Android Development] NYCHitman1:
My pleasure. Let me know if you're looking for other CPU gov's because I'm in the process of porting a slew over to Bullhead, which is also a 3.10.y kernel.
[Nexus 9 Original Android Development] wantowan2:
Hey man, thanks for the work!

Currently the kernel is messing with all of my batt stats. eg: 4,108% on my status bar. The real number is 83% Infact, it seems to be corrupting the battery app altogether as it disappears from the settings menu after boot.
[Nexus 9 Original Android Development] USBhost:
Flash AOSPM not AOSPML
[Nexus 9 Original Android Development] USBhost:
K9.9.1 is up

K9.9.1

-| memory updates (huge)

-| added Wheatley cpu gov

-| zram updated (as to 4.4rc2)

-| lmk updated

-| others updates (under the hood)

huge thanks to shminer

Note's:

LMK

The milestone has been reached. :highfive:

The truth of life has been reached. :angel:

The epicness has been reached. :cool:

our swap now will be as in normal linux

lmk will only kill when swap is near full, so this means...

no more reloads, we can finally use all our swap before lmk starts killing.

so guys dont make crazy big swap or zram

anything over 1g is way too much, hey even 700mb is too much at lest for me.

so if you dont want much lag dont make swap over 500mb.

swap actually works now guys so remember that, dont make swap too big.

do not make zram over 2g just dont.

also guys you can change the swap file location to any where you want except system

so if you have too much free room just set CSWAP to /data/swap or anywhere

CSWAP=/data/swap

just remember that ram is faster than mmc
[Nexus 9 Original Android Development] Martin_Devil:
I selected blu_active governor and tablet go in reboot
[Nexus 9 Original Android Development] USBhost:
no reboot here..

can you get a log

after the reboot

adb shell cat /sys/fs/pstore/*
[Nexus 9 Original Android Development] tyvar1:
Thank you for the update! :D

Can you be so kind to give us the recommended setup? Thanks!
[Nexus 9 Original Android Development] USBhost:
Still testing here but

If you want something moderate just go with

500mb zram only
[Nexus 9 Original Android Development] shminer:
[MENTION=5501864]USBhost[/MENTION]

HI bro.

I am JZ shminer,

I found your aospm kernel couldn`t mount usbdisk. I think you forget fix fstab.flounde.

/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/VNR /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs nosuid,nodev,flush_merge,discard,background_gc=sync wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 nosuid,nodev,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/devices/platform/tegra-ehci.0/usb* auto auto defaults voldmanaged=usb:auto
[Nexus 9 Original Android Development] USBhost:
lol thanks man i have no idea how i forgot /usb* lol

thanks for the report
[Nexus 9 Original Android Development] Nalorokk:
What governor do you prefer and use?
[Nexus 9 Original Android Development] Bastlwastl2010:
For me Wheatley ist extrem laggy in gaming, go back to interactice
[Nexus 9 Original Android Development] Nalorokk:
Since interactive is kinda laggy too, i'm looking for new governor.

Blu_active seems fast, but seems like it will eat battery very fust.

ElemenalX seems better than stock interactive, so i'm using it now.

So it's intresting what governor use USBHost, it should be best supported and tested =)
[Nexus 9 Original Android Development] Kyuubi10:
Hey guys, since I was the one to request Wheatley governor which USBhost kindly added (I'm extremely grateful), I'd like to fight it's corner and be defence attorney lol.

There is no perfect governor, unfortunately. There is no single governor which can do everything. The same is true to Wheatley.

It's major strengths are everyday usage. Such as media consumption, browsing, messaging etc...

It will offer a lag free but also battery saving experience. Using the race to idle scheme.

For thing which are constant stress on the CPU, thus not allowing it to go back into idle, Wheatley will act more like a conservative in order to save battery. Thus installing, moving large files, and yes... Gaming Will suffer due to their continuous demand on the CPU.

Wheatley is made for those who want best performance in general use, while saving as much battery as possible.

The best advice I can give (many serious power users do this) is to change the governor when you begin a gaming session.

Choose something more like blu_active.

It's great for gaming, but it will bleed out battery during normal usage.

So use Wheatley as your main governor, and switch to blu during gaming sessions.

This is what I myself do.
[Nexus 9 Original Android Development] stonebear:
Thanks for the update. :)

To enable cswap in the override file I would do "cswap=150", for example and for zram would I add "zram=500"?

No need to put "raid=1" is there? I remember something about that, I think?
[Nexus 9 Original Android Development] b1g.p0ppa:
Close. zswap instead of zram. I wouldn't think one would want to use raid=1 as it would stripe between compressed memory and a file on mmc and as USBhost said, mmc is slower than ram. Without raid=1, it will use memory first and then mmc.
[Nexus 9 Original Android Development] Bastlwastl2010:
I playing around with tasker on my tablets and its easy.....

Tasker have Kernel Audiutor plugin support. I make two profiles, One with weatley and one with blue_activ.

Task: Start App - Set Profile blue_active / Exit Task - Set profile weatley

Thats it.....
[Nexus 9 Original Android Development] b1g.p0ppa:
Tasker has built-in cpu governor settings too. Under System category. Set governor, max and min freq's. But cool to know Audiutor has support for Tasker. Could change so many system settings with one task.
[Nexus 9 Original Android Development] USBhost:
i use plain old interactive

with gfix=1

the reason why i use gfix=1 is because i need to keep things laggy so i can see if stuff improves performance

or not. its easier to find more lag when you have lag plus improving battery is also nice.

yep but make that zswap

and you can still use zswap with cswap

but cswap will be second priority. so when zram gets used up

cswap will start to be used. you also can change CSWAP to somewhere other then cache then you can make it bigger.

like cswap=500 raid=1 that will give you 1g swap, i tryed that lol its vary vary laggy lol but you can have a bunch of apps open

i had like 20-30 chrome tabs open of android police.

our ram speed is ~7gb/s

our zram speed is like ~1gb/s read and write ~600mb/s ( depends on cpu speed )

our mmc is ~150mb/s read and ~45mb/s write ( not random )( random is a lot slower it goes down to ~120mb/s read ~22mb/s write or lower )

using raid with our swap, read speed is ~300mb/s and write is ~90mb/s ( on a good day )

you learn something everyday :good:
[Nexus 9 Original Android Development] stonebear:
Thanks [MENTION=3721939]b1g.p0ppa[/MENTION] and [MENTION=5501864]USBhost[/MENTION], I will do zswap=500 and no cswap. :)
[Nexus 9 Original Android Development] Kyuubi10:
Awesome, I didn't even know that was possible. Exactly as USBhost said, you learn something new everyday.

You've got the right idea.
[Nexus 9 Original Android Development] b1g.p0ppa:
Me too. interactive and gfix=1. Wheatley is just too laggy waking from sleep, moving between apps, doing almost anything. I set my animations to 0 in dev opts and just want my stuff to *pop*. I will check out blu_active when playing World of Tanks though. Using Tasker to set an Audiutor profile just as [MENTION=4909149]Bastlwastl2010[/MENTION] outlined. I just switch back to an 'interactive' profile on exit. Will report results.

Edit: Nope. Short, unscientific test but I started off in a battle too late, a phenomenon I'm associating with too much lag in WoT with blu_active. Just didn't really keep up and battery usage--again, during a very short interval, was not noticeably better. Deleted all my Tasker profile and tasks and restored to interactive profile. Dat governor, as USBhost has it tweaked, is da bomb.dot.com. Now back to the game!
[Nexus 9 Original Android Development] Nalorokk:
So entire OS freezes 1-2 times in day, all FIRE-ICE during all kernels i'm tested. Is this known behavior?

Sometimes it just dead freeze, only reboot using long press on power button. Sometimes it says that "system process stopped alert" and "phone stopped". But completly unstable and slow after it, reboot is needed.

I don't have adb log, cause i don't want to wait for it to happen during entire day, and because it's usually happens in moments when i don't have PC nearby. I thought that it is known problem and will be fixed, but now i don't sure =(

Use stock latest official ROM. Ofcourse there is no problems at all on official kernel. Don't tested other customs.
[Nexus 9 Original Android Development] USBhost:
When it freezes can you try to wait for the kernel to panic

if it unfreezes after a while then can you install

https://play.google.com/store/apps/details?id=jackpal.androidterm

and do " dmesg > /sdcard/kmsg.txt "

then give me that file.
[Nexus 9 Original Android Development] stonebear:
Yea, Wheatley might be good on other devices but it's laggy as hell on the N9. Interactive and gfix=1 for me too.

Using the zswap seems to work well, I am happy with it. :)
[Nexus 9 Original Android Development] stonebear:
One thing though, could zswap affect battery life? Mine seems to be going down faster but it might be a coincidence.
[Nexus 9 Original Android Development] USBhost:
yes it does use more battery
[Nexus 9 Original Android Development] Bastlwastl2010:
[MENTION=5501864]USBhost[/MENTION]

is it possible to change the change the volume control buttons in landscape mode with this kernel?

Most of the time i use the tablet in landscape mode and it is terrible for me that vol+ is on the left and vol- on the right side

I think it is possible with a xposed module, but more software more failures.....
[Nexus 9 Original Android Development] Nalorokk:
It is dmesg after major lag without reboot after it. About 1 - 2 minute tablet was compeletely frozen, then something crashed, after blackscreen launcher was relaunched. Now it works, but slow and unreliable.

As you see it's uptime is around 3 hours, i don't rebooted it today, so it's actually crashed once and rebooted while it was in my handbag. I don't saw this =)
[Nexus 9 Original Android Development] Nikki1993:
I actually had the same thing as [MENTION=2462459]Nalorokk[/MENTION] but it went away when I just used default values in Fi.d script. Previously I went with OC=1 which caused tablet to freeze. Felt like worth mentioning.
[Nexus 9 Original Android Development] enriquejones666:
This is a ROM feature, not a kernel feature. You can do this in the Pure Nexus ROM.
[Nexus 9 Original Android Development] stonebear:
Ubermallow has this feature too. I am using it now, it's good. :)
[Nexus 9 Original Android Development] USBhost:
K9.9.1r2 is up

K9.9.1r2

-| FI.d: v33

-| BUGFIX: mounting usb drives

Note's:

this update is only for Android MM

i was hoping to have k9.9.2 today but i ran into some problems..

so its being delayed.

[MENTION=2462459]Nalorokk[/MENTION] try this one.

also guys hows the new lmk

does your apps stay im memory a lot more than before?
[Nexus 9 Original Android Development] Nalorokk:
Thanks, trying this one now. Cant say about that bug so fast, but it seems like faster / less lags for me than before :good:
[Nexus 9 Original Android Development] Nalorokk:
Good news everyone! =)

I'm got good logs of big crash like i'm described before (so it don't fixed yet).

It was nearly not working (very slow, all apps crashes often) condition, after system rebooted. I don't touched tablet when and before it happens long enough. I'm just saw boot animation when it happens, it was in sleep mode before.

Shell seems don't working in this condition. Android Terminal freezes, adb shell show error.

But i'm got adb logcat, and seems like it shows error good enough =)
[Nexus 9 Original Android Development] MECK187:
Hi,

where do I set cswap to 500 how USBHost recommended? I can only find ZRAM in Kernel Auditor.

Thanks

Gesendet von meinem Nexus 9 mit Tapatalk
[Nexus 9 Original Android Development] Bastlwastl2010:
Read OP
[Nexus 9 Original Android Development] stonebear:
either create a file in the root of internal storage called "override" and add the line "cswap=500" or go to system/etc/fld and open the "afterboot" file and change "cswap=0" (which means disabled) to "cswap=500".

However, I am not sure if USBHost meant 500 was good for cswap, I think he might have meant 500 was a good size for zswap (which is Zram). When I used cswap I set it to 150. Now I use either "zswap=500" or no swaps at all.
[Nexus 9 Original Android Development] MECK187:
Thank you guys.

So ZRAM=zswap which I should just set to 500 in Kernal Auditor without changing cswap value in FI.d?

Gesendet von meinem SM-G925F mit Tapatalk
[Nexus 9 Original Android Development] stonebear:
Yes, zswap is Zram and I assume you can set that in Kernel Adiutor.
[Nexus 9 Original Android Development] USBhost:
I think you meant zswap

if you wanted cswap that will be super slow at 500

also cache is not big enough for 500

but if you wanted to use cswap

set it to "CSWAP=/data/swap"

and "cswap=500"

so just make a override file in the root of internal storage

/sdcard/override

then add zswap=500
[Nexus 9 Original Android Development] MECK187:
Thanks again. What I want is to keep my Apps longer in RAM without reloading.

What would you recommend? cswap 150 only, zswap 500 only or cswap 150 + zswap 500 together?

Best regards

Gesendet von meinem SM-G925F mit Tapatalk
[Nexus 9 Original Android Development] USBhost:
zswap only

if you use cswap you swap speed will drastically decline.
[Nexus 9 Original Android Development] USBhost:
I don't see any errors in that log

are you sure that's the right log?
[Nexus 9 Original Android Development] smayonak:
I went ahead and pulled the log for the crash (it's attached). It's the same crash experienced on Elemental X and every Fire Ice kernel since 9.8.5. It has to do with Nvidia's drivers. Here's the very last log entry:

Let me know if you need anything else. The last stable build for me was 9.8.4.

Thanks again!

EDIT: I need to clarify. I'm getting crashes on boot from 9.8.5 onward. It's a clean installation of the latest factory image, using a permissive bootloader.

EDIT: I am stupid. USBHost was kind enough to include AOSPML kernels, which work if the AOSPM kernels don't work. It's mentioned only briefly, so if you're like me and missed mention of it earlier, do yourself a favor a search the thread for 9.8.5.
[Nexus 9 Original Android Development] Bastlwastl2010:
Every day i learn something new :good:

That is something for the OP.

Anyone new on this device/kernel like me never find this in this long thread, because he dont now what to search

EDIT: [MENTION=5501864]USBhost[/MENTION]

Can i also set the UV settings in the override file?
[Nexus 9 Original Android Development] USBhost:
yes I need to add it to the OP

yes... but you did not hear it from me
[Nexus 9 Original Android Development] stonebear:
What? Undervolting? Hmmm... :)
[Nexus 9 Original Android Development] smayonak:
It's really easy. Here's the instructions:

http://www.overclock.net/t/1566797/guide-howto-undervolt-your-nexus-9

I found even a tiny undervolt reduces stability. It might be because Denver uses dynamic voltage scaling. A voltage offset might not work so good with a chip that's constantly adjusting its voltage. Also, it doesn't seem to increase battery life by much, although it does dramatically reduce temperatures.

USBHost: Why is one of the kernels called AOSPML (legacy)? I recently flashed the latest build of MM using a clean installation (erased everything) and yet the mainline AOSPM kernels weren't working. Is there some way to get the N9 working on the regular AOSPM kernels?
[Nexus 9 Original Android Development] stonebear:
Thanks smayonak, btw, the Legacy is for when the normal AOSPM won't boot.
[Nexus 9 Original Android Development] Freak07:
Is anyone using du with this kernel?

I just dirty flashed latest du test version and reflashed latest r2 zip too. However I got a bootloop. On the previous test version all was running fine..

Edit: I formatted chache to f2fs and it's working again!