yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] TotallyAnxious:
It's stable for me at 204, which is the lowest option.
[Nexus 9 Original Android Development] CerB:
was thinking about the top freq, i have mine at 1500 max and high frew 1100, GPU at 600, i dont really feel any diffrence using my device.

Yesterday i got 4,45 SOT, and was playing GTA San andreas for 3,45 hours.

I think that is really nice numbers. put it on the charger with 15% left.
[Nexus 9 Original Android Development] mrshades812:
Excellent job on the ElementalX app [MENTION=4684315]flar2[/MENTION]!

Put it through it's paces, and it works well. I like the power mode switching, very cool. :)
[Nexus 9 Original Android Development] Scotlac:
As I mentioned earlier my N9 is running amazingly with this latest release! There is one strange thing going on and although I'm not sure it's related to the kernel it started right after I flashed.

Every time I reopen Chrome it asks me to sign in as if it was the first time I was using the app. I've also had to sign back into XDA through Tapatalk on a couple of occasions too. Any idea what might be causing this?

Thanks for all you do!
[Nexus 9 Original Android Development] flar2:
Most likely not related to the kernel. If it is related somehow, I would suspect it's not due to the kernel itself, but from changing the kernel. Meaning that changing the kernel back to stock or to one of the other custom kernels would cause the same behaviour.
[Nexus 9 Original Android Development] ilatimer1:
So what are some recommended settings for a good balance between performance and battery life i.e Max CPU, GPU, I/O scheduler, etc?
[Nexus 9 Original Android Development] flar2:
I haven't really used it enough to know yet. Experiment a bit and any feedback would be appreciated.
[Nexus 9 Original Android Development] _Infamous_:
Can you add 2.0a charging??
[Nexus 9 Original Android Development] flar2:
I'm not sure if it's a good idea. I know the device charges pretty slow, but there is a very recent commit by one of the HTC devs to limit current to 1.5A. https://github.com/flar2/ElementalX-N9/commit/081ed57219ea77d9c8c5475d05539757031988eb

I don't know what the reason is, could be safety, could be heat, could be that it will shorten the battery's lifespan. Maybe it's completely fine.

You would also need a non-stock charger to get 2A charging.
[Nexus 9 Original Android Development] _Infamous_:
Well that sucks but no big deal, thanks kernel is working great
[Nexus 9 Original Android Development] prdog1:
I thought 2.0 was a Qualcom exclusive and that is why it is not included. :cool:
[Nexus 9 Original Android Development] Jeltel:
I tried the app, but it failed to install the kernel. Looks like the path was wrong.
[Nexus 9 Original Android Development] brushrop03:
Had to sign back into my Google account after updating. No biggie just informing
[Nexus 9 Original Android Development] flar2:
A couple people reported that. I don't know what the problem is. I installed both the Express and Custom version from the app using TWRP recovery.
[Nexus 9 Original Android Development] Jeltel:
Ah, twpr recovery is needed?

I haven't installed that yet since I updated to R.
[Nexus 9 Original Android Development] flar2:
Absolutely, TWRP is necessary. Stock recovery will not work. I don't know if other recoveries will work, they need to be able to handle recovery scripts. My app works the same way as the Cyanogenmod updater.
[Nexus 9 Original Android Development] CerB:
I installed the kernel his your app, worked fine

Sendt fra min Nexus 9 med Tapatalk
[Nexus 9 Original Android Development] Sayan1987:
4 hours idle 1% drain, great!
[Nexus 9 Original Android Development] paychex:
GCM seemed wonky for me yesterday. They could have just been turning their servers off and back on again
[Nexus 9 Original Android Development] mag13:
+1
[Nexus 9 Original Android Development] daniii88:
I had the same issue when comming from the FIRE ICE kernel and forgot to format back the cache partition to ext4. (FIRE ICE uses f2fs file system). So try to format the cache partition to ext4 and wipe cache and dalvik cache. This should solve your problem
[Nexus 9 Original Android Development] CerB:
Is there a way to combine tasker and the power profile ? so i can choose when to use power profile rather than having to enable it every time ?

something like per app mode that Franco uses on the N5
[Nexus 9 Original Android Development] mag13:
My filesystem is ext4
[Nexus 9 Original Android Development] flar2:
You mean with the elementalx app? Try these intents:

flar2.elementalxkernel.powersaver.DISABLE_POWERSAVE

