yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] aaa12585:
Can no longer keep stable undervolt since r53-r55. Chrome crashes/freezes randomly and Netflix will freeze image but continue playing as normal.

Apologies, running phone at stock voltages for now, will update if stability status true.

Edit: Yeah, no. Still happening.

Hoping r56 brings phone back to life.

Sorry for being a newbie, but did you need a logcat for these things?
[Nexus 5 Original Android Development] mr.right77:
No, I forgot it. Just checked because you remembered me that. I was sleeping (my phone also) for 2 hours (so absolutely is not the temperature) and it's stuck at 1958. I disabled per app mode days ago. Can't really figure it out.
[Nexus 5 Original Android Development] Flrc:
I set boostpulse to 0 (I think this disable inputboost?) and see no difference in performance.
[Nexus 5 Original Android Development] Kaydin:
Hello, [MENTION=3292224]franciscofranco[/MENTION], and thanks for the awesome kernel! Running very smooth.

I was wondering if you could merge 2 commits about Gamma Corrected Brightness.

Here and here.

[MENTION=4809179]yorici[/MENTION] said that there's a tendency to use lower brightness when running this, so, it might save some battery life.

Here's the info about it.

Thank you!
[Nexus 5 Original Android Development] akash3656:
That patch is good. It fixes one problem on the nexus 5 where changing the brightness from 10% to 15% causes a dramatic increase in brightness compared to other phones. But going from 50% to 70% hardly increases the screen brightness.

With that patch, the brightness curve is more sane. And you generally have more usable brightness % levels. And with more usable brightness levels, one can easily reduce their brightness levels precisely. Ever felt adjusting the brightness can be a matter of too bright to dim at times no matter how much you try to adjust? This patches fixes that.

---------- Post added at 12:56 AM ---------- Previous post was at 12:48 AM ----------

Do yourself a favor and DO NOT undervolt unless if you want reboots.

Want reboots? Then UV. And enjoy the (1-2%) battery drain to reboot the phone.

Want stability and great battery life? Don't UV.

Especially on this device where certain kernels UV at different thresholds, it is not worth the hassle. When my UV doesn't reboot, battery life takes a hit for me on this device.
[Nexus 5 Original Android Development] Technecium:
Don't know why your permissions are off. Might ask in the ROM thread.
[Nexus 5 Original Android Development] yorici:
We applied standard gamma correction to it. So the difference between 50% and 70% is actually just 12%. (50%=>73%, 70%=>85%). Your eyes can differentiate shadows better than highlights (For example: difference on stock between 0% and 1% seems enormous, but is actually quite linear). For these reasons the difference is smaller, though you should try this:

Set some widgets for 0%, 25%, 50%, 75%, 100% brightness. Then switch consecutively between them. I'm sure you will see the 75% seems more in place. If not, try gamma 3.0 ;)
[Nexus 5 Original Android Development] cubandanger05:
So I've flashed the new test img with flashify and by putting it in the restore/backup folder but after reboot Im still in r55, any ideas?
[Nexus 5 Original Android Development] eigokyoukan:
Just use the file manager in FKU? Works every time for me. [emoji106]
[Nexus 5 Original Android Development] aaa12585:
Agreed. But I kept it that way since it worked and allowed faster charging during usage.

However, I'm still getting the issue with stock voltages, soooo....... yeahhh.... :(

<3 Franco+kernels
[Nexus 5 Original Android Development] matesc:
50% battery. Latest r56test. Battery.....will...not.....die!
[Nexus 5 Original Android Development] sjknight413:
How is everybody getting these sort of battery stats?!

I have a brand new device and I cannot get more than 3 hours and fifteen minutes screen on time.
[Nexus 5 Original Android Development] pkelly517:
You use your device like you want.

Check the wakelocks. BBS is pretty useful, along with the BBS thread. See if there's something you want to turn off. Google is absolutely your friend.

