yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] SlimSnoopOS:
Yea, just a screenshot of the fastboot window on your computer showing the error from the point that you write fastboot flash system. It would help for troubleshooting. Cuz from reading your recent posts, you flashed boot.img just fine, but system and vendor have an error. I think it is better to see what that error is. Otherwise, I would suggest you redownload the MMB29V factory image then verify the MD5 in command line.

---------- Post added at 02:36 PM ---------- Previous post was at 02:33 PM ----------

You are right. Sorry about taking up so much space flar2.

Could you post your picture in the above thread and we'll continue there?
[Nexus 5X Original Android Development] joetheshmo:
Welcome to XDA, where sometimes we get off topic because we want everyone to succeed.
[Nexus 5X Original Android Development] Komodoketavaran:
Sorry I posted here because of using elementalx kernel and the elementalx guide.

Nevermind. It just worked now.... I'm so sorry I really don't know what happen the first time. Flashed supersu and elementalx on top and it booted fine. Sorry.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] SlimSnoopOS:
No worries! You see [MENTION=7037416]joetheshmo[/MENTION] and I were trying to help haha glad you're squared away!
[Nexus 5X Original Android Development] Komodoketavaran:
Thank you two Buddies!

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] alwaysbelieve1:
I just flashed the newest version yesterday and I do not have the shed governor. How would I get that?
[Nexus 5X Original Android Development] shindiggity:
Flash EAS (experimental)
[Nexus 5X Original Android Development] flar2:
Update!!!

A quick update to improve wake gesture detection. The new kernel tick rate required some adjustments to the timing of the wake gestures.

EAS version is also available at the link below.

Download

ElementalX-N5X-1.10

Changes:

-fix wake gestures timing
[Nexus 5X Original Android Development] joetheshmo:
Big ups for all the work you've been putting in this crazy week!!
[Nexus 5X Original Android Development] bmbm:
TWRP build for MHC19J﻿ is out https://plus.google.com/u/0/+JoshuaLynch50036/posts/ZcNqBDvNmo7
[Nexus 5X Original Android Development] oo0:
[MENTION=4684315]flar2[/MENTION] can't get Idle Battery drain to less than 1% while dozing.

1.5% with 30min gesture timeout overnight.

no wakelocks, beside connectivityservice for a couple of minutes - it happens on any device, immediately when you disable data and turn screen off. hoped that it will make stats better, but no.

how do you get <1% idle drain even with data on? maybe it will settle in a couple of days and will show better numbers?
[Nexus 5X Original Android Development] Schrotty35:
I have see this yesterday. Not new and its a beta version.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] yanleites:
https://dl.twrp.me/bullhead/

Not beta...
[Nexus 5X Original Android Development] bmbm:
Since we have working TWRP for MHC19J﻿, can we flash it over "V" version?

I suppose we have to flash not only boot.img, system.img and vendor.img, but bootloader and radio also. Anyone tried it with encrypted partition already? Thanks.
[Nexus 5X Original Android Development] ale_191:
I don't understand: if I have a rom based on MHC19J, I need the normal version or eas? because I try the color temperature, but don't work...
[Nexus 5X Original Android Development] therealmarv:
Use the normal newest version. EAS is experimental from Google and Qualcomm and not intended for production use currently.
[Nexus 5X Original Android Development] flar2:
I tried the color setting and it works on both was and normal version.
[Nexus 5X Original Android Development] flar2:
With mobile connection, you probably won't get under 1%/hr

Same on my 6P.

With WiFi, you can get pretty low, around 0.2 to 0.4
[Nexus 5X Original Android Development] ale_191:
I have tested now with kernel stock, without result...

I don't know... I active the switch, push power button, unlock device but I do not see differences :eek::(

thank you for the reply :fingers-crossed:
[Nexus 5X Original Android Development] dickenam:
Yes, I just did bootloader and radio then system and vendor. Booom. I am also encrypted.
[Nexus 5X Original Android Development] yanleites:
[MENTION=4684315]flar2[/MENTION], can the kernel be as Modified Boot for Nexus 5X android N, so it will DECRYPT the phone ?
[Nexus 5X Original Android Development] SlimSnoopOS:
Cool Color temperature is working for me. Stock MHC19J with eas 1.10 version. I notice it more when the brightness is turned up. It may be more subtle for your display compared to more obvious for someone with a yellow display.
[Nexus 5X Original Android Development] Maritus1:
I think the reason is your poor network coverage. I am living in a city with very good 4G coverage, and i don't notice a big difference in doze mode with mobile network on vs. off. It's always about 2% for a whole night! Wifi causes much more battery drain on my device compared to mobile data.

