yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] gpvecchi:
I haven't understand one thing: if I use the app, do I have to install the express version or the aroma one?

Just because if I set a max screen off setting and I set at boot, at the next boot the clock is the one in the conf file.
[Nexus 5 Original Android Development] mo976:
The whole comparison of battery life is a bit pointless due to the myriad of factors involved. For example after 12 hours I was at 20% battery with three hours of screen time about an hour of that was with mobile data and while browsing/checking social media/ email and streaming music via tune in radio. Using the standard cpu setting and auto brightness. From my experience and this is hardly scientific I get about 20 minutes SOT per 10% of battery using the GPS and streaming music while running, 25 minutes SOT browsing etc with mobile data and no GPS, and 30 minutes+ SOT while using WiFi. That means anywhere from about 3 hours to 5+ hours on a full charge depending on usage conditions.
[Nexus 5 Original Android Development] danarama:
Yep its pointless and clutters the threads making useful info easier to miss
[Nexus 5 Original Android Development] flar2:
Use the little disk icon (formerly a down arrow) to save the setting. If you install the express version, it will preserve the setting.
[Nexus 5 Original Android Development] xzilem:
The reason of creating custom kernel are for features, battery life and performance. So it's not pointless at all to discuss about battery life because people choose custom kernel by comparing battery life.

I agree this will clutters the thread if they just give their sot without telling what they do to get that sot.
[Nexus 5 Original Android Development] topgeardave:
Battery life is extremely subjective. That's the issue here. Depending on your usage you can eke out anywhere between 3-6 hours SOT. Only time I reckon battery should be discussed is a new kernel release if there's anything that might go wrong.
[Nexus 5 Original Android Development] a0b1c2:
Slightly off topic: CM11 - change vibration /duration/?

Hi,

I posted on the CM forum but I've yet to receive any responses, searched google, searched the CM forum, etc... so I thought I'd ask here ... if it's too off-topic, let me know and I'll delete the message.

Now that we've solved the vibration intensity on CM, is there a file to affect which will change the duration of the system vibration duration?

Thx!

-pablo
[Nexus 5 Original Android Development] xzilem:
Yep, i agree with you. Battery life should be disccused and not just showing sot screenshot. So it's not pointless at all right?
[Nexus 5 Original Android Development] Galaxo60:
Maybe is something pointless for you because you don't have a problem with this, but people like me that is having problems or is trying to maximize the battery, the advices and opinions from people are really useful and can give me an idea of how I can improve or resolve my issue.

:angel:

Totally agree.

:D

Although it seems subjective, I think is the other way around. It would be subjective if we have different devices with different batteries, but if we have same device with same battery, it should be in general the same performance and battery life. I mean, if 90% people is getting around 3-4 hours SOT over a day of normal use, and I just can get half of that, then something is wrong, and I will try to solve the issue.

I know that gaming, not having full signal or perform any other heavy stuff on the phone will drain a lot more of battery, but as far as I know for the people who answered to my questions, we don't have in general that behavior.

So from my point of view, it could be subjective, but within a range, and I'm trying to find how to get there.

:)
[Nexus 5 Original Android Development] drawde40599:
a thread like better battery stats would be a better place to diag battery issues http://xdaforums.com/showthread.php?t=1179809
[Nexus 5 Original Android Development] winamp26:
doesn't have uninstaller like UBER kernel?
[Nexus 5 Original Android Development] xzilem:
Stock = 3 Hours SOT.

Kernel A = No info about battery life

Kernel B = 3,000 Hours Screen On Time Screenshot

Kernel C = 5 Hours Screen On Time with detailed guide to achieve.

Which one would you choose? Don't tell me you need to go to BBS Thread to choose your kernel because Dev also need user info to make a better kernel (performance, feature, bettery life).

I don't think kernel dev will go to that thread to get user info.

We should not stop bettery life discussion but we need to stop posting SOT Screenshot without any good info.

Pst: My sot only 2-3 Hours because i use it as Wi-Fi Hotspot. I will stop now :o
[Nexus 5 Original Android Development] drawde40599:
No , dirty flash or restore backup is recommend .

---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------

I don't have a clue what your talking about . if someone is having battery ISSUES BBS is good place to go for very detailed info .
[Nexus 5 Original Android Development] xzilem:
Sorry, it's from the earlier discussion :o
[Nexus 5 Original Android Development] danarama:
Alright let me elaborate...

