yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] JNewms:
Yes, when you turn the screen on to check the time the 2 cores will be at 300. They only ramp up when you touch your screen.

As far as UV, no, it does not save that much battery. A small amount of it can help to keep your CPU a little cooler, but battery savings will be slight.
[Nexus 5 Original Android Development] safendi:
Thank you
[Nexus 5 Original Android Development] nerotix:
OMG girls where? :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
[Nexus 5 Original Android Development] david279:
You guys won't let it go....
[Nexus 5 Original Android Development] Andypandiiee:
It's comprehensive not comprehension. Your two liner nonsense leads me to believe you have issues.
[Nexus 5 Original Android Development] alanwyl:
Stop it
[Nexus 5 Original Android Development] detdett:
On purpose? Source?
[Nexus 5 Original Android Development] yorici:
You shouldn't change the white point in the first place. It reduces your maximum luminance and shifts colors. It should be at 32 at all times.

But if you really like it, I won't stop you. I just recommend not doing it.
[Nexus 5 Original Android Development] vomer:
Guys... why have we suddenly switched to arguments on this thread... please stop bickering and be a happy/constructive community :good:
[Nexus 5 Original Android Development] neriamarillo:
Wait.. Even if it's switching to 32? Given that 32 is the base that we have a lot of profiles have been configured to use a lower white point. Do you recommend not changing it back to 32?
[Nexus 5 Original Android Development] chikimonke:
Maybe people are in withdrawal, there haven't been any new color profiles for almost a week...
[Nexus 5 Original Android Development] vomer:
lol, true but we have enough to satisfy anyone's needs now :p
[Nexus 5 Original Android Development] dastinger:
Thank you for your insight.

Thing is, I really like Piereligio color profile but greys look a bit red/pink-ish. I don't really know how to mess around with color profiles but by changing the white point I stop getting those greys. Or at least I think I do. Does that make sense? If not, what should I try doing?
[Nexus 5 Original Android Development] aaroncal:
So after reading for awhile I'm still not quite sure what ROMs are working currently with Franco kernel and if I choose to use cm11 when did they make the changes...so I can choose the correct cm11 rom. Just made the switch from the g2 and this battery life is killing me....well at least its killing my phone.used to have nexus 4 and loved this kernel
[Nexus 5 Original Android Development] misterviolinguy:
I'm not sure what what point CM become incompatible, but every other ROM I've tried works perfect with it. I'm currently running cataclysm, but have run Omni and ParanoidAndroid with no problems.

Try something new. Maybe you'll like it. :)
[Nexus 5 Original Android Development] aaroncal:
I tried slimkat and it was a "no go" got stuck at the Google splash screen. I only ask because I'm looking for something with a theme engine in it, being that I have a bunch of paid themes.
[Nexus 5 Original Android Development] Circaflex:
something was wrong then because it works here just fine
[Nexus 5 Original Android Development] aaroncal:
OK that's good to know maybe I had a bad download on the kernel
[Nexus 5 Original Android Development] Enddo:
it's a nightly. if you expect anything else then you should not be flashing nightly builds

---------- Post added at 10:47 PM ---------- Previous post was at 10:41 PM ----------

seems like someone has their panties in a bunch today
[Nexus 5 Original Android Development] jtwlbz:
Is it just me I like stock color the best.
[Nexus 5 Original Android Development] detdett:
"I did not see any changes compared to the last version" - as requested by our friendly mod
[Nexus 5 Original Android Development] :
The stock white point is 32 ..
[Nexus 5 Original Android Development] kufikugel:
Well AFAIK (correct me Franco if it is not the case) the main user base are ppl with stock firmware. So Franco supports nexus phones and tablets and has nearly all his users on it. Compared to a quiet low cm user base (which is on nexus devices nothing new....either ppl stay stock or a small group using whatever ROMs which are around).

And honestly from developer point of view and marketing view (you mentioned) this alone would be a reason to do not both and to handle a load of extra work. Especially on cm it is not that they stop doing major changes which need always to be tracked and modified to work with the own kernel.

If it makes sense or not what cm is doing on googles qcom phones....well you can see it from two views....if you just want to have a fully working device tree then stay stock. If you want to experiment and get newer changes from caf....live with it that it is not stable like it was before....if you have at the end really advantages....well at least for me very questionable. Easy example things like slimport which are partly closed source are difficult to handle then. So you start like on a lot other fully closed phones to reverse engineer to experiment etc etc. On a phone which is basically very open but not fully and on a phone which is 100% working on stock sources.