flar2.elementalxkernel.powersaver.ENABLE_POWERSAVE

flar2.elementalxkernel.performance.DISABLE_PERFORMANCE

flar2.elementalxkernel.performance.ENABLE_PERFORMANCE﻿

I checked and have no issue like that, please reformat your cache.
[Nexus 9 Original Android Development] mag13:
I formated the cache in ext4 and flashed the kernel with TWRP. What else can I do?
[Nexus 9 Original Android Development] flar2:
Maybe clear the data for Chrome? I don't know, I don't have this problem and it's definitely not related to this kernel.
[Nexus 9 Original Android Development] mag13:
I tried flashing ElementalX via TWRP and I tried FauxKernel via Flashify.

First I formated cache in ext4. When the N9 has started I get several errors: YouTube stopped, Calendar stopped, process com.google.process.gapps stopped and so on

So it is not possible to try these kernels. Am I doing something wrong?

My N9 is rooted and now runs fire ice kernel without any problem.
[Nexus 9 Original Android Development] flar2:
I don't know what the problem is exactly, but it seems like ART or your cache is screwed up.
[Nexus 9 Original Android Development] mag13:
Do you have an idea what I could try to use your kernel?
[Nexus 9 Original Android Development] flar2:
Your system is obviously screwed up. If thing get screwed up that badly, I usually start over. Do a full stock install and then factory reset. Let your apps install and get everything set up, completely stock. Then do a full nandroid backup. Then install ElementalX and everything will work perfectly and you can always go back to a clean starting point with your backup.
[Nexus 9 Original Android Development] CerB:
yea with elementalx app, cant figure out where in tasker to use that wou wrote
[Nexus 9 Original Android Development] flar2:
I've never used tasker, someone told me it could use intents
[Nexus 9 Original Android Development] USBhost:
Have you guys

Ever tryed using am

Or am cant start intents?
[Nexus 9 Original Android Development] CerB:
Thats alright :) i will see if i can figure it out, the N9 uses alot less battery when turning down the CPU and GPU playing games that dont need all that power.

So i guess i can get a lot out of it
[Nexus 9 Original Android Development] Hiro Nakamura:
Hey flar2,

what are your thoughts about undervolting the cpu ?
[Nexus 9 Original Android Development] flar2:
My initial tests showed that I had to disable the automatic hardware controlled voltage scaling to adjust voltages. The automatic voltaages on my device were lower than the default voltages for my cpu bin, so I think for now it is best to use the automatic voltage, which optimizes for actual power requirements.
[Nexus 9 Original Android Development] Gormsen:
How did you figure out what binning your CPU has? Did you just figure that based on what the standard voltages?

Smashed down on the mighty Nexus 9
[Nexus 9 Original Android Development] hover99:
I cant get fastcharge to work, have enabled it in the Aroma setup but the charing still takes ages.

Is there a way to verify if the 900mA charge is working right?

Thanks
[Nexus 9 Original Android Development] oRAirwolf:
As a flashlight enthusiast, I own about 50+ lithium ion batteries of various sizes and capacities. The higher the current that you charge a lithium ion at, the less capacity it has overall. It may take a long time to charge at a lower current, but you will actually get more usage out of that charge. I wouldn't enable fast charge just for that reason.
[Nexus 9 Original Android Development] flar2:
Find a battery app that shows input current.

Basically, it will definitely charge up to 900mA if your USB port can deliver the current. Some USB ports are capped at 500 (which is the USB standard).

I can't make it higher. I tried 1100 and the charger driver lowered it to 500 because it sense the power supply was unstable (probably dependent on my USB ports). As I said, the USB design specification is for USB ports to deliver 500mA.
[Nexus 9 Original Android Development] flar2:
It pulls 1.5A if you use the AC charger, USB fastcharge increases the current limit from 0.5 to 0.9 if you are using a USB port to charge. Shouldn't make any difference in the quality of the charge.
[Nexus 9 Original Android Development] USBhost:
i was able to make it 2a from a usb port lol

according to the kernel log aka /proc/kmsg

i know i should not be doing this lol