~4 hr seems average for those who don't turn off everything. You're right on the edge.
[Nexus 5 Original Android Development] matesc:
I am most of the time on WiFi. That's why my results are so good. But there is definitely a noticeable difference between r55 and the test builds in battery life anyway.
[Nexus 5 Original Android Development] shohag2018:
good sir, can i have a link to the flashable zip for the latest test build pls?
[Nexus 5 Original Android Development] cobhc:
There aren't zips built for the test builds. Just flash the .IMG with FKU.
[Nexus 5 Original Android Development] matesc:
There are only boot.img - grab it from the OP and navigate in Franco kernel updated to that file and there is an option to flash it. Done
[Nexus 5 Original Android Development] rbrenart:
I had the same response to these threads for a couple months... Then I switched to ART and manual brightness and I'm getting much better life. Not this good because I run 5 emails, 6 calendars, and other synch hungry stuff, but about a 75% increase from dalvik and auto brightness.
[Nexus 5 Original Android Development] cubandanger05:
That didn't do the trick. While on omni rom when it reboots after "flashing" the img via fku or flashify my phone reboots into my primary stock ROM (I'm using multirom) and I have to boot into recovery to inject the thingy so I can reboot into into multirom from there on forward. When I finally boot into omni ROM and check the kernel version it still showes r55
[Nexus 5 Original Android Development] Tylog:
Boot.img doesn't have kexec patch. Dual boot can't work, that's the reason. Take the boot img. and create a flashable zip. No big deal :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] eigokyoukan:
Deleted multi replies from Tapatalk freaking out... *facepalm*
[Nexus 5 Original Android Development] akash3656:
Thanks and wow being quoted by yorici!

Earlier on I was mentioning the behavior of stock brightness levels. And yes with the new patch, the brightness levels on this device seem to work better than stock (at least to the human eye).

Personally, I like the value the value (2.0) best. Hope more kernels incorporate this patch.
[Nexus 5 Original Android Development] eigokyoukan:
Or that :D beat me to the reply lol
[Nexus 5 Original Android Development] Tylog:
:)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] cubandanger05:
Thanks to both, I don't know why it didn't occur to me to extract the r55 zip, put the new img in it and then zip it again. Up and running now ?
[Nexus 5 Original Android Development] jfim88:
Flashed latest test with PA and all is good here

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
I will need to take a look into those patches today :)

Yes it does...
[Nexus 5 Original Android Development] hjjiang:
Not sure if people other people are still getting the no scrolling in Backup/restore mode, but I am still getting it on the latest beta App. Anyway to fix this? i tried clearing the data but that didnt work
[Nexus 5 Original Android Development] freshlysqueezed:
Because it flashed the boot.IMG to the primary rom. Fku and flashify are oblivious to the fact you are running in a secondary ROM on multirom.

Easiest thing to do is take the boot.IMG and copy it into a r55 kernel zip. Go into twrp-> advanced-> multirom->list ROMs-> select ROM and flash the zip.

Edit: didn't see the other 2 replies before i posted. [emoji106]
[Nexus 5 Original Android Development] Andromendous:
It seems as if this kernel+slimkat+art = heavy battery drain.

I am using the latest test img

---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------

I am using the latest test img

---------- Post added at 06:36 PM ---------- Previous post was at 06:34 PM ----------

I am using the latest test img

---------- Post added at 06:37 PM ---------- Previous post was at 06:36 PM ----------

I am using the latest test img

---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------

I am using the latest test img
[Nexus 5 Original Android Development] LiquidSolstice:
But are you using the latest test img??

Sorry, I couldn't resist :P
[Nexus 5 Original Android Development] Andromendous:
Wow, dunno what all those replies are about

---------- Post added at 06:51 PM ---------- Previous post was at 06:49 PM ----------

Im on the one from yesterday. Ill try the new one ;)

---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------

Im on the one from yesterday. Ill try the new one ;)

---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------

Im on the one from yesterday. Ill try the new one ;)
[Nexus 5 Original Android Development] kufikugel:
lmao but tell me .... you are on the one from yesterday?

sorry could not resist as well :D
[Nexus 5 Original Android Development] Andromendous:
Im on the one from yesterday. Ill try the new one ;)
[Nexus 5 Original Android Development] Tzfardaya:
I'm guessing you're using tapatalk? I've noticed that if it has difficulties connecting to the forum, it will just keep retrying (and sending the same post over and over and over again) even if the forum has accepted the post ...

When tapatalk seems to be taking longer than normal to send the message, I usually swipe tapatalk out of the recent apps window, then log back into tapa and check if the post was successful or not.
[Nexus 5 Original Android Development] franciscofranco:
Why are you still on the beta? Production app has been pushed like 2 weeks ago. Don't you people check for app updates every now and then? :p
[Nexus 5 Original Android Development] hjjiang:
Im using 11.53 at its doing that, just did a fresh install
[Nexus 5 Original Android Development] combatdeity:
The only problem I have with this phone is the auto brightness, suddenly blinding you, and just too bright in general.