What I have noticed on my other snapdragon 800 powered devices is that the 3G network causes much more battery drain than 4G, perhaps snapdragon 810 shows similar bevahiour.
[Nexus 5X Original Android Development] Komodoketavaran:
I get 0,25%/hr with mobile data. I went to bed with 35% and woke up with 35%. Thank you for your work [MENTION=4684315]flar2[/MENTION]. This thing sleeps deeper than a Lion Baby.

View attachment 3680076

View attachment 3680077

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] |DM|:
error
[Nexus 5X Original Android Development] SlimSnoopOS:
ElementalX EAS 1.10 has perfectly working gestures again [MENTION=4684315]flar2[/MENTION]. I'm using stock, rooted MHC19J. Spent Wed/Thurs sorely missing Sweep2Sleep, thanks for updating for us.

One question, did you notice any changes for WiFi in AOSP? My WiFi takes longer to connect on MHC19J, sometimes it's greyed out for ~10 seconds. Hadn't happened on previous monthly updates.
[Nexus 5X Original Android Development] luckana:
Is it necessary to use the sched governor on the eas version to achieve the benefits of EAS in general
[Nexus 5X Original Android Development] 2x4:
how do you get idle so low, what's your setup? I'm getting 1.75%/h right now
[Nexus 5X Original Android Development] luckana:
He probably has better cell coverage than you
[Nexus 5X Original Android Development] Komodoketavaran:
Yeah you right. I had the dark green color in the coverage bar over the whole time.

My setup is stock J build with elementalx 1.10 + Heimdall v4 and app "naptime" from play store setting to aggressive doze.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] 2x4:
i have bad coverage at work, its true. i use wifi all the time though.

i use the aggressive doze from greenify, is that the same thing?
[Nexus 5X Original Android Development] joetheshmo:
They're similar although the new greenify beta has aggressive doze that isn't affected by movement so it's better for pocket doze
[Nexus 5X Original Android Development] Shyciii:
I will try Naptime, but what is Heimdall v4?
[Nexus 5X Original Android Development] joetheshmo:
It's a governor profile from the interactive governor tweaks thread
[Nexus 5X Original Android Development] 2x4:
Great that's the one I have
[Nexus 5X Original Android Development] Komodoketavaran:
It's a really good profile but since some hours i have some strange ghosting at scrolling. Don't know if it has something to do with the stock J build, elementalx kernel (i don't think so because it was all fine since using this kernel) or the governor profile. I've tried to restart the phone but no difference :/

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] gmi78:
iam stock-root with 1.10, its possible enable led charging with ex manager?:confused:
[Nexus 5X Original Android Development] joetheshmo:
No that's a ROM or gravity box feature
[Nexus 5X Original Android Development] flar2:
Update!!!

A quick update to fix the camera gesture

EAS version is also available at the link below.

Download

ElementalX-N5X-1.11

Changes:

-fix camera gesture
[Nexus 5X Original Android Development] netinetinet:
No comment [MENTION=4684315]flar2[/MENTION] you are king..
[Nexus 5X Original Android Development] RusherDude:
Why?
[Nexus 5X Original Android Development] mishko:
Question to [MENTION=4684315]flar2[/MENTION] regarding EX kernel manager. Wouldn't it be a good idea for us to see which governor profile we're on? There is no clear way of telling now.

Edit: Same with color profiles.

Skickat från min Nexus 5X via Tapatalk
[Nexus 5X Original Android Development] peltus:
Edit: sorry never mind.
[Nexus 5X Original Android Development] 2x4:
What do the new msm_thermal and core_control options do?
[Nexus 5X Original Android Development] Quarktown:
exctracted from here https://github.com/gokulnatha/GT-I9...n/devicetree/bindings/arm/msm/msm_thermal.txt

MSM_THERMAL is a kernel platform driver which regulates thermal conditions

on the device during kernel boot. The goal of MSM_THERMAL is to prevent the

temperature of the system from exceeding a thermal limit at which it cannot

operate. Examples are CPU junction thermal limit, or POP memory thermal limit.

The MSM_THERMAL driver polls the TSENS sensor hardware during boot, and

reduces the maximum CPU frequency allowed in steps, to limit power/thermal

output when a threshold temperature is crossed. It restores the maximum CPU

