yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] tylerdurden83:
[MENTION=3292224]franciscofranco[/MENTION] ragarding our suggestions to start or not from scratch, I'll give you my two cents.

Are all the cm or caf patches, the merges and reverting, really worth it? I'm not saying that their benefits are placebo like undervolting, but from my point of view, no, their benefits arent worth the loss of stability for the end users, nor your time to commit and debug and revert and read around for them.

Stock kernel just works. It doesn't panic, it doesnt disconnect the bt stream, the right ear doesnt die, etc. There is one thing where it works, but hardly at his best, battery life.

Can't you simply take the stock kernel, apply your smarter governor and tunables to make it way less aggressive than it is at stock, and so be it as far as battery life goes? I know that you merged power management patches to improve battery life even more, but again, maybe that's overkill.

I'd love to have a stock kernel enhanced with your governor/tunables, the gamma interface support, and possibly some very very slight extra tuning (like the wlan_rx_wakelock tune that you did to help with it).

For those not cheap users that want to squeeze even more battery life out of your kernel, or maybe they want to sacrifice it for more power, then there is the FKU app! And I'm not saying that it's not perfect as is, but maybe if you gained some spare time from the kernel development as you'd not have to do all those rebases and reverts etc, you could use said time to add even more functionalities to FKU (or to just do something else entirely, your call!)
[Nexus 5 Original Android Development] JNewms:
The thing is, those patches have done wonders with the battery. The battery and performance I'm getting in the 34 test is amazing. Also, I've never had any issues with RAM being low, or any issues with my headphones not working. It's of because those two issues aren't affecting everyone. Seems like it's a small number of people, compared to how many use this Kernel. I'm not sure what direction Franco is planning to take as I haven't talked to him in a few days, but I'm really going he doesn't have to start from scratch again. There would be a lot of hard work and amazing progress lost.
[Nexus 5 Original Android Development] inscythe:
Just google about that with Bing!
[Nexus 5 Original Android Development] tylerdurden83:
Not saying that they havent, but at what cost all the patches came in terms of stability and time consumption for the developer?

If you look around the thread, there are quite absurd 6-7 hours screen uptimes around, taken before those patches were applied. I think that it's a matter of saying enough is enough, if my battery lasts 6-7 hours with franco's own changes + per app modes, I can't care less if it becomes 8.

I do care that I can't use franco cause I always stream music to my car stereo on the commute to work, and use runkeeper and google play music when I jog at night...
[Nexus 5 Original Android Development] JNewms:
I guess I'm just lucky then. I have none of the issues you describe. My bluetooth works fine. I've never used runkeeper though. But the other things you've mentioned all work on my device.
[Nexus 5 Original Android Development] ArtieQ:
So what tweaks can be done after flashing the kernel? I have only flashed it.
[Nexus 5 Original Android Development] tylerdurden83:
Franco releases it as is, meaning with the best setup in mind. If you have FKU you can apply some per app modes to lower frequencies while using some apps, or raising them while using some other apps, but other than that you are pretty must set to go!
[Nexus 5 Original Android Development] Cuapy:
Hi Franco just got a kernel panic, I was at work listening to music via Poweramp when phone just rebooted.. No Uv slight underclock, and settings modification nothing fancy though.. Here's a link to last ksmg: http://pastebin.com/DTiSLTYQ

Thx in advance for looking into it
[Nexus 5 Original Android Development] italia0101:
Hi , just wondering if someone could help me out with the " per-app modes" app .. it says you can set custom paths for turnables... does anyone know where are they actually located?

or how to add them?
[Nexus 5 Original Android Development] gaurav2009:
+1 no problems here also except some launcher redraws after 2-3 days :)
[Nexus 5 Original Android Development] 1337RYoN:
I apologise if this has been asked. I think Franco said this kernel supports USB Audio out to an external DAC, but has anyone tried it with Cataclysm ROM?
[Nexus 5 Original Android Development] winhhh:
Is anyone here running a build of Franco on PA 4.1 ?

I'm about to install PA and interested in flashing Franco too...
[Nexus 5 Original Android Development] FAdrums:
Me! r34 test build! Working beautifully! :)