These patches could be great.
[Nexus 5 Original Android Development] K Rich:
Agreed.

Franco said he is looking into it
[Nexus 5 Original Android Development] sordna:
Francisco could you please bring back the setting to set the custom voltages on boot ?

It was especially useful on the Nexus 4.
[Nexus 5 Original Android Development] franciscofranco:
I already pushed the fix to the store, it was a small derp on my code.
[Nexus 5 Original Android Development] namurt:
i think i may already know the answer to my question (after various searches across various threads). that being said, i'd like to just double check.

i'm running the latest carbon nightly.

i'm running ART.

i'm running franco r55.

every time a new nightly is installed (via the delta update system baked into the rom) i, of course, must reflash franco as the delta update flashes the rom's stock kernel. when i reflash franco, i get a ton of apk's force closing. (the 'unfortunately this app has stopped' message) if i wipe cache and dalvik after a franco reflash, then things get even weirder. some of my apps simply disappear and i have to reinstall them from the play store.

is this because the latest nightlies of carbon are incorporating more and more CM commits and it's a potential CAF incompatibility kind of issue?
[Nexus 5 Original Android Development] Tzfardaya:
Most likely.
[Nexus 5 Original Android Development] franciscofranco:
I think it's related to dalvik patches, I've seen that happen on other roms with those same patches. There's a reason why it doesn't occur on stock.
[Nexus 5 Original Android Development] K Rich:
Just out of curiosity, what ROM are you running? Stock?
[Nexus 5 Original Android Development] akash3656:
Yep, he uses stock ROM.
[Nexus 5 Original Android Development] franciscofranco:
Pushed a new test boot.img with refactored thermal driver code. I tested running the StabilityTest app and the device was throttling and restoring the frequencies just fine. I made it throttle on boot and it throttled during the boot process and then restored the frequencies afterwards. Please test it out, specially the ones who were having problems with it.
[Nexus 5 Original Android Development] franciscofranco:
The latest boot.img on the tests folder has the gamma 2.2 backlight levels map by default. Please test it out guys, I'm off to dinner, be back later.
[Nexus 5 Original Android Development] tlrsax54:
Fwiw I am running with touch boost lowered to 1ghz and at duration 250,000 which is a little under stock and haven't seen any performance drop. Too cool! Might back it off even more soon. I like the latest changes :)
[Nexus 5 Original Android Development] aimcr7:
Just flashed the newest boot img and I don't know if it placebo or not but I feel that the lowest brightness is brighter than before. It can save some battery I guess with lower brightness value needed for outdoor usage.
[Nexus 5 Original Android Development] zenxaero:
Delete
[Nexus 5 Original Android Development] akash3656:
I know this sounds counter productive, but try the opposite of undervolting, which is overvolting (+25mV) and see if it helps.

If that doesn't help, maybe its time to start fresh. Your pick either to flash factory image or another ROM.

---------- Post added at 12:56 PM ---------- Previous post was at 12:50 PM ----------

Not placebo; if you look 1-2 pages back, yorici and some other people were talking about it....