frequency allowed in the same stepwise fashion when the threshold temperature

(with hysteresis gap) is cleared.

the goal is to optimize the hotplugging feature of the SoC,cuz not always less performance = more battery life so this try to prevent the SoC to exceed the temperature limit I guess, dunno if it is the same on N5X.

waiting for some experts who explain this :)
[Nexus 5X Original Android Development] till22:
I'm currently on stock MMB29Q with the Cataclysm mod flashed over it + ElementalX 1.08 EAS kernel with stock settings. Not using Greenify, Xposed, Doze times editor and the likes. Only controlling some misbehaving apps with Tasker and also using it to switch to 2G network whenever I'm connected to a WLAN and switching back to 3G upon disconnecting (I don't use 4G because I 1) don't need the speeds, 2) the 4G coverage isn't good where I live and 3) I don't like the extra drain I get with it).

I'm getting very good battery life (signal strength was very bad as you can see in the screenshots), but in the EXKM app the big cluster is always shown as offline, even if the CPU is at 25°C. I'm positive this is not due to thermal throttling because the CPU never had the chance to rise above 42°C (checked various times throughout the day when using the phone for more than 5 minutes). This is with light usage, mainly chatting and browsing. Haven't really noted a hit in GUI smoothness though.

View attachment 3682592View attachment 3682593View attachment 3682594View attachment 3682595View attachment 3682596View attachment 3682601View attachment 3682602View attachment 3682607View attachment 3682608
[Nexus 5X Original Android Development] RusherDude:
[MENTION=4684315]flar2[/MENTION] Im having a problem on ElemX1.11 eas on stock MMB29Q where the phone screen is waking up some times when a notification arrives, and from that point gestures s2w do not work until I turn on the screen with the power button.

Also another problem when the notification led is glowing, gestures dont work either. This is specially reproducible using lightflow and setting any event for a continuous light.

Edit: I am not able to reproduce the second problem now, it happened to me while charging, not sure if that is relevant.

Thanks for the awesome work!
[Nexus 5X Original Android Development] roofrider:
It is a feature.

U can disable Wake function timeout in EXKM if you want. But I wouldn't suggest it since it a could case more drain. The screen flashes when it times out, and thereafter the gestures wont work till you hit the power button or a notification arrives.
[Nexus 5X Original Android Development] RusherDude:
But when I installed ElemX 1.11 I set up the option for no gestures timeout. I use this kernel since loong ago and always used it without timeout, 100% of the time with the gestures working. (This is why I didnt know this was related to the timeout feature :p). But [MENTION=4684315]flar2[/MENTION] this is a bug, on the aroma installer I did set up to no timeout, and I have 30 minutes wake function timeout set up :S, this never happened before either on N5 or N5X, it's kinda rare..

Thank you! I was getting paranoid :P
[Nexus 5X Original Android Development] pletpetplet:
PureNexus rom Ex kernel 1.11 Ghost peper Profile nothing else 50% of the usege is on LTE only,other time Wifi :D
[Nexus 5X Original Android Development] elmagio:
Does the app/kernel fully work with CM root now? Back in the days some features were unavailable that way...
[Nexus 5X Original Android Development] gorilla p:
I'm noticing that even with conservative governor and touchboost disabled, with no apps open and most temporarily closed via Greenify, all 4 small cores will be around 384 and as soon as I touch the screen, they all jump to the max frequency.

Also, maybe this is just a reporting issue, but none of the cores ever appear to be offline, but will stay at 384. This isn't the only kernel I have noticed this on, but am just curious as to the reason for the different behavior from what I'm used to seeing on previous devices.
[Nexus 5X Original Android Development] SlimSnoopOS:
Did your previous phones have multi-cluster CPUs?

If you're using EKXM, enable "Deep Sleep" in the CPU Times tab to show the deep sleep times. The little cluster does not offline, it stays at 384 mhz, big cluster only goes offline when overheating or low battery.

Edit: As for the CPU ramping up to max, I have not paid attention to it. It may happen but I rather look at the overall stats and how much the clusters spend at each frequency.
[Nexus 5X Original Android Development] SlimSnoopOS:
Here are my stats. EAS v. 1.10 is running well on stock, decrypted MHC19J. This March OTA has been stellar for me. Noticeably lower consumption of memory and rather solid battery life. Oh, and sweep gestures working perfectly.