Its people who come here and arbitrarily post "omgz, I get 6 hours SoT. This kernel is the best!" That's annoying me. As are all the screenshots. Its useless.

1) who cares?

2) its pointless. No one can compare.

Asking for advice is fine. However do bear I'm mind there is a dedicated battery sticky thread too.

But here is the thing. People shouldn't compare kernels by battery life. They should compare them by features. Battery life is almost entirely down to how you use and configure your phone. Signal, usage, whats running, whats not , what network you're on... There are far too many variables here... You could easily get almost identical battery results on pretty much any custom kernel. Its all about how you configure your governors. People think that because different devs have different out-of-the-box configurations, that kernel x is better than kernel y, but this is mostly a fabrication.

...so yes, ask questions about how people set their governors, by all means.

But let's not post screenshots showing off, or useless posts bragging how much SoT you have. Its ridiculous and we don't have a baseline to compare anything against. We don't know (or care) what you got on another kernel and its useless to know what you get here. Even Flar advised he gets 3 hours. So asking for governor help is fine, but expecting to match someone else's SoT is an unrealistic goal and attempting to is a superfluous direction for this thread to take.

I hope my stance is clear.
[Nexus 5 Original Android Development] lzzar:
[MENTION=4684315]flar2[/MENTION] just a suggestion. proximity sensor integration to DT2W an S2W so that it does not activate in your pocket. That would be great as it activates in my pocket all the time
[Nexus 5 Original Android Development] xmlnoob:
iirc, flar or some other gurus here had stated n5's sensors wont work in deep sleep and kernels cant control the sensors so not very viable atm....

從我的 Nexus 5 發送
[Nexus 5 Original Android Development] Elluel:
You can do that with Tasker afaik

ふかつどう
[Nexus 5 Original Android Development] SynnyG:
Hi all, I'm back to the nexus 5 after a period of iphone use (don't blame me, once jailbroken they are good phone ^^), when I select backlight dimmer in the installer, when the brightness is at the minimum, the left bottom corner is really darker than the rest of the screen, I mean like if the phone has fallen and the screen is "broken". It's an effect of this feature, to turn the screen darker, or is my screen has issue ? Thanks in advance ;)
[Nexus 5 Original Android Development] and313:
Yes that is probably a hardware issue
[Nexus 5 Original Android Development] flar2:
A few people have this issue, it's hardware.

There is a min brightness setting (can't remember the path right now, maybe someone could help me out). The default is 5, try changing it to 6 or 7.

I've added this setting to the next version of my app
[Nexus 5 Original Android Development] Zhypr:
Could you add support for audio over USB? I love this kernel, but sadly my DAC doesn't work with it.
[Nexus 5 Original Android Development] vin4yak:
You mean this?? http://review.cyanogenmod.org/#/c/54343/
[Nexus 5 Original Android Development] GialanG:
Some people including me also suggested this, but [MENTION=4684315]flar2[/MENTION] said it's impossible because proximity sensor in N5 is controlled by roms (userspace) rather than kernels. I'm running Mahdi, which has the accidental wake up prevention feature, and it perfectly matches your need. Give it a try.
[Nexus 5 Original Android Development] flar2:
I'll double check that its enabled in the kernel, but this does require ROM support as well.

Indeed, not impossible, just has to be implemented in userspace rather than kernel.
[Nexus 5 Original Android Development] GialanG:
Yes, I mean impossible to kernels :)

Sent from my NEXU5
[Nexus 5 Original Android Development] der_sascha:
hi, is doubletap2wake/sweep2wake disable or enable by deffault? and what app should i use for do some settings on this kernel?
[Nexus 5 Original Android Development] Zhypr:
Ah, I see. I was not aware it needs ROM support. I'm using PA with your kernel. I'll just wait for Android L then I guess, which has better support by default.
[Nexus 5 Original Android Development] NovaSlim:
It is disabled by default if you flash the express version, but new users should be flashing the standard(aroma) version(1.05 or 1.05 cm) which allows you to choose all your settings(including dt2w/s2w) during flashing. No app is needed for setting adjustment, you can just edit /etc/elementalx.conf file or reflash the standard kernel to enter aroma again for that.

