yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] GjorgiDxc:
Does anyone else notice a delay on dt2w when using "Pocket Mode"? I tap and after a 2-3 sec the screen comes on, but sometimes the delay is longer like 10 sec or so. I'm on stock rooted only.
[Nexus 5 Original Android Development] magnamentis:
usually it's best practice to follow advice, if it tells you to format it, why don't you just format it then before stirring things up?

and don't tell me you don't want to loos data on it, should be no problem to store them elsewhere in the mean time

EDIT: forgot to mention that i use this kernel on 2 devices for years and never had issues to mount via stickmount while without it may be subject to rom feature.

and i copy about 4 nandroid backups per week and for 7 devices to my stick, mean many GBs
[Nexus 5 Original Android Development] wkwkwk:
Hi,

Are there any rough instructions on how to compile this kernel from source? I want to add the usb keyboard patch (https://github.com/pelya/android-keyboard-gadget).

Just wondering if these instructions are valid for all kernels or not - http://www.xda-developers.com/compile-kernel-tutorial/

Thank you.
[Nexus 5 Original Android Development] onesolo:
I know that and my flash drive is empty, but I guess if android is telling me to format the drive to be recognized, he is going to format it as an FAT32 device and not as a NTFS... that's why I didn't format it...
[Nexus 5 Original Android Development] magnamentis:
it's boring to have to pull everything out of peoples nose. now you explained why you don't want to format which btw you could have done in the first place but still you did not explain what your problem with FAT32 would be or in other words why you NTFS. first priority would be that the drive stores data. but anyway it doesn't matter since it's your choice but still it would be nice if people would provide relevant info in one post instead of making people ponder and fill threads with multiple posts instead. just sayin'

and to point it out, i have mine formated, didn't even care which format and it worked well, including on my computer (it's a hybrid with 2 usb ports)
[Nexus 5 Original Android Development] ajeesh vijayan:
pedometer doubt

nexus 5 has low power core and its used for step detection.

stock kernel is using low power core..(I don't know if that's related to kernel)

my doubt is, does ex uses the same low power core? or kernel have any effect on that?
[Nexus 5 Original Android Development] flar2:
Kernel has no effect
[Nexus 5 Original Android Development] bseos:
does the latest version have CIFS support?
[Nexus 5 Original Android Development] onesolo:
just to fill out your senseless approach, I format the drive, and as obviously after the format the drive was formatted as a FAT32 drive... clap clap... are u satisfied now?!

If the kernel or stickmount worked alright, system would not asked me to format (again) it in the first way... because the drive was already formatted as a NTFS drive... this is a no brainer
[Nexus 5 Original Android Development] flar2:
The NTFS driver is built into the kernel. It works.
[Nexus 5 Original Android Development] grep_i:
Maybe a stupid question ?

Have you also downloaded Ntfs-3g driver and put it in the root of your device's internal /sdcard
[Nexus 5 Original Android Development] magnamentis:
it does not have a low power core as far as i know which is one of the reasons that dt2w cannot have low power consumption and pedometers are usually connected via low power bluetooth standards that were implemented with kitkat at the time. at least this is what i remember, while a more tech savvy user perhaps can either confirm or correct that laymen's find ;)
[Nexus 5 Original Android Development] TJKV:
As far as I know you are right in that the N5 doesn't have (or doesn't use?) a low power sensor core/cluster in the SD800. The DT2W issue however is unrelated, that issue is because of how the display/touchscreen power connections are wired up. ie they are powered together, not separately.
[Nexus 5 Original Android Development] magnamentis:
true while i thought it's both. it's a long time since we all were dealing with the details, hence i might mix something up, but thought that what you said is one side while it would take a low power core to get those 1% in 10 hours except the 2% in 1 hour but as i said, i may be wrong, just throwing this is as a thought. thanks for the clarification however, very much appreciated
[Nexus 5 Original Android Development] ajeesh vijayan:
nexus 5 does have low power core and its used for step counting even screen off without impact on battery

other SD800 uses it for always on listening even screen off (moto x 2014)

I have seen a video , proof of concept from omni rom developer xplod wild that always listening while screen off can be enabled using low power core..but didn't published due to SD licensing issues

https://plus.google.com/app/basic/stream/z13eu5ar5omkvlzmz22ge5rxonrqe5g5b04

