yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Bobtehblob:
Franco little bug in FKU. Set on boot dialogue keeps popping up every single time I enter the CPU Manager tab for the first time.
[Nexus 5 Original Android Development] Arstoien:
Or rather: any time you click on CPU manager from the drawer.

Btw I saw a few people talking about changed default tunables in the gpu? I've flashed several times, with flashing Stock inbetween, and my gpu tunables are the same as always: 450/50/25 (max clock/up/down). No init.d scripts, no apps changing values on boot.
[Nexus 5 Original Android Development] vickyjusme:
Hi I am on r51 and i get reboots while opening camera. Undervolt by 50mv. Logcat attached.
[Nexus 5 Original Android Development] WettbackMartyr:
Have you tried a lesser undervolt? Or how bout no undervolt at all?
[Nexus 5 Original Android Development] shawnaye:
Cool. I thought they would be like a clash or something.
[Nexus 5 Original Android Development] Red5:
Coming to California, eh? Hmm...
[Nexus 5 Original Android Development] vickyjusme:
yes done that. Backed up ROM clean flashed ROM and kernel and tried opening camera still the same issue. Torch function causes reboot too. Now i'm on Elemental kernel now :|
[Nexus 5 Original Android Development] tlrsax54:
Happens to me every time I'm scrolled to the top of the CPU manager page as well.
[Nexus 5 Original Android Development] WettbackMartyr:
Gotta do what ya gotta do. Can't seem to replicate the problem on stock ROM though and r51 going with -50 undervolt. Hmmm.
[Nexus 5 Original Android Development] leAndroid91:
What is the last stable version w/o SODs? 48?

tapatalked from hammerhead
[Nexus 5 Original Android Development] EPayne123:
It isn't for everyone. One may have it and one may not. . . seems too scattered as of right now.
[Nexus 5 Original Android Development] Ronaldo Forenucci:
Long, long, long time FK user, paid app, etc...

Are you guys seeing acceptable battery drain? Once FK hit the mid r40's, I was having horrible battery life. GSAM was showing up to 3-4% per hour idle.

Now, I know what your going to say, BBS, look for apps, etc... I did, and there were none. I recently updated my ROM (RastaKat) and decided to leave the stock kernel. No changes in apps or settings, and I'm getting 0.5% - 0.7%, maybe 0.9% per hour idle.

Is it possible something was borked in the old ROM (I didn't notice any irregularity) and the new flash fixed it? Guess I should try the latest r50 series and see... just wanted to see if anyone else has seen any high drain that went away with stock kernel.

Thx!
[Nexus 5 Original Android Development] leAndroid91:
Not really, no.

I've about 5h SOT on 12h runtime

The only issue i'm facing is SOD -.-

tapatalked from hammerhead
[Nexus 5 Original Android Development] keepermike:
I was having the same problem with the stock rom and FK and ended up doing a factory reset and with everything turned on I'm seeing normal 0.5% to 0.9% an hour with everything turned on. I just assumed a random app or system process was causing a bunch of wakelocks.

I also tried the BBS and all it said was the usual location services, nothing jumped out at me. Figured a clean install and put my apps back one at a time
[Nexus 5 Original Android Development] Mr.Wolf:
I have 2 USB/AC chargers (Puro 2,4A and Ksix 2,1A) and a 2A car lighter USB charger.

All of them do +-1,2A in CurrentWidget (with nexus 5 stock microUSB cable, battery 51% full, with very low screen brightness).

If you set screen brightness to 100%, charging current lowers to 1A (-200mA).

I tried a direct USB<->MicroUSB adapter without cable and it does 1.8A :)

So we can do 1.8A with a better than stock cable.

I also tried a Ipad compatible USB charger and now it charges at 1,2A, before R49 it only charged at 500mA :good:
[Nexus 5 Original Android Development] Delacor:
Thank you man!

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
About to push the fix for that on the beta channel.

EDIT: pushed.

Yes I'll be in S. Francisco for 2 months starting 2 of June.

Seems like an app that was frakking you.
[Nexus 5 Original Android Development] Ryrynz:
Running r51 and I have about 5% loss over a 12 hour idle period. Running stock.
[Nexus 5 Original Android Development] franciscofranco:
Been a while since I've seen this so quiet :)
[Nexus 5 Original Android Development] occtec:
[MENTION=3292224]franciscofranco[/MENTION] on latest test boot I am experiencing my very first SOD ever, when making a call on speaker. Once screen times out, the only way i wake it is by pressing the power button??