If you are interested though, EX does have its own app which is still in beta stage, here is the link. It allows you to do setting adjustment and a lot more with more features to come.
[Nexus 5 Original Android Development] SynnyG:
F*** ! It's my second nexus 5, I hate when I have to RMA ... I'm seriously considering to be refunded ... Sorry for the little OT but do you think it's possible ?
[Nexus 5 Original Android Development] notbrodie:
that doesn't happen in the kernel. it is a compile time mod that has to be made in the rom. cm roms do this. AOSP does not.
[Nexus 5 Original Android Development] relevant_placeholder:
I don't know if there's a difference but on my new Honda Fit HDMI port it plays perfectly.
[Nexus 5 Original Android Development] Zhypr:
I see. It think it does require kernel support though. I've done it in the past with my HTC One X and only some kernels worked.
[Nexus 5 Original Android Development] relevant_placeholder:
Can you take a photo of your phone in dark room so we have some idea what you're talking about? While flar2 replied to your post I'm not clear what are you talking about.
[Nexus 5 Original Android Development] SynnyG:
Humm, I'll try to be clear... In fact when the brightness is at less than 10%, there is like a blot in the left bottom edge of the screen, not visible in high brightness situation. The screen is darker in this edge and with ElementalX kernel, this blot is more visible, and with backlight dimmer and slighty cooler color features from this kernel, this blot is more visible yet !

So I've two questions:

- [MENTION=4684315]flar2[/MENTION]: ( Without the Backlight dimmer option activated so stock minimum brightness level ) Do you have changed the minimum brightness level if we doesn't have activated this feature ?

- To all, Can you try to reproduce my issue ? Flash the kernel and activate the backlight dimmer option and slight cooler color feature, set the brightness level to manual and at the minimum ? I'll be extremely grateful !
[Nexus 5 Original Android Development] SynnyG:
Sorry, I've forgotten to attach a picture of my phone, there is a photo so ...
[Nexus 5 Original Android Development] flar2:
I don't think this is grounds for RMA, it's using the hardware beyond its specifications, some screens are just unevenly lit with the backlight that low . There were several people reporting this exact issue here and in franco's thread when the backlight dimmer was under development. Try changing he min brightness a bit higher.

The kernel has to have the driver to connect the hardware, but the hardware won't get used unless the system (ROM) supports it.
[Nexus 5 Original Android Development] SynnyG:
Thanks for the info, I know now that I'm not the only one in this case. I'll try to find the file's path and chaging the minimum. Now I remember that in the past I've changed this value in fku app and the situation was better but not perfect...

I really wanted this phone, but I have some many issue thaht now I'm disgusted !
[Nexus 5 Original Android Development] hooliganx:
I had this time ago [emoji15]

when I had a black N5

now,I have a Red N5 and don't have this problem.

only remember now, that I see your pic.

and I use same Rom and Kernel than before.

n5sk7.8.Robbie09.03gapps226art

El.X.105twrp2.7.1.0rd2.08v4a

----------------------------------------------------------------------------

have doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Nexus 5 Original Android Development] drawde40599:
Its hardware but there's nothing wrong with your device , u just can't handle screen that dim , just like some can

UV more than others. Every phone is different . Just don't go that low .
[Nexus 5 Original Android Development] swat4samp:
Can i use this kernel with UKM? It's mentioned in UKM thread that it supports this kernel. I am ready to donate for the new app but i have no source :( That's why i was asking. I usually prefer Apps like ukm rather than editing manually in config file.

Sent from my Nexus 5
[Nexus 5 Original Android Development] lzzar:
Wow, using that now. Great! The combination with mahdi ROM and ElementalX is just perfect! Thanks for the tip
[Nexus 5 Original Android Development] yukkio:
What's the advantage of ukm?