but its fun
[Nexus 9 Original Android Development] oRAirwolf:
The way lithium ion batteries are charged is with a CC/CV profile (constant current, constant voltage). This means that the battery will first be charged at a constant current (500ma, 1.5A, etc) until it reaches it's target voltage (4.35v for the m8). Once the target voltage is reached, the charger will then throttle back the current to keep the voltage constant. When you charge at a higher current, the battery reaches it's target voltage much faster and the charging circuitry has to reduce the current more drastically to maintain the target voltage. There is a limitation as to how quickly the lithium ions can enter into the intercalation layers of the anode. This means that when it's discharging, as in being used, you will get a shorter amount of usable time from the charge. Additionally, charging at a higher current can cause lithium ions to be deposited onto the anode as lithium metal, which plates the anode and decreases it's ability to absorb and discharge energy. Also, the electrolyte polymer inside the battery will start to break down more quickly. All of this leads to decreased battery life. Even though quickly charging the phone/tablet is convenient, it is also detrimental in the short term and the long term.
[Nexus 9 Original Android Development] omvir:
So to prevent this from happening too quickly would charging your tablet or phone with slower speeds be better then? Or would that too come with risks in harming the battery?
[Nexus 9 Original Android Development] oRAirwolf:
Using a lower charge current will cause less wear to your battery over time and also allow you to utilize more of it's peak capacity from charge to charge. The difference may be like 5-10%, capacity wise, but it's there. It's not that bad to use quickcharge at 1.5 A, as the general rule for lithium cobalt chemistry batteries, such as those used in phones, is to charge them somewhere between .5C and .8C, where C is the capacity of the battery in amp-hours. So if 2,600 mAh ÷ 1000 = 2.6, then a normal charging current would be 1.3 A to 2.1 A. That being said, charging at a lower current is perfectly fine and is, in fact, better for the battery. I would only use quickcharge when you actually need to charge it quickly and not all the time.
[Nexus 9 Original Android Development] hoekzemaar:
Am i correct in saying there is no color control (RGB) available yet in this kernel?
[Nexus 9 Original Android Development] flar2:
This is something I will look into eventually.
[Nexus 9 Original Android Development] fazbender:
otg access from device settings\storage broke?

Had to install the fire/ice kernel over this one as after installing the lollipoloza rom and then flashing this kernel the option to mount/see the otg drive was lost. Had it with the stock kernel in the custom rom / and now again with the fire/ice kernel.

---------- Post added at 03:01 PM ---------- Previous post was at 02:56 PM ----------

Had to install the fire/ice kernel over this one as after installing the lollipoloza rom and then flashing this kernel the option to mount/see the otg drive was lost. Had access to mount and see the status of the drive with the stock kernel in the custom rom / and now again with the fire/ice kernel. I could still access the corsair card from any of the third party apps but the device needs to see it in order to save songs from google play music to the card.... and on a semi-related note... Anybody answer the question as to why google play movies doesn't have the same option to save on teh external card?
[Nexus 9 Original Android Development] Hiro Nakamura:
Hey flar2,

do you have some plans on a more conservative cpu governor? I feel like the nexus 9 is ramping the cpu too high. My nexus 5 for comparison keeps cooler all the time (simple and heavy tasks included).
[Nexus 9 Original Android Development] omvir:
If you guys don't game much, and use the tablet for videos and browsing then try changing the hispeed freq down from 1.530ghz to 1.122ghz, boostpulse from 1,000,000 to 500,000 and under clock GPU to 468mhz. Its been giving me better battery life while keeping the smoothness. Thanks for this awesome kernel flar. Bought your app last week, it's awesome.
[Nexus 9 Original Android Development] elghouchd:
How exactly is it better if you dont mind me asking? Is the battery life better? Less heat? And also how did you change the values?
[Nexus 9 Original Android Development] omvir:
How stupid of me lol. The whole point of my post was to say that it gives me better battery life, and I left that part out -.- ...

Yes it gave me a battery boost and also slightly less heat while using the tablet for prolonged periods.
[Nexus 9 Original Android Development] USBhost:
Lol
[Nexus 9 Original Android Development] vomer:
ah, good to see [MENTION=4684315]flar2[/MENTION] doing his magic on the n9. Will give this is a go when mine arrives :good:
[Nexus 9 Original Android Development] Dr. Hurt:
Could you please add support for MHL?

I wonder why Google removed that?!!

Here's an example of an MHL implementation on a Tegra 3 device:

https://github.com/mzhou/lge-kernel-p880-iodak/tree/master/drivers/video/tegra/mhl
[Nexus 9 Original Android Development] ethanjim:
Correct me if I'm wrong but I believe that MHL requires specific hardware, which the Nexus 9 does not have.