Refer to this thread for more details: http://xdaforums.com/showpost.php?p=52940349&postcount=2
[Nexus 5 Original Android Development] Cuapy:
Hi Franco, could you please update pam settings so the input boot freq would be a drop down list rather than a "text field"? Would be easier for ppl to set it :)
[Nexus 5 Original Android Development] franciscofranco:
Absolutely! :)
[Nexus 5 Original Android Development] Cuapy:
Haha, do you ever sleep? :) I honestly didn't expect such blazing fast reply :) Thanks!
[Nexus 5 Original Android Development] franciscofranco:
I sleep, but most of the time beside that is in front of the computer. Specially now, Sunday, the office is empty I'm here just with cgollner coding, it's a bliss - nobody to bother me with questions or other random crap I don't care about! Also my GF is not here to "consume" my time, so all is well :)
[Nexus 5 Original Android Development] omvir:
Franco, have you forgotten about my suggestion :p lol. About being able to add custom path to tunables in the CPU manager tab? Just like how you can do it for the PAM app, but instead its under the CPU manager tab, that way we can set on boot for whichever tunable we define. (Most likely useful for people who have bought your app and don't use your kernel/use device other than the ones you dev for)
[Nexus 5 Original Android Development] franciscofranco:
I haven't forgot it, don't worry ;)
[Nexus 5 Original Android Development] omvir:
This idea could be a reason to make a whole new app as well. I'd buy it for sure ;). It could be an all around kernel tweaker, leaving the user in charge of adding which tunables to tweak and what not.
[Nexus 5 Original Android Development] matesc:
The latest test builds auto brightness is somehow incorrect. With or without backlight dimmer the screen is just too dark. Is it maybe in conflict with the brightness curve from slimkat ROM? Just an idea.
[Nexus 5 Original Android Development] eeliah:
Hi! I've UV'ed somehow but can't remember stock voltages. Someone wants to take screen from stock voltages? :D I see i've done it in +/-25mV steps but dont know how much ;)
[Nexus 5 Original Android Development] Flyview:
The stock voltages depend on your phone (different CPU "bins"). You have to try to somehow reset it through the kernel.
[Nexus 5 Original Android Development] ben_pyett:
Hold on a moment that's what FKU is? Seems perfectly positioned in an advanced option within that. Not to mention that Franco has had that on the to-do list for quite some time and always seemed to like the idea, must never been the priority.
[Nexus 5 Original Android Development] rjnikku:
I facing this issue again.... I m on fku 11.5 and whenever i reboot.. None of my settings stick.. Like color profile gpu cpu vibaration etc.... Im pa 4.41 and r55... Last week it was sticking after reboot... But now it doesn't.. Not sure why... Any help would be appreciated... Btw thnxx frnaco for awsm kernel....
[Nexus 5 Original Android Development] omvir:
Yeah it does seem like the best position for it is to just stay in the FKU app. It was just a suggestion because that feature would pretty much let you tweak anything kernel related which could be an app on its own. And yes I know it has been on his list for a while. When I first suggested it to him, he had told me that it would be in the next production release, but it wasn't. So I was just asking to get an update.
[Nexus 5 Original Android Development] ben_pyett:
I think it would also be wonderful if we could add commands to a queue one at a time (similar to zips in TWRP) that then get flushed to a file and run on startup
[Nexus 5 Original Android Development] omvir:
Lol wouldn't that defeat the purpose of the 'set on boot' feature? Or did I misunderstand you?
[Nexus 5 Original Android Development] apeiron6:
+1

Sent fra min Nexus 5 via Tapatalk
[Nexus 5 Original Android Development] ben_pyett:
would be the same except this would be for custom tunables, not covered by app, although this can currently all be achieved thorough user scripts and applications like tasker
[Nexus 5 Original Android Development] antifocus:
Hi,

Using system monitor I found out that my 4 cores will always go online no matter what the load is in PAM, and I set the hotplug load threshold to 100...

Tried clearing FKU data, reinstalling FKU and reflashing kernel, no luck. currently on r55

Thanks..

edit:

core offline seems to be fine in PAM in my mother's Nexus 4, but stopped working after updating to the newest FKU 11.54.

Not 100% sure though, didn't pay much attention to updating the app.
[Nexus 5 Original Android Development] aimcr7:
I experienced otherwise, the brightness seems brighter than before, on auto and backlight dimmer on. I am using Mahdi fyi.
[Nexus 5 Original Android Development] franciscofranco:
Wtf... are you streaming through Wi-Fi? I've been listening to spotify the last 3 hours straight from my N5 and its flawless.

Wow your chip must be really really bad. You have to reduce the thermal throttle threshold then to 65C or something.
[Nexus 5 Original Android Development] jm6001:
Bah. Of course just my luck... Could it be anything else? I'm on the cataclysm rom..
[Nexus 5 Original Android Development] shaker2k:
Not that I care. I love the phone bad chip or not. I froze at 21% r14 cataclysm rom on antutu.
[Nexus 5 Original Android Development] PhantomGamers:
What cpu binning do you guys have?
[Nexus 5 Original Android Development] mercuriox85:
Speaker gain work on ringtones?

Regards!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] omegajester:
Phone bootlooped when I flashed r14 from the app... Luckily I had r13 in stock.
[Nexus 5 Original Android Development] shaker2k:
I'm running default settings. I haven't adjusted anything.
[Nexus 5 Original Android Development] PresidentMcCain:
Obviously the kernel won't work on the iPhone.

