yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] franciscofranco:
Is this understandable enough that the icon needs to be clicked?

https://www.youtube.com/watch?v=53cnsm79yro

It looks like you have some **** doing that. Did you cherry-pick my code or change something else?
[Nexus 5 Original Android Development] Technecium:
No, that's with the boot.img from test/ and default fku settings.
[Nexus 5 Original Android Development] eigokyoukan:
Ahhh I see its first run experience after updating/fresh install. Well either way I like it! The circle wipe is slick looking when it transitions from the logo to the welcome area
[Nexus 5 Original Android Development] PetritH:
When using pam with latest test whenever I wanna hold an icon using nova it gives me this.. anyone else?

edit: also using latest fku beta
[Nexus 5 Original Android Development] franciscofranco:
Its only for fresh installs :)
[Nexus 5 Original Android Development] franciscofranco:
Nova launcher bug/derp/****/whatever.
[Nexus 5 Original Android Development] PetritH:
Interesting, wasn't happening till I started using pam, also fresh rom+kernel install.

also didn't set any pam for nova either
[Nexus 5 Original Android Development] tmihai20:
Quick question: what is happening when an OTA arrives? Will it overwrite the kernel? I know that you lose root, that is not a big deal.
[Nexus 5 Original Android Development] eigokyoukan:
Oh, for what is worth I got it after updating via the Play store. [emoji16]
[Nexus 5 Original Android Development] prstorero:
Yes an ota would override the kernel.
[Nexus 5 Original Android Development] Mihnea1996:
OTA fails if any part of system is modified. If you want to clean the persistant notification with OTA, you can disable notifications from Google Framework Service. A clean factory image is required to apply an update through OTA.
[Nexus 5 Original Android Development] omvir:
Franco, remember a couple days ago I suggested something related to having custom tunables that we can set on boot? You said they'd be in next release. But I think you misunderstood. I meant custom tunables (like you have for PAM) for the "CPU manager" tab. So we can add a custom tunable and then be able to set it on boot. :p hopefully its something that is easy to merge and that you wouldn't mind adding :) it would make your app a bit "universal"
[Nexus 5 Original Android Development] tmihai20:
I only changed the kernel, everything else is stock. I applied OTA before with custom recovery, it has overwritten the custom recovery, I haven't applied OTA with a custom kernel. I guess I will see when 4.4.3 arrives. I do not want to lose anything. Thank you both for replying.
[Nexus 5 Original Android Development] justibasa:
Just a quick question? Any reason the new beta installs fine on the n5 but not on the n7 2013? Keep getting installation error 24?

Edit: actually I figured it out. Had to delete Franco kernel in the data folder on root explorer. Installed fine after that.
[Nexus 5 Original Android Development] whytechapel_x:
Anyone else gets a sod when tethering?
[Nexus 5 Original Android Development] nexusmaniac:
Well... On t50 I just got an SOD, had to go to the bootloader to boot :'( Just holding the power button down didn't do it :S

Last_Kmsg: http://pastie.org/9187718
[Nexus 5 Original Android Development] PetritH:
Ok, it was in my end, I freezed google search, looks like freezing search and GEL cause this, even if you defroze later it doesnt work, u have to reinstall the rom.. lol.
[Nexus 5 Original Android Development] aavvaallooss:
Don't freeze GEL unless you have another launcher
[Nexus 5 Original Android Development] PetritH:
I had nova, but then, whenever I tried to hold on homscreen or move any app on nova it force closed.. and started again.. so couldn't move anything..
[Nexus 5 Original Android Development] JNewms:
I'm not sure anyone understand what you mean. You can already customize tunables and set them to load at boot. Of you're referring to preset custom tunables, they're coming.
[Nexus 5 Original Android Development] cdx47:
Actually what happened was that the screen wouldn't turn on so I tried to reboot. It rebooted but went into a loop. Then I tried to reboot into recovery but it wouldn't go there , instead it just went straight to the nexus login multicolored circles. I tried this a few times, same result!
[Nexus 5 Original Android Development] :
First cycle on r49. Around 3 hours SOT with stock settings. Thanks [MENTION=3292224]franciscofranco[/MENTION]!
[Nexus 5 Original Android Development] Arstoien:
UV?
[Nexus 5 Original Android Development] franciscofranco:
But that the Kernel doesn't have any effect. You need to understand that the recovery is in a different partition and the Linux Kernel bundled with Android has absolutely no clue about recovery, its just a block and in no possible way a Kernel flash that affect that other bock partition.
[Nexus 5 Original Android Development] franciscofranco:
Sorry no idea, logs don't show anything.
[Nexus 5 Original Android Development] cdx47:
Thanks for the info but in a way isn't this missing the point? The boot cycle never got to recovery in the first place. Remember the boot loop started after the SOD. Maybe I am missing something?
[Nexus 5 Original Android Development] franciscofranco:
I answered you... maybe you misclick the buttons to entry the bootloader -> recovery... I do that sometimes. Maybe I'm missing your point, if that's the case I'm sorry, I don't know what else to say.
[Nexus 5 Original Android Development] cdx47:
Thanks for replying. I know this is very unusual LoL. But I selected Recovery 3 times and each time it would go back to Google logo then straight to the boot sequence then loop. I suppose the point is that there was an SOD then a fatal boot loop which I couldn't escape from.