Br.
[Nexus 5 Original Android Development] drawde40599:
No apps are recommend ( besides flar2's ) , but we all use them , you just need try that one yourself
[Nexus 5 Original Android Development] gpvecchi:
Problem with the app: max screen off doesn't stick after reboot, even if flagged... Always back to the conf value.
[Nexus 5 Original Android Development] swat4samp:
As i said earlier, i have no source to buy the app. My card doesn't accept international transactions. And it's easier for me to change values on apps rather than editing them everytime in Config file. Well, so far i didn't find any issues with ukm. So will stick to it until something happens.

Sent from my Nexus 5
[Nexus 5 Original Android Development] skttrbrain:
Hi, I have a problem. Whenever I reboot, my live wallpaper is more often than not (but not always) removed and reverted back to the default Nexus 5 one. It could be a CPU or GPU issue as it's a relatively demanding wallpaper, but I'm not quite sure what to do to remedy this. I'm almost 100% certain it is the kernel and not another app as I haven't changed anything else recently (although I am also using the beta ElementalX kernel app) and this was never a problem before. Does anyone have any advice? Thank you.
[Nexus 5 Original Android Development] ^Reloaded^:
After flashing this kernel on pa 4.6 beta 1 flash light doesn't work
[Nexus 5 Original Android Development] hooliganx:
working here.

not kernel problem. [emoji111]

n5sk7.8.Robbie09.03gapps226art

El.X.105twrp2.7.1.0rd2.08v4a

----------------------------------------------------------------------------

have doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Nexus 5 Original Android Development] baggord:
https://github.com/AOSPA/android_de...mmit/26fde48a0964613eceb7ec73b8b7536c0223ce20

http://xdaforums.com/google-nexus-5/orig-development/rom-paranoidandroid-4-4-t2603881/page1119
[Nexus 5 Original Android Development] swat4samp:
Forgive my noob question :o Does S2W/DT2W cause battery drain even when you use your phone? Or it just drains when the phone is in sleep with those being active?
[Nexus 5 Original Android Development] walpurgisnacht30:
That's not a kernel issue. It is related to PA latest commit for the lightbulb, wait for them to fix that or you can use another Lightbulb app from Play Store, or you can manually add the latest commit lines to the 99elementalx file in init.d folder

Sent from my Nexus 5
[Nexus 5 Original Android Development] flar2:
Hang on, I need to make a change in the kernel to make it stick 100%

It's most definitely not the kernel. There is no relationship between the kernel and wallpaper.

No, makes no diff when the screen is on.
[Nexus 5 Original Android Development] skttrbrain:
It's not even possible that the kernel is overriding the demand for the CPU/GPU on boot, which is making the Nexus revert back to a static image? I don't really understand these things so I'm sure it's not if you're saying that, but I just want to be 100% sure, because the fact it's doing it sometimes but not all the time makes me think it's not an app doing it.
[Nexus 5 Original Android Development] sjknight413:
No, definitely not possible.
[Nexus 5 Original Android Development] skttrbrain:
Okay, cheers!
[Nexus 5 Original Android Development] educk:
It's userspace, the kernel has nothing to do with the wallpaper.

You could try a different launcher though..
[Nexus 5 Original Android Development] skttrbrain:
It's weird though, because I reverted back to stock kernel and was not getting the "wallpaper service gone" logcat I was sometimes getting on boot with ElementalX. When that service doesn't start, it notes that it's reverting to the stock wallpaper, so it's that error that's making this happen.

I even tried Franco just to eliminate that and got the same results as stock kernel - live wallpaper was fine after 5 reboots and no logcat error. Went back to ElementalX (edit- after flashing stock again, by the way) just to see if anything changed and it worked fine, live wallpaper was there. Decided to reboot again, the same logcat error showed again with the live wallpaper removed. I even tried it with a less demanding LWP - Phase Beam - and that was getting the error too. I made NO other changes to the phone, simply flashed the kernels. Again, I'm a layman. Not trying to sound repetitive or even anywhere near knowledgeable on this topic, just that it's fair to say the correlation seems to be there.

It's not a big deal but I just thought I'd note down what I found. If others aren't having the issue - and it seems they're not - then I suppose it doesn't matter.
[Nexus 5 Original Android Development] Mr.Jay:
I would like to ask some questions: Is this kernel compatible with ART? I tried Franco kernel on stock 4.4.4 with ART and I'm having random reboots all the time.

How's battery life and performance?
[Nexus 5 Original Android Development] Hatshipuh:
ART has nothing to do with kernel.

Never had any problems with ART on any kernel incl. ElementalX and franco.

As for battery life, decide for yourself, I doubt anyone would stay on any kernel if they had bad battery life or performance with it.

Tap-a-talked from my Nexus 5
[Nexus 5 Original Android Development] car vs driver:
Works just fine. FWIW, I'm running this under SlimKat and have multirom installed.
[Nexus 5 Original Android Development] drawde40599:
Still not the kernel. Try dirty or full wipe then install Elementalx , something is gummed up on your side or your ROM/ something u installed is acting up
[Nexus 5 Original Android Development] skttrbrain:
You're probably right, but with me using stock ROM and ElementalX being the only thing that's triggering this for me it'd be easier for me to just use another kernel. After 20 reboots on stock kernel for testing I still have zero issues. I was just noting my findings really :)

