yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Laurentyu1995:
I'm running r34 since it was a test release and I've flashed official update and i can say that i don't have any kind of problems. Battery life is amazing, very good performance and automatic brightness it's working now as it should be. I don't understand why some users have problems with this kernel... i haven't had a reboot only when I've undervolted too much. Thank you Franco !!!!
[Nexus 5 Original Android Development] bigknowz:
Happens from time to time

These sync wakelocks appear from time to time. Go into accounts, if Sync is running for Google+, turn off and on . Otherwise, it completed and either way, you should be all set.
[Nexus 5 Original Android Development] vinnyutd6899:
is this r34 the same as the r34 test2 of has there been some more changes?
[Nexus 5 Original Android Development] drdrewdown:
take a look inside your /system/etc/init.d folder for some clues.
[Nexus 5 Original Android Development] Laurentyu1995:
This have more changes
[Nexus 5 Original Android Development] yorici:
There is no way of having no flickering and not having to turn the screen on/off?

Could you (or anyone else) please point me to the commit? (I want to understand every part of the process:)) There are no recent commits in hammerhead/arch/arm/boot/dts/msm8974-hammerhead and for some reason github indeed says you updated your repository, but the commits only go till the 8th of January. Am I stupid?
[Nexus 5 Original Android Development] whitedragonz83:
Select his "staging" branch

https://github.com/franciscofranco/hammerhead/commits/staging
[Nexus 5 Original Android Development] yorici:
Thank you very much. I'm a github noob :o
[Nexus 5 Original Android Development] pkelly517:
We all were at some point.

At most points, I still am.
[Nexus 5 Original Android Development] KingBeike:
Still have some stuttering when i open close apps, but only sometimes ! All stock settings, did also a complete clean flash of purity but Problem still persists :( stock settings, deleted fku data. What is that ?
[Nexus 5 Original Android Development] shinesthru:
Have you tried upping your touch boost?
[Nexus 5 Original Android Development] sordna:
Interesting ! Can we expect this feature on the Nexus 4 too ?
[Nexus 5 Original Android Development] Tomson74:
Anyone Have Recommended Settings That Work For Them?

Hey guys,

Just wondering if anyone would like to share their settings that are working for them?

I am on stock.

I know, I know, what may be working for someone else, may not work for me. I am just trying to get a feel, and see what WOULD work for me.

Thanks.
[Nexus 5 Original Android Development] KingBeike:
Seems that increasing boostpulse to 1000000 is the solution for me.
[Nexus 5 Original Android Development] vs0587:
Can you add a toggle to FKU for the "new" backlight control? Because is too much low and change the intensity too many times......... :fingers-crossed:
[Nexus 5 Original Android Development] granets:
Is the weird "right channel on earphones skipping or going mute all together" fixed in r34? Thanks in advance for the info. This is such a great kernel, I love your work [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 5 Original Android Development] joyj112:
Max: 1728

Min: 300

Governor: Interactive

GPU: 320

Voltage: -50 global

300 mhz: 650mV

IO: Deadline

Using Franco's Per App Modes for Gaming(Asphalt,Heart Breaker,Swordigo)

Max:2265

Min 300

Governor: Performance

GPU: 450

Still on Dalvik because of Xposed Modules, but really don't care that much about it. Still buttery smooth and no stuttering whatsoever. Deep sleeps like a baby and per app mode works flawlessly.
[Nexus 5 Original Android Development] KuChar_:
create script init.d. You don't have to type manually every time after boot
[Nexus 5 Original Android Development] vs0587:
I don't know how to do it....
[Nexus 5 Original Android Development] Piereligio:
TrueRGBv6.6

A new, latest TrueRGBv6.6 is coming. And this time should really be the latest for a long time, or forever.

In v6 there was just a little problem, I solved it, but the profile is in testing phase, u will have it soon. Stay tuned :p
[Nexus 5 Original Android Development] Enddo:
no one said undervolting was a placebo for battery life. we say undervolting has such a minimal effect on battery life. which is true. your little undervolting will save you at most 10-15 minutes of battery life for a 100% - 0% discharge. people undervolt for heat purposes

a nice warning would be to tell anyone who uses minimal brightness to increase it before flashing the kernel. i usually kept it at 2% to 5% and i could barely see the screen after i flashed

can confirm lowest brightness changed a lot

i was seeing this but it seems a reboot fixed the issue. the response time is just a little slow
[Nexus 5 Original Android Development] KuChar_:
I don't like this new auto brightness. I turned it off after flash. I prefer using lux app for this.

_____

Nexus 5 & SwiftKey_
[Nexus 5 Original Android Development] vomer:
I will be expecting the link :D
[Nexus 5 Original Android Development] rajunks:
How do you access the feature? How do you access any kernel feature for that matter?
[Nexus 5 Original Android Development] vomer:
use the FKU app or do it manually using terminal emulator.

I am working on a script right now that will make manual stuff easier
[Nexus 5 Original Android Development] pbryson:
Is the new auto brightness feature already active or do i have to enable it?
[Nexus 5 Original Android Development] drdrewdown:
on by default
[Nexus 5 Original Android Development] Savant:
Yup and it works wonderfully since, it does what it supposed too . Glad they take gradual steps instead of big leaps like other kernels.
[Nexus 5 Original Android Development] Empty Hand:
On a somewhat related topic, I remember reading that auto brightness is bad for battery because the phone is constantly looking to see if it needs to adjust the brightness. Is that true?
[Nexus 5 Original Android Development] Zainiak:
If it is bad for battery, that is not the cause. The sensors use a negligible amount of power afaik, if you get bad battery life then its because the brightness is too high
[Nexus 5 Original Android Development] JasonX199:
I will stick with r32, I get framdrops with r33 and r34 on myboy and other gaming apps. Which is weird, no one actually posted this in here.
[Nexus 5 Original Android Development] Zainiak:
I searched and read the last few pages and it seems that nobody else is having this problem. On the latest r34, I'm getting screen flickering on the lowest brightness level. anyone else?
[Nexus 5 Original Android Development] mibtnt:
While posting on the PA thread I remember seeing a mic tweak in FKU, by chance is there anything we can do via the kernel to fix the AGC issue with the mic? I think I have the issue.

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] sordna:
Franco is working on an FKU feature that will allow FKU to invoke a custom script on boot, so we can call our custom commands.
[Nexus 5 Original Android Development] franciscofranco:
???