So at the end I understand every kernel and ROM dev which stays aosp....for the one who like to experiment and do new things....new caf patches are the way.

And last one do not forget caf is the code base for qcom and a very good coding group. Our aosp tree is full of caf patches. So it is nothing bad and they are very good and pushed a lot we have now. Only question is does someone want to play with sources and patches which are still experimental or not ready for release or not hand able because you do not know what is going on in the proprietarys.

End of story :-p

PS: and believe me there are roms out there...not much but they exist which are doing on frameworks side and features the same or better quality then cm ;) Hardware tree wise absolutly no question CM is doing a great great job since some years.
[Nexus 5 Original Android Development] P.Mobile:
holy isshh! someone else from 401!:good:
[Nexus 5 Original Android Development] justibasa:
Newest aokp nightly is no longer compatible with this kernel. Losing one Rom after another. Just awesome.
[Nexus 5 Original Android Development] kufikugel:
lol well.....lets count the big original dev roms or the popular roms

Stock = stock aosp

PA = stock aosp with a bit modifications but near stock and compatible all the time

Slim = stock aosp with a bit modifications but near stock and compatible all the time

Omni = stock aosp with a bit modifications but near stock and compatible all the time

CM = caf modified trees

AOKP = caf modified trees

Carbon just switched to slim trees back

Liquid switched afaik as well to slim trees back

Purity afaik stock aosp

Catalysm stock aosp

.

.

.

For the first 3 original development roms I can guaranty they will not switch

So one rom after the other is a bit much said ;)
[Nexus 5 Original Android Development] Technecium:
wicked pissa!

that makes 3!

I moved away 8 yeehs ago... oh.. gahd, the voices in my head just stahted drahpping oll my ahs.

nooooo!

Sent from AOSP koeMod 4.4.2 w/ Franco kernel

---------- Post added at 02:49 PM ---------- Previous post was at 02:31 PM ----------

I have 'since boot' output that spans about 10 hrs. Lots of stuff in there but most references are probably false positives. I just did clear and scan about an hour ago and will continue to collect output. Do you want my output to compare against or is that not helpful?

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] Nocturnal86:
Franco I was wondering if the issues with max kernel Freq still sticking at seemingly random freq (or thermal throttle freqs possibly) Cause Ive updated the new FKU from beta a while back and cleared FKU data and I'm on r32 and still get those freq stuck (the times I usually notice are after gaming and gaming on charger but Im not sure if thats always the case) and have to randomly switch it back to stock 2.26ghz. Im not sure how to reproduce or when it actually happens. Do you have a suggestion on how to find out a way to log this if I can ever get down the pattern why it happens?

and also FKU seems to be dropping the per app mode process at times but the service stays open. I have to check and uncheck the "Disable per app modes" box in the setting to start up the process again.
[Nexus 5 Original Android Development] pitjago74:
Awnsome profile IPhone 5:D:D:D

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] panart:
On my device it has a greenish tint...
[Nexus 5 Original Android Development] The Gingerbread Man:
It must be broken
[Nexus 5 Original Android Development] braders2k:
Hi, just flashed R32 on PA Beta 4 ROM.. now when try use front camera on phone it shows error "Can't connect to camera" back camera working fine, any ideas?
[Nexus 5 Original Android Development] nexusmaniac:
Think it's a ROM issue :)
[Nexus 5 Original Android Development] Vercion3:
You should post that to the PA thread. Not here. It's not kennel issue. More of a ROM/app issue.
[Nexus 5 Original Android Development] braders2k:
Thought it would be kernal related as was working fine before I flashed kernal...

All ok now though as just wiped dalvik and cache and all's seems to be working now!!!
[Nexus 5 Original Android Development] big_adventure:
No! Don't be a twit!

;) ;) ;) ;)

Not being serious.
[Nexus 5 Original Android Development] comentator:
Hey, i have the exact same configuratiom and my camera works just fine

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] fbf2201:
Looks great as it is!

... for a iPhone. :D
[Nexus 5 Original Android Development] panart:
All other profiles except iPhone5 and iPhone are fine.