My only solution was to wipe and start again.

Thanks again!
[Nexus 5 Original Android Development] aow1980:
Sounds like for some reason your recovery got deleted and needs reflashed. I had it happen once before when using fku to update. I thought it to be a fluke so didn't report it.
[Nexus 5 Original Android Development] Arstoien:
On the test #50 I can see 3rd and 4th core onlining and offlining for tenth of a second every now and then even when not doing anything on the homescreen. It's bypassing the hotplug tunables, like min_time_cpu_online. Not sure if intended to bypass it, just reporting. I like the idea behind the patch but not the way it's behaving :\ This constant onlining and offlining doesn't seem good at all.
[Nexus 5 Original Android Development] cdx47:
Yeah I saw that it had happened before while searching on Google. But thew only solution was to start again.
[Nexus 5 Original Android Development] omvir:
Let's say I'm using the code_blue kernel. It uses myfluxis MSM_hotplug. I have the paths to the MSM hotplug tunables. I'd like to add a custom tunable path(like you can for the PAM app) to one of the MSM tunables so I can change it and then make it set on boot.

In other words, have the same ability (to be able to add custom paths to tunables) as PAM app, in FKU but under the "CPU manager tab".

I know you can use scripts and all that fancy stuff to do it. But this is just a suggestion. People who have his app can then use it for other kernels which lack apps to control them. And makes it a easy alternate to using scripts(some people would argue scripts are easier but we all have different opinions)
[Nexus 5 Original Android Development] franciscofranco:
Yes. I'm already using a newer code. Still debating if push it to /tests or not.

Yes I remember that. Its planned!
[Nexus 5 Original Android Development] Arstoien:
Btw Franco, may I remind you about sending a shutdown notification when auto-rebooting, so the apps don't force close and finish their stuff properly (as I understand ACTION_DEVICE_SHUTDOWN broadcast)? You said once you were gonna do that, I'm just reminding you in case you've forgotten. :)
[Nexus 5 Original Android Development] franciscofranco:
I've researched on that and as far as I remember I didn't do it because of some restriction, I think its a system broadcast, I can't send it AFAIK.

BTW check tests folder, I ended up compiling with the new code. I did a code refactor, check git.
[Nexus 5 Original Android Development] Arstoien:
Now it's looking good. None of the previously described problems (y)
[Nexus 5 Original Android Development] Technecium:
Very nice. It is behaving much better.
[Nexus 5 Original Android Development] franciscofranco:
Did you check the code?
[Nexus 5 Original Android Development] PetritH:
HAAAALP!!! I can't drain it.
[Nexus 5 Original Android Development] Technecium:
Yes, but only quickly. The new condition definitely reduces how often the cores come online. I only hope it doesn't defeat the purpose.

This is more of a question than a suggestion but possibly food for thought.

To my understanding, the kernel/governor/mako_hotplug is not aware of why it is bringing cores online, other than it only knows that some process wants processor time. I think it's safe to say the governor is not always selecting frequencies that are in the best interest of battery life, hence per-app modes. Would it make sense to always bring the core online at say 300mhz or 600mhz, rather than what the governor might have calculated is the "best" speed?

Could, when the 100% x n condition is met, mako_hotplug, bring a core online at 300mhz and then let the governor raise the freq or offline the core based whatever brought it online?

EDIT: I've been playing with interactive target_loads and by raising the loads and reducing the freqs, I've been able to reduce the onlined core speeds. The trick is to figure out what is most often being reported to interactive and what speeds won't require too much adjustment once online.