I suspect that MHL & Slimport have not been included in the hardware spec because it's very easy and sometimes cheaper to pick up a Chromecast then an MHL adapter (I do own a MHL adapter!) and just mirror the screen wirelessly.
[Nexus 9 Original Android Development] Dr. Hurt:
I honestly have no idea how mhl works nor have I ever tried it.
[Nexus 9 Original Android Development] bruce2662:
Any higher overclocks?

Hey flar2,

I am wondering whether you can make n9 run beyond 2.5GHz

something around 3.0GHz with increased voltage would be good

also, i'm wondering whether you can make n9 gpu run beyond 1GHz, maybe something around 1.2GHz so that there is a 20% boost. The 2K screen does suck up lots of system resources.

more choices is always better, even though there's risks. people are always asking for the maximum performance possible for any devices.

These are just suggestions and hope that everything will be improved soon.

one more problem, anyway to make the gpu clock locked at the max frequency?

GOOD JOB ANYWAYS:good:
[Nexus 9 Original Android Development] kyleco:
Is there fast charging enabled to 2.1a(EDIT: 2a) like FIRE&ICE kernel? Not on USB but on AC charging. I apologize if this has been asked&answered but I'm on the XDA app and the search is horrific (or idk how to use). Any tips on that(alternate app or way to use XDA)? Ive used your kernel a ton on N7 and N5 and hoping to continue in N9

Thanks a ton!
[Nexus 9 Original Android Development] USBhost:
No its not

Also i went back to 2A only

do to 2.1A the kernal did not like it
[Nexus 9 Original Android Development] omvir:
GPU can be locked to max, only way I know how to is by using his app.
[Nexus 9 Original Android Development] bruce2662:
Hi

Thanks for your reply

But So far I can only set to 520MHz min by elementalx app, there's no 984MHz as an option.

Is there anything wrong

Anyway to make it 984MHz at all times?

Even though I use root explorer to change the value to 984000000 manually, it just goes back to 520000000 automatically.
[Nexus 9 Original Android Development] omvir:
Oh, my bad. I didn't know there was a limit to the min GPU frequency... Um... I'm not on my tablet right now but if there's a performance governor for the GPU, you can try that?
[Nexus 9 Original Android Development] bruce2662:
As I see there isn't any performance governor...

Hopefully flar2 will fix it soon

1. Remove maximum min freq limit

2. Set a performance governor

3. Raise overclock frequency

By the way whats the stock freq of GPU
[Nexus 9 Original Android Development] flar2:
There will be more updates soon, but some of the features take time and my time is very limited. Performance tuning, in particular, takes time if you want to do it right. I customize the governor specifically for every device I develop a kernel for.
[Nexus 9 Original Android Development] Asaggynoodle:
Kernel No longer works with the new LRX22C (5.0.1) AOSP. :L
[Nexus 9 Original Android Development] prdog1:
Haven't tried with stock image but could see having problems with AOSP build. :cool:
[Nexus 9 Original Android Development] Asaggynoodle:
Here is what Elementalx Kernel App provides :L

[IMG="Elementalx App"]http://i.imgur.com/a8R5w0C.png[/IMG]
[Nexus 9 Original Android Development] prdog1:
That don't mean kernel not compatible. That means his app not updated yet. Can flash manually and then will know if it is compatible.:cool:
[Nexus 9 Original Android Development] flar2:
I'm sure the new source will be posted soon, if they changed the kernel.

I have to update the app to look for Android 5.1.
[Nexus 9 Original Android Development] USBhost:
ain't this the new source ? https://android.googlesource.com/kernel/tegra/+/android-5.0.1_r0.3
[Nexus 9 Original Android Development] Asaggynoodle:
have hededE

Sorry, I already meant to say I tried flashing it alternatively lol.