Lol, but seriously the iPhone color profile was awesome on Nexus 4.
[Nexus 5 Original Android Development] Alfonso87:
Sorry [MENTION=4790322]kufikugel[/MENTION] but CAF shouldn't lead to a much more massive develop of roms, with a more integration between software and hardware?? They are 100% open drivers, that's mean you can modify them all for your own purpose (correct me if i'm wrong).

This doubt were born to me after reading this post from faux123 http://xdaforums.com/showpost.php?p=46098546&postcount=15393

So, shouldn't be logic tring to use CAF instead of stock drivers to obtain more from rom developing? Why would you decide to continue using a close driver resource? Thank you for the answer :)
[Nexus 5 Original Android Development] sirovai:
https://www.youtube.com/watch?v=_81Lx8f0s2k&feature=youtube_gdata_player

Hammerhead-Purity-Franco
[Nexus 5 Original Android Development] laureanop:
Great explanation from Paul Reioux.

It'd be interesting to hear official word from CM as to why they're deciding to adopt this supposedly inferior branch of Qualcomm drivers .
[Nexus 5 Original Android Development] sempot:
They're messing with you
[Nexus 5 Original Android Development] kufikugel:
Well the link explained pretty good where the problem is. Open Driver != proprietary blobs. That are two stories. The driver needs to address the closed source hardware parts to work perfect together and actually address the hardware. So problem is a custom ROM which usually does not have sources for this need to reverse engineer or try things based on documentation which is often rarly available. And tbh it is absolutely understandable that a hardware manufactor close them. That's the competition the real secret behind what devices are able to do. And even when you got the chance to see this sources (I am that lucky to know some) they have strict licenses on it with a good reason. Like faux said Qualcomm is a good example...they close them completely and have very strict licenses on it.

Let me take a simple example not directly Qualcomm related but good to understand.....imagine whatever manufactor will open the camera sources and documentation on the hardware chips and blobs....they will immediately lose the competition lol. And we would have HDR on nexus aosp source :D

So to summarize.....driver is the one part (where we are on nexus lucky that the basic drivers are mostly all open) but to address the hardware is another story especially when you start to change major things on the drivers. Otherwise we all would have on qcom way more easy life :)

And just to clarify....Qualcomm is already very open for driver sources. Way more then all other platforms....but still there is the proprietary part which is at least the hard part to replace without knowing what the hardware is doing exactly :)

Hope I could explained it in a not to technical way and with my bad English lol
[Nexus 5 Original Android Development] yorici:
No i recommend staying always at 32
[Nexus 5 Original Android Development] Alfonso87:
Yep thank you, your answer was clear and useful :)

Just one more thing, so caf drivers are better/comparable to AOSP drivers, but with fewer limitation, or they are in an early fase to compete with them?
[Nexus 5 Original Android Development] yorici:
Yes and keep it there.

Edit: I didn't read his post well enough. But I ment that everyone should keep it at 32. I replied at 4am local time, that's why;)
[Nexus 5 Original Android Development] :
Hahaha that iPhone profile looks so stupid xD xD

Best troll ever!!
[Nexus 5 Original Android Development] Diesel779:
Hi,

Could anyone tell me which version of this kernel is best to use on my Nexus 5 with Cataclysm ROM? Thanks.
[Nexus 5 Original Android Development] MoJo:
r32 is a last stable one.
[Nexus 5 Original Android Development] mythenmetz:
Just take the latest, which is r32. R33 is a test build, and when you read the last pages you can see why it's a test build.
[Nexus 5 Original Android Development] Diesel779:
Thank you both for the fast and helpful replies.

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

Does this kernel slow the phone down? I've noticed that it regulates cpu clock speed so I just wanted to ask before I flash. Thanks.
[Nexus 5 Original Android Development] sjondenon:
This kernel somehow causes occassional (micro)lags when scrolling and during transitions. Never had this when i was using the stock kernel together with the stock rom
[Nexus 5 Original Android Development] Diesel779:
Thanks :)
[Nexus 5 Original Android Development] panart:
No worries, it just shows how mature they are.
[Nexus 5 Original Android Development] big_adventure:
To be fair, if you had searched the thread for information on that profile, you would have realized that the profile is a joke. You are not the first person to be taken by it.

In general, if you are in a Nexus device developer forum and someone offers you something called iPhone-anything for your phone, you should probably expect a joke or a hack. Hopefully the former, which is the case here.
[Nexus 5 Original Android Development] Enddo:
lawyered
[Nexus 5 Original Android Development] chrisch91:
FKU doesn't work for me perfectly. I can't swipe from left to the rigjt for the menu points. They are shown only in landscape mode. Any solutions?
[Nexus 5 Original Android Development] The Gingerbread Man:
Y u have a nexus if you want iPhone looks :sly::what:
[Nexus 5 Original Android Development] tylerdurden83:
Hello Franco,

I've read every page of the thread and I know that you have been super busy with the r33 tests and the major news in it like the new audio, but I was wondering if you managed to have some spare time to look this value up.

Although my battery consumption on standby isn't that high to begin with, it just saddens me to see my device and its perfectly optimized kernel get out of deep sleep for so many minutes for nothing. As I said I tried to fix the network at home by disabling upnp and giving the phone a static ip, but it didn't change anything. Plus I cant do that on the work network, so that would be only a partial workaround....

Thanks again and keep up the good work!
[Nexus 5 Original Android Development] P.Mobile:
wicked! :D
[Nexus 5 Original Android Development] maddes1402:
[MENTION=4114496]tylerdurden83[/MENTION]

To reduce the wifi wakelocks I can recommend "better wifi on/of":

http://xdaforums.com/showthread.php?t=1801284

Regards, Matt

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Puzzlegirl:
Here I am :)
[Nexus 5 Original Android Development] Aerowinder:
If you already have optimize wifi selected, replace your router because it's garbage.
[Nexus 5 Original Android Development] linqdesires:
you're wrong...

I like stock color too and I think it's an interesting opinion to share. I don't feel comfortable in any of the color profile I tried.

About CM... I believe people need to respect others opinion, don't feel a better person just because you chose to ban CM. reading of people "tired" of other people opinion: not a wealth environment to talk. people using CM have reason for that.

I'm back to stock (+xposed) actually, I can see the differences and I see all the good in CM.
[Nexus 5 Original Android Development] Techimplant:
People I think I have an issue that hasnt been discussed coz I guess nobody has faced it..

While talking on my phone I have to keep the mic very close to my mouth otherwise the other person says that he cannot hear me..speak louder please..n this is so if I keep my phone at normal distance with earpiece pressed against my ear..the normal talking position ..

I already have the Mic boost at "1" in kernel settings in the FKU app...

What shall I do now?

I am on r32 btw..
[Nexus 5 Original Android Development] detdett:
Low mic volume is a known issue
[Nexus 5 Original Android Development] foxmolder1985:
I'm sorry if this is a thing already said, but how to configure vibration back to stock 4.4.2 values?

Because with "vibration config" to 70, the keyboard vibration is too low. The notification vibration, whereas, is too high.

Thank you in advance :cowboy:
[Nexus 5 Original Android Development] bobby janow:
Really? I never knew that. I just figured that I had to talk closer never realizing that there could be an issue. It works great on speaker though, which I've taken to using more often now. So it's a hardware issue or stock rom issue? Are there any work arounds?
[Nexus 5 Original Android Development] nerotix:
OMG! Girls on the interwebz exist? really? It's a phenomenon ;D Must be a mistake, interwebz is a jungle for men!
[Nexus 5 Original Android Development] franciscofranco:
I think I found the problem, I think it was one ion patch that invalidades cache & uncached entries and then I think there's a leak in the ion heap allocation function in ion_system_heap file. I reverted those two patches and after 12 hours my device is still hitting 650mb ram used, which is normal for me. I'll push it in a couple minutes.

Max freq by default is 2,26GHz.

This time with my changes the service can work without the process so its ok.

Yes, you're using a pirated version.

If its getting out of deep sleep you have apps doing it for you.
[Nexus 5 Original Android Development] nexusmaniac:
F5 F5 F5 F5 ;)
[Nexus 5 Original Android Development] FAdrums:
LMAO

Tapatalked from my Franco Carbonized ARTy Hammerhead
[Nexus 5 Original Android Development] franciscofranco:
Not yet, I'm gonna relax a little bit, its saturday after all :)
[Nexus 5 Original Android Development] The Gingerbread Man:
The stock value for vibration is 63. You can set it on boot in fku
[Nexus 5 Original Android Development] 00MATRIX00:
noob here.does r32 support 4.4.2.i am using franco kernal free app
[Nexus 5 Original Android Development] Bill Gamble:
Yes.
[Nexus 5 Original Android Development] ChazzMatt:
bug reports