I'm not sure a transparent navigation bar makes sense with the dark Holo theme. I'll have to test it.

App derp.

Nope, I cannot, my eyes hurt.

That behaviour comes from the hardware sensor.

More changes.

So far myfluxi didn't find a way to do it without flickering or weird panel glitches. If he couldn't do it I doubt I'll be able to make it better.

Dunno, I don't know what backlight video driver the N4 is using, but if its similar I'll try to port it over (its not my original code, its from flar2).

Yes I'll add it.

Ok.
[Nexus 5 Original Android Development] franciscofranco:
Its mostly finished by now because I can borrow the "Custom Paths" feature code from the Per-App Modes app ;)
[Nexus 5 Original Android Development] Tzfardaya:
per app modes app getting folded into fku shortly? (one of these days I'm going to have to grep through this thread to find the paths to all the existing tunable files.. :P )

And I think the immersive mode for kitkat would work with any theme style wouldn't it? slide the nav and status bars off screen until needed?
[Nexus 5 Original Android Development] Verro3:
Will this work with slimkat?
[Nexus 5 Original Android Development] mystique47:
me too. I hope it's not dangerous for the phone. It's even lower than r33 in fact drains less battery!
[Nexus 5 Original Android Development] Zainiak:
It seems weird to me so I'm not gonna use it. Its too dark to see even at night for me. Personally, I liked it better before because I could quickly move the slider to the bottom, now I can't
[Nexus 5 Original Android Development] Mawtin:
Did you not read the OP at all?
[Nexus 5 Original Android Development] Enddo:
yes, it does
[Nexus 5 Original Android Development] jaj473:
yes and when idle, sleeps like a beauty..
[Nexus 5 Original Android Development] Fluidification:
Screen pulses on lowest 2 brightness levels, and on lowest, left side of the display is dimmer

R34
[Nexus 5 Original Android Development] Nucleotide:
Love this kernel. Everything working awesome as per usual - except the sounds issues while playing music. It will occasionally cut in and out but it's completely random and I'm not even sure if it's kernel related.
[Nexus 5 Original Android Development] justibasa:
I've noticed the left side of the screen also. A lot darker than the right side.

Don't like me.......BITE ME!!!
[Nexus 5 Original Android Development] gerbig:
Some phones have that or the flicker on the lowest backlight setting. It's been that way with all the screen dimmer modules. Does it happen if you're one level above the minimum? At what brightness level does it go back to normal?

Maybe there's a way for Franco to add a third setting for minimum brightness. It could be stock, Franco default, and a step or two above Franco default for phones with the flicker/uneven backlight.

Thanks Franco! I'm glad minimum brightness works on my phone :)
[Nexus 5 Original Android Development] alamarco:
Not a big fan of r34. The change log mentioned something about auto-brightness levels, but this wasn't just auto-brightness. I have auto-brightness turned off, but immediately noticed the screen had a washed out look upon rebooting after the r34 install. Going back to r33 removes the washed out look.

I use a custom color profile (Gingerbread man's), but even going back to stock color on r34 didn't fix the wash out. It wasn't brightness either, it was washout. Increasing the brightness just increased the backlight, the screen still had the washed out look.
[Nexus 5 Original Android Development] perrocaliente:
I don't quite understand. I tried typing in what Franco said to echo in the terminal editor to undo the auto brightness levels and it's not doing anything. What did I do wrong? I'm a bit of a noob when it comes to echoing stuff.

---------- Post added at 11:49 PM ---------- Previous post was at 11:45 PM ----------

Should I leave multicore power saving on in trickster? By default it's on 2 but I'm not sure if that's due to Franco kernel or default because on stock I also had this option. Will it actually save battery by turning it on?
[Nexus 5 Original Android Development] Zyphur:
Is it possible to change a value somewhere to remove/modify at what point the OS tells you your volume is reaching a 'dangerous' level?
[Nexus 5 Original Android Development] gparmar76:
Has the audio clipping issue been resolved with r34? I'd love to test it with various ROMS but its so time consuming.
[Nexus 5 Original Android Development] bradputt:
Don't think so, ppl have been reporting this even when r34 is at the test image stage.
[Nexus 5 Original Android Development] inscythe:
Again, from r34test to r34 final, the Bluetooth LE connection issue is still there:

http://pastebin.com/wRjyR3bm

It didn't take long for it to break. Returning to r32 fixes the problem again.
[Nexus 5 Original Android Development] jkpark17:
Still audio clipping through r32-34 at the low volume or max volume using deadbeef, poweramp, google music and neutron. I might have to go back to stock kernel for now since its really.bothering me alot.
[Nexus 5 Original Android Development] omvir:
...And the biggest placebo effect award goes to alamarco!
[Nexus 5 Original Android Development] Bobtehblob:
A control for the new brightness minimum would be great Franco! I accidentally put mine to zero today and the screen is literally impossible to see even in a backed out room. Had to sit there for a good 10 minutes on and off trying to changr the brightness from muscle memory :D managed to get it in the end!

Otherwise r34 is running great Franco. Based of my experience on the tests and now the full releases, I've never been happier with a phone ever. I've got my phone so well under control that I don't even bother with BBS these days and I just let your kernel do the rest. If you're having battery or performance issues it's operator fault guys :) None of the memory leak issues have bothered me at all, though I do reboot once a day just after I finish my charge cycle.

Is there still any chance of you being able to make the camera mic gain adjustable? I record a lot of videos with my phone and anything remotely loud just distorts to no end. Would really be the cherry on top for me :)

Thanks again Franco, you're a bloody legend!
[Nexus 5 Original Android Development] wardawgmalvicious:
Idk if you've already done so, but you could try using MultiROM and in recovery use the option to share kernel across your multiple ROMs you have installed. Just make sure Franco is compatible with that ROM beforehand, otherwise you could into some odd problems.

-wardawgmalvicious

Rooted N5/N7 2nd Gen

MultiROM TWRP

Franco Kernel

Stock 4.4.2 infused with GB

Ubuntu Touch r206

-Sent using Tapatalk
[Nexus 5 Original Android Development] stacio88:
I went back to r32 but now y settings won't stick with fku. Anyone running r32 have the same problem?
[Nexus 5 Original Android Development] KuChar_:
Nope, try deleting app data.

_____

Nexus 5 & SwiftKey_
[Nexus 5 Original Android Development] Ben36:
It's too dark even on stock auto brightness :-\
[Nexus 5 Original Android Development] rofik_gitara:
i get little dark with r34 and i can't use touch control app,can't loading modulle

anyone gat the same?
[Nexus 5 Original Android Development] fugn:
OT. quizup is amazing.
[Nexus 5 Original Android Development] Pete182:
Anyone having trouble getting usb otg to work? I'm having trouble mounting the drives. I'm using the stick mount app
[Nexus 5 Original Android Development] whytechapel_x:
I love the new auto brightness
[Nexus 5 Original Android Development] stacio88:
Tried that and had no luck. Settings just won't stock after reboot on r32. Oh well I'll just try r34 again.
[Nexus 5 Original Android Development] RobbieL811:
What ROM are you using? I am using SlimKat & I had trouble with it also. If you aren't using SuperSU, try flashing that. That's what fixed it for me.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Enddo:
no pulsing here. it just goes so dark that i can't see anything. this issue has to be hardware specific and will not affect everyone.

sounds like people with this issue will have to control how low they drop the brightness. like with speakers or headphones that distort when increasing the volume so loudly.

---------- Post added at 02:59 AM ---------- Previous post was at 02:56 AM ----------

same thing happened to me, but since i flashed the new kernel with such a low brightness level, the screen was not visible when it booted back up into Android

a warning for users would be nice
[Nexus 5 Original Android Development] fradbari:
Hi, anyone tried the last franco with paranoid 4.1?

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Nexus 5 Original Android Development] misterviolinguy:
Yes.