Tapatalked from my Franco Paranoid ARTified Hammerhead
[Nexus 5 Original Android Development] The Gingerbread Man:
I'm in absolute agreement. My own opinion is hold of the rebuild until Google releases the next maintance android version, so 4.4.3 / 4.4.4. Google have acknowledged the camera issue with camera deamon, when that's fixed it should help with memory management. The sound issue can be avoided if people just don't use the top two steps for volume and use headphone boost to 1/2/3 and headset gain -1 which sounds better. But back to my origin point, let google play their hand first.
[Nexus 5 Original Android Development] winhhh:
Cheers for the quick reply mate! Gonna give it a shot now :)
[Nexus 5 Original Android Development] :
Even people who don't use camera often or at all have gotten memory issues so its not guaranteed the maintenance release will help, you're just assuming it will, last I've heard the camera daemon issue locks the frequency of a core/s at max, same as what some users on this thread have mentioned, nowhere is it mentioned memory management issues till r33 was in testing and after it's release. It's probably a combination of those patches and/or random one and there were so many that it's difficult tracking down which one/s, so it seems like the logical solution to go back to a clean base and test the patches to track down problematic ones. I have zero issues on r32 so I'll stick to it till Franco decides he's ready to release a new one
[Nexus 5 Original Android Development] elnahir:
I've been having an enormous amount of redraws with the latest r34-test.zip. Whenever I would open 7-8 apps and switch between them (Chrome / Chanu / Flow / Imgur + Play Music in the background and lets say Facebook), the phone would just start to crawl. My experience from the past 4 days painfully reminded me of the old Nexus S days. So, I just flashed r32 and now feel like everything's as it should be.

To be perfectly honest, last 2 days on r34-test were with PerApp Modes - UC on 4-5 apps to 1.2GHz, just to test it out. My best guess is that switching between apps with no PerApp Modes and apps WITH PerApp Modes is quite stressful on the battery/performance.

Anyway, r32 feels quite smooth for the past ~18 hrs, hope it stays that way. :)
[Nexus 5 Original Android Development] tylerdurden83:
See, you are corroborating my position on the matter. You are effectively rolling back to a 2 months old (jan 8th) build because the massive merges of the following releases just enhanced aspects of the kernel at a too high cost. The past two months of work done my franco on the kernel are, in a way, going into the backburner.
[Nexus 5 Original Android Development] combatdeity:
As to if the re-write is a good idea, yes, I believe it is, the alternative is franco just takes a break till 4.5.

I think it would be a good idea for franco to keep releasing tests builds as he goes through the patches, that way if he does end up merging a problematic patch, we can narrow it down much more easily.
[Nexus 5 Original Android Development] bog3nator:
Does the newest Franco kernel fix the diaper fcs on vanir using Google dialer?
[Nexus 5 Original Android Development] nerotix:
Because a kernel effects how apps in a rom work. (Y)
[Nexus 5 Original Android Development] oddlyshapedstickman:
Maybe you should try these, the latest model:
[Nexus 5 Original Android Development] bog3nator:
Dam autocorrect. Yes it can effect some app usage. Someone on vanir Google plus page said it was bc the telephony lib had to be added to the ramdisk.. But thanks. For the smart reply back
[Nexus 5 Original Android Development] Wenzo2:
Someone had said that undervolt is only placebo... But i didn't agree it... So I've done some test...

I underclock to 1,4 GHz and disable thermal trottling.

First: 1,4 GHz @835mv (-75mv)

-20% battery in 25 minutes

Second: 1.4ghz [MENTION=2450033]910[/MENTION]mv

-20% battery in 18 minutes

With Antutu battery tester the CPU go a 1.4 GHz all time.
[Nexus 5 Original Android Development] nerotix:
Well the thing is, I use google dialer since day one in combination with franco and never had an issue, as many have reported before. So I'm quite sure its a problem with your rom and/or clearing data/chaches.
[Nexus 5 Original Android Development] tylerdurden83:
Ofc in that case you saw a difference. If you disable throttling what happens is that without uv you hit thermal throttling sooner, which lowers the frequency a bit, thus keeping the power consumption constant. The question is, in a normal usage scenario, with non constant cpu frequency for the duration of the usage, and thermal throttling, would you have noticed lag due to the throttle kicking in slighty sooner? 99% of the usage cases you wouldnt have. So in a real world usage case, undervolting makes no difference.
[Nexus 5 Original Android Development] Wenzo2:
Why run to 1,2ghz instead 1,4ghz? And in a normal usage thermal throttling don't go down the frequency... Thermal throttling acts only when you play game.
[Nexus 5 Original Android Development] perrocaliente:
I agree. If I wanted a stock kernel with no noticeable improvements I would use stock. Franco has always been more efficient and faster. I don't believe the solution is to throw out the baby with the bath water. We just might need to clean the bathwater before we put the baby back in.

---------- Post added at 11:18 AM ---------- Previous post was at 11:15 AM ----------

Well on r32 I barely made 4 hours of screen time on a brand new Nexus 5. I'm fairly confident that if I was willing to deal with the issues of r34/r33 it would be significantly better.
[Nexus 5 Original Android Development] tylerdurden83:
There are 6-8 hours pre r32 printscreens in this thread, I'm kinda sure that if you barely made 4 hours, you won't immediately get to 6 just thanks to the caf merges, without changing anything in terms of apps, signal strength etc
[Nexus 5 Original Android Development] franciscofranco:
I decided I'll push r34 regardless because it has a couple fixes on top of r33 and a nice new feature from flar2 for a better Auto-Brightness experience. Uploading r34 as I post this.
[Nexus 5 Original Android Development] BRiANj64:
I don't wanna be a ****, but FC's can be a kernel problem...
[Nexus 5 Original Android Development] dastinger:
Thanks [MENTION=3292224]franciscofranco[/MENTION]! And, if I may ask, what are your plans for r35? Doing the reverting commits job until you find the culprit?
[Nexus 5 Original Android Development] franciscofranco:
Pushed r34:

* No more display flickering after applying a color profile, but now you have to screen off/on to apply the new colors

* New feature that improves Auto-Brightness experience (active by default)

* Merged a feature from upstream Linux to make the system use power efficient workqueues for several systems which will save some battery in the long run

* Other misc patches, improvements, fixes and merges - check my github

Have fun and obviously send feedback!

Not 100% sure yet. Let's see how r34 goes :) I'm expecting a new update from Google sooner than later, curious to see what they've done on the Kernel level.
[Nexus 5 Original Android Development] thesebastian:
[MENTION=3292224]franciscofranco[/MENTION] The work in the kernel level by Google is private until the next release? Or its possible to see it on the Android git repository?

Sent from my Nexus 5
[Nexus 5 Original Android Development] iPsychoGeek:
[MENTION=3292224]franciscofranco[/MENTION] just updated, why did you revert 1344MHz step? Isn't it better for battery?

Update: oh, sorry, found an answer at github.

Nexus 5 with Tapatalk Pro
[Nexus 5 Original Android Development] GeekMcLeod:
As always, your work is greatly appreciated! Just flashed, now to wait until tomorrow after work to see battery usage. Don't post it too much, but I will tomorrow night.

Posted from under your bed.
[Nexus 5 Original Android Development] franciscofranco:
Its private :/
[Nexus 5 Original Android Development] Kpoch:
i just installed R34 and wiped Dalvik to fully test it.

im gonna post results at night
[Nexus 5 Original Android Development] franciscofranco:
You don't need to wipe dalvik when flashing a Kernel... I never wiped anything since getting the phone in November.
[Nexus 5 Original Android Development] bog3nator:
Franco out of curiosity which rom are you using?
[Nexus 5 Original Android Development] drdrewdown:
he uses stock rom
[Nexus 5 Original Android Development] Empty Hand:
All together now:

STOCK
[Nexus 5 Original Android Development] Tzfardaya:
What was the rest of the methodology? What apps were running, what radios? We're both tests from the same starting charge?
[Nexus 5 Original Android Development] Wenzo2:
Only flying mode... Is a fast test... I don't have reboot the phone... And don't know what app run I think that can't change anything in 20 minutes... I don't have time to retest with more accuracy... Maybe sunday I can.
[Nexus 5 Original Android Development] ConMcCRay:
Did you lower the brightness cause it looks like its on the verge of turning off LOL plus I can tell that I have backlight bleeding now.
[Nexus 5 Original Android Development] monkey hung:
I auto flashed r34 and it wouldn't let me pass the boot screen logo. The phone would just shut off, not reboot. I'm on PA 4.1 and when I tried the test r34 that worked but autoflashing the new one doesn't work for me.
[Nexus 5 Original Android Development] saranwrap:
What were changes made to auto brightness?
[Nexus 5 Original Android Development] chikimonke:
Hi Franco, just flashed r34 and tried to apply a color profile and it locked up and rebooted my phone. Pastie.org says my paste is too big, so I have attached the last_kmsg here. I tried again after the reboot and nothing happened, so may very well have just been a one time derp.
[Nexus 5 Original Android Development] Wenzo2:
i solved :)
[Nexus 5 Original Android Development] DesertVelo:
Glad to hear!!!
[Nexus 5 Original Android Development] drawde40599:
patch

[MENTION=470754]Franco[/MENTION] . if already been mentioned or u new about sorry , but I'll post anyways https://www.codeaurora.org/projects...hecks-putusergetuser-kernel-api-cve-2013-6282 don't nonif it even effects us but good reading anyways :p
[Nexus 5 Original Android Development] Wenzo2:
i've imposted the max freq to 200mhz using a terminal. but i'm creating a script... why don't it run?

#!/system/bin/sh

echo 200000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk

edit: i've solved. it run.
[Nexus 5 Original Android Development] franciscofranco:
No need for that patch, its already implemented by default ;)
[Nexus 5 Original Android Development] djnewt:
Anyone getting a reboot using Antutu?. It happens everytime at 21% floating point cpu test.

I expect hiccups using beta builds so no biggie, just thought id mention. (r10)
[Nexus 5 Original Android Development] notbrodie:
happens to me with both franco and faux kernels

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Log please.
[Nexus 5 Original Android Development] i860:
No reboots for me, I run the test 4 times before your post.

Do you uv?
[Nexus 5 Original Android Development] johno168:
Anyone confirm that this fixes Android OS drain?
[Nexus 5 Original Android Development] franciscofranco:
Just pushed r11 to my server:

* Full sound control: headphones, headset, speaker and mic. Headphones boost is being reset everytime you plug/unplug your headphones or change music apps. I don't know why, seems like Qualcomm & Google are at it again. Theres no documentation for this chip so its hard to debug, it could come from userspace too. path is /sys/class/misc/soundcontrol/

* Increased suspend max freq to 1190MHz to fix those music stutter during screen off

* Touchboost is now being called once during the wake-up routine to speed things up after clicking the power button

* Increased interactive timer_rate to 25000 from 20000 and increased input_boost_freq to 1267GHz - this will give the device an extra performance burst during interactive, while providing better battery life in medium-long time frame because the freqs will jump much less when not interacting with the device directly due to higher timer_rate

* Merged a couple mutex/rwsem fixes from upstream
[Nexus 5 Original Android Development] djnewt:
Sorry, i have to go out now but ill do one if it does it again when i get back...Thanks FF.
[Nexus 5 Original Android Development] thyroidgland:
Thanks Franco!

So i usually never post.. but franco kernel and cataclysm rom have bascically made me love my n5 more than any phone I've ever owned in my life. Obviously I only have close to 2 hours of screen time, which will steer my battery life in a totally opposite direction, but I'm amazed it even made it this far. So thank you to the amazing devs around here, and especially to you franco for your amazing work! :)
[Nexus 5 Original Android Development] djnewt:
No i never UV but thanks for the reply..

Have to leave now..Have a good day/night all.
[Nexus 5 Original Android Development] dannstarr:
Auto flashed with FKU Beta :D
[Nexus 5 Original Android Development] casonswag:
How can we get this to run on cm11 type roms?
[Nexus 5 Original Android Development] dannstarr:
You choose one, or the other ;)
[Nexus 5 Original Android Development] casonswag:
U need a rom to run the kernel so i would like both
[Nexus 5 Original Android Development] suchevent:
i think what he meant is that you can choose cm11 or fk, you can't run both i.e. fk is not compatible with cm11
[Nexus 5 Original Android Development] casonswag:
I know what he meant thats why i said u cant run a rom without a kernel but ohh i see its not compatible i wish it was
[Nexus 5 Original Android Development] franciscofranco:
I didn't lower anything, but when you use Auto-Brightness, like I stated in the changelog, it will be different than before. If you don't like it:

echo 0 > /sys/module/lm3630_bl/parameters/backlight_dimmer

It just changed how the backlight scales. Check github.

Dunno, some iommu crash. I apply profiles all the time and no problems. I've seen this log before, looks like its situational.
[Nexus 5 Original Android Development] xXghostXx313:
R34 oh yeah and FYI: favorite car if you get it.
[Nexus 5 Original Android Development] blinde:
Noticed this too, Auto brightness is all screwed up.
[Nexus 5 Original Android Development] carlese:
Define "screwed up" please..
[Nexus 5 Original Android Development] KuChar_:
I'm using Lux, so should i delete this feature or not? I'm not using stock auto-brightness
[Nexus 5 Original Android Development] tcat007:
Just flashed from zip with TWRP, working smooth. Auto brightness seems very smooth transitioning from bright to dark. I don't use Auto much, but I may now.
[Nexus 5 Original Android Development] jordirpz:
[MENTION=334712]francisco[/MENTION]

Can you make volume up in bluetooth? For bluethoot speaker.

The same with speaker of phone. Thanks

vía n7II r-paco
[Nexus 5 Original Android Development] ArtieQ:
r34 is stable or should I stick with r33?
[Nexus 5 Original Android Development] aavvaallooss:
Stable since today
[Nexus 5 Original Android Development] KuChar_:
r34 is stable.

[MENTION=3292224]franciscofranco[/MENTION]

I'm using Lux autu-brightness right now, so should i delete this feature in terminal or not?
[Nexus 5 Original Android Development] drdrewdown:
that's your call. you can easily uninstall lux for a while & try the new auto brightness setup or continue using LUX.
[Nexus 5 Original Android Development] Splder:
I tried this but after I reboot it turns back on

I'm using slimkat

I'm turning it off because the screen keeps going dark bright dark bright and it's kinda annoying.

Thanks for the help
[Nexus 5 Original Android Development] eustilou:
I can also confirm that the brightness goes lower... as low as the dimmer module so I don't need to use it anymore.

Thanks
[Nexus 5 Original Android Development] Shane_IL:
Auto brightness doesn't respond to changing light conditions properly, stays dull when it's meant to get brighter or shifts from bright to dull when there is no changes.
[Nexus 5 Original Android Development] vomer:
Working nice :good: I was not expecting this :D
[Nexus 5 Original Android Development] notbrodie:
lux can benefit from form the lower brightness. just set up your brightness profiles to take advantage of the lower levels
[Nexus 5 Original Android Development] drdrewdown:
add it to a script in init.d if you want it to persist on reboot
[Nexus 5 Original Android Development] gundamboy:
Touch to wake has been disabled :(
[Nexus 5 Original Android Development] Tzfardaya:
Screwed up... Definition... Attached to the ceiling using screws...
[Nexus 5 Original Android Development] vomer:
[MENTION=3292224]franciscofranco[/MENTION] so I am really liking per-app modes design/UI. You plan on UI changes to FKU? Especially love that transparent nav bar integration :D

---------- Post added at 02:27 PM ---------- Previous post was at 02:27 PM ----------

dafaq? it was never enabled :eek:
[Nexus 5 Original Android Development] gundamboy:
I had it enabled using an app called touch control and it worked up until r33 :/
[Nexus 5 Original Android Development] elnahir:
3 hours after going from r32 to r34 I see a 40-minute Google Plus CPU wakelock which drains 25% of my battery. Anyone else experiencing similar issues? How do you deal with this?

Sent from my Nexus 5
[Nexus 5 Original Android Development] vomer:
you need to contact touch control developer I believe
[Nexus 5 Original Android Development] jolur:
about touch control please: how many drains per hour in deep sleep?
[Nexus 5 Original Android Development] fugn:
I feel the same way. Before I was always adjusting the slider but I'm going to use auto brightness for this kernel for awhile. If all goes well I don't expect a difference in battery consumption.
[Nexus 5 Original Android Development] mr-tical:
Yes it would be beautifull thing. Full integration with KitKat UI.

Wysłane z mojego Nexus 5 przy użyciu Tapatalka
[Nexus 5 Original Android Development] Chochiwpg:
[MENTION=3292224]franciscofranco[/MENTION]

I was just curious if you still run your Nexus 5 at full brightness at all times? :good:
[Nexus 5 Original Android Development] myprecious27:
Loading color profiles change nothing on r34.
[Nexus 5 Original Android Development] ironjon:
Do you turn off/on the screen?
[Nexus 5 Original Android Development] myprecious27:
I stand corrected - when you turn off/on the screen profiles load. It's just on the previous version it wasn't necessary.
[Nexus 5 Original Android Development] ironjon:
Yes you are right but in r34 you need turn on/off the said, see changelog
[Nexus 5 Original Android Development] italia0101:
This has 0 to do with the kernel, sometimes google+ gets stuck doing something, very annoying
[Nexus 5 Original Android Development] vomer:
[MENTION=3292224]franciscofranco[/MENTION] you should get on QuizUp so I can challenge you to a game! :D
[Nexus 5 Original Android Development] EnricoTFYKD:
I like the new autobrightness, because it keeps the screen dimmer, a thing that I used to do manually by adjusting the autobrightness levels. However I think that the lowest level kicks in a little bit too soon. Would it be possible to correct this behavior?
[Nexus 5 Original Android Development] KuChar_:
Can you explain me how to do that?

_____

Nexus 5 & SwiftKey_