yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] UpSpin:
I agree with that. I would like to play around with using a single core too, especially to test if demanding games can run with a single core, causing less heat, prolonging the long-time battery life.

Without experimental data to verify this, I think the best set-up, for me, would be: 1 core in standby, 2 cores while active with the option to hotplug two further cores to handle multi-tasking, web-browsing, .... In games 2 or just a single core to reduce thermal throttling and allow the GPU to run at higher frequencies.
[Nexus 5 Original Android Development] Miz_Buzzer:
Is there a problem with auto brightness? :confused:
[Nexus 5 Original Android Development] FormeriPhoney:
OK so I finally flashed the latest version on my stock rom with Gb.

I ended up going with Vomer as the color profile for now.

Huge difference out of the gate. Looks like an amoled screen. ?

Do you guys recommend any other profiles? I'm looking for something not too too saturated, but to richen up the colors a bit.

Glad I purchased the FK updater app. ??
[Nexus 5 Original Android Development] Technecium:
yes/no
[Nexus 5 Original Android Development] shaker2k:
Try vomers or the ginger bread man's settings.
[Nexus 5 Original Android Development] Tzfardaya:
No prize, just something to do..

Last time I maxed the achievements, he added the 250, wonder what he'll add now... :P

No problem with it

If you want to get an Ota update, resetting to stock kernel is normally required... There are other reasons to flash back as well... Such as testing if a problem you're experiencing is Rom related or Franco specific...

---------- Post added at 06:03 AM ---------- Previous post was at 05:56 AM ----------

The /proc/config.gz should be taken from a valid Franco installed phone... It's different from the hammerhead_defconfig because Franco makes substantial changes to the kernel source.

Make menuconfig is a graphical (somewhat) interface to include/disable kernel components. If you pulled francos config.gz file to base your build off, menuconfig isn't necessary, but still recommended for additional learning... Look through it at the available options.. But it should build properly from Franco config.. (it's the config he built his running kernel from)
[Nexus 5 Original Android Development] FormeriPhoney:
Would those profiles work on slims kernel or does it have to be Francos?
[Nexus 5 Original Android Development] danieljcf:
Yes, but not caused by this kernel.
[Nexus 5 Original Android Development] FormeriPhoney:
Vomers is nice, but seems like contrast is over the top. Losing some of the dark colors imo. GB Man seems a little more true but doesn't give an amoled experience.

Guess I'll have to test out some more
[Nexus 5 Original Android Development] alcurtis93:
Vomers is perfect 2.2 gamma on my display
[Nexus 5 Original Android Development] Tzfardaya:
using display tester or an actual colorimeter?

keep in mind that dt only checks the gamma at one point in the display range...

(and which vomer colour profile? I'll test that next)

---------- Post added at 07:42 AM ---------- Previous post was at 07:40 AM ----------

just finished testing origin... so far it's the closedt to sRGB spec... nearly perfect 6500k temp, colour/saturation spread in cie is closest to the target so far... except for the reds...
[Nexus 5 Original Android Development] FormeriPhoney:
Can you be more specific? There are 3 vomers and what exactly do you mean by 2.2 as far as the gamma settings go?

Thanks
[Nexus 5 Original Android Development] Tzfardaya:
You never said which vomer you're using either.. :p

sRGB specifications call for an "average" gamma of approx 2.2
[Nexus 5 Original Android Development] Tylog:
Vomer Balance , best one, use it since long time:)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] FormeriPhoney:
It seems I don't have one that specifically says vomers balance..
[Nexus 5 Original Android Development] Tzfardaya:
might need to grab the zip in [MENTION=1363323]vomer[/MENTION]'s signature... he keeps a zip of all the latest colour profiles...
[Nexus 5 Original Android Development] Tylog:
Look there http://192.227.135.147/N5_ColorProfiles/
[Nexus 5 Original Android Development] FormeriPhoney:
I figured it out. I uninstalled the nexus color display app and went directly through the paid FK updater app and the profiles showed up. Running the Vomer Balance now
[Nexus 5 Original Android Development] Tzfardaya:
Running Vomer_Balance tests now. :p

I'll post my findings in a couple minutes..

edit:

okay, tests finished...

vomer_balanced...

temp range: 7500k to 9000k

gamma range: 1.45 to 2.3