EDIT- reflashing system.img and adding Xposed/root back on after fixed it - for a bit. Then it came back. Tried a multitude of things, then wondered if it was the custom bootanimation I was using - and yep, seems to be that.
[Nexus 5 Original Android Development] drawde40599:
I'm on stock ROM with no modifications NO hacks , mods , "patches" xposed , nothing . and everything works perfect so dunno
[Nexus 5 Original Android Development] pietropizzi:
Touch_Boost errors, LOGCAT attached

Thank you for that kernel !

I want to use that kernel cause of -lower i2c clockrate

I installed the aroma 1.05 installer with predifened settings one week ago on AICP-Rom. Had some problems with the Rom, not kernel related, and sent the developer an LOGCAT. We solved my Problems but by chance he told me to better to solve out my touch_boost problems.

So

- I made a LOGCAT with Stock AICP Rom / Kernel runnig for 10sec (just unlocked my phone)

- Flashed ElementalX 1.05 Aroma

- made a LOGCAT once again, now with AICP Rom / ElementalX-Kernel

Attaching the 2 LOG files, I see lots of touch_boost errors in the second LOG. How can I solve this, anything I should care or worry about ?

Thank you !
[Nexus 5 Original Android Development] flar2:
Do the first two cores get boosted to 1267MHz when you touch the screen? If so, the error message is completely harmless. Even if touchboost is broken, it's not a huge deal.

It might be because I replace powerhal and mpdecision files with stock during installation. I think some paths might be hardcoded in the ROM build. You could try using the /system/lib/hw/power.msm8974.so that comes with AICP.
[Nexus 5 Original Android Development] a0b1c2:
HOWTO: CM - Change system vibration /duration/

By trial-and-error, I have tweaked on CM 11 the system's default vibration duration:

#
# Previous value was 20, set to 40ms
#
echo 40 > /sys/class/timed_output/vibrator/driving_ms

Now that's what OSS is all about. :)

Addendum

Ugh, after rebooting, the settings are not kept even if I tweak my boot script. If I add the hack to the end of the ElementalX conf file, it works. I may have to create another /etc/init.d file which executes after the 99* file: A1_mine :)

Cheers,

-pablo
[Nexus 5 Original Android Development] pietropizzi:
Thank you for your reply. All 4 cores get boosted to 1267 when touching the screen. I'll not worry anymore.
[Nexus 5 Original Android Development] Fulbring:
So I'm trying to flash this with Carbon ROM and it just gets stuck at the google logo everytime I try on the Nexus 5. Am I doing something wrong? I did a dirty and clean flash and still nothing,
[Nexus 5 Original Android Development] GtrCraft:
Flash the cm version
[Nexus 5 Original Android Development] notbrodie:
it shouldn't boost all 4. only cores 0 and 1 should be getting touchboosted
[Nexus 5 Original Android Development] gravedigger76:
Probably too quick but is there a change log for 1.06?
[Nexus 5 Original Android Development] flar2:
Update!!!!

A few fixes (color and vibration should work on CM, flashlight on PA) and support for the USB Keyboard app: https://play.google.com/store/apps/details?id=remote.hid.keyboard.client

Download:

ElementalX-N5-1.06 (all versions)

Changes:

-fix permissions for vib and color settings

-update msm-sleeper

-fix flashlight permissions

-add support for USB Keyboard app
[Nexus 5 Original Android Development] jayplusone:
EX App

[MENTION=4684315]flar2[/MENTION] here's the logcat for the app I was talking about on gplus. Hope it helps. :fingers-crossed:
[Nexus 5 Original Android Development] hooliganx:
app crashe when open miscellaneous tab.

anyone else?

n5sk7.8.Robbie09.03gapps226art

El.X.105twrp2.7.1.0rd2.08v4a

----------------------------------------------------------------------------

have doubts about Slim? click here:

http://slimroms.net/index.php/faqandmanual
[Nexus 5 Original Android Development] jayplusone:
Yeah that's what the log was for. I mentioned it on the gplus page. Exact same thing on my end. Touch miscellaneous and the app crashes.

Sent from my Nexus 5