View attachment 3683241View attachment 3683242View attachment 3683243
[Nexus 5X Original Android Development] Aetos7:
Hi. Can anyone recommend a good kernel configuration for a compromise between battery and performance? Thank you
[Nexus 5X Original Android Development] nathanchance:
Stock.
[Nexus 5X Original Android Development] flar2:
Everything is different on this chipset. There is no hotplugging (except to cool down the chip). The cores jump in frequency due to touchboost, which you can turn off in the app. Voltage control is automatic and overclocking/underclocking has little effect.

Do not use the conservative governor, it's not updated for big.LITTLE chips at all, and even if it were, it's not actually very "conservative"

Use interactive, or elementalx. They are the only governors updated to work on this chip (use sched governor if you have teh EAS version).
[Nexus 5X Original Android Development] iPwn_:
Hey, what does the new "core_control" setting in EXKM do?

Does it just disable hotplugging, making the temp threshold useless?
[Nexus 5X Original Android Development] Komodoketavaran:
Omg this time I had 0,14%/h with mobile data on and a good cell coverage.

View attachment 3683522

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] jani.1984:
Hey guys

Anybody help me plz in this topic. Thx

http://xdaforums.com/nexus-5x/help/lag-keyboard-t3336215
[Nexus 5X Original Android Development] till22:
Now here's something I won't be achieving with my N5 :o

View attachment 3683756View attachment 3683757
[Nexus 5X Original Android Development] aryayush:
Just so I am not making a mistake here, ElementalX has not been updated since the release of MHC19J, has it? I was using it before the release of MHC19J but have not installed it since updating to it. I assume I’ll lose out on the stability of the camera and other performance improvements if I were to install ElementalX before its next update. Am I wrong?
[Nexus 5X Original Android Development] SlimSnoopOS:
There have been 4 updates beginning with the initial March compatibility update v. 1.08. The changelog on post #2 indicates this as well. ElementalX is fully compatible with MHC19J.
[Nexus 5X Original Android Development] joetheshmo:
It's been updated a handful of times since MHC19J so flash away!
[Nexus 5X Original Android Development] flar2:
ElementalX is updated for MHC19J, both regular and eas versions. I have not yet updated for the N preview
[Nexus 5X Original Android Development] P1an:
I love the option to change the vibration in this kernel, but would it be possible to only change the vibration for the buttons and not the buttons + notifications like it is now?

So lower the vibration for buttons and have standard vibration for the notifications.

Thank you for the great work with this kernel flar2! :D
[Nexus 5X Original Android Development] iPwn_:
EAS with input boost (1000 ms, full speed for little cores) is plenty smooth, but I suppose I'm limiting any power savings to when I'm not actively interacting with the device.

EDIT: Nvm, it's still pretty janky.
[Nexus 5X Original Android Development] joetheshmo:
Touch boost or input boost?
[Nexus 5X Original Android Development] |DM|:
Mmm I don't know why for this moment but with MHC19J and ElementalX 1.11 I had some reboots (two from yesterday to now). I don't know why, I installed Skype (that it's the only difference, now I tried to remove it).

With 1.06 and 1.08 I never had auto reboots, howerver I have the MHC19J only from saturday but with 1.10 seems ok. Now I will check without Skype app, then it the problem still I will try to reflash kernel and wipe cache and art cache. Could be it related with the gestures?
[Nexus 5X Original Android Development] jonup:
I can confirm random reboots. I believe I had them on both 1.10 and 1.11 but definitely on 1.11. Switching the kernel fixes it. It generally happens when there is no load i.e. with the screen off. I use the kernel on a permissive ROM with the permissive.zip that's available in this thread if that makes any difference.
[Nexus 5X Original Android Development] luckana:
Try using stock governor settings if you are using a custom profile
[Nexus 5X Original Android Development] flar2:
Don't ever post about reboots without posting logs and details.

It's really not helpful.

Also, before you post about reboots, you need to do a clean install, including data wipe, to rule out other things. No mods.

This is a stock replacement kernel, meaning it is like stock in important ways and should be as stable as stock.

My wife uses this phone and kernel as her daily driver, she uses it heavily, and has never had a reboot.
[Nexus 5X Original Android Development] jonup:
When I get a chance I'll post some logs, but for now it's up to you to ignore my feedback. Fact of the matter is your latest kernel causes reboots on my end and other kernels flashed on top of the same setup don't. And your chance of making me clean flash is as good as making [MENTION=1811927]simms22[/MENTION] clean flash.
[Nexus 5X Original Android Development] dickenam:
"Hey, don't worry about my bad behavior...it's for you to ignore." Really bro...?

[MENTION=5029685]jonup[/MENTION] Fact of the matter is, no one is 'making' you wipe anything.... All he's saying is that if you're not going to do your due diligence then keep your super useless 'feedback' to yourself..........

Lastly, over the course of basically every kernel version [MENTION=4684315]flar2[/MENTION] has ever posted for this device..... I have, not once, had a random reboot.
[Nexus 5X Original Android Development] oo0:
Guys, I just don't get the magic behind the Idle drain you report!

Debloated CM13 - device sleeps well, having like 5 micro wakelocks per hour and CPU idles to lowest freq 99% of time. But i just can't get below 1.34% idle overnight with EAS and sched. Even though having low Active drain which i'm very satisfied with. Have second revision CPU (faster, but probably drains more? doubtful, but i can't find anything else to blame). Signal is fine, wifi, gps, brightness stuff, vibration, daydream disabled, temperature around is not cold enough to affect battery(now i count even this neglible stuff, lol). Maybe i should recalibrate? Any ideas on what can drain power in deepsleep are appreciated.

For night experiment data was off

Ambient On

Swipe Up only with 15min timeout

All else default, Fsync Off, KSM off, GPU sched msm-adreno-tz

Greenify + Agressive doze and additional permission - disable whatsapp updates

Have logging disabled in build prop

debugtool.anrhistory=0
profiler.debugmonitor=false
profiler.launch=false
profiler.hung.dumpdobugreport=false
logcat.live=0
ro.config.nocheckin=1
dalvik.vm.checkjni=false
ro.config.htc.nocheckin=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0

wifi.supplicant_scan_interval=8000
pm.sleep_mode=1
[Nexus 5X Original Android Development] |DM|:
My system is clean. As I wrote, I did a full factory reflash saturday and I'm on factory image. I flashed only the TWRP and the kernel so I don't think that the problem is my phone. Also, I don't have the root so I don't know if I can get the log, in any case how i can get the log and how much time I have? Because for now it always appen in office or outside home...
[Nexus 5X Original Android Development] flar2:
The only changes in 1.10 and 1.11 are timeouts for the wake gestures. Are you using wake gestures?

Also, J had some very significant changes. You might need a clean install. And are flashing ex over a fresh boot.img?
[Nexus 5X Original Android Development] SlimSnoopOS:
Hey, how did you get a "screen off" profile in BBS? I don't see that on BBS 2.2 beta 5.

I think my screen off drain is lower cuz I don't use Swipe2Wake. More than likely it is due to toggling off GPS, WiFi, and/or mobile data at night. Comcast WiFi drains my battery relentlessly overnight so I must turn it off.
[Nexus 5X Original Android Development] jonup:
I flashed elementalx over a the ROM's kernel, which is probably phasma. I've had similar reboots when the dev built the ROM with elemental about a month ago. So I'm starting to think it might be combination of the ROM and your kernel. I'm having the other people who have access to that ROM test elementalx. Unfortunately I'm the only one running BH on that ROM. They'll test on Angler. I'll report back with results. I just need a stable phone during the week and cannot get any logs for you right now. I can probably do that over the weekend.

Edit: I am not 100% sure if this is the error last_kmsg because I have a few and some of them are just me rebooting. But anyway:

https://drive.google.com/file/d/0B9Jx5VcIWwpTb0FVMHZ0U3VZRFU/view?usp=docslist_api
[Nexus 5X Original Android Development] oo0:
it will appear, when watchdog is enabled.
[Nexus 5X Original Android Development] respider:
I had a random reboot today too, my phone was idling (screen off).

After reboot it was stuck on boot animation screen, wouldnt turn on. I had to force shut down and start it again.

I'm using 1.09. I factory reste my phone and wiped data (flashed userdata.img) 2 weeks ago.And I didnt restore from a previous backup, I was trying to solve the lags I was having

edit: just to clarify, this is not common at all. It was my first reboot, my phone uptime as 130+ hours

Unfortunately I didnt get a log. If this happens again, how can I get it?
[Nexus 5X Original Android Development] 2x4:
im on 1.11 EAS, no reboots here
[Nexus 5X Original Android Development] lutz890:
Question: how can I verify which version (normal or eas) I have on my phone? I knew for sure I installed EAS, and thought I would see it listed somewhere in EX manager. So far haven't been able to find any indication in the manager app...

BTW, will EX manager be able to update the kernel accordingly? from eas to eas?