I would say that it's slightly slower, with approximately the same battery life. But YMMV.

I do really like the color control though.
[Nexus 5 Original Android Development] TrainNanpaMaster:
Let me guess, you're getting immediate force

closes. It's because if the ram disk. Many roms have switched to the newer CAF one.

sent from the back of a magical, prancing unicorn.
[Nexus 5 Original Android Development] Teenight:
Why?Is CAF better than AOSP?
[Nexus 5 Original Android Development] nerotix:
Not at all.. I've tried 2/3 CAF roms with stock and custom CAF kernels and for some reason they are all laggy.. specialy when opening apps. AOSP roms and kernel seem to make the device alot smoother and giving me no lag at all.
[Nexus 5 Original Android Development] TrainNanpaMaster:
Franco, is it possible you can implement the newest CAF ramdisk telephony commits into your next r35 test? r34 force closes on many of the newest rom nightlies because of this

change><.

sent from the back of a magical, prancing unicorn.
[Nexus 5 Original Android Development] momomok:
Is your ROM CM-based? If so, switch ROM or search for a zip somewhere in xda to revert all those CAF ****s

Franco has made himself pretty clear that he will stick with the AOSP side

Sent from my Nexus 5
[Nexus 5 Original Android Development] macacao:
+1
[Nexus 5 Original Android Development] thesebastian:
I wonder why the "scanning always available" function keeps WiFi ON 24/7 instead of just enabling/disabling WiFi when something ask for location.