Boot loop as result :(
[Nexus 9 Original Android Development] prdog1:
HaHaaa. Bootloop definitly = not compatible. :cool:
[Nexus 9 Original Android Development] Zadeis:
I have 5.0.1 installed along with the latest elemental x and its fine with me...
[Nexus 9 Original Android Development] farmerbb:
The kernel works fine for me with the LRX22C factory image. It doesn't look like there were any kernel changes for flounder in 5.0.1.
[Nexus 9 Original Android Development] Asaggynoodle:
I'll have to reflash and see what in the world went wrong.. Although the elementalx updater is indeed broken, so you must have to do it manually.
[Nexus 9 Original Android Development] Holer Togni:
I (dirty) flashed boot, system and vendor via fastboot, then directly booted into TWRP, flashed EX 0.08 and went back into the bootloader to boot the CF-autoroot image and let it boot.

(Didn't let the factory kernel boot because I wanted to keep the device unencrypted)

Not sure if I saw it right but it appeared to me that it tried to boot a couple of times (Google logo re-appeared) and eventually succeeded. Whatever happened, it runs fine now.
[Nexus 9 Original Android Development] Holer Togni:
Guess I forgot about it and went back to old habits. Anyway, tablet is still running fine with dirty flashed stock 5.0.1 and Ex 0.08. Actually I'm still on the first boot.
[Nexus 9 Original Android Development] Dr. Hurt:
flar2,

According to CPU-Z the CPU has a frequency range of 204MHz-2.50GHz, however the governor limits it between 510MHz and 2.3GHz and keeps the 2 cores active all the time.

I think this is such a waste especially with such a powerful and power hungry CPU.

Any idea why this is the case?

Can we somehow modify the governor to have a minimum frequency of 204MHz and disable the second core under low workload.

I wonder if this has to do with Dynamic Code Optimization.

Thanks for your work.
[Nexus 9 Original Android Development] ericplatham:
Not sure if this will help... but did you see this thread?

http://xdaforums.com/nexus-9/help/set-governor-settings-using-shell-t2951402
[Nexus 9 Original Android Development] flar2:
I haven't done any testing yet, but I think it will be best to leave both cores online. There is a power cost as well as latency for hotplugging. There is a better possibility of making them scale independently. I will do a lot of testing when I start working on my governor. The elementalx governor is multiphase governor that acts differently according to context, so it requires quite a bit of device specific tuning. I'm optimistic about the powersaving potential. I think I can make equal or better performance than stock interactive and have signifcant battery savings during casual usage.
[Nexus 9 Original Android Development] Dr. Hurt:
Yes, but this particular statement from the nvidia blog is what got me thinking about hotplugging.

Anyway, looking forward to seeing your updates for this kernel, especially the independant core frequency scaling.

Really appreciate your work and time.
[Nexus 9 Original Android Development] Hiro Nakamura:
Hey flar2,

i recently purchased your elementalx app and i gotta say it's a very beautiful app :) It gives a lot of things to tweak.

Now i see the min freq is already at 204Mhz which is nice. I guess it's save to lower the boostpulse_duration to something like 250ms to save battery and keep it cooler.

I was also thinking to lower the hispeed_freq to something more like 1ghz. Maybe that helps too.

But the more interesting part is how the gpu behaves. From my point of view it seems like it easily ramps the frequency to 704mhz or to max frequency just by touching the screen lol.

I guess there is a lot of potential to make the SoC more power efficient.
[Nexus 9 Original Android Development] Asaggynoodle:
Alright, I reflashed erverything... ROM, Recovery, Vendor, Kernel.

Everything is working as supposed to.

Updated the Elementalx App, version checker has been fixed and the tap 2 wake feature seems to be working very well!

Only thing if i may make a suggestion is:

1: Unlock user controlled frequencies to 3.0Ghz , so we can overclock to our own devices limits. (Same with GPU)

2: Add back User voltage control. Or a special version of the latest Kernel w/ it. I MUST BREAK 60K ON ANTUTU, MUST HAVE WORLD RECORD!!!!! (Plus, it'd show your kernel in specs ;)

3. PLEASE, PLEASE, PLEASE Add USB automount support, and 2.0A Fast Charge as default. I'm sick of my usb sticks not working on my nexus :L

Thanks as always.
[Nexus 9 Original Android Development] USBhost:
I got to 62k on it a while back
[Nexus 9 Original Android Development] Asaggynoodle:
0:

Fine, then I will break 65K. If i must sacrifice my tablet by adding insane amount of voltages and clock speeds then I shall.

I just need the means to do it!!
[Nexus 9 Original Android Development] bruce2662:
That is all I hope too!!! Though 2.5ghz is good for now. I think it's better to leave users to determine their Max frequency by them selves.

DON'T GIVE UP N9

ITS LITERALLY THE BEST ANDROID TABLET IN THE WORLD!!

KEEP IT UP! I'm looking forward to seeing a 3.0GHz running my n9!
[Nexus 9 Original Android Development] paychex:
Its not that serious.
[Nexus 9 Original Android Development] USBhost:
+1