Note: I apologize for the inconvenience of not using g+ or Hangouts.
[Nexus 5 Original Android Development] TR2N:
With r50 latest test my audio hickups on cell change are gone. Is this possible? I mean is this wanted by you, Franco?
[Nexus 5 Original Android Development] sam razzy:
Sorry for this stupid question.. I was in a vacation and now I'm back, I wanna try the latest test build. So I tried the search engine, but I couldn't find 50 test build. So please would you mind to help me..?
[Nexus 5 Original Android Development] Tzfardaya:
Linked in the op, image files...

Same as always...
[Nexus 5 Original Android Development] rani9990:
I really hope Franco doesn't mind, but I threw the latest test image into a zip for convenience. Here's the link (I'll take it down if Franco does not want it up) https://mega.co.nz/#!Y1V0RC4S!Au7DaKMR_xwLfo4fgHJPbfP7mtrecOLzGcZdWw2m2z4
[Nexus 5 Original Android Development] kecinzer:
With latest builds I'm experiencing long delay when someone call me - I mean delay between ringtone start ringing and screen turns on.

It looks like device has problem to wake up from deep sleep fast as in past.

Anyone else can confirm this?
[Nexus 5 Original Android Development] castaway1:
i can confirm slow wake up time. Try screen off and on.
[Nexus 5 Original Android Development] Arstoien:
Onlining new cores to low frequencies and then wait for the governor to ramp up, could introduce lag, no?

Just fyi, if you didn't know, you can flash .img files within franco's app (file manager).

Not here :\
[Nexus 5 Original Android Development] rani9990:
Ah. Thanks for letting me know, I was unaware.
[Nexus 5 Original Android Development] Technecium:
Absolutely, it can.

[MENTION=3292224]franciscofranco[/MENTION]

FYI I have reverted the latest commit to limit how quickly cores come online and played with target_loads. Cores come on as you originally intended but at more reasonable speeds. Need to find a balance.
[Nexus 5 Original Android Development] jordirpz:
Francisco, is the kernel that controls the Qi charging?

Enviado desde mi Nexus 7 2013 mediante Tapatalk
[Nexus 5 Original Android Development] Haidary.T:
What if I let all cores online at all time? Will it introduce lag?
[Nexus 5 Original Android Development] granets:
Nope
[Nexus 5 Original Android Development] franciscofranco:
The cores ALWAYS come online at 300MHz, which is the base frequency, then the governor plays with it. I'm not following what you're suggesting, sorry :(

Well... I was not expecting that :) keep testing and let me know about your experience.

I just tested, 0 lag :(

Let us know what you changed with target_loads and I'll test.

Yes. Why do you ask?
[Nexus 5 Original Android Development] PetritH:
With latest test im getting best battery/perfornance i ever got since I have the n5...I also tested the screen coming on after a call and it immediately comes on atm ringtone starts.
[Nexus 5 Original Android Development] jordirpz:
In r49 work well, in last r50 test, doesnt work(for me).thnks

Enviado desde mi Nexus 7 2013 mediante Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
Coincidence, 0 changes on anything remotely related to the charger.
[Nexus 5 Original Android Development] Technecium:
A misunderstanding of how the speeds are chosen, sorry about that. BBS flying monitor was only updating every second, which makes it look as though cores were brought online at 2-2.3ghz. If it refreshes at 1/10 sec you can see the scaling. My bad.
[Nexus 5 Original Android Development] big_bum:
Only on calls.
[Nexus 5 Original Android Development] franciscofranco:
Yeah eheh... best way is adding prints on the driver and cat /proc/kmsg, everything else on userland picks it up with latency.
[Nexus 5 Original Android Development] Technecium:
Can you elaborate on that or have a link so I can learn?
[Nexus 5 Original Android Development] franciscofranco:
For example:

pr_info("online cpus: %d\n", num_online_cpus());
[Nexus 5 Original Android Development] mzaur:
Hmm this is weird. I got bad battery drain overnight but my phone was in deep sleep. Anyone ever get this? I'm on r49
[Nexus 5 Original Android Development] franciscofranco:
**** signal + wifi location thingy enabled?
[Nexus 5 Original Android Development] mzaur:
Location mode is high accuracy (is that what you mean?).
[Nexus 5 Original Android Development] RobbieL811:
I think that he is talking about "scanning always available" under your WiFi settings. Turn it off.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
That and Wi-Fi always scanning...
[Nexus 5 Original Android Development] suchevent:
I've experienced this a couple times on various versions of this kernel. I've never been able to identify the root cause but, for me, it seems to happen after flashing a newer version and is easily fixed by rebooting the phone.

Powered by Android
[Nexus 5 Original Android Development] franciscofranco:
I must have magical powers on my phone, I have it since November, never wiped it, only flashed Kernels on top, and for some odd magical reason I never have any of these so called "problems".

I already explained, the user had that happen because: **** signal + wi-fi always scanning. It can also happen if Wi-Fi optimisation is off, then the Wi-Fi chip never goes into power saving mode. Its no rocket science.
[Nexus 5 Original Android Development] neriamarillo:
This happened to me last night too with the latest test. Left it at 90% woke up at 54%. Device was not woken up, Wifi was off, no scanning and no location on. No wakelocks either. Never had that happen before. I did achieve 1:15 of sot for that 10% so would love to see what happened there.
[Nexus 5 Original Android Development] franciscofranco:
Weird thing. This is mine, absolutely normal, 1h of screen on time.
[Nexus 5 Original Android Development] PetritH:
Usually a reboot solve this kind of problems, i left it on 90% last night when I woke up it was on 89% wifi on.
[Nexus 5 Original Android Development] neriamarillo:
It was the weirdest thing because it always sleeps like a baby. Maybe it was just a fluke. I'll see what happens today. [emoji14][emoji6]
[Nexus 5 Original Android Development] harshalkatakia:
Sorry for a bit off topic question, but couldn't think any where else to ask where I'd get a proper reply.

My N5 charger stopped working and I'm supposed to buy a new one. It's either a 750mA/ 1A or a 2.1A Sony Fast Charger. I've read that a fast charger, as the name suggests charges fast, but the battery depletes faster than, when charged with a 1A charger as a 1A charger relaxes the battery while charging. Which charger should I get? Price difference isn't much and there's no 1.2A charger available.

Thanks
[Nexus 5 Original Android Development] slider112:
I've been experiencing this mystery battery drain recently as well, and as of yet have found nothing concrete that could be causing it. It started out of nowhere about 2 weeks ago, and doesn't happen all the time... nothing done that I can attribute to triggering anything. Running stock, no mods whatsoever except for franco kernel. Phone deep sleeps just fine, no wakelocks, nothing running in the background, no rogue apps... location set to battery saving, location reporting off, Wifi "scanning always available" is off, nothing showing up in BBS or GSAM. Just the downward drain, mainly overnight. No clue. It comes and goes.

For a while I thought it may be tied to all the Google Play Service updates that have been pushed out recently, or maybe updates to Google Now or Search, or one of the other multitude of updates to Google apps... and that's still my best guess. The only thing I can think is that some sort of behind the scenes Google analytic reporting is going on that just simply doesn't show up. Frustrating, but I don't believe it's kernel related at all. I've followed this thread religiously since November, and even though I rarely post and am admittedly NOT a crack kernel flasher/updater, I'm pretty well up to speed on things. I've been on the same release for weeks, er, months now without a single issue; no SOD's or audio issues ever... One could say I am REALLY a "don't fix it if it ain't broke" kind of guy :D

Anyway, just wanted to relay to OP that they're not alone on this issue.
[Nexus 5 Original Android Development] marf28101995:
The phone will only take what it needs... You can use a 2.1A 5V without any problem..

2.1 is the maximum that the charger can offer.. It won't be always that.. The max that can happen it's to heat a little bit more

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] Tzfardaya:
Fast/slow charging is based upon the "C" raring of the battery, or what draw would drain the battery in one hour... (the mAh rating of the battery) out n5 has a 2300mAh battery, so a 1C draw is 2.3A.... So a 1C charger is 2.3A as well....

But, a slower charger is easier on the battery, as it doesn't stress/heat the battery as much... and gives a more complete saturation charge

there was a pretty involved conversation about battery charging and the like at this thread
[Nexus 5 Original Android Development] marf28101995:
Check the new Google travel charge.. I think the output is 1.8A

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Nexus 5 Original Android Development] mzaur:
I just disabled wifi scanning, wifi completely turned off, location turned off, and I'm still having issue. I didn't reboot phone yet just to see if I can narrow down a cause, but so far it goes perfectly into deep sleep but still drains. I'm on Cataclysm ROM btw if that makes any difference.
[Nexus 5 Original Android Development] Tzfardaya:
which is still below the 1C rating of the nexus 5
[Nexus 5 Original Android Development] harshalkatakia:
Thanks a lot for the help guys. Appreciate it!