The files are 10MB text files and seem too big for pastie or pastebin. Pastie gives me this error message repeatedly:

and pastebin says the file is too big unless I go "pro".

Any solution? I have two recent bug reports for r32.
[Nexus 5 Original Android Development] lukazzo:
im on cm 11 i tryed to flash r32 kernel but after that n5 stuck at google logo

what could be the problem?
[Nexus 5 Original Android Development] RealSlimShadyMC:
Franco doesn't support CM because of all the rogue patches they keep adding that break kernel compatibility. You're out of luck for CM. There are a few deCAF'd CM builds floating around though
[Nexus 5 Original Android Development] blueren:
Yes. CM is no longer compatible with franco kernel. Either stay with stock CM kernel, or change the rom that conforms to AOSP.
[Nexus 5 Original Android Development] lukazzo:
oh okk, thx for the quick reply

---------- Post added at 04:20 PM ---------- Previous post was at 04:16 PM ----------

there is somewhere the kernel of cm 11 to flash without need to reflash all the rom?
[Nexus 5 Original Android Development] Technecium:
If you would be so kind, for posterity sake, post the reference or references from the output that led you to the leak. I'd like to see to compare. This was a cool learning experience for me.

I was unsure if you looked for large amounts of ram or multiple refrences to the same thing. I can see so disregard the first part of the post.

And I was using addr2line to resolve the backtrace addresses but was not getting complete references. For example,

android.c:?

The ? should have been a line number but I couldn't get it. Do you know how I can fix this?

arm-linux-androideabi-addr2line -C -f -e vmlinux c04c8220
$a
ion_iommu_heap.c:?

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] Lawlbringer:
My guild cleared up to Kil'Jaeden pre-nerf, but 2 weeks later was the 3.0 patch. It was kind of disappointing seeing guilds that couldn't even clear Black Temple just mow through Sunwell in one night after the patch...but that's what always happens with pre-expansion patches with new talents.

I played a Warlock and got pretty burnt out from raiding during Sunwell though. We had a hard time with M'uru's last phase(mainly healers) so I focused more on trying to get Gladiator in arena around that time. I always loved raiding but PvP was too much fun, even though it was always pretty up and down in terms of balance in WoW. I miss those days, the game was probably the funnest it ever was during TBC. Have you played much at all recently? The new expansion looks fun, but so did Mists of Pandaria and I've hardly played since it launched. :laugh:

Oh, and has anyone had any issues with mobile network connectivity using Purity ROM + Franco? Seems the only ROM/Franco combo I've tried that hasn't given me any weird issues is Cataclysm/Franco. I'm very happy with both, super stable with awesome battery life.
[Nexus 5 Original Android Development] DerItaliener:
https://android.googlesource.com/platform/build/+/08d410f53249c18d752f56a881ed2335403080d4^!/
[Nexus 5 Original Android Development] tylerdurden83:
If apps are to blame they would show on the screens that I posted. Out of 4 h 30 min I had 1 min 25 sec of PowerManagerService.WakeLocks in the kernel wakelock tab.

In the partial wakelock tab besides the AudioMix wakelock because I havent disabled system sounds I have basically no app wakelocks.

Btw, I actually found out a post from a user having this exact problem: http://xdaforums.com/showpost.php?p=47279988&postcount=1

and besides the usual suggestions, plus another one I didn't hear of before, disabling ipv6: echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6

he says that you have already done some commits to lower its impact: https://github.com/franciscofranco/hammerhead/commit/5dd724eb19f768e641041a0b897c5e8464077949
[Nexus 5 Original Android Development] nicholaschan24:
Try disabling noise cancellation mic. When you have your phone away from your face, the actual mic has trouble picking up your voice and the phone will see your voice as background noise and cancel it out. Disabling noise cancellation should help
[Nexus 5 Original Android Development] tylerdurden83:
It's an Asus N55U: http://www.asus.com/Networking/DSLN55U_Annex_A/

Right now I don't really have 100+€ to invest on a new router, but could you suggest a good one which has all the main features like port forwarding / mapping, snr regulation etc?

Cheers!