That function steals more than 10-15% of my battery. But I let it on because i really need it for Maps or location services specially when I'm indoors.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Stevemeister:
Indeed, CM feels less smooth. I'd rather stick to a non CAF firmware like Omni or Stock. I don't care about top of the line branches sometimes close to experimental. Having stable firmware is way more important to me plus this is a Nexus, I didn't switch from Crapsung to Nexus to have a unstable device :p.
[Nexus 5 Original Android Development] blueren:
Interesting to Note that the stutters in animation.. app open/close have indeed been minimised but not fully gone. Also noticed that the touch boost is already bumped up.. with regards to the 34 test previously.

Sent from my Nexus 5
[Nexus 5 Original Android Development] TrainNanpaMaster:
Dude. Relax. Calm down, take a deep breath. Know what you're talking about before you type something ignorant like that.

Everyone knows Franco doesn't support CAF based roms. I am of course talking about AOSP based roms. You do realize since r33

Franco is pulling loads of patches and commits from CAF right? And 'innovative' AOSP roms like Slim, Omni, PA,, Vanir Etc constantly pull and update CAF commits on almost a nightly basis, right? Do you know why they do this? Because CAF has the most up to date,, bleeding edge, lowest latency, most efficient technology.

Many of the biggest AOSP roms have switched to the newer, more efficient CAF ramdisk in the newest nightlies. That's why I'm inquiring to Franco.

Do some research before ignorantly posting next time. Thank you.

sent from the back of a magical, prancing unicorn.
[Nexus 5 Original Android Development] bushako:
Any difference between FKU update and the one from Mega server? I've got the r34 from Mega but my internet is too damn slow(GPRS) to download again.
[Nexus 5 Original Android Development] oddlyshapedstickman:
Daaaaaamn. But yeah, I love all the hate CAF gets on this thread when Franco uses CAF patches himself. He just doesn't use some on the ones CM uses (and hence causes the incompatibility issues), which is totally his choice and fine by me, but don't hate on CAF. They do some incredible work.
[Nexus 5 Original Android Development] momomok:
Some CAF commits doesn't require ROM side modification to work... I believe that's what Franco and other AOSP ROMs have been merging.

But thanks for the info, haven't known that you're talking about ramdisk...

Anyway, isn't ramdisk only affecting bootup?

Sent from my Nexus 5
[Nexus 5 Original Android Development] oddlyshapedstickman:
Yeah, it's effectively an img that helps boot the rest of the img's (system, data etc...).
[Nexus 5 Original Android Development] momomok:
How would it cause FC then...?

Sent from my Nexus 5
[Nexus 5 Original Android Development] alamarco:
Sorry dude, I'm so sorry for experiencing an issue. I mean, because you don't experience it, it must be placebo. I apologize, I really do.

You would think, at a place such as XDA, that most people would understand what bugs are. I mean, it is a place for developers. I'm guessing you don't understand much about bugs do you omvir?
[Nexus 5 Original Android Development] oddlyshapedstickman:
FC's? FC's are caused by app incompatibilities (i.e. missing libs, incorrect version and stuff like that...).
[Nexus 5 Original Android Development] tsubus:
I was skeptical to flash r34 after reading all the comments, but after doing so I'm not experiencing any of those issues, everything works flawlessly. Thanks for a great kernel, franco.
[Nexus 5 Original Android Development] The Gingerbread Man:
Reboot on latest r34 I launched camera by accident when I was using gallery and it went boom! Wdog reset last kmsg https://www.dropbox.com/s/4xcg4zrn5ovx5uc/last_kmsg

Kernel settings in sig, undervolt has been stable since I reworked it since the change from a test r33.
[Nexus 5 Original Android Development] momomok:
Thanks for confirming.

Maybe FCs experienced by [MENTION=5271321]TrainNanpaMaster[/MENTION] is due to ROM-side issue then?

The way he said is like the ramdisk change is causing the FCs... I just wonder if that is possible

Sent from my Nexus 5
[Nexus 5 Original Android Development] Nucleotide:
I'm not one to usually complain, but the auto-brightness in r34 is terrible. It goes way to dark too quickly.

Restoring r33 for now. :(
[Nexus 5 Original Android Development] italia0101:
Seems a little excessive to go back a whole kernel version ...

Originally Posted by franciscofranco View Post

If you don't like it:

echo 0 > /sys/module/lm3630_bl/parameters/backlight_dimmer
[Nexus 5 Original Android Development] KuChar_:
You can turn it off

_____

Nexus 5 & SwiftKey_
[Nexus 5 Original Android Development] karlj38:
Will the new brightness implementation interfere with Lux? Or will Lux override any system set options like it normally would.
[Nexus 5 Original Android Development] fradbari:
sorry, but on which rom?
[Nexus 5 Original Android Development] tsubus:
DU, it's in my sig.
[Nexus 5 Original Android Development] Nucleotide:
I did see that, but I've seen someone complaining that it doesn't work for one. Assuming it does work I've got to use it every reboot or add it to an init.d script.

There was nothing wrong with r33 for me so it's easier to just restore it. No big deal.
[Nexus 5 Original Android Development] italia0101:
Fair enough , just thought id let ya know
[Nexus 5 Original Android Development] KuChar_:
If you are using lux then you should disable new auto brightness or set whole settings from start in lux

_____

Nexus 5 & SwiftKey_
[Nexus 5 Original Android Development] floepie:
Sorry for my boldness but I don't understand why brightness levels have been changed when lux is admired by so many. The lowest level is just too dark in low ambient light levels.
[Nexus 5 Original Android Development] blueren:
Um.. I think the new auto brightness thing is a little too aggressive. May need to get used to it though.. normal till now, suddenly screen dims and eyes need to adapt.. and by that time, it brightens up again. [MENTION=3292224]franciscofranco[/MENTION] - is this a test feature? Or Is it gonna stay this way?

Also, was anything find to the sensitivity of the touch response? O.o

Sent from my Nexus 5
[Nexus 5 Original Android Development] sirovai:
I wondered the same thing. Sorry for my frankness, maybe hasn't it would been better to focus on other things?
[Nexus 5 Original Android Development] dankross:
Completely agree. Bit of a nuisance having to readjust all the brightness settings in Lux because of what's been foisted upon us in r34.

Could there not be a setting in FKU to disable this new brightness feature?