---------- Post added at 11:31 PM ---------- Previous post was at 11:30 PM ----------

Looked at it, but it's turning out to be around twice the price of the Sony 2.1A fast charger.
[Nexus 5 Original Android Development] suchevent:
Don't get me wrong, I wasn't implying that the kernel was the culprit. I was simply sharing my experience. I'm sure it's my setup. Regardless, for me, it's a simple fix (i.e. reboot).

Powered by Android
[Nexus 5 Original Android Development] adame09:
Is it the charger that stopped working or the cable?
[Nexus 5 Original Android Development] harshalkatakia:
Charger stopped. Checked the cord, works fine with other chargers and when connected to laptop.
[Nexus 5 Original Android Development] franciscofranco:
I know you weren't complaining, I merely explained my point of view ;)
[Nexus 5 Original Android Development] franciscofranco:
Maybe low signal? That's enough to derp it.
[Nexus 5 Original Android Development] Nocturnal86:
This happened to me to I was at 93% or so when I went to bed and woke up to 64% with no wake locks. WIFI was the second highest drainer to screen. I dont have wifi scanning on or anything on. It has happened before and it stopped but idk why or if it was related to Xposed or GB or FK for some odd reason.

Oh and my signal was solid green the entire time except for small slivers of yellow here and there but id say 92% green.
[Nexus 5 Original Android Development] franciscofranco:
Wi-Fi or any other network related changes are non-existent so something weird is going on there. I don't use any Xposed or gravitybox, pretty useless stuff for me.
[Nexus 5 Original Android Development] Nocturnal86:
Yea thats why im thinking it may be xposed or GB since they updated recently but then again others are reporting they are stock with no mods and still have the issue so im not to sure whats going on either. Maybe some google back end stuff like another user posted? Would you know if that would show up in the wakelocks at all if it was the case?
[Nexus 5 Original Android Development] Piereligio:
1005 downloads. Wow, that's awesome! I think I'll try to contact some android Italian website to make compare nexus 5 display with my profile on vs LG G2 display or something else. :)
[Nexus 5 Original Android Development] FAdrums:
V7? Anyway congrats! I'm using V7 ever since! Can't really live without it!

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] Piereligio:
Yes, the v7! :)
[Nexus 5 Original Android Development] FAdrums:
My Nexus loves your v7! :P

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] Red5:
Im using V7 too. Looks really good IMO. Thank you for sharing it with us.
[Nexus 5 Original Android Development] TrenchKato:
And that doesn't even include the previous versions built into fku. I'm using v7 also.
[Nexus 5 Original Android Development] franciscofranco:
Can you elaborate?

