yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] squadz:
Don't have that setting, but I compared with my girlfriend who has the N5, and both our settings match, so it must be something else.

Franco confirmed it's not the kernel, what can I reflash or do to fix? I'm assuming something went wrong going to 4.4.2.
[Nexus 5 Original Android Development] Rashiel:
Hey, little question..

Where I can find the option to activate d2tw?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] aavvaallooss:
Not available on this kernel. Try Phantom variant
[Nexus 5 Original Android Development] absoluterebirth:
There is no d2tw on Franco's kernel. If you want, you may want to check out Linaro Kernel in the Android Development Forum. It has d2tw and a couple of other goodies.

http://xdaforums.com/showthread.php?t=2527130
[Nexus 5 Original Android Development] zephiK:
Or Touch Control. I rather not use dt2w etc etc, extra battery consumption isn't worth it.

The phone was made for your buttons to work and has been stress tested to ensure that it doesn't break. So just use the phone.
[Nexus 5 Original Android Development] absoluterebirth:
Did Franco remove the faux sound control on his kernel? That's the only reason I'm on Linaro right now.
[Nexus 5 Original Android Development] kenkiller:
Or just get one of those flip case that switches on and off the screen automatically, at least the N5 supports those.

My previous N4's power button, I dunno, maybe it wasn't stress tested to ensure it won't ever break. :(
[Nexus 5 Original Android Development] pkelly517:
I'm pretty sure that every phone/tablet/device with buttons was made for 'your buttons to work'.

Yet there are reports on every device where the buttons fail. The XOOM and N4 come to mind immediately, as two devices I've owned.

I'd love a battery sipping no-button method to wake up the phone. Touch Control on the N4 wasn't bad. I've been a little less pleased with the N5 version. But since it's only been a month...
[Nexus 5 Original Android Development] DoesntPostAThing:
Gave Franco another go after persisting GPU issues on Faux that have yet to be fixed. Franco seems to be the only one free of these issues. Had good experiences with Franco on my Galaxy Nexus, so looking to join this community again! Will likely purchase the app and get into more tweaking over the holidays.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Never had faux code here.
[Nexus 5 Original Android Development] absoluterebirth:
A couple of version back I was able to control the sound completely though? Such as speaker volume, left and right headphone, left and right poweramp heaphone, mic, etc.

Edit: Never mind, it wasn't faux code. But you did have full sound control, didn't you? What happened to that?
[Nexus 5 Original Android Development] franciscofranco:
Nothing, code is still there...

/sys/class/misc/soundcontrol/
[Nexus 5 Original Android Development] IIMaxII:
Hey Franco, I'm just wondering if there's any plans to implement underclocking and undervolting below 700v, and if not why? Just curious.
[Nexus 5 Original Android Development] franciscofranco:
Underclocking -> never, not a chance. There's really no major improvement by using lower frequencies as it would not only make the device scale for higher frequencies because a lower minimum would not be enough and because Qualcomm, which has engineers far more experienced than any of us on XDA, didn't add lower minimum than we have on stock

Undervoltage below 700mV -> I really haven't had much thought on this. What actual gains would we have with it? I mean real gains besides having users come in here crying for reboots and blaming me? I can decrease the limit, but if shít starts I'll go back to 700mV, no questions asked or warnings given. And I was mistaken before, I actually added a 700mV minimum voltage limit to my voltage interface, I just didn't remember before.
[Nexus 5 Original Android Development] IIMaxII:
Well a possible slight increase in battery life when the screen is off and idling at lowering frequencies. Honestly if people are blaming you for messing with stuff that they have little to know information about, then it's their own fault and they should probably just stay stock. Maybe just make it an option for paid users to limit the amount of n00bs. :P
[Nexus 5 Original Android Development] franciscofranco:
Bold part -> absolutely not!

When the screen is off and there are no wakelocks the device is in deep sleep, doesn't matter what voltages the cpus are or what frequency they are, they are shut down. The only gain I can see is when you're reading an ebook or reading text altogether when the interaction with the device is almost null.

TL DR

pretty much damn useless to get it lower than 700mV in the long run.
[Nexus 5 Original Android Development] IIMaxII:
Wouldn't most social networking apps such as Facebook, Whatsapp, or KiK cause wakelocks and throw the device out of deep sleep?
[Nexus 5 Original Android Development] The Gingerbread Man:
Your right about the people needing to learn to be responsible how ever the free fku 1 doesn't work on n5 yet and 2 the paid version allows users to tune what they want how they want to and 3 they could use another free app like trickster to change voltage.

I seem to remember this lower limit of 700mv being introduced on galaxy nexus because a lot of people got SODs trying to use lower and it got to the point everyone was pisses off with people *****ing and not understanding their device limits or how to recover.
[Nexus 5 Original Android Development] franciscofranco:
Sure if they need to do background work with the device awake, but that's not my problem or concern. At that point voltage won't do you mostly any good, most of the device internals are clock and voltage gated, and are most likely a sleep and the main battery hog, the display, its turned off. Its just fúcking pointless, you get good battery during screen off my controlling the apps and having the device on deep sleep. And even during runtime the biggest battery improvements come from a properly calibrated governor that ramps up very fast and as soon as the work is done ramps down very very fast (lets not take into consideration the display brightness in this example). All in all at this point of the hardware, where clock and voltage gatings are everywhere, plus all the sleep states that the CPUs go through, reducing the frequencies voltage is pretty pointless in my opinion. I never know if I'm undervolted or not, my battery is always the same. Besides, there are more voltage points in the device than anyone that doesn't go through Kernel files realize. CPU frequencies voltages are just the tip of the iceberg.

All in all, I don't give rats ass about CPU frequencies voltages and there hasn't been a day where I regret having merged those interfaces in the Kernels.

Feel free to constructively criticize my points, I'm all hears and open for a healthy discussion :)
[Nexus 5 Original Android Development] The Gingerbread Man:
A voltage window maybe an idea, like say for 1500mhz being able only only use values between 800mv 950mv just as an example. It could be interesting to see if these sd800 beasts could go lower than 700mv but the battery gain wouldn't be great, I can't see anyone running 500mv at 300mhz which is a sizable saving but anything less than 50mv I don't think make any difference. The main benefit imo undervolting is to the higher speeds to reduce heat generated as a by product of usage of the device
[Nexus 5 Original Android Development] IIMaxII:
Definitely! lowering voltage for less heat is a good point, could prevent the phone from throttling.

---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------

OT: But when do the FKU cruzerlite case for the N5 come out?
[Nexus 5 Original Android Development] franciscofranco:
If your device is throttling it means you're using the higher frequencies, therefore lower voltage on lower freqs is moot.

About the cases I dunno, we haven't talked about it to be honest.
[Nexus 5 Original Android Development] Nbsss:
300 is my most used frequency, guess I do a lot of reading on xda and the web, would be interesting to see how low voltages can go for this one frequency... Maybe for funzies like the OC :)
[Nexus 5 Original Android Development] drawde40599:
I never notice anything when I undervolt , no battery increase , never less heat , nothing . And I never see before and after results from anyone ? I do have my own personl results and they show no difference on any of my nexus phones or not enough I care . maybe just me
[Nexus 5 Original Android Development] franciscofranco:
I will decrease to 600mV as minimum, but I'll revert it back the second I see posts about crashes and how to recover from crashes or whatever someone will make up when they post.
[Nexus 5 Original Android Development] BTT8:
Is the default max at 1190 for r20?
[Nexus 5 Original Android Development] KTT16:
[MENTION=3292224]franciscofranco[/MENTION] - Hey man, great work on your kernel. I've really enjoyed following the development and thread. Just wanted to mention that I ran into a small issue. These were the steps:

1) Started from stock

2) Flashed r20

3) Underclock to 1574MHz - Set on Boot

4) Undervolt -50mV - Set on Boot

5) Try to set Speaker gain to 5, but when I access the menu, it doesn't want to scroll all the way down, and actually the menu seems stuck where it is. I can swipe to the main menu and access other parts of the app, but nothing seems to take..wasn't a huge deal so i decided to reboot the phone.

I rebooted the phone and it didn't set the values, probably a good thing. I was then able to access the speaker gain function...

Curious, it didn't seem like underclocking and undervolting should have caused this...(these were similar settings when we were still at r 13) Your thoughts on what might have happened there..or whether you are able to duplicate?

Thanks as always.

Best,

K
[Nexus 5 Original Android Development] yoyoz808:
Please don't do it Franco. You already know what's going to happen.....
[Nexus 5 Original Android Development] BTT8:
Hmm. That's weird. Its showing thats the default in Trickster after flashing r20. No biggie because I can just bump it back to 2.2.
[Nexus 5 Original Android Development] itzallgood707:
Looms fine on mine.

Nexus 5 is alive!

---------- Post added at 05:49 AM ---------- Previous post was at 05:49 AM ----------

Nexus 5 is alive!
[Nexus 5 Original Android Development] Bobtehblob:
My thoughts about going lower than 700mv is that it might save us a few degrees on idle? That way when the CPU does need to ramp up. It can do so for longer before needing to throttle. Then when it ramps back down again it should theoretically cool faster? Even if it is minimal.

Either way I'll take any temperature savings that I can right now. Here in Perth we're currently in a heat wave with day after day of 40c weather! Still not as hot as the old n4 got!
[Nexus 5 Original Android Development] DoesntPostAThing:
My N5 is like a refrigerator compared to my Galaxy Nexus... would heat up to >70 randomly and ambient temperatures were only ~28C. N5 stays at a nice 40-50 on light usage, ~60 when playing intense games. No undervolting.
[Nexus 5 Original Android Development] franciscofranco:
I cannot replicate. Are you using v11 or the beta version that I pushed couple days ago? That'll help me narrow down the possibilities because on the beta I've done a huge number of fixes and improvements in the layouts. Thanks.

Yes I know, but I want to laugh a little bit just for the sake of it :)

Because after a flash and after the boot the sensor reports high temperature (kinda fake temperature but that's what it reports) and then the thermal throttle kicks in and limits the max freq until the sensor reports a cooler temperature. Just leave it and its all automatic.

I doubt you can notice anything with less 50mV on 300MHz, things happen to fast inside these little chips.
[Nexus 5 Original Android Development] hosmsdos:
Guys i am losing lots of battery when gaming. Is this normal? Can anyone who tried gaming on stock advise on this. Thanks
[Nexus 5 Original Android Development] DoesntPostAThing:
If anything stock uses more battery. Then again, depends on what game you're playing.
[Nexus 5 Original Android Development] Technecium:
You give very little info. Try flashing back to stock and compare.
[Nexus 5 Original Android Development] Nocturnal86:
Can you be a little less vague?... But gaming is super heavy on the processor so of course shorter battery life is expected...
[Nexus 5 Original Android Development] KTT16:
[MENTION=3292224]franciscofranco[/MENTION] - I flashed straight from FKU, which...is V11...correct?

Thanks again,

K
[Nexus 5 Original Android Development] franciscofranco:
Yeah you're in the stable. v11.1 will be out tomorrow/sunday to production if I have time to finish adding a couple things
[Nexus 5 Original Android Development] Nocturnal86:
Is there a beta update in the store right now? I just got one when I checked my apps in googleplay
[Nexus 5 Original Android Development] franciscofranco:
Beta v11.1 has been up since December 6th, I pushed a new update less than an hour ago.
[Nexus 5 Original Android Development] Nocturnal86:
Yup been on the beta.Thanks!
[Nexus 5 Original Android Development] zoltrix:
Guys is there any way to increase the microphone strength with this kernel? Or is that more OS based?

Unless the mic is pointed directly at my mouth, the person on the other end can't hear me too well...

Its starting to get annoying.

I know there is the Mic Gain option in FKU but my testing didn't show any changes
[Nexus 5 Original Android Development] BTT8:
So I tried setting the max back to 2.2 via trickster but every time I save, the max gets reverted back to 1.1. Shed some light here?

EDIT:

Fixed it. Just reboot.
[Nexus 5 Original Android Development] JPhantom95:
For the past few days I've been plagued by a problem where, upon receiving a notification while my phone display is off and the sound is at max volume, my notification sound will buzz as if my speaker were broken. After uninstalling this kernel the sound has gone back to normal with no buzzing. This was on r19 with no extra tweaking or modifying.
[Nexus 5 Original Android Development] parkson:
The classic, "Have you tried turning it off and on again?"
[Nexus 5 Original Android Development] LaboDJ:
Franco I found a bug in latest fku beta, how to replicate it:

Open voltage control

Open menu and go to kernel settings

Hit back button

See the tab title
[Nexus 5 Original Android Development] Gauss23:
Would it be possible to enable CONFIG_IP_MULTICAST?

There are some cases where multicast is needed. Is it a big problem for battery drain?

More infos here:

https://code.google.com/p/android/issues/detail?id=51195

Thanks for the good work!
[Nexus 5 Original Android Development] Nbsss:
Is interesting that the colour tweak r20 (phantoms version) gives me a perfect 1.8 gamma across all colours, even grey, whereas stock colours were all over the place. I think you were onto something with that tweak franco, maybe that's why I prefer it - made the colours consistent with each other, although it's a side effect as you said...
[Nexus 5 Original Android Development] Zeduaz:
Franco one question - are in r20 latest drivers for cam from 4.4.2 update? Im going on mountains and I want make some nice photos... ;) thank You
[Nexus 5 Original Android Development] floepie:
Could I ask anyone if the video recording issues have cleared up, i.e. dark and somewhat choppy videos? Thanks...
[Nexus 5 Original Android Development] 75markus:
Everything is fine for me, r20 & cataclysm

Gesendet von meinem Nexus 5 mit Tapatalk 4
[Nexus 5 Original Android Development] rayz93:
Hey Franco, since LaboDJ is posting a FKU related issue here, I think I might as well too,

-Nexus 5

-Stock Android 4.4.2

-Franco kernel r20, stock settings

-LCD Density in build prop 280 (tablet mode),

I'm having issue with the back button, it just won't work, but if I swap back to phone mode by upping the LCD density value in build prop, the back button is functioning normally again
[Nexus 5 Original Android Development] drawde40599:
Its updated from 4.4 to 4.4.1 there were no kernel changes in 4.4.2 whatever was updated was in the ROm

---------- Post added at 02:17 AM ---------- Previous post was at 02:14 AM ----------

That happened to people on stock kernel also it was never a Franco issue .... Make sure your 4.4.2 ROM with this kernel and u should not have that issue
[Nexus 5 Original Android Development] Moh_Jay:
Dark recording is an issue with the camera, not the kernel and only tends to happen in low light situations.
[Nexus 5 Original Android Development] GNEXc:
Franco, got an update on play store. Updated but the version still says as 11.1-beta. What's the new version ?
[Nexus 5 Original Android Development] BrandoHD:
What are you using to test this gamma value, as most in-depth reviews would tell you, the gamma and calibration on this devices is probably the best and most accurate on any android device
[Nexus 5 Original Android Development] CaspaTheGhost:
Most are using Display Tester in conjunction with Faux's app.

https://play.google.com/store/apps/details?id=com.gombosdev.displaytester

Sent from my Slim N5
[Nexus 5 Original Android Development] ChazzMatt:
And it shows the display needs improvement. 2.0 gamma, out of the box for most people -- while 2.2 is the standard. Some even prefer 2.4. But 2.0 makes blacks and colors look washed out.

_______

Sent from my Nexus 5 (LG-D820)
[Nexus 5 Original Android Development] theamazingaustin:
Hows your battery / performance with Franco + CM11 Been?

Just jumped to CM to see how it runs with this Kernel - was hoping to improve battery + performance over stock, but I'm seeing the opposite so far.
[Nexus 5 Original Android Development] Pretoriano80:
Here's the battery drain with R20 and stock rom.

Lots of tweaks installed here and never used a clean flash since I've bought the phone, so quite "dirty" rom here.Here's some of the tweaks i have here:

- exposed framework (with 3 or 4 modules loaded)

- moto-x dalvik patch

- Better Battery Stats

- Grenify

- Android Tuner

- FKU & Faux Gamma app

- GPS always On and Location on high precision

- Tasker (with a couple of scipts to help me use WiFi and Data connection only when needed/available)

- Launcher = Next Launcher 3D

- Undervolt = -75mV on almost all frequencies with a CPU bin 0

So battery wise i can't ask more from this kernel, thx franco and keep up the good work.

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Dunno, I'll check.

Dunno, I don't test the app on that dpi setting.

Beta update.
[Nexus 5 Original Android Development] JUMPhil:
Franco, can you implement native OTG too?
[Nexus 5 Original Android Development] Sydius08:
Just flashed Franco Kernel R20 to my Nexus 5 (stock rooted). I noticed there's no app to do overclocking/underclocking and other custom kernel things like that. Which app can I use? I'm hoping to get great battery life using this kernel. I see a lot of you have!

New to this kernel, that's why I ask. Thanks!
[Nexus 5 Original Android Development] XtraWho:
Trickster Mod

https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
[Nexus 5 Original Android Development] Sydius08:
Thanks, I'll try that app. Had to install some Busybox thing though haha
[Nexus 5 Original Android Development] franciscofranco:
OTG code is the same as stock. If it works on stock it works here, if it doesn't then it doesn't here. CM team has 0 commits on Hammerhead Kernel so we're all using the same code. Apart from that I dunno, I don't use OTG.
[Nexus 5 Original Android Development] franciscofranco:
I'm off to see my grandmother today so I'll leave you all with a boot-test21.img to play with. I'll explain more in detail what I merged later when I back, but in the mean time I'm interested in some gaming performance tests due to some interactive changes from me and that I merged from CAF. http://192.241.177.15/Nexus5/4.4/tests/boot-test21.img but there's some neat code that I merged that helps how a couple of important subsystems in a lower level work (not visible to userland).
[Nexus 5 Original Android Development] XtraWho:
*^ thanks mang!
[Nexus 5 Original Android Development] klin1344:
Thanks!! Trying it out right now
[Nexus 5 Original Android Development] Testraindrop:
Franco can you change /sys/class/leds/led:flash_torch/brightness permissions to 666 / rwrwrw to fix so torch issues?
[Nexus 5 Original Android Development] The Gingerbread Man:
Since release iv been playing dead trigger 1 and downloaded and played sonic dash. 1, I discovered I'm **** at dash type games 2, I was suprised that sonic was only needing 2 cores most of the time 3, didn't see any lag and fps seemed fine to me. I don't often game on my mobile, I couldn't see that anything was wrong it just worked with the normal speed I have come to expect from the phone.
[Nexus 5 Original Android Development] javacody:
I just flashed r21-test.

Battery life is amazing! I got nine hours of SOT already and 3 days on a charge!

Franco, your granny must have super powers! ;)

Have a good time and thanks for everything yo do for us!
[Nexus 5 Original Android Development] AhmedFaiz:
Just wanna clarify is the fast charge still broken?

Nexus 5, Cataclysm, Franco r20
[Nexus 5 Original Android Development] the baptizer:
???????

which rom, settings, and kernel settings?
[Nexus 5 Original Android Development] XtraWho:
Fast charge been working on my end. I normally get a full charge in 30 mins.

You can use trickster to enable force fast charge if you like, I never needed to do so.

If this kernel doesn't have fast charge damn if my phone doesn't charge fast and if that's the case I have to find out why it charges so fast.
[Nexus 5 Original Android Development] franciscofranco:
Kernel settings: sarcasm.
[Nexus 5 Original Android Development] AhmedFaiz:
Thanks Will switch it on and try now.

Nexus 5, Cataclysm, Franco r20
[Nexus 5 Original Android Development] nexusmaniac:
Hi, all of your kernels are pretty smooth but r21 feels much smoother than any previous release, can't tell if placebo or the interactive enhancements have done something incredible :)
[Nexus 5 Original Android Development] :
Why wouldn't everyone use fastcharge? Why is it not enabled by default if it's charging faster?

Am I missing something?
[Nexus 5 Original Android Development] mitchdickson:
Yes, you're missing something. If it were enabled by default, a user would not be able to browse their phone by USB when connected to their computer. Wouldn't that suck?

Also, fast charge should only be used when plugged into your computer. I have heard that it should not be used when plugged into a wall charger.
[Nexus 5 Original Android Development] XtraWho:
Not sure if fast charge is enabled by default for this kernel or not, trickster mod will allow you to force fast charge, I never enabled it through the app due to my charge times (30 mins or so).

I didn't see the need to try and make it faster.

Truth be told a nice slow trickle charge goes a long way, IMO you don't want your phone charging too fast, you don't get full use out of the battery that way.

That's why my reply said if its not enabled by default I need to dig in and find out why it's charging so fast.

Also
[Nexus 5 Original Android Development] franciscofranco:
Yes that helped, but there are other numerous lower level enhancements to kthreads management and other crap thank to the great upstream Linux developers.
[Nexus 5 Original Android Development] XtraWho:
Noticeable improvement over t20.

Running some test, pushing this baby to her limits, let you know of any problems, by the looks of it I feel comfortable in saying slim to none.

Great kernel
[Nexus 5 Original Android Development] bilago:
Well I'm sorry you see this as a myth. I was stuck on 2.26GHz in your app, not lower. Pressing other values higher than that, did not change the value shown on your application, even after clearing data. Only started to change once I reflashed your kernel again.