EDIT: STOCK ROM, XPOSED MODULES, NEVER AN ISSUE B4 ;)
[Nexus 5 Original Android Development] franciscofranco:
Pressing the power button its usually how you turn your screen on...
[Nexus 5 Original Android Development] occtec:
LOL, really I thought the sensor should kick in and wake the screen when you're looking at it??
[Nexus 5 Original Android Development] Ben36:
Not on speaker
[Nexus 5 Original Android Development] occtec:
Haha, my bad [emoji12]

Never really took much notice. [MENTION=3292224]franciscofranco[/MENTION] Sorry Boss [emoji109]
[Nexus 5 Original Android Development] franciscofranco:
I also thought my coffee cup would fill up when I look at it.

Never happens, but I already reported SoD to the developer :)

Just joking with you :angel:
[Nexus 5 Original Android Development] donwhall70:
A couple days ago I went totally stock with no mods or root while using this kernel.. All is still well in the world :)
[Nexus 5 Original Android Development] icethegreat:
Just wanted to complain real quick. Tired of this bug that I've noticed since r48. This POS kernel hasn't given me one issue. So pissed. Wtf do I do now?
[Nexus 5 Original Android Development] granets:
YEAH, I have the same complaint. Stupid kernel has no bugs. I even don't get any SOD's and audio issues anymore... So sad...
[Nexus 5 Original Android Development] philippsp:
sorry for this question but is this kernel actually working on the latest cm11?
[Nexus 5 Original Android Development] Tzfardaya:
Nandroid backup, install, test, let us know....
[Nexus 5 Original Android Development] PetritH:
AFAIK, this only work on aosp roms. Not on CAF based roms
[Nexus 5 Original Android Development] granets:
It's written in the OP - does not work with CM11 and roms that are based on CAF. You are free to try, but I bet all you'll get is a boot loop.
[Nexus 5 Original Android Development] Tzfardaya:
Look, if they're not going to read the op or search the thread, they deserve to get bootlooped...
[Nexus 5 Original Android Development] granets:
Yeah but if they don't know how to deal with that, it's a terrible place to be :) so I'd rather they don't get there
[Nexus 5 Original Android Development] Tzfardaya:
If they can't figure out how to deal with bootloops they shouldn't be flashing roms and kernels.....
[Nexus 5 Original Android Development] granets:
That's just one way of becoming a flashaholic like us :D
[Nexus 5 Original Android Development] vickyjusme:
Help please