https://m.youtube.com/watch?v=F1ANpeexBTQ

so all snapdragon 800 has dedicated low power core

sorry for my English
[Nexus 5 Original Android Development] Arstoien:
Exactly. The difference from a normal "low power" core is that it's got a single purpose – you can't assign tasks to it like a normal core. That's the reason why it's not being discussed much and it's mostly less known. And yeah, pedometer isn't as useful as some other uses but I'll take it over always on listening. For example "on body detection" doesn't really use any extra battery, although it's using the accelerometer. I'm pretty sure Doze's significant motion is also taking advantage of the low power core, so it's barely using energy. You can see from BBS for example that 100% of the time the phone is in Doze, it's got "sensors" running, but at the same time the battery is used very, very slowly.
[Nexus 5 Original Android Development] kojak1989:
when i flash this kernel i think i have a little bit volume down, this is normal ?
[Nexus 5 Original Android Development] kojak1989:
So what went wrong?
[Nexus 5 Original Android Development] flar2:
How could I possibly know?
[Nexus 5 Original Android Development] simplicio11:
[MENTION=4684315]flar2[/MENTION] no further update?

Thanks
[Nexus 5 Original Android Development] flar2:
I'll update when necessary
[Nexus 5 Original Android Development] aavvaallooss:
I fully agree with you!

My solution is to increase the speaker volume gain to + 6
[Nexus 5 Original Android Development] autry7:
I'm having an issue with getting changes to minimum frequency to stick. I'm using the ex app. With MP decision on the frequency will sit at the new minimum for a second and then just dropped to 300 and with it off or using the custom hotplugging only the first core will be at the set minimum. Is this behavior normal?

Edited to add: changing the hotplugging to custom and then changing it back to mpdecision made it stick but the when I change the minimum back to 300 it'll stay at the 1036 until I toggle through the hotplugging options again
[Nexus 5 Original Android Development] magnamentis:
thanks for the perfect clarification which leaves no more doubts :good:
[Nexus 5 Original Android Development] flar2:
I put warnings on those settings for a reason, and have repeatedly recommended not to change them. You can't change them if mpdecision is active because it will always change them back.
[Nexus 5 Original Android Development] ajeesh vijayan:
you're welcome sir
[Nexus 5 Original Android Development] Subrad5446@aol.com:
Hi. Im still on 4.4.4 and am having random reboots. Looked.at my last_ksmg and it seems last reboot is by key. Can someone please make sure.I'm reading this right? And if I am does that mean RMA? It reboots by itself every few hours just sitting on the table with no case. If not can u help me find out what's causing it? Thanks you!

.
[Nexus 5 Original Android Development] Mrcactuseater:
4.4.4 was deprecated a long time ago, update your damn phone.
[Nexus 5 Original Android Development] Subrad5446@aol.com:
I'm comfortable with kit kat. Didn't care for lollipop or marshmallow. Plus since I feel its a hardware issue don't really matter what I'm on. Just looking for confirmation because I don't know how to read these.
[Nexus 5 Original Android Development] looney_tkp™:
hey man..i really love kitkat too

but its kernel isn't that good for me so i had to update

marshmallow is awesome but i still love kitkat [emoji4]
[Nexus 5 Original Android Development] simplicio11:
No reason to use Kitkat in 2016!
[Nexus 5 Original Android Development] Arstoien:
Except that I can't replicate the good battery of the older Android versions, even with new battery and stuff like more aggressive Doze settings, Inactive Apps, Greenify, etc. Though, everything else into account – no reason to stay in the past
[Nexus 5 Original Android Development] Subrad5446@aol.com:
Yep. All my apps and themes work. If I have to RMA this phone I would get a diff phone. This would be the third one I sent in. That's any I wanna make Surr it's a hardware Issue.
[Nexus 5 Original Android Development] Flyview:
I just installed 6.12 and noticed my "stereo mod" by chdloc wasn't quite working. The ear speaker is still on but very low volume. He just confirmed faux sound is the problem. Is there a way to turn faux sound off? Alternatively is there a way to control the ear speaker from your ElementalX Kernel Manager app?
[Nexus 5 Original Android Development] flar2:
If you don't change any volume controls, fauxsound is off. I'm not sure why he thinks fauxsound interferes with it.

Im not sure about controlling the ear piece volume, I haven't looked for whatever controls it.