Its not a bug. Thats on purpose because I don't want the tab headers to be visible when the drawer is open.
[Nexus 5 Original Android Development] The Gingerbread Man:
I think you dont really need to be sorry as such but the same goes for all here. Think about what you want to say, how you want to say it and place your self in the persons position who is the end recepitant ie Franco unless your quoting another and then still you have to have respect. My father always told me talk to others how you want to be treated. Franco is here sharing his kernel for free with the best set up without configuration (unlike others I have read about recently). I'm not trying to single you out RusherDude or anyone else for that matter I'm just wishing more posts had some more respect and Franco is here providing a service and product for free to enhance our devices. There's a reason his thanks and reputation are stupidly high ?
[Nexus 5 Original Android Development] Kristi-Tech:
Colors look so much better than stock kernel :)
[Nexus 5 Original Android Development] kepapas:
Idk if its a kernel problem my phone isn't charging it stayed at 45% for 1hour I rebooted and still was at 45% .Any one experience this issue?
[Nexus 5 Original Android Development] franciscofranco:
No one is reporting that, so no, no one does. In fact there are no changes to the charger subsystem, its 100% stock.
[Nexus 5 Original Android Development] jphilippon:
Not sure if it's related at all but on r13 I had more than 50% uptime was a wakelock by Google search. Never had that on my top battery users so I figured I'd report it.

sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Quick question: does Google Search looks like Kernel to you? :cowboy: