yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Tzfardaya:
If you're using Vomer's init.d system, yes, delete (or remove the execute permission) and reboot to reset to stock values..

Based on the tests I ran a while ago, we decided that yes, DSP tunneling is working... (I got the same performance/behavior with Franco as stock kernel wrt to screen off music...)
[Nexus 5 Original Android Development] Devhux:
It actually isn't as far-fetched as you might think. A higher clock speed can help the device finish tasks faster and thus, allow the SoC to go back into Deep Sleep faster.

Your mileage may vary of course, but it just goes to show that settings that work well for someone's usage scenario may not work as well for others.

Sent using radio waves of some sort
[Nexus 5 Original Android Development] cdx47:
I have been thinking about this issue for quite a while now. I recently used vomers settings which reduces the clock top frequency and uses the lowest and intermediary steps a lot more, but I don't think I got any benefit personally. I think my best SOTs etc come when reducing t he cpu freq but to not less than 1700. Anyway now I am trying default settings with full cpu and gpu to see what happens over the next few days.
[Nexus 5 Original Android Development] vomer:
yup :cool:
[Nexus 5 Original Android Development] jmudrick:
I haven't rigorously tested the N5 but I found that to be true with underclocking the N4, I saw no discernable benefit in general usage (no heavy gaming) and got 6hrs typical SOT on average with Franco stock settings. My untested impression with the N5 is the same.
[Nexus 5 Original Android Development] blueren:
...anyone?

Sent from my Nexus 5

Just double confirmed in this. It's the thermal throttle while in pam that derps up my max freq settings :(
[Nexus 5 Original Android Development] lkthomas:
It's default setting right after the first installation of FKU + franco kernel.

so I should push it up a bit, like other people suggested: 1.5GHz
[Nexus 5 Original Android Development] zephiK:
1.2 is not the default setting. The max cpu clock of this phone is the default setting. Make sure you're on 11.0 and clear app cache and reboot. Something is messed up with your settings that's causing it to lag.
[Nexus 5 Original Android Development] lkthomas:
Thanks. I will try that again.
[Nexus 5 Original Android Development] Testraindrop:
Hey Franco, thanks for exposing all the gain options.

I set speaker gain to 11 and now even the speaker doesn't sound crappy anymore (with some DSP settings) :)

btw. I haven't seen it reverting back to normal yet as someone else reported.

It seems Google is really trying to make the Nexus devices real developer devices, you need to fix Colors, Thermal throttling, speaker, hotplug etc. before its an absolutely fabulous device :D

I just feel sorry for the guys who don't know XDA...
[Nexus 5 Original Android Development] bobloadmire:
Hi Franco, I was wondering if it would be hard to incorporate "Load stock table" feature for CPU voltages. I forget what my stock values are. I should write them down haha.
[Nexus 5 Original Android Development] franciscofranco:
No its not the default. The default is stock 2,26GHz. I flash a gazillion Kernels a day, I know what the defaults are. You probably have something else conflicting.
[Nexus 5 Original Android Development] franciscofranco:
Untick set on boot and reboot.
[Nexus 5 Original Android Development] magnamentis:
combination of reasons

yes it's annoying to read about the app all the time but the way how the only N5 compatible version is made available

is definitely not very easy.

a) i will not join G+ to get an app which i paid for to work on my device, i'm waiting for the release.

b) yes i would like the app now but neither google nor anyone else will force me to join G+

there are better ways to make a beta version available by simply let people choose, so there must

be a reason behind this procedure which is always suspiceous. why do i have to join in social

media to get access to an app ?

i was mentioning this before but never got an answer, which includes no good argument as for the motives.

it's not even possible to rate an app without joining G+ which was the original reason when i opted out of G+

back then i was one of the first to join. but enough OT, just wanted to say that this annoyance is partly home made.
[Nexus 5 Original Android Development] bobloadmire:
I am honestly not seeing that in the CPU or Kernal page. Or app settings page.
[Nexus 5 Original Android Development] Testraindrop:
That are Googles rules not Francos.

If he would release a beta app not on Google Play, it would be incompatible to the Play version. Nova Launcher had the same problem, now they are also running beta through Google Play.

Complain at Google.

I also don't like how you need G+, then need to join a community, and after that you need to Join Beta tests.

I hope Google finds a faster and easier way in the future.
[Nexus 5 Original Android Development] eep2378:
Then wait.

I'm not sure what your overall point is, but it sounds like you have an issue with G+. Franco has already mentioned the reason/process by which he has to abide in order to make certain things available. It may not be the most straightforward solution but its one that is mostly out of his hands.
[Nexus 5 Original Android Development] Moose0704:
A gain of 6 on speakers seems to be perfect. Sounds great
[Nexus 5 Original Android Development] franciscofranco:
Its not my fault that Google enforces users to join the G+ community that is bound to the beta program. Without bounding a community to the beta channel there couldn't exist betas. That's the system Google built, its not my fault and I don't like it more than you do.

If I don't push betas I don't get bug reports prior to production release, thus the likely hood of having a buggy production release is bigger. Nobody forces anyone to join the beta program - the update is finished when its finished and its released when I decide to, if its tomorrow or in 5 months.

Untick whatever set on boot on voltages that you set and reboot.
[Nexus 5 Original Android Development] cobyman7035:
am I the only one that has trouble with fast USB charging? I cannot get it to work

Via my N€×us 5 on XDA premium
[Nexus 5 Original Android Development] franciscofranco:
If you've searched you've seen that I already stated that I have not yet thoroughly tested that feature and its possible, due to the subsystem and usb stack changes for this device, that the code I merged is broken. Since I don't care much about USB Fast charge I haven't yet decided to take a look - I will do so when my other priorities are finished.
[Nexus 5 Original Android Development] MikeLibbey:
I completely agree but it would also help franco more if he had a bit of notes in the OP, some potential users may be put off by not knowing anything that's in his kernel and might not want to search, I think it would benefit franco greatly if he put something in the OP.. Me personally I'll search for what I need and still use his kernel all day every day but some might not be willing to search which results in less people using his kernel
[Nexus 5 Original Android Development] franciscofranco:
Once upon a time I wasted hours on posting information on the OP. Once upon a time self-entitled users didn't give a damn, so they posted on the last page questions that were either in the OP or in the post above theirs. Once upon a time I decided screw it, and stopped giving a damn to the OP. Once upon today I'm a happy guy by not cramming 1000 text lines in the OP that nobody (almost) cares :) what I will do sometime is copy paste my small famous FAQ to the OP.
[Nexus 5 Original Android Development] DaX05:
Those were the old times.
[Nexus 5 Original Android Development] JNewms:
[MENTION=3292224]franciscofranco[/MENTION] OK, feedback time! I jumped onto r13 last night towards the end of my work shift. I was using my phone to play music through the speakers there, so I tweaked the volumes, which seemed to work like a charm. On performance, I don't really feel the need to day it, but I will. Performance has been, and still is beast.

After getting home from work I spent a couple hours browsing Google+, Tapatalk, played asphalt (thanks for getting me hooked on that Franco). I then feel asleep without putting my phone on the charger. When I woke up this morning I had only lost 3% battery... That's amazing.

Great work Franco, I'm not sure where else you could possibly improve your hotplug, as it's already just awesome, but I'm sure you'll throw some more voodoo in somewhere. ?
[Nexus 5 Original Android Development] Langduscher:
How high a gain would be too high? Could you (or anyone) point me to infos to learn from or share it here? Thx
[Nexus 5 Original Android Development] gravityy:
there is nothing wrong in ur pam mode in my opinion :p
[Nexus 5 Original Android Development] squeeish:
I'm back to r37 again.Somehow I get force closes for Google related apps when I'm flashed the r4* series, and my phone hangs for a few seconds occasionally. Just sayin'.
[Nexus 5 Original Android Development] blueren:
This is really troublesome. What's more is that no one else is having this issue.

Pam off - 2256

App -> pam on - 1.4ghz

temp throttles -> 60° -> 1.2ghz

app close -> pam off -> 1.2 ghz.

Temp < 60° --> max freq becomes 1.4ghz. Stays stuck there.

Reboot -> max freq = 1.2ghz!

Stays stuck there. Dafaq?

Sent from my Nexus 5
[Nexus 5 Original Android Development] granets:
Disable PAM, use all stock settings = enjoy r47 the way it was ment to be used.
[Nexus 5 Original Android Development] Laggalot:
how to use the exact stock settings..... not even undervolting?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] jmudrick:
I've been Ok on r47 so far but I did experience the same Ghost in the Machine changing my frequency settings on a prior r4_ series kernel. Not just you.
[Nexus 5 Original Android Development] granets:
remove the set on boot settings that you have, reboot and voila
[Nexus 5 Original Android Development] blueren:
True. But reading a book on the phone doesn't really require so much power. Don't you think? That's where the pam's true potential comes into play. Too bad it derps on my phone :(

Sent from my Nexus 5
[Nexus 5 Original Android Development] granets:
Well I think the phone knows that and lowers it's frequency when it's not needed ;) I don't see why people use PAM when the processor's management systems take care of load balancing and ramping up. I think the people at Qualcom/Google far better know what should be done when you read a book, than you, by using PAM :) Just let the phone decide, I guarantee you'll see better results with all stock settings.
[Nexus 5 Original Android Development] gravityy:
lol. do disabling the pam solve the issue? if you're just reading, you can test using stock setting.

back on r33/34 when i'm just using my phone for reading using stock setting, i'm getting 9hours sot :D
[Nexus 5 Original Android Development] blueren:
Disabling pam solves the issue. Yes.

I totally agree with you. But when you're given an option to screw around.. Why not? :)

Sent from my Nexus 5
[Nexus 5 Original Android Development] granets:
And I agree with you - screwing around is fun. But I did alot of it to find something better than stock and I couldn't. :) Tried vomer and a couple of other people's settings, and again results were worse than stock. If you want god battery life and a smooth experience - stick to stock. If you want to have fun - PAM is a great way to do it at some moderate battery drain. I will say that If you play a GPU Intensive game it could help, but that's about all I would use PAM for - reduce the active cores when gaming, to reduce heat from CPU, so GPU doesn't throttle.
[Nexus 5 Original Android Development] linqdesires:
r47, kernel panic and rebooted while watching youtube video

log attached

thank you
[Nexus 5 Original Android Development] blueren:
Agreed. But what I do more than read books is play clash of clans. Now I've noticed that this game works butter smooth even at 883mhz. N 320 gpu. Here's where pam works out at it's best! This is the only app I really want to use pam with. Everything else is as stock as it can get! :)

Sent from my Nexus 5

---------- Post added at 07:22 PM ---------- Previous post was at 06:54 PM ----------

@franciscofranco - I think it's the thermal throttle in pam that's causing issues for me.. I bumped up the thermal throttle in pam to 70 and it somehow seems to be holding good. Lemme try testing this some more...

Sent from my Nexus 5
[Nexus 5 Original Android Development] graffix31:
just wanted to say r47 has been awesome for me. havent had to restart in a week and battery has been great. thanks for all your work.
[Nexus 5 Original Android Development] SketchyStunts:
Just had my 1st SOD ever on R47. No log so i'm useless lol. No biggie though, love this kernel
[Nexus 5 Original Android Development] Arstoien:
Google/Qualcom and many users have different goals with the settings. Stock google settings try to satisfy most people, which of course makes sense, but what I am looking for in my phone is probably different than what others are. If you know what you're doing you can achieve what you're looking for.

Actually when you get to bigger villages and bigger armies, you need a little bit more than this, I've found. We need PAM that changes automatically as you progress in the game :p
[Nexus 5 Original Android Development] amrmorsy:
apps crashes

All,

Thanks for the help. Looks like I will just do a full wipe and reinstall everything from scratch. Safest way to go.

You guys are awesome.
[Nexus 5 Original Android Development] blueren:
Ahahaha! Hm.. haven't noticed that though.. but i think it's more to do with the gpu. I don't find any stutter at all...
[Nexus 5 Original Android Development] arg1001:
USB otg it's not working for me in Franco r47

PD: I installed stock kernel and otg works perfect

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] :
Works fine here, I just backed up my storage via OTG on r47. Using stickmount. The only time I had issues was when I skipped through the superuser permission request.
[Nexus 5 Original Android Development] dipzb90:
I'm loving r47! Definitely on course for my best on screen time... Using settings which are similar to Vomers. I mainly use WhatsApp, twitter, Instagram, Tapatalk and browsing the web :)
[Nexus 5 Original Android Development] jcpq:
r47 don´t work on Mahdi-Rom 2.5
[Nexus 5 Original Android Development] Savant:
Logs or it didn't happen. Lol
[Nexus 5 Original Android Development] Ben36:
Anyone fancy giving my settings a go and give opinions on smoothness (i know u can only go 300 minimum but it won't matter)

http://xdaforums.com/showthread.php?p=52214708
[Nexus 5 Original Android Development] whytechapel_x:
Well obviously it will work with stickmount but not when the ROM itself has support for it.
[Nexus 5 Original Android Development] Nbsss:
Just flashed r47, coming from r46.

Immediately noticed screen off and on is way more responsive, great work!
[Nexus 5 Original Android Development] benthian89:
Recently, I did an app for my school project. The requirement is that the app must be intelligent and context aware. So I did a self-learning news app where it will try to find out what is your favorite type of news depending on your sent messages in sms, email Facebook etc.

Similarly this concept can be applied for PAM, where there can be an intelligent mode where PAM will find out what are most used freq for the foreground app for a short duration and then calibrate the min and Max freq based on that.

For example, if the game mostly uses 800mhz, then the min can be the default and the max can be peg at 800
[Nexus 5 Original Android Development] Tzfardaya:
I think he was talking about a floating max...
[Nexus 5 Original Android Development] eigokyoukan:
I'll give it a go :)

And bit off topic, but I rock clash of clans too! Hah small world... Anyone looking for a clan? We are not the biggest yet, but we are 5 for 5 on some clan wars! Haha
[Nexus 5 Original Android Development] rabbo3:
Hi little question how is my battery consuption?

?
[Nexus 5 Original Android Development] matique:
Hi guys. What are your averages for idling drain? Mine is 1% an hour when I'm asleep. It isn't bad but I think i can do better. How about you guys?
[Nexus 5 Original Android Development] Zainiak:
It's fine as long as it works for you. It's different for everyone.
[Nexus 5 Original Android Development] Tråget:
My idle drain is about 1%/3-4h.

But it all depends on what you have running on your phone of course. :)
[Nexus 5 Original Android Development] blueren:
[MENTION=3292224]franciscofranco[/MENTION]

I think i figured out my weird max freq bug. Need someone else to test this out for me.

I am able to reproduce this behavior multiple times:

Set max freq to 2.2Ghz (this is default)

Set thermal throttle to 60 (this is default)

Set PAM to a lower freq (Eg. 1.4GHz)

Set PAM thermal throttle to 60 (this is default)

Open app that is capable of making temps raise beyond throttle temp. Use it for awhile.

Quit from the app so that PAM gets off

Wait until temp < thermal temp

Check max freq --> something other than default max of 2.2GHz (Tadaaaa! -- this is the weird behavior in my phone)

How to avoid this weird behavior:

Set max freq to 2.2Ghz (this is default)

Set thermal throttle to 60 (this is default)

Set PAM to a lower freq (Eg. 1.4GHz)

Set PAM thermal throttle to 70

(this should be greater than original non PAM temp threshold)

Open app that is capable of making temps raise beyond throttle temp. Use it for awhile.

Quit from the app so that PAM gets off, now the default non pam thermal throttle of 60 degrees will kick in

Wait until temp < thermal temp

Check max freq --> it will be magically working as it's intended to be. Default max will be correctly set to 2.2GHz
[Nexus 5 Original Android Development] ali262883:
Guys is there any color profile which just sharpenes the display a bit.. So that it doesn't look washed out.. I've tried vomer profile they are awesome but faces are completely blown.. They look too dark.. Please if anyone can suggest?
[Nexus 5 Original Android Development] Ben36:
Every display is different that's why. Try my settings and see what you think. As a few have said they're spot on settings for their screens. So i assume we have the same screen as each other
[Nexus 5 Original Android Development] ali262883:
What's the name of ur settings?
[Nexus 5 Original Android Development] The Gingerbread Man:
I have one of the 1.8 stock gamma displays and been using the 0rigin profile for a day or so. In my own opinion and without having any speciallist equipment etc I find that profile to have very accurate colour reproduction and 'white' whites not blue whites. I don't remember who made it but thanks!
[Nexus 5 Original Android Development] ali262883:
Can u share it?
[Nexus 5 Original Android Development] The Gingerbread Man:
It should be in the fku app already, or follow the link in my sig to grab a download and use the free nexus display control app if you don't already have the full fku app http://xdaforums.com/showthread.php?p=45091387
[Nexus 5 Original Android Development] ali262883:
Okk thanks
[Nexus 5 Original Android Development] Ben36:
Ben36 lol. Easy as that. Gives me and a few others 2.2 across the gamma
[Nexus 5 Original Android Development] ali262883:
Okk
[Nexus 5 Original Android Development] yorici:
You do know the Display Tester App is completely flawed right? You are just testing one out of 256 RGB values with a degree of inaccuracy due to factors like ambient lighting and viewing angles. Saying the gamma is 2,6 overall is exactly as precise as your statement.
[Nexus 5 Original Android Development] Laggalot:
ben36 and pierv7 are almost the same! is there a way to compare them side by side? because switching back and forth isnt that good for comparing.... ben36 seems to be a little more pinkish though

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] yorici:
Look at their parameters or use a colorimeter. You can open up the profiles with a text editor. A higher value for the first 12 parameters means darker, a higher value for the last 12 parameters means it's lighter. You have 24 parameters in total per channel, times two for more precision. Each one of the 24 parameters control a range of RGB values (see attachment for how big the affected range is per parameter). The Displaytester app only checks for RGB-value 186, controlled by parameters 10/11. The background is made up of RGB-0 and RGB-255 (controlled by parameter 0 and 24). Therefore making the gamma image in the Displaytester app dependant of parameters 1,10,11,24. By no means you are calibrating though. You are just viewing the results. Calibrating requires you to calibrate the parameters, not single RGB values.

So you can compare them with the parameters, but that's about it. Without a colorimeter you will never be sure if it is accurate.
[Nexus 5 Original Android Development] Laggalot:
i know, i was thinking about :one half of the screen this profile the other half the other one .... this should be totally doable with root....

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] AGiLiT:
I introduced it but can't take credit for it. From my original post (and for those that didn't follow all this, Mag01 was as far as I know the first to use a colorimeter to calibrate the settings):

In Mag01's definitive post he had one intermediate group of settings, which he found gave the highest contrast. 0rigin was the first to note these settings with a white balance of 31 were quite close to optimal.

So if you like the Mag profile, try this one, also.
[Nexus 5 Original Android Development] yorici:
I'm also creating a profile (on wp 31) and I'm nearly finished, I'm just getting stuck on this bug: Could you test this bug? http://xdaforums.com/showpost.php?p=52181760&postcount=27759

If it is a real bug and not just on my phone, we should notify Franco.
[Nexus 5 Original Android Development] AGiLiT:
Following the steps, I do not see a light blue color after screen off/on. It still looks white to me. I have to slide the red down quite a bit to make it look bluish. Bringing all back to 255, and it's white.

What I do see is that if I go into Franco, it is reading the red pos as 0. Screen off/on changes it to 0; confirmed by going back into Gamma app. I tried to test it on stock (from 4.4.2), but gamma app gives me the old version message.

Hope this helps.
[Nexus 5 Original Android Development] tcat007:
Take screenshot of each and edit the photos to half screen each.
[Nexus 5 Original Android Development] franciscofranco:
That is really cool concept. Its easier said than done, but its something I can potentially see me doing in the future. I'll brainstorm a little bit with myself :)

I'll try to reproduce! :)

[MENTION=4809179]yorici[/MENTION]

Next FKU version will have proper 100% gamma calibration interface with a proper UI and easy to use.
[Nexus 5 Original Android Development] benthian89:
The crucial part is in the learning algorithm (machine learning of some sort). But I think this will spark some idea for you.

Self-learning apps are getting popular but it always has the problem of privacy.

For PAM, privacy is not an issue since you are only monitoring the CPU freq (and possibly GPU load as well).

And I am looking at gaming scenarios where most people use PAM for.
[Nexus 5 Original Android Development] franciscofranco:
The problem about machine learning on this specific case is that even though a game, for example, doesn't need more than 1,2GHz on each core, it will ramp to the max regardless most of the time. How am I supposed to figure out "ok this game can run at 1,2GHz without a problem" when it tries to over-utilize higher freqs? I'm gonna think about this in a couple weeks, I have some projects to finish :)