If you have the fauxsound app, remove it. I don't know what it does.
[Nexus 5 Original Android Development] Flyview:
No I don't have the faux app. He says faux sound could control the second speaker if it was modified. Check out our discussion here:

http://xdaforums.com/google-nexus-5/development/mod-camcorder-audio-quality-fix-t2837930/page106
[Nexus 5 Original Android Development] Droid_Evo_8:
So, what's a good profile to use for my Nexus 6p with the new update?
[Nexus 5 Original Android Development] flar2:
I'll have to look at the code again. I thought that all gains would be at default levels if nothing is touched.

He can feel free to make a pull request or contact me about adjusting the earpiece speaker.
[Nexus 5 Original Android Development] Flyview:
The values are at default, the problem is they get changed back to default by faux even when installing the stereo mod after the kernel.
[Nexus 5 Original Android Development] chdloc:
I have no direct proof as I'm not running your kernel myself, but from the evidence shown by [MENTION=2584205]Flyview[/MENTION] it appears that fauxsound (triggered by whatever process) seems to be applying the gain defaults from linux/mfd/wcd9xxx/wcd9320_registers.h. Normally the audio HAL reads mixer_paths.xml (where [MENTION=2584205]Flyview[/MENTION] entered some custom gain values) only once, i.e. upon system boot. Unfortunately, the gain values in the mixer file are not cached and changes made with, i.e. tinymix, are temporary only. It is my understanding that fauxsound enables caching and is, hence, able to overwrite the values in the mixer file.

Not having looked at the code in sufficient detail, the only explanation I can come up with is that fauxsound overrules (or blocks via the snd_ctrl_locked variable?) the mixer values that the audio HAL is trying to apply.
[Nexus 5 Original Android Development] Flyview:
I just wanted to add [MENTION=4684315]flar2[/MENTION] [MENTION=2760454]chdloc[/MENTION] that after installing ElementalX 6.11 (before faux sound was reintroduced), the problem immediately resolved itself without even having to re-flash the stereo mod.
[Nexus 5 Original Android Development] flar2:
Now this is making some sense.

In 6.11 I modified franco sound to skip the registers completely if all the gain controls were at 0. Fauxsound does cache the registers and I changed it to automatically lock the registers, and they are locked by default. I think the solution might be to unlock them if all gain controls are at defaults.
[Nexus 5 Original Android Development] Gordietm:
On the latest update, it's mentioned that a future sound option for the N5 was added. I don't see where that is or what it should be doing?
[Nexus 5 Original Android Development] flar2:
You can't see anything yet because it's in the future
[Nexus 5 Original Android Development] flar2:
I still use this phone a lot for app development (I still think this and my HTC m8 are my fastest phones) and every once in a while I get a crazy idea to start from scratch and redo the kernel, thinking I can make it better. I was even starting to believe some of the people on here who say battery life isn't so great on this kernel. So I made this phone my primary phone over the weekend and tried out some other kernels. My conclusion: no need to change a thing.

With that said, I am still making improvements. Expect a new release tonight.
[Nexus 5 Original Android Development] YassGo:
I confirm dude. I've tried many kernels and I always reflash EX :). Still the best IMO.
[Nexus 5 Original Android Development] flar2:
Update!!!

Fauxsound is now disabled by default. If you want to use it, enable it through EX Kernel Manager on the sound options screen. This will prevent any interference with other audio modifications and guarantees that anything audio related is exactly the same as stock for those who don't want to mess with anything.

I have removed the enforcing option from the installer. Selinux is enforcing by default, just as it was before. Removing this option will allow you to use setenforce again to change selinux mode on the fly. I found it inconvenient not to be able to do this. Generally, there is no reason to run in permissive mode, but if you must, then use the permissive.zip found here: https://www.androidfilehost.com/?fid=23991606952602503

The useless insecure kernel option has been removed as well.

I also made some slight adjustments to the elementalx governor to further reduce audio glitches with Viper4Android.

Download

ElementalX-N5-6.13

Changes:

-disable fauxsound by default (enable it with EX Kernel Manager)

-slight tweaks to ElementalX governor

-remove enforcing option (enforcing is still default)