I flashed stock kernel and flashed Franco r 51 again still the issue exists. i captured logcat someone please helpppppp!!! [MENTION=3292224]franciscofranco[/MENTION] please see the logcat if u get time :(
[Nexus 5 Original Android Development] Tzfardaya:
If you want us to check the log, please don't post it as a rar file... Pastie/pastebin and the like please... Not all of us have/use/like rar...
[Nexus 5 Original Android Development] granets:
Did you try setting kernel settings to stock, then maybe go into apps, find the Gallery app, clear it's data, find camera next, clear data again, reboot and maybe try camera. That sometimes helps me when I get camera related problems on my other phones.
[Nexus 5 Original Android Development] Tzfardaya:
Clean flash your Rom, see if the problem persists, if yes, likely hardware issue, if now, slowly reinstall all your apps, mods, tunes, and tweaks checking where the problem starts again...

Oh, and logcat is the wrong log for this...
[Nexus 5 Original Android Development] vickyjusme:
Sorry newbie for posting logs.

pastebin.com/embed_js.php?i=9Mg6gWLi

Yes just flashed kernel and tried and it causes reboot.

No problem with other kernels. Only in Franco's kernel this happens :(
[Nexus 5 Original Android Development] Tzfardaya:
Doesn't mean it's not something else in your setup that triggering it on Franco... Clean flash your rom, install Franco, see if it still reboots...

Since you seem to be the only person this is affecting, that implies it's something unique to your setup...

Clean flash back to stock, install francos kernel, test.
[Nexus 5 Original Android Development] vickyjusme:
Yes going back to stock tomorrow. I got my stock backup from when I first rooted the phone. I can factory reset and restore that and install Franco and test right?
[Nexus 5 Original Android Development] Tzfardaya:
I would just download the factory image file from Google and flash that way... That way it's a new clean file...
[Nexus 5 Original Android Development] vickyjusme:
Yes. Thanks for the replies :D Hope that fixes the issue.
[Nexus 5 Original Android Development] incognico:
I'm running the /tests/boot.img from 2014-05-27 atm and SOD is not an issue with this kernel - working good. Keep up! :)
[Nexus 5 Original Android Development] -DroidIsDNA-:
Where are the tests? Sorry, I'm new

Edit: Never mind, found in parent directory
[Nexus 5 Original Android Development] wildestpixel:
pls forgive my ignorance - what are the valid integers (numbers) to input for headphone boost ?
[Nexus 5 Original Android Development] Tzfardaya:
Any that don't cause your phone to self destruct....

But, I'm pretty sure it's only irrational numbers that cause that....
[Nexus 5 Original Android Development] franciscofranco:
-20 to 20.
[Nexus 5 Original Android Development] wildestpixel:
Thanks Franco - Greater numbers meaning greater boost ?

Not like how decibels in negative increase amplitude ?
[Nexus 5 Original Android Development] franciscofranco:
20 is more boost, -20 is less.
[Nexus 5 Original Android Development] galakanokis:
Finally back on a Franco kernel after a year or two away. I go back to the old Samsung nexus and loved it back then.Glad to see The Gingerbread Man is still around and helping out, appreciate your thread man, been reading all day playing with tuneables. Osmosis still kicking? You two contributed a lot than and more now it seems.

Thanks Francisco, r51 running great so far. Still lots of reading and playing to do.
[Nexus 5 Original Android Development] Martin-Doc:
Instructions were not clear, my **** got stuck in the headphone jack.
[Nexus 5 Original Android Development] wildestpixel:
Charming.

I've just moved back to Nexus 5 from Moto G which whilst amazing in its own right was a bit limited in some respects.

Now the only thing I do actually miss from that little diamond is Motorola Assist.

---------- Post added at 09:25 PM ---------- Previous post was at 09:22 PM ----------

Are you recalling the delights of Oxygen ROM and Franco Kernel (R16 I think) ?

---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------

Are you recalling the delights of Oxygen ROM and Franco Kernel (R16 I think) ?

---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------

Are you recalling the delights of Oxygen ROM and Franco Kernel (R16 I think) ?

---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------

Are you recalling the delights of Oxygen ROM and Franco Kernel (R16 I think) ?
[Nexus 5 Original Android Development] incognico:
Welp, posted too early. It lasted really long withouth SOD but not I get them.

I guess it happens more likely when the device goes to sleep by itself, not when the user puts the device to sleep.
[Nexus 5 Original Android Development] wildestpixel:
Are you recalling the delights of Oxygen ROM and Franco Kernel (R16 I think) ?
[Nexus 5 Original Android Development] tlrsax54:
I noticed when playing around with the volume boosts, I raised the speaker gain +7 but now when I talk to people on speaker phone they have a hard time hearing me. Do I need to raise the mic gain to fix this? I'm kind of new to tweaking these settings :(
[Nexus 5 Original Android Development] galakanokis:
I know nothing of the Oxygen ROM, usually ran CM or Slim on the old Nexus. I run stock rooted now.
[Nexus 5 Original Android Development] THE_KINGDOM:
I don't know if it's the latest r51 51 but I have some serious battery drain even while charging my phone I'm losing battery percentage

And this is with fast charge on.

My brother has the same phone same ROM no Franco kernel and has no battery issues at all.

His phone has persistently charged faster than mine even though he doesn't have fast charge

Just while writing this message and charging in my car down from 6% to 0%.

and this is while saying charging AC. Which since the last update seems to say charging AC no matter what it's connected to and no matter if it's on fast charge or not
[Nexus 5 Original Android Development] Rxpert:
Did you tell it to include the governor in the build settings? Been a while since I've built, so I remember the exact menu name sorry

Your actual conflict appears to be the bit here:

: error: conflicting types for ‘get_cpu_idle_time’

static inline cputime64_t get_cpu_idle_time(unsigned int cpu, cputime64_t *wall)

^

In file included from drivers/cpufreq/cpufreq_intellidemand.c:18:0:

include/linux/cpufreq.h:320:5: note: previous declaration of ‘get_cpu_idle_time’ was here

u64 get_cpu_idle_time(unsigned int cpu, u64 *wall, int io_busy);
[Nexus 5 Original Android Development] RobbieL811:
What do you mean tell it to include the governor? I added it to franco_defconfig and configured defconfig to add it in the build. Then that terminal is the output from when I tried to compile it with the gov added.
[Nexus 5 Original Android Development] EvanA:
Do you have your current source state on github so I can take a look?
[Nexus 5 Original Android Development] Tzfardaya:
Sounds like a possible Rom derp, reflash Rom (clean) and kernel and see if still persists... (written while charging in truck, 2% gain)
[Nexus 5 Original Android Development] RobbieL811:
I have it locally. Give me a sec and I'll push it. https://github.com/RobbieL811/My_FK/commits/nightlies

Edit - It's there now.
[Nexus 5 Original Android Development] THE_KINGDOM:
rom derp?

Right after completing my message my phone actually died while charging and the LED started flashing red then had to leave the phone off while charging just to be able to start it back up again
[Nexus 5 Original Android Development] nexusmaniac:
Really loving the r52 test, it's smooth and the battery is great! High accuracy GPS and Google now activated with over 2.5 hours screen on easily! :)
[Nexus 5 Original Android Development] Tzfardaya:
Try a clean flash of your Rom... Sounds like something got messed up that's draining your battery...
[Nexus 5 Original Android Development] franciscofranco:
You need to use the generic get_cpu_idle_time that I added to cpufreq.c/cpufreq.h instead of the one defined in the governor.

You have apps derping you.
[Nexus 5 Original Android Development] EvanA:
Yep just as I suspected. The header file defines the function as "u64 get_cpu_idle_time(unsigned int cpu, u64 *wall, int io_busy);" but the implementation in the governor file is "static inline cputime64_t get_cpu_idle_time(unsigned int cpu, cputime64_t *wall)." My guess is you're missing some needed changes to the header file.
[Nexus 5 Original Android Development] RobbieL811:
Not sure how to do this.
[Nexus 5 Original Android Development] RobbieL811:
Yeah. I saw that. I tried some editing, but when it comes to code, idk what the hell I'm doing. I gave up. I screwed my source all up so I just deleted my repo and redid it.
[Nexus 5 Original Android Development] The Gingerbread Man:
Welcome back! Yes, I'm still here but not as active as I once was but Tzfardaya has been doing great trouble shooting problems for people recently. Osmosis doesn't really post here, maybe be lurks this thread i don't know. I have a lot of respect for him, a valuable member of the FKU gang! Enjoy your nexus 5 and tweaking the hell out of it, its a great device :D my tunables might just help with your battery life depending on your usage pattern and be sure to check out the per app modes
[Nexus 5 Original Android Development] granets:
Lies, all Tzfardaya does is troll people :D

Jokes aside, he does help alot. Such a patient person :)
[Nexus 5 Original Android Development] Momotani-Hitoshi:
Yea R32 was the last version to work with encryption. I've been posting kernel logs since R34-51. Franco said he has no clue what is wrong, but it seems like you might be able to give him clues! Does he know about this?
[Nexus 5 Original Android Development] galakanokis:
Thanks dude, nice to be back on a Nexus. I like the Samsung hardware but running a Nexus just feels better, really like stock Android with a few tweaks here and there.

I am currently using your settings and I am 12hrs up time with 3hrs screen and just passed the 45% mark. Great battery so far and really haven't noticed any performance hits, running great here.
[Nexus 5 Original Android Development] Technecium:
It's not that easy. I don't know the specific reasons why he chose to switch. I suspect it was either performance or security. Both are good reasons so that's the first thing. It's his kernel and has to make that decision. In turn, users have to respect that and choose to use or not use the kernel.

Second, switching back is almost guaranteed to be difficult. There have been thousands of commits since r32. Any one or combination of commits could and most likely will complicate switching back.

So, it comes down to someone who believes that functioning encryption outweighs performance and/or security and that person has the time/energy to get it working again.

I don't know who it was that mentioned that thousands of people have complained. It only takes one with basic understanding of kernels and some initiative to fork the kernel and make something that works the way you want.
[Nexus 5 Original Android Development] xdaywalkerx:
I can't play different video types on webpages. The video starts with crackling sound and right after a few seconds the browser crashes (Firefox, opera, chrome). I'm on stock KitKat.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Enddo:
do you have any example links that this is happening on? so we can test them on our devices and see if it's a user issue or a kernel issue
[Nexus 5 Original Android Development] xdaywalkerx:
http://www.4players.de/4players.php/dispbericht/Allgemein/Special/31372/80500/0/Watch_Dogs.html

Or

http://www.pcgames.de/Watch-Dogs-PC...ogs-PC-versus-PS4-im-Grafikvergleich-1122570/

(Right after the commercial)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Enddo:
I can confirm that there is an issue with the video. Have you tested this with the stock kernel to see if it's directly related to the kernel? I have a suspision that it's an issue with the video or the website.

The first link plays the video for 2 or 3 seconds. There is some video effects to act like there is hacking going on(since that is what the game is about). Then an error pops up on the video and it says there was an issue loading it.

The second link plays the video again for 2 or 3 seconds and then just goes black. I tested these links on both Chrome and AOSP browser and neither caused the browser to crash, just that there was an issue loading the video. Both of them play fine on the desktop browser though.

I am very interested in knowing if these videos play with the stock kernel in place
[Nexus 5 Original Android Development] xdaywalkerx:
I've tried the videos on a iPhone 5, an BB Z 10 an HTC One mini and a LG G2. No issues so far on this devices. I don't want to go back to stock kernel so I haven't tested this yet.

And it's not dedicated to this webpages - found several sites with this issue (just on my nexus) - for the 2 named above the issue is present within the last 10+ revisions. i thought it will be fixed within future updates for sure, no need to report that - but now it's been a while :D
[Nexus 5 Original Android Development] myfluxi:
This is a framework issue in libstagefright.
[Nexus 5 Original Android Development] fix21:
Great Kernel ;)
[Nexus 5 Original Android Development] FAdrums:
Hey guys,

I have this impression that from r30 onwards the battery life is getting worst. Before with stock setting I would get 5/6 and even 7h sot. Nowadays I can't get more than 3/3,5h. Anyone else has experienced this?

PS. Not bashing the kernel as I'm a day one user one my N5 and bug Franco supporter. My post is merely feedback and feedback search.

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] blackt5:
Google has made some major changes since then. Who knows if its something they did like changes to Google play services. I've seen a hit in battery too.
[Nexus 5 Original Android Development] FAdrums:
Yeah, definately something happened!

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] RobbieL811:
I have to disagree with you on that one. I think that it was r33, I had like 9 hrs screen on time with over 24 he's total usage. The latest is working pretty good for me too. I use my own version of r52 test with some minor tweaks & it is running great.

These are from r33.

Sent from my Nexus 5
[Nexus 5 Original Android Development] FAdrums:
Well when I said r30 I wasn't being version specific but from the 30's onwards! Sorry If didn't explain myself right!

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] RobbieL811:
I know what you meant. Just that general time but it still hasn't been horrible for me lately.

I sent you a PM.

Sent from my Nexus 5
[Nexus 5 Original Android Development] theowner997:
9% idle ????

Hmm someone just left the phone with screen on without even touching it xD
[Nexus 5 Original Android Development] RobbieL811:
I turned the screen off 2 nights in that screen shot. I just turned off sync, location, WiFi, & LTE. Look at the screen on of the battery graph. I didn't just leave the screen on. When the screen was on I was using it.

Sent from my Nexus 5
[Nexus 5 Original Android Development] Tzfardaya:
Or read a book...
[Nexus 5 Original Android Development] iboj007:
Personally, I got the Kernel at about R46 and i've never been able to get even 4 hrs even with multiple tweaks, battery monitors, wakelock detectors etc. I consider myself a "normal"user.
[Nexus 5 Original Android Development] FAdrums:
My avarage before was 5/6h now 3/3,5h same type of usage! I tried stock and loads of ROMs and can't get more than that!

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] WettbackMartyr:
I firmly believe it's a Google Play services issue. Whether location is on or off I am seeing a play service wakelock. It is what it is. Waiting for Google to fix.
[Nexus 5 Original Android Development] FAdrums:
I'm not doubting that. I just wanted to share my opinion and my experience and yes, it my be Google's fault but it was a coincidence changing around the 30's era!

PS. Oh god I wrote avarage instead of average! ?

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] iboj007:
Is this the same issue that they have acknowledged and say that they have an internal fix for?
[Nexus 5 Original Android Development] WettbackMartyr:
Possibly. I'm not 100% sure on that
[Nexus 5 Original Android Development] FAdrums:
It's sharing experiences about each one's battery life nothing else!

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] laureanop:
Francisco your Peek app is taking the world by storm !!! It was featured in the Phone Arena portal (in my opinion the best website for phone reviews and news)http://www.phonearena.com/news/Peek...stom-ROMs-to-any-Android-KitKat-phone_id56635