yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] franciscofranco:
Nah, that won't happen. Test kernels are pretty rare, and they are aimed to select and power users that actually help me with constructive feedback and are not afraid that their N5 may crash.
[Nexus 5 Original Android Development] Techimplant:
U guys are always testing and modifying and improving different profiles and then checking Gamma every time..Even Dr.Bruce Banner didn't had so much Gamma exposure..look what happened to him :p
[Nexus 5 Original Android Development] thecryof:
Don't make him angry! LOL
[Nexus 5 Original Android Development] franciscofranco:
Pushed a new r33-test to keep ya'll busy for a couple days and to get feedback. http://192.241.177.15/Nexus5/4.4/tests/boot-test33.img

Have fun.
[Nexus 5 Original Android Development] Vaizen:
Don't know if it's throttling or what but when playing heavy games or hungry ones like plants vs Zombies 2 perApp process get killed or so i think, because after closing the game there's no prompt message saying that system returned to normal settings and in fact by looking on FKU it shows that the processor is underclocked as the perApp profile that I use for gaming.
[Nexus 5 Original Android Development] PhantomGamers:
Is this in the next branch or staging?

Thanks for your work! :)
[Nexus 5 Original Android Development] TrainNanpaMaster:
Franco, flashed your brand new boot (33) test, and almost immediately I'm getting hard reboots and force closes. I can barely make it into the actual operating system before I get another reboot. Anyone else having these issues?

Sent from my magical prancing unicorn.
[Nexus 5 Original Android Development] vomer:
Nope all good here! Try flashing again

Sent from my Nexus 7
[Nexus 5 Original Android Development] P.Mobile:
all good here also.. :good: dont kno if its just me but this new test r33 build is running great... my phone feels way smoother.. i normally dont notice a big change but i do now!! dont kno whats in this new test build but my phone loves it!!! :)
[Nexus 5 Original Android Development] aeroseek:
4 cores on full time?

Edit: maybe not
[Nexus 5 Original Android Development] Annihlist:
Hi franco,

I am getting the full volume bug on google music with your latest test build 33 Jan25. Cm nightly 21st Jan.
[Nexus 5 Original Android Development] dwang:
The reboots seem to be because the kernel is automatically overclocking the cpu to 3ghz in certain situations.

Seems to be related to the thermal throttling logic.
[Nexus 5 Original Android Development] P.Mobile:
i just ran quadrant and my cpu is not going near 3GHz mine hits stock 2265ghZ..
[Nexus 5 Original Android Development] dwang:
I think what's happening is when the kernel throttles the max CPU down due to high temp and then when the temp goes back down the kernel increases the max CPU speed, but it doesn't seem to stop at 2.2ghz it goes all the way to 3ghz.
[Nexus 5 Original Android Development] Bobtehblob:
I'm having the same issue on the vanir nightly from the 24th :( Anyone know of a fix? Happens in soundcloud and other apps too
[Nexus 5 Original Android Development] maksud_ans:
How to flash Franco kernel my nexus 5?my mobile rooted and latest cwm and running officially 4.4.2 odex please help
[Nexus 5 Original Android Development] ben_pyett:
easiest way is to download flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify , or Franco's own application https://play.google.com/store/apps/details?id=com.franco.kernel.free
[Nexus 5 Original Android Development] Annihlist:
Enable equaliser temporary to fix.
[Nexus 5 Original Android Development] yoyoz808:
The performance seems great on the latest test kernel but the sound quality on ringtones and everything else is not so great. Can't use the speaker gain if i use this test kernel.
[Nexus 5 Original Android Development] JNewms:
OK. Quick message to everyone reporting problems with the test kernel. Every post so far has been totally unhelpful. This is a test kernel. If you're not providing logs AND steps to reproduce issues, you're not helping. If you don't know how to get logs then stick with the latest official release. This isn't meant to be rude, but test versions are meant to be tested by people willing to contribute logs and help with the development.
[Nexus 5 Original Android Development] dwang:
Never mind, I reflashed the kernel and cleared the fku data and now its fine.
[Nexus 5 Original Android Development] JNewms:
Speaker gain is working perfectly fine. I've just tested it with 4 different settings. No problems with the speaker
[Nexus 5 Original Android Development] melbourne408:
Here is mine
[Nexus 5 Original Android Development] DryaT:
I want to thank you Franco for your great kernel, good work! you are the best!

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] JNewms:
Thanks for the log. Mind sharing what you were doing when you encountered your issue, and what happened? Also, quick tip, Franco prefers logs from pastie.org
[Nexus 5 Original Android Development] yoyoz808:
I know speaker gain works fine. It's just the sound gets distorted now when that wasn't the case before.
[Nexus 5 Original Android Development] Enddo:
he's posting for something different. someone was asking for those results to maybe identify different screen types(maybe like how there's different chip versions). but i could be completely mistaken
[Nexus 5 Original Android Development] JNewms:
OK. I could have misunderstood what he was doing.
[Nexus 5 Original Android Development] drakexpl:
5 hours of screen Yesterday, even my xperia z1 couldnt do this with 3000 mah battery. This is serious madness. Ive bought app because i think its worth to help you since youre first kernel developer who provides true enhancement over stock for me.

Keep up Franco

Wysłane z mojego Nexus 5 przy użyciu Tapatalka
[Nexus 5 Original Android Development] The Gingerbread Man:
Awesome we could be onto it now, this looks about right. JDI I know is a display manufacture they make the nexus 7 2013 display too and I read something about this by supercurio when he was trying to calibrate that screen. It stands for Japan Display Inc http://www.androidauthority.com/jdi-super-bright-full-hd-displays-282810/ . The 1080p is obviously the resolution. The second command gave me panel ID of 5.

We need some more results. Can some more people put this into terminal and copy paste the command into it. Perform a reboot before as terminal is picky sometimes if it wants to work properly.

su

dmesg | grep mdss_dsi_panel_probe

su

dmesg | grep mdss_panel_parse_dt
[Nexus 5 Original Android Development] jb0ne:
Here's mine, same as yours...https://www.dropbox.com/s/v4gi6vkbwjdh1s2/2014-01-25%2010.28.08.png

How do you make the attachment thumbnail inline?

I'm not sure I understand why gamma is "supposed" to be 2.2-2.4; if the colors are all correct and blacks and whites ok per Display Tester, what does it matter what gamma is?
[Nexus 5 Original Android Development] yorici:
Same results:

Panel_id= 5

Panel-name= JDI 1080p...

Lge.rev = rev_11

Stock gamma 1.8/2.0
[Nexus 5 Original Android Development] melbourne408:
My bad.

It was to confirm for the screen types.

Yup, confirmed.

(Everything related to beta's Franco pushes I'll upload the log to pastie and link back here, bed time for me.)
[Nexus 5 Original Android Development] cdx47:
That's also what I found on my panel.
[Nexus 5 Original Android Development] OptimusVDarwin:
stays 300mhz when idle but jumped up on screenshot. And had a random reboot on r33 test.
[Nexus 5 Original Android Development] ironjon:
Here you have

Panel ID: 5

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] sirovai:
I hope that Franco fixes the audio problems with the latest CM11 nightly.

Sent from my Nexus 5 with Tapatalk
[Nexus 5 Original Android Development] jb0ne:
R33v3, UV to 1.7ghz, has rebooted multiple times right after system startup and once on starting antutu with perapp mode set to a higher speed (not sure what since you can't bring up/edit profiles previously created, but I think it was 2.3ghz). It reboots when I run Antutu (yeah I know peoples' oppinion of Antutu, I'm just trying to push the system). Other reboots seem random.

+++++++++++

Actually just re-flashed it and cleared app data in FKU. Went back in and max clock was set to 1ghz (?). Changed it to 2.3ghz, ran antutu again while cat'ing /proc/mksg, got a reboot when I unlocked display. Here's the output:

http://pastie.org/8666293

Actually it reboots frequently just running antutu and there's nothing in kmsg - it just dumps me back to the cmd prompt. I don't know if there's a better way to be getting logs than adb shell; su; cat /proc/kmsg, but there's nothing logged when it reboots - it just reboots.

I ran Antutu once with no per-app settings, max clock 2.3 ghz, got 18000 and no reboot.

Gave it a per-app profile of 2.5ghz and cpu throttle increase to 80C and ran again, no reboot. Here's the newest kmsg:

http://pastie.org/8666308

If there's a better way to collect a log please let me know.

Also possible bug in (beta) FKU: I made a per-app setting then tried to delete it. It said "bye bye per app mode!" or something similar, but the mode is still listed under my saved modes and still assigned to my app.
[Nexus 5 Original Android Development] Kaydin:
The "cores_on_touch" parameter is gone in the new 33 test. I guess that's the cause of all cores running.
[Nexus 5 Original Android Development] Pretoriano80:
Same results here.Also the stock gamma is 1.8 - 2.0.

Honestly it looks that so far everybody gets the same result, it's odd, considering the different results we have here with various colour profiles (e.s. even if my display seems to be exactly as yorici's, his colour profiles are way off for me).

Maybe we should really start a new thread and build a database with stock values vs. some of the best profiles (a poll could help as with this).

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] myfluxi:
The gamma interface does a hardware check, it will error out on anything else than board revision r11*. This is because we don't know if the command offsets of our panel on command table would maybe change in future revisions, posssibly leading to unpredictable results.

There are two variations, r11 and r11j. Both use JDI panels with the the same structure of command tables but different values. r11's name is "JDI 1080p command mode dsi panel", r11j's is "JDI(J1) 1080p command mode dsi panel".

https://github.com/myfluxi/kernel_m...8974-hammerhead/msm8974-hammerhead-panel.dtsi
[Nexus 5 Original Android Development] Technecium:
Stop that crazy talk. That would make too much sense.

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] daniel84cs:
The last leaves R33 test all cores turned on and consumes far more than the R25.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] ricey1986:
All cores running only lasted for a couple of minutes after first flash now running on 2 cores at 300mhz when idle
[Nexus 5 Original Android Development] Hatshipuh:
Piereligio v4 used to give me perfect colors at home lighting and over night I found it the perfect setting, but when leaving the house and switching the phone on outside I find it to have a blue tint again.

So I'm back to mag01 which gave me perfect whites again.

Funny since after using Piereligio v4 after a while I found mag01 to have a yellow tint, but I guess I like warmer calibration more.

Tap-a-talked from my Nexus 5
[Nexus 5 Original Android Development] daniel84cs:
I love this kernel, I achieved the best performance in terms of battery life. The only thing I "do not like" the vibration is set by default to 100, many problems have nexus to the motor vibration, amplifying the problem increases. Despite my not suffer from this problem amplified 100 is too strong and makes it noisy.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] ironjon:
Yes I agree, I always change the value at 70

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] droid@xda:
You always have option to lower it according to your preference. What if its locked at say 63 by default like in stock kernel? What people will do if they want to increase then?

---------- Post added at 07:49 PM ---------- Previous post was at 07:43 PM ----------

Using r33 latest build from last 5hrs. Everything all right till now. I notice more battery backup but it might be a placebo. Currently at 84% battery with 4hr 41min since last charge and 55min SOT. Moderate use, mainly tapatalk and browsing sessions.

Performance is unaffected and still a buttery smooth. Have 2 cores online in normal usages like in previous versions.
[Nexus 5 Original Android Development] franciscofranco:
Staging!

So what?

As for the reboot logs or didn't happen.

I hope CM didn't go crazy on CAF again by merging their latest hardware_audio_qcom branch. Here we go again...

I tried to reproduce it, but no dice... thanks for the detailed info though.

No... what the frakk are you both talking about? Cores are behaving normally as they ever did -.-
[Nexus 5 Original Android Development] Kaydin:
No... what the frakk are you both talking about? Cores are behaving normally as they ever did -.-[/QUOTE]

Cleared FKU data and reflashed. Works as intended, now. Thanks!
[Nexus 5 Original Android Development] daniel84cs:
Even on my N5 regularly uses 2 cores, had to settle the kernel. For what concerns the vibration I would leave 63 as default, it is so easy to increase or decrease the value in any kernel controll application.....

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Kaydin:
[/QUOTE=Kaydin;49752082]No... what the frakk are you both talking about? Cores are behaving normally as they ever did -.-[/QUOTE]

Cleared FKU data and reflashed. Works as intended, now. Thanks!

****, sorry for double post. Tapatalk acting weird.
[Nexus 5 Original Android Development] Laurentyu1995:
Latest test of r33 includes OC and UV ? Thanks !
[Nexus 5 Original Android Development] fbf2201:
No! You're welcome.
[Nexus 5 Original Android Development] franciscofranco:
echo X > /sys/devices/virtual/timed_output/amp

It does.
[Nexus 5 Original Android Development] Technecium:
FYI: Latest r33 test seems to handle audio better. On previous versions, after listening to 7-8 hours of music with PowerAmp and the device on Airplane Mode, BBS CPU States would show 6-7 hrs at 300mhz and 1-1.5 hrs at 1.5/1.7ghz. So I would throttle the cpu with Tasker to keep it from running amok.

I just tested for an hour and it didn't move from 300mhz. I'll check for certain tonight with my normal 7-8 hrs of listening and let you know how it works out.

Thanks again for your time and energy!

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] sam razzy:
I'm on to the party... Sold Nexus4 n Boughy Nexus 5,,,
[Nexus 5 Original Android Development] franciscofranco:
You're comparing the latest r33 test image to r32? Because that assessment is correct, merged commits that push our sound chip codec driver to its nearly latest stage and some commits to the dsp driver that decrease power consumption.
[Nexus 5 Original Android Development] DerItaliener:
Freezed and rebooted after flashing 3rd r33test, rebooting and unlocking the screen. http://pastebin.com/k1LXya3p

No clue why, as I didn't touch any settings since at least r30.

---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------

Kernel Panic directly after, when I switched off WLAN. http://pastebin.com/Rq0f0e92
[Nexus 5 Original Android Development] Smallsmx3:
Any reason why notification sound is so low on new test kernel?
[Nexus 5 Original Android Development] sirovai:
I switched to Purity rom and solved this problem. I can't keep my N5 without Franco
[Nexus 5 Original Android Development] franciscofranco:
That's weird. The log was also weird. One of the logs shown an error on the dsp driver, so I'll tackle there, thanks.
[Nexus 5 Original Android Development] whitedragonz83:
Is a setting missing for core online under the hotplug section on r33?

Noticed 4 cores always online also.

Never mind the always online part... Took a few minutes, but now just 2 cores online when idle.
[Nexus 5 Original Android Development] DerItaliener:
I'm clearing FKU Data now and see how it behaves, maybe just any leftover settings from previous versions. Don't know if it's an important Detail, but I'm on Purity ROM.

edit : seems to have solved the problem until now. No reboots yet.
[Nexus 5 Original Android Development] cobyman7035:
New fku get rid of apply settings bug?

Via my NeXus™ 7 FHD on Tapatalk⁴ Pro
[Nexus 5 Original Android Development] Technecium:
Yes, r32 and earlier. If I didn't choke the cpu I would always get the higher cpu states and lose over 35% battery. Limiting the cpu to 300mhz would result in about 20% battery loss. In tonight's test I'm not going to limit the cpu and see if it can stay at 300mhz and not lose more than 20% battery.

I'll post the results when I get up.

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] The Gingerbread Man:
So its a waste of time trying to base recommended colour profiles for different screens? Unless r11 is non yellow tinted screen and r11j is yellowish tinted. But still peoples gamma results are all varying so much using a profile which works really well on one persons screen and gamma a few points difference, unless that variance is dependent on the screen brightness it was tested with. Hmmm. Do you think its worth while further exploring if we can get some recommend profiles together for the two different screen types or just let people have free choice as things are now?
[Nexus 5 Original Android Development] ChazzMatt:
Color Control apply bug

I think he's talking about the Color Control "apply, share, delete" box staying up no matter how many times you hit apply. Or even if you turn off/turn

on the screen. It just stays there until you hit another tab. We discussed it earlier...and you said you would look into it.

To explain better, in the screenshot below, I've already hit apply twice AND turned off/turned on the screen. So, why is it still there? :) Were the settings not applied successfully? :confused: It shouldn't be "persistent" after hitting "apply". Makes you think apply was not actually applied... Seems like a bug? :)

Plus, the pop up notice to turn off/turn on the screen is very brief. Can't even get a screen shot of that. :) That notice should be persistent until turning off/turning on the screen.
[Nexus 5 Original Android Development] franciscofranco:
Ah that. His post was so vague I could not understand.
[Nexus 5 Original Android Development] Ben36:
It's mad how different all the screen displays are!
[Nexus 5 Original Android Development] ChazzMatt:
Piereligio_TrueRGBv4.1 starts out with 33 whitepoint. Change to 32 whitepoint and Piereligio_TrueRGBv4.1 gamma improves to 2.2 - 2.3. As stock color profile from Google has 32 whitepoint, there's no harm in going to that.

Changing Piereligio_TrueRGBv4.1 to 31 whitepoint then gives me 2.3 - 2.4. Just sayin... I'm not recommending that for anyone, it's up to you.

But there should be no controversy changing to 32 whitepoint.
[Nexus 5 Original Android Development] chikimonke:
Just adding to the info.
[Nexus 5 Original Android Development] anaglich:
Love the color. Looks amazing! I just fell in love with this phone.
[Nexus 5 Original Android Development] Neejay:
Ha, cool. I never realized that. Thanks, very convenient.
[Nexus 5 Original Android Development] Revthejedi:
App looks great, hopefully there are no SODs I need my alarm for class.
[Nexus 5 Original Android Development] Neejay:
Yeah, the colors were the first thing noticed. Looks great!
[Nexus 5 Original Android Development] ptesmoke:
haha this is my only fear as well! the contrast looks awesome francisco! Black's actually look real real good :)
[Nexus 5 Original Android Development] PresidentMcCain:
Fantastic color tweaks. Makes the screen look that much closer to the higher priced phones.

Will be testing the battery life, and stability, etc.
[Nexus 5 Original Android Development] norcalsfinest:
What phones are you comparing it to? I came from an S4 and the N5 screen was hands down better than that right out the box.

Franco, you're an animal. Thanks for the hard work man, now my N5 can enjoy the same great features my Nexus 7 FHD does and my Nexus 7 did before that
[Nexus 5 Original Android Development] Zainiak:
Colors are cooler (LOVE IT) and seems smoother. But that could be because of the reboot

---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
[Nexus 5 Original Android Development] jenkem110:
"It'll make your whites, whiter" Like the new colors hehe
[Nexus 5 Original Android Development] anaglich:
Never will, thanks to the washed out viewing angle issue, but you're right that this is one step closer.
[Nexus 5 Original Android Development] Bobtehblob:
Is the max freq returning to normal for you guys? Seems to throttle for me and then never come back up again...
[Nexus 5 Original Android Development] franciscofranco:
r9 or r10?
[Nexus 5 Original Android Development] Habs69M:
Is it meant to be set at default 2265 mhz for max cpu freq? Cause it was lower on r9 , love the colors by the way :)

Sent from my Nexus 7 (2013)
[Nexus 5 Original Android Development] Bobtehblob:
R10

Throttle temp is set to 90 degrees as well so there's no way it should be throttling that hard.
[Nexus 5 Original Android Development] anaglich:
This is stupid picky, but a bug nonetheless - I have noticed that the swipe to unlock radial animation lags at the end without fail every time I turn on the screen.
[Nexus 5 Original Android Development] Dolphin Trainer:
Another vote for the new colour changes; fantastic! I don't know if it's placebo or not, but even the viewing angles look way better.

Franco thanks so much for your work, your efforts are half the reason I got a Nexus 5... and I am so glad I did now.
[Nexus 5 Original Android Development] vomer:
New colours look nice franco. Some much needed contrast :good:

---------- Post added at 11:08 PM ---------- Previous post was at 11:07 PM ----------

I think its an app bug in FKU beta. Normal version does not do that...
[Nexus 5 Original Android Development] cobyman7035:
do we need to do color calibration on a nexus 5?

Via my NeXus 5 on Tapatalk⁴
[Nexus 5 Original Android Development] digweed4me:
How about benchmarks is it on par with LG g2 on r10? I get lousy 7000 on S800 cpu
[Nexus 5 Original Android Development] ptesmoke:
huh? mines at 75 degrees....
[Nexus 5 Original Android Development] ChazzMatt:
32 whitepoint is the same as stock color profile, so why not? If you can adjust colors to get at least 2.22 - 2.4 gamma and keep 32 whitepoint at the same time, yes that's desirable. :)

Anything less than 2.22 gamma is what's not desirable. :)
[Nexus 5 Original Android Development] vomer:
Thanks for the head's up! I incuded it in the zip but forgot the individual upload. Done now :good:
[Nexus 5 Original Android Development] c_brown93:
Sound seems to be lower on new test r33. Running stock 4.4.2. Reverted to r32 and sound increased back and sounded normal again.
[Nexus 5 Original Android Development] sam razzy:
Friends I'm new to nexus 5 party from Nexus4 so I would like to know whether my Franco kernel has USb otg support ? When I open change log in op it gives some error saying the link isn't working.
[Nexus 5 Original Android Development] martinezma99:
[MENTION=5062505]finr0d[/MENTION] We have the same exact screen. I get 2.2 across the board on Ben36 profile and 2.0 across the board on Pierelegio_trueRGBv4.1
[Nexus 5 Original Android Development] chikimonke:
It is supported, just need to use something like Stickmount I believe.