cie chart: reds close, everything else biased towards blue/green
[Nexus 5 Original Android Development] FormeriPhoney:
So is there a perfect profile?
[Nexus 5 Original Android Development] romgnascher:
I would like to add a data point to the r37 Bluetooth issue. I have a device called the "SmartMini aux". It's basically a car kit that gives you a microphone and an audio out jack to go to the aux port in your car radio.

With r36 and earlier, it connects fine. On r37, it tries to connect, but can't.

I'm on latest ParanoidAndroid, and was running r37 unmodified.

Happy to get whatever data you'd like to help diagnose this ... but will need step-by-step direcetions. :)
[Nexus 5 Original Android Development] Tzfardaya:
If there is, I haven't found it yet... Mag01 and Origin seem closest to a true sRGB so far... but I haven't tested all the profiles yet... (thats today's plan)

but as for "perfect" do you mean looks best, or best matches the sRGB standard. sRGB will give you closest "true to life" colours as thats what proper recording devices, digital cameras (still and video), scanners and the like should (usually claim to) be calibrated to.

sRGB wiki here

---------- Post added at 08:40 AM ---------- Previous post was at 08:30 AM ----------

I know this is a simple test, but it does tend to get overlooked...

Have you tried "forgetting" the pairing and trying to re-pair it again?
[Nexus 5 Original Android Development] granets:
What about piereligio's True RGB profiles? V7 seems pretty good as far as I can tell with display tester app? Maybe a bit colder but other than that the gamma is bang on between 2.2 and 2.3

edit: another good one is spoorthy4's profile. It is also colder than 6500K, but other than gamma being low in the reds, everything else is just shy of 2.2 on all other colours.

If anyone is choosing a accurate profile, I'd suggest one of those two (piereligio's V7 or spoorthy4's) As far as accuracy goes, they seem to be the best in terms of gamma. If you want better whites, closer to 6500K, just stick to stock, gamma is a bit lower but it's not that bad (around 2.0 to 2.1)
[Nexus 5 Original Android Development] franciscofranco:
Congratulations :)

You sent me a recovery Kernel log.
[Nexus 5 Original Android Development] FormeriPhoney:
I guess I should have said "looks best" just looking for a little bit richer color like amoled but not grossly over saturated
[Nexus 5 Original Android Development] franciscofranco:
Log says hw_reset, no crash no error. Are you undervolting?

No changes on r37 that affect BT so dunno.
[Nexus 5 Original Android Development] Tzfardaya:
v7 was the first I checked..

here's the colour temp, gamma, and cie chart
[Nexus 5 Original Android Development] Tzfardaya:
what "looks best" is entirely up to you... I think the sRGB "looks best" but I use my devices to display Photographs... odd colour settings make the colours seem off.. People's skin is too red, leaves the wrong shade of green, or too blue... etc, etc, etc...
[Nexus 5 Original Android Development] ebahena:
I've been using Son_Of_Sammy and it looks very rich in color but not overdone.
[Nexus 5 Original Android Development] FormeriPhoney:
Very true. I'm running the 0rigin profile right now and it looks very nice. Balanced, colors looks pretty true. [emoji106]
[Nexus 5 Original Android Development] granets:
thanks for that. I was away for a couple of days so I've missed the post. Keep up the good work. Also, I'd love to see you compile those results in a thread or maybe a google doc, so we can see them as reference when choosing an accurate profile. Also I've edited my post with another profile that seemed good to me. Check it out if you have the time, it's not part of the default profiles. If you don't have it I'll just add it to this post.
[Nexus 5 Original Android Development] FormeriPhoney:
This also looks good. Definitely amoled look to it, less heavy contrast like Vomers. How the hell do you choose, lol. So many to choose from and a lot are very similar
[Nexus 5 Original Android Development] Tzfardaya:
I'm putting my results up on my d-h.st (linked in my signature... need to edit that.. not just scripts anymore) but they do require a 3rd party app on your pc/mac to view the files... I'll add a howto to the link in my sig shortly... (hopefully some time today, want to get these profiles all tested..)

If the profile you're using is in Vomer's zip collection, I have it...
[Nexus 5 Original Android Development] granets:
You don't have it then :P I'll try and figure out a way to view your charts, because I need something to do right now :D
[Nexus 5 Original Android Development] franciscofranco:
Dont forget we now have RGB tunables. I've been running with 245 255 255 to get rid of the redish/yellowish hue.

I'll hopefully will have that interface added on the color app in the next days.
[Nexus 5 Original Android Development] PresidentMcCain:
r12: Antutu still reboots in the middle of testing, and also this is happening again:

http://i.imgur.com/qAnXJmu.png

Coincidence or not.. both Antutu and Quadrant crashed during the floating point CPU tests.

11-15 22:59:05.595: E/Fg(4966): Exception
11-15 22:59:05.595: E/Fg(4966): com.aurorasoftworks.quadrant.api.BenchmarkException: java.util.concurrent.ExecutionException: java.lang.ArrayIndexOutOfBoundsException: length=0; index=3802
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aj.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.F.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.F.apply(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at yS.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at qj.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.n.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aj.g(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aj.h(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aj.d(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.f.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aj.g(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aj.h(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aj.d(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.core.aq.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.ui.runner.x.apply$mcV$sp(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.ui.runner.x.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.ui.runner.x.apply(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at Fg.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.ui.runner.l.a(Unknown Source)
11-15 22:59:05.595: E/Fg(4966): at com.aurorasoftworks.quadrant.ui.runner.l.apply(Unknown Source)
[Nexus 5 Original Android Development] lukas_s:
This is the first time I've really ever played around with kernels, so please forgive my lowly questions.

Is there a "settle-in" period for kernels? For instance, I flashed r11 earlier this afternoon, and r12 about 2 hours ago. I'm getting MUCH worse battery life than stock now, and I'm barely touching my phone. There are no wake locks occurring.

This is not a critique of Franco's work, I'm just genuinely confused by what is going on. I haven't messed with any of the settings. I just flashed the kernels and let them do their thing in the background.
[Nexus 5 Original Android Development] franciscofranco:
Just tried the game, don't see any perceived lag :'(
[Nexus 5 Original Android Development] franciscofranco:
That's not Kernel related, Quadrant noobs have that bug since forever. The app code tried to access an index of an array (all app internal code) that doesn't exist, then it booms.

There's no settle-in, this is all bits and bytes. What can happen is for example you flash in the middle of your battery cycle and sometimes the battery reporting can be a bit erratic that's why its always a good practice to judge a battery life after a full battery cycle.
[Nexus 5 Original Android Development] Nocturnal86:
How did you get to that? The app ops aps dont get there like before :(
[Nexus 5 Original Android Development] PresidentMcCain:
Passmark caused phone to reboot during the CPU test similar symptoms as Antutu:

https://play.google.com/store/apps/details?id=com.passmark.pt_mobile

Kmsg:

No errors detected
Boot info:
Last boot reason: hw_reset

r12 kernel
[Nexus 5 Original Android Development] caribouxda:
Yupp definitely! The new android version sucks just because you do not like 3 apps...I mean who uses stock keyboard anyways?!
[Nexus 5 Original Android Development] beaver2233:
I am on slimkat rom, but I don't think it's a feature of that (could be wrong)... go to settings > security, then scroll down to privacy guard... there you'll see all your apps. Touch and hold on the app you want and there.

---------- Post added at 03:23 PM ---------- Previous post was at 03:20 PM ----------

This is getting heaps of topic sorry Franco... but, agreed and also you can change the alarm to whatever you want...
[Nexus 5 Original Android Development] franciscofranco:
Yeah the Alarm app changes suck... :'(

I don't wanna let you down, but at this moment I'm completely clueless about that. I have other apps that test floating point and they don't crash. According to one of the logs I gathered on my testing there is a L1/TLB unrecoverable errors, which is a D-cache parity failure. There is hardware that can recover from L1 errors, while others cannot but there should be a graceful way to not panic with a L1 cache bug. Apart from this I have no more idea of what it can be, and cannot fix something that I don't understand.
[Nexus 5 Original Android Development] PresidentMcCain:
Hope Qualcomm/Google has a better idea of what are the proper steps to resolve that issue then :\

Don't get me wrong, I really appreciate your work.. it's just that seeing multiple apps crashing (the phone in most cases) makes me feel uneasy about daily driving an otherwise excellent kernel release.

A workaround for preventing the kernel panic would be fantastic for now though seeing that I'm not the only one seeing the crashes in the exact same apps.
[Nexus 5 Original Android Development] Nocturnal86:
crap I guess it is rom related...
[Nexus 5 Original Android Development] zephiK:
Its a possibility that they re-enabled it. I wasn't able to find it in shortcuts for Settings (thats how I found it in 4.3)
[Nexus 5 Original Android Development] franciscofranco:
I don't wanna sound like a ****, but how important are those benchmark apps for you? Do they turn your device unusable?

Like I said before there are thousands of users with the same problems, with various devices, its not isolated to the N5, or this Kernel for that matter. Just read Antutu app reviews from other users.

No workaround available, its too low level for my knowledge, sorry.
[Nexus 5 Original Android Development] bikeryder007:
That antutu app is buggier than a smiling cyclists teeth. It did the same thing on my last phone even though it was otherwise stable. Franco could find a better use of his time than polishing that turd.
[Nexus 5 Original Android Development] kojaraty:
Enough with the benchmark apps. Show me battery life samples people.
[Nexus 5 Original Android Development] PresidentMcCain:
Back in the day, people would say "ignore Prime95, Linpack, FurMark", just go with "everyday applications" for stability testing. And then one day CPU instability rears its ugly head, and something legitimately important (like your work document) gets corrupted during an edit, or say.. you're crunching some accounting numbers for whatever reason (float operations), and phone random reboots one day.

Not isolated to Antutu, as you said so yourself.

Perhaps there are two workarounds that are straight-forward: disable thermal-engine-hh renaming and put the file back (and deal with aggressive throttling algorithms but maintain stability), or force max CPU clock to 1.7 GHz (which several people here tried and worked as reported).

The proper fix though would be to fix whatever mess Qualcomm created... after a discussion with a friend of mine we conclude that thermal-engine-hh is probably doing the aggressive throttling because it has to... to keep the CPU under stable conditions.. since it's either incorrectly binned or to cover for half-assed drivers... Just pure speculations on our part though.
[Nexus 5 Original Android Development] Nocturnal86:
Battery life is relative... Do your own tests if you want to see some.
[Nexus 5 Original Android Development] franciscofranco:
No, I said this doesn't only happens with the Nexus 5 or this Kernel. Read the user reviews:

https://play.google.com/store/apps/details?id=com.antutu.ABenchMark

You're mixing things, if you know X benchmark app crashes why do you use it? Or better, why would you open important documents, edit them, them run a bench app that crashes? Doesn't seem a scenario that anyone would do.

That is not a proper fix because:

1 - The device is not unstable by any means. It crashes on two or three benchmark apps doing floating point benches? No big deal. Games use floating point operations for everything. Do they crash? No.

2 - I'm not gonna ship a Kernel with a dumb thermal throttling engine just because LGE sucks with their battery chips (LGE is the only OEM that throttles based on battery temperature)

3 - I'm not gonna force max CPU clock to 1.7GHz, that would be a serious bottlenecking for a dumb problem that its not important at all.

BTW Linpack does floating point test and it doesn't crash.
[Nexus 5 Original Android Development] KTT16:
Just wanted to say thanks Franco for the hard work and efforts...on r12 right now. Haven't been able to do many test, but bought the app, and will report with results after a full battery cycle. Thanks again! :good:
[Nexus 5 Original Android Development] PresidentMcCain:
I'll give you that one.

Not the point. The point was that there could be a legitimate application that executes a similar workload which could trigger the kernel to panic in a similar fashion resulting in lost work.

I agree with #2, and #3... they aren't good solutions or proper fixes, hence the title "workaround".

#1. Just because some games don't crash doesn't mean there isn't a problem that could affect other games. E.g. unstable desktop CPU OC could run X game for hours and hours.. but crash in Prime95 and Y game right away.

Linpack for Android doesn't put enough workload out... nowhere near the similarly named Desktop benchmark.
[Nexus 5 Original Android Development] Tzfardaya:
well, I figured I'd measure the current profiles on the default RGB before I started messing with my own calibration setting.. :p
[Nexus 5 Original Android Development] romgnascher:
Yeah, I tried that. It would see the device was available, attempt to re-pair, but it would never connect.

The phone "registers" that it's attempting the connection, because it launches my CarHome Ultra (which I have config'd to launch on connecting to this device), but the connection never completes (never get a solid bluetooth icon in notification). If I go back to the bluetooth menu, it says "connecting..." for a while ... but eventually times out.

Reverted to r36 (with no other changes) ... and it connects in under a second.
[Nexus 5 Original Android Development] Tzfardaya:
good good, next, I would suggest disabling the CarHome Ultra auto load... (I'm a big believer in one step at a time troubleshooting..)

I've had similar issues, bluetooth dongle for the radio to stream music from the device (autolaunched play music when detecting the dongle)

if it was having issues pairing the app launch would get in the way...

try to pair that way, no autolaunched apps, also, if you have any kernel settings made, reset to franco's defaults see if that helps too.. (no apps, fail, then reset settings, only one change at a time, that way we can figure out which change it was)
[Nexus 5 Original Android Development] romgnascher:
Yup, yup ... tried that too. ...and I always run Franco's defaults.

I also tried rebooting ... no joy.
[Nexus 5 Original Android Development] Tzfardaya:
well, I'm lost then.. :p
[Nexus 5 Original Android Development] franciscofranco:
You can reproduce that 100% of the times? If so can you get me logcat logs when your devices are trying to pair?
[Nexus 5 Original Android Development] fugn:
Try Aditya_Amoledarks
[Nexus 5 Original Android Development] Kevin Goot:
Quick question guys,

I used to UV -50 on all boards but that seemed to cause my phone to act sluggish, so I decided only to UV -25. Now my phone takes a while to bring up the lockscreen when I unlock it. Is my phone not capable of UV!?! MY main goal is life is to save battery.
[Nexus 5 Original Android Development] Tzfardaya:
oh... I'd rather not..

doesn't work for what I want...
[Nexus 5 Original Android Development] Wenzo2:
Hi guys! Here my fisrt color profile!
[MENTION=1363323]vomer[/MENTION] can you add this?

https://drive.google.com/file/d/0B_0L4lSVQUQMZjVUOFJuLUZ0VlU/edit?usp=sharing
[Nexus 5 Original Android Development] aavvaallooss:
Maybe PVS 0???
[Nexus 5 Original Android Development] sordna:
If you cannot undervolt reliably that means your voltage is already optimized as much as possible. You are at the hardware's limit, so be happy that you don't need to apply custom undervolt settings. You are already where you need to be, so don't undervolt.

You need to look at other settings to save more battery.
[Nexus 5 Original Android Development] granets:
So far mag01's profile is the most accurate one of them all.

Here is a link to all the charts [MENTION=4860519]Tzfardaya[/MENTION] has done as of this moment. I'll add more when he is done making them :)

https://docs.google.com/spreadsheet/pub?key=0Al63fQ5qe1q9dEMxYnVFMDlLS19iWmlCWEVCMVM0OGc&output=html

EDIT: This is still a work in progress. Not all the data is in the charts, and not all profiles are done.
[Nexus 5 Original Android Development] romgnascher:
It was 100% reproducible when I was on r37 ... works fine on r36.

I'd be happy to get you a logcat, but I've never done it ... point me to a how-to?

---------- Post added at 01:24 PM ---------- Previous post was at 01:21 PM ----------

My guess is that while you may not have touched bluetooth directly, perhaps you've fiddled with something bluetooth relies upon?
[Nexus 5 Original Android Development] rongregoryred:
Me too. :(
[Nexus 5 Original Android Development] floepie:
Dbolot is very nice to my eyes. It seems very close to stock and isn't as cold as some of the others mentioned.
[Nexus 5 Original Android Development] suchevent:
[MENTION=4860519]Tzfardaya[/MENTION] I just wanted to say thanks for analyzing the color profiles. I find your findings quite informative and useful. I'm sure others find them useful as well. :good:
[Nexus 5 Original Android Development] romgnascher:
Ok ... so I downoaded alogcat and pastebin for android ... flashed back to r37 ... all ready to once-and-for-all get you a logcat of bluetooth blues.

Got my device in-hand, turn on my bluetooth, waiting for it to not to connect ... and ... Mr. Murphy intervened and it works as expected. :( :) :rolleyes:

I'll stay on r37 and If it does in fact happen again, I am now equipped to get you a logcat ... odd.
[Nexus 5 Original Android Development] Tzfardaya:
see, logs and it never happened.. :p