http://xdaforums.com/showthread.php?t=2515593
[Nexus 5 Original Android Development] omegajester:
Neither will it on a bootlooping N5
[Nexus 5 Original Android Development] TheSpaceManatee:
When franco mentioned bad chip, I think I have a bad chip too. Not that Antutu doesn't wor, but my score hovers around 20k in Antutu :(
[Nexus 5 Original Android Development] franciscofranco:
That's because of thermal throttling only.
[Nexus 5 Original Android Development] davy917:
You guys are mind****ing yourselves. This is why I won't benchmark because I love my phone and I know I'll feel bitter if I think I have a bad chip or get low scores. The less you know...
[Nexus 5 Original Android Development] noneabove:
Can confirm. I normally have a lot of skipping (i listen to my phone while playing on the computer) and it hasn't skipped in over 2 hours where it used to skip every 2nd song
[Nexus 5 Original Android Development] kepapas:
Smooth
[Nexus 5 Original Android Development] TheSpaceManatee:
just lowered thermal throttling to 65, rebooted in antutu @.@ something is so wrong. although stock kernel does not reboot

forgot to mention that when the device does force reboot, it never boots into ROM again, and the only way to fix is flash factory image. for me that is
[Nexus 5 Original Android Development] spelaben:
There are still those weird sounds when playing music with screen off on r14. Idk if that's what was supposed to fixed, not sure how to describe the sound. :/
[Nexus 5 Original Android Development] franciscofranco:
Doesn't happen on stock because thermal throttling is SO FRIKKING HEAVY that almost as soon as you open Antutu your device is already starting to throttle in fear that it will burst in flames. If you keep lowering that threshold you'll be able to complete the benchmark. That's how it is, sorry.
[Nexus 5 Original Android Development] franciscofranco:
Can you increase suspend frequency a notch to see what goes? Is that streaming through Wi-Fi or normal local music files?
[Nexus 5 Original Android Development] spelaben:
Will do, I'm playing downloaded spotify playlists so that would be local.
[Nexus 5 Original Android Development] lkthomas:
any chance to get sweep2wake support on Franco kernel?
[Nexus 5 Original Android Development] akash3656:
The brightness levels/curve has changed with this new release.

If you want the old behavior refer to this post: http://xdaforums.com/showpost.php?p=52940349&postcount=2
[Nexus 5 Original Android Development] Kaydin:
Thanks, [MENTION=3292224]franciscofranco[/MENTION]! Going to test it out.
[Nexus 5 Original Android Development] Tylog:
I have expressed myself wrong, patch available but can not be activated in the recovery. :) Option 1 MultiROM app take and change over to the second Rom boats or Option 2 Boot.img in flashable zip, that's what i want to say :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] tylerdurden83:
[MENTION=3292224]franciscofranco[/MENTION]

I've had a random reboot when I opened candy crush saga, I noticed that the colors where off and it rebooted, here is the last kmsg: https://www.dropbox.com/s/w6olga5h378iqa8/last_kmsg.log
[Nexus 5 Original Android Development] Edge330:
I'm not sure but I think lowering input boost freq to 1 GHz really saving my battery...
[Nexus 5 Original Android Development] Enddo:
what's the input boost set to by default? 1.4GHz? the difference between those two frequencies are 820mV and 860mV. While 40mV could save you some battery, i don't think it would save you much. i guess it all depends on how much you touch the display

some are currently testing putting the input boost to 300mhz right now. I have to say, I like the results
[Nexus 5 Original Android Development] The Gingerbread Man:
Currently 1ghz is touch boost speed. Its not all about the voltage difference between the cycles per second is quite high and also measure that by 2x as 2 cores at minimum are online. It could probably be lowered even more, I am using 883mhz as touch boost without lag. Another factor to consider is the ram speed. During a conversation between me and Franco he explained to me that even 300mhz and 345mhz the ram steps up a frequency which will use more battery.
[Nexus 5 Original Android Development] Technecium:
Just putting something out that crossed my mind.

With the recent changes in the behavior of interactive, would there be any benefits to either enabling/disabling cpu freqs in acpuclock-8974.c?

I did do a quick build to test out while I walked my dog. Enabled the whole lot of them, however it just got stuck at the Google logo. :( Crash course in freqs I suppose.

Anywhoo, got any thoughts?
[Nexus 5 Original Android Development] htcsnap93:
i'm Having issues too. When i freshly install the latest carbon + PAgapps it runs fine. Whenever I install franco kernel I lose my service and can't unlock my sim.

I thought this one was compatible with Carbon ?