-option to disable sensor_ind wakelock
[Nexus 5 Original Android Development] xmaciek82x:
Oh wow flar2, THANK YOU!!! Now that audio mods are disabled I can finally run this kernel! I was the guy that had the static noise when running your kernel along with V4A + ATOMS mods. Backing up now, dirty flashing my rom, and then going to flash your kernel! Super excited right now. I always liked your kernel but never could run it long term since I listen to music at work all the time and prefer quality of my tunes over kernel performance/battery.

I'll report back after kernel and V4A + ATOMS mods are flashed.
[Nexus 5 Original Android Development] YassGo:
Sorry to ask, but what's this sensor_ind wakelock. I've googled it and didn't find a good answer.
[Nexus 5 Original Android Development] jindal.shreyansh:
The Sensor_ind wakelock let the Android-OS keep your Nexus 6 awake, it generally kicks in after an incoming Hangouts message was sent to you and it had't been read on your device.
[Nexus 5 Original Android Development] looney_tkp™:
sorry for this question guys, i don't have enough information of it

, TCP-Congession Algorithm

which setting is good ?
[Nexus 5 Original Android Development] dpaine88:
I am being dense? I upgraded kernel and app but don't see an option to enable the sound settings..
[Nexus 5 Original Android Development] fantamadnesss:
Me too, i am using ex kernel manager and when i change sound settings nothing changes.
[Nexus 5 Original Android Development] flar2:
Do you have version 2.57 or 2.58?

Works for me.
[Nexus 5 Original Android Development] zerosum0:
I wish to God you would leave faux sound in the bin. Its in n out like…… ..

..Be nice to get kernel backup on the app again as its one of the reasons I love it. This kernel used to be very few updates because it worked .Worked perfectly then idk. Somthing changed. Faux is one example in n out.. X2 ?x3 ? . set and forget was, the mantra. If you wanna fiddle try another used to be said.... That last build had issues for me but in the past I've been told its something I'm doing, but by its blessedly short lifecu don't think so. If this one is good and goes into deepsleep properly I'll stick with it and that's it. I split coffee on the phone and spent hours repairing the hardware from sources but with a new nexus 6 64 gig for £220pounds time for a, move. I'll take EX of course. That and a stock rom is ideal… when left alone; ]
[Nexus 5 Original Android Development] flar2:
Every version of the kernel works perfectly fine in terms of deep sleep and all that. Any problems with performance or battery are due to something else. That's the one thing I don't mess with.

As regards sound control, it is an essential feature used by many, many people. So I have to keep it.
[Nexus 5 Original Android Development] dpaine88:
I have 2.57 which is up to date according to my Google play.

Where is the option supposed to be to enable sound settings? Right with the sound settings? I only have the sliders like before but the changes seemed to indicate we will have to turn sound settings on.
[Nexus 5 Original Android Development] lmulli:
£220 for a brand new 64gb Nexus 6? Where from? Ta.
[Nexus 5 Original Android Development] fantamadnesss:
Just updated to ver 2.58 and wiped cache too, now all is working good!
[Nexus 5 Original Android Development] s0ur0v:
[MENTION=4684315]flar2[/MENTION] Permissive is missing in aroma installer. I can't even change enforcing to permissive by flashing your permissive.zip
[Nexus 5 Original Android Development] flar2:
It's on the sound settings screen, not sure why it wouldn't show up.
[Nexus 5 Original Android Development] mixtapes08:
Permissive.zip not working for me also.

Sent from my Nexus 5
[Nexus 5 Original Android Development] flar2:
I'm really trying to discourage people from running in permissive mode, there is no reason for it. So I'm not particularly interested in making things easy, although running in permissive mode is as simple as typing "setenforce 0"

Maybe the permissive.zip needs to be updated for systemless root, I think the directory it needs is /su/su.d/ instead of /system/su.d (which is where the permissive.zip installation currently points)

This is so dead simple, I will leave it to someone else to change that line in the permissive.zip and post it.
[Nexus 5 Original Android Development] mixtapes08:
Ive tried changing the zip but I'm not sure if changing the folder directory and changing the system lines on the updater script is correct so I'm not risking it yet.

I've tried typing this commands in terminal and soft reboot my phone but still shows enforcing on the settings..

su

setenforce 0

Anyway I'm using a root app that still needs a permissive selinux mode to run properly. I might go back to an older version for now. Thanks anyways.

Sent from my Nexus 5
[Nexus 5 Original Android Development] flar2:
If you reboot or soft reboot, it will go back to enforcing.

You can just make a text file containing "setenforce 0" in the /su/su.d directory and it should work. I think you will need to give the file execute permissions (can be done with a file manager or with chmod 777 command)
[Nexus 5 Original Android Development] mixtapes08:
The problem is I can't find those directories on the rom I'm using.

Sent from my Nexus 5
[Nexus 5 Original Android Development] dpaine88:
Problem fixed. Turns out it wasn't flashing new version of kernel after all until I deleted the kernel download folder. Got new kernel flashed n all looks good.
[Nexus 5 Original Android Development] thereal_bigjake:
[MENTION=4684315]flar2[/MENTION] after flashing the new update wireless adb no longer works. I was running permissive before the update so I thought maybe wireless adb does not work on enforcing.

Well I tried switching to permissive in a terminal, su.d and the switch in the rom and all failed to do anything.

Does wireless adb work with SELinux enforcing? Or did something else in the update break wireless adb?

I'm using the latest DU stable
[Nexus 5 Original Android Development] flar2:
I have no idea. That shouldn't be related to the kernel at all, but may be related to selinux.

Try it after making selinux permissive with setenforce 0
[Nexus 5 Original Android Development] flar2:
You would have to create the directory. If you are using systemless root, create a directory called su.d under /su. Otherwise, it would be /system/su.d
[Nexus 5 Original Android Development] thereal_bigjake:
That's the thing, setenforce does not work after the update also. It was the first thing I tried to see if selinux affected wireless adb
[Nexus 5 Original Android Development] flar2:
Oh, crap. Nevermind, I forgot to revert the selinux changes I made, so that's why it's not working. Another update tonight.
[Nexus 5 Original Android Development] magnamentis:
just to tell as a general input, both latest build for the first time in years broke something on my N5 as well as N6, on N5 file system is messed up and when i restore backed up kernel from within EX app and/or flash stock kernel and/or flash earlier version all is ok.

on N6 media force close, tried 6 hours to make things run, including stock kernel + root + EX, always had to go back to either nandroid and/or earlier EX kernel and all is well. i would tend to say (as a reader) how can this be kernel related but there is something going on. right now all running as usual on previous versions 6.04 & 3.11 respectively and both issues have to do with permissions/file system. sometimes certain folders like i.e nandroid backup folders show as files and can't be opened. again all works again when flashing ANY other kernel or EX kernel variant, be it from backup through the app and/or flashing the zip from recovery.

if it persists i'll take logs sooner or later when i find time but for now i spent too many hours on this today and have to go into a meeting.

just wanted to drop the info quickly so that as i get a feel that others have different but file system related issues as well there could be more to it.

further i find it cannot be a coincidence that after years of zero glitches within such short time (days) both devices misbehave file system related.

and you know me long flar2 i rarely have anything that i can't or won't resolve alone or by reading, just for what it's worth
[Nexus 5 Original Android Development] flar2:
Unless you were running in permissive mode before, I find that strange, as the changes are very minor on the last updates. Nothing with the filesystem should be affected and the updates went smoothly on my phones.
[Nexus 5 Original Android Development] pdclose:
March security update

Build MMB29V was just released (March 1 2016 Security patch level), any idea if it will require an update to ElementalX to match?

Thanks!
[Nexus 5 Original Android Development] grep_i:
[MENTION=4684315]flar2[/MENTION]

Thanks for this update it installs and runs smoothly, no problems whatsoever.

:thumbup:
[Nexus 5 Original Android Development] flar2:
Yes, it needs to be updated
[Nexus 5 Original Android Development] looney_tkp™:
heyy big man flar2...what does the temperature setting do please ?
[Nexus 5 Original Android Development] flar2:
In the app?

Click on it and you will see all the temperature sensors on your device. If you tap one of them, the Dashboard and the CPU temp notification will use that sensor
[Nexus 5 Original Android Development] looney_tkp™:
yes in the app please,sorry for not adding it...

that was the explanation i needed..thank you [emoji106]
[Nexus 5 Original Android Development] J3:16:
When in enforcing mode, some apps keep force closing or doesn't start at all, not even the UI. I understand everyone has his own preference/philosophy, but why in the world making things harder/longer and imposing a point of view? Just leave that option and let people decide...