yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] :
On purity as well, didn't check with stock hmm anyone else have this issue?
[Nexus 5 Original Android Development] silvan g:
Works here with paranoid Android beta 3 and fk r32

Edit: using root Explorer
[Nexus 5 Original Android Development] Fluidification:
I'm on cataclysm + art.

I wiped the pebble app's data, and it's working consistently now. Let's see if it acts up again
[Nexus 5 Original Android Development] cdx47:
That's interesting! I was doing it the opposite way. Leaving it at 450 then underclocking cpu and gpu for the games. If there was a problem then I would use a different setup where the gpu stayed at 450 but the cpu was still underclocked. Didn't hit many problems though. I assume your logic is based on the gpu using less power than the cpu for a game. My logic was that the games I played simply didn't need 450 gpu so underclocking both could save more battery. I may now simply underclocking both cpu and gpu and see what happens.
[Nexus 5 Original Android Development] JNewms:
Not being able to mount the system as RW has nothing to do with the kernel. It's something on the user space side. I just double checked and had no issue. Using root explorer.

---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------

There's no need to use any benchmarking app. All that matters is how the device performs while you're using it. The only time Franco asked me to benchmark is when he was just getting hotplug put into the kernel. The app he had me use is quadrant. But now there is really no use in benchmarking

---------- Post added at 06:33 PM ---------- Previous post was at 06:29 PM ----------

Yea, you were doing it backwards. ? If you want to under clock the GPU and set up per app modes, you should have UC for all of your normal tasks and then raise the clock for gaming.
[Nexus 5 Original Android Development] Krunk83:
My color profile will not load on boot. I have the bookmark checked for that option. I'm using the beta fku app and test 33. Any ideas? I've already tried clearing app data.
[Nexus 5 Original Android Development] JNewms:
It loads on boot. It doesn't happen immediately. You have to wait for the SU toast to appear, and then turn your screen off and on again.
[Nexus 5 Original Android Development] Krunk83:
Been waiting two hours. That long enough?
[Nexus 5 Original Android Development] PresidentMcCain:
Also note that there's a bug in FKU Color Tweaker and the standalone Display Control app in that if you check Set On Boot before loading a profile, it will not set the desired profile on boot.
[Nexus 5 Original Android Development] Empty Hand:
I've seen people talking about the pebble and connection issues with r33v3. I am having bluetooth connection issues in my car that don't exist with r32. After playing music, I have issues making calls. Doesn't happen every time though.
[Nexus 5 Original Android Development] JNewms:
Lol. Yep. Not sure how you did your setup, but I'm on the latest beta and test 3 and it loads every time.

Did you do like Mr McCain said and load the profile before setting it on boot?
[Nexus 5 Original Android Development] EarlZ:
Same with me, I thought I was the only one having that issue.. Can you also check if Enabling USB fastcharge and disabling logcat will apply on boot on your end.. if we have the very same issue then just maybe Franco can look into it.
[Nexus 5 Original Android Development] JNewms:
I don't mess with fast charge so I'm not sure about that option, but disabling logcat is applying on boot just fine.

In regards to your issue with gamma applying on boot. If it was something with the app that was wrong, everyone would be experiencing it.

I'm wondering something. What ROM are both of you guys using? I'm curious to what similarities you have with you setups. It could be something there causing you issues.
[Nexus 5 Original Android Development] EarlZ:
Stock rom
[Nexus 5 Original Android Development] JNewms:
Hmmm, well then, I think that rules out the ROM being the issue.

Try clearing FKU app data, then reboot. Set your color profile and then check set on boot AFTER you've selected your profile. Then reboot again and just let your phone sit until after all of the SU toasts. Then screen off and then on.
[Nexus 5 Original Android Development] EarlZ:
I've already tried that, I have the same issue with USB fastcharge and logcat. I've even reinstalled the app.
[Nexus 5 Original Android Development] absoluterebirth:
what changes would i have to make if i'm going to another kernel? reflashing my rom seems like a lot of hassle
[Nexus 5 Original Android Development] JNewms:
Hmm, OK, I'm not really sure what the issue is then. I can't log anything since I don't have that problem.

I'll continue to think about it, if I have anymore ideas I'll let you know.
[Nexus 5 Original Android Development] EarlZ:
Please do, you could also drop me a PM or just quote one of my posts so I can see the notification. I also have Xposed framework if that matters but I've tried disabling all the modules on boot but it does not help.
[Nexus 5 Original Android Development] Enddo:
no, he shouldn't. i doubt most games even need the full 450MHz clock. the whole point of underclocking the CPU and GPU during gaming is to save battery and keep the heat down

it's like im in the twilight zone all of a sudden. go ~400 pages back and you'll hear EVERYONE here talking about underclocking the CPU and GPU for gaming(like PvZ2 and tapped out)

---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------

are you 100% positive you have superSU installed and it is giving root privileges to FKU and/or the color display app
[Nexus 5 Original Android Development] EarlZ:
yes, 100% positive. I doubt the settings would even apply if you dont have SU.
[Nexus 5 Original Android Development] JNewms:
He doesn't necessarily have to be at 450, but yes, for gaming its better to have the GPU clocked higher. If it's a more graphically intensive game 450 would actually be ideal. Keeping the GPU too low on intense games will lead to the posts where people say this kernel lags in games.

I don't need to go back all those pages, I've been in this thread from the beginning.
[Nexus 5 Original Android Development] jb0ne:
I still haven't seen a response to this...would sure love to know. There are characters in that field which aren't on the keypad yet people are somehow setting it.
[Nexus 5 Original Android Development] JNewms:
He was referring to SuperSU. Not Super user. You need to be on Chain fire's super SU in order for everything to work correctly.
[Nexus 5 Original Android Development] Enddo:
it's like we're going in circles lol
[Nexus 5 Original Android Development] Krunk83:
That was it. Thanks.
[Nexus 5 Original Android Development] EarlZ:
Yes I have SuperSU, I didnt even realize SuperSU and SU are different, I've been using SuperSU way back.

Ive also noticed a bug on per app mode, at rare times it will not revert back to normal mode locking my CPU at 1.6Ghz which is also reflected on the maximum CPU speed, NOT a big deal as theres probably no day to day task that needs more than 1.6Ghz but just reporting.
[Nexus 5 Original Android Development] JNewms:
That show used to blow my mind as a kid. It would always leave me questioning reality. ?
[Nexus 5 Original Android Development] jb0ne:
Have you tried flashing the latest SuperSU? That's where I'd start. Then make sure ES Explorer's root mode is turned on and it asks for root perms...Or check SuperSU's logs.
[Nexus 5 Original Android Development] cdx47:
You are both right and in a round about way so am I. A lot of games simply don't need 450. Total Table Racing in high graphics mode runs totally smooth on 320 with cpu on 1728.
[Nexus 5 Original Android Development] JNewms:
You need to enter them either using shell scripts, or you can edit them through root explorer.
[Nexus 5 Original Android Development] zxyz:
Can someone please tell me the default boost pulse duration? 350000?

Sent from my Nexus 5
[Nexus 5 Original Android Development] Krunk83:
Yeah they both apply on boot.
[Nexus 5 Original Android Development] jb0ne:
And which file would that be?

I assume you'd need to make a startup script that reenters them too or could you enter them, then go into FKU and tick Set on boot flag?
[Nexus 5 Original Android Development] Enddo:
it still holds up today too. puts a lot of current TV writing to shame
[Nexus 5 Original Android Development] peikojose:
Thanks [MENTION=3292224]franciscofranco[/MENTION] today I got 6:30h SOT incredible... At the end I was trying to drain it and was hard he he. I am using some of the battery tweaks posted here.
[Nexus 5 Original Android Development] JNewms:
/sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay

/sys/devices/system/cpu/cpufreq/interactive/target_loads

Once you manually enter the values you want into root explorer, or through ADB, go to FKU and set them on boot.
[Nexus 5 Original Android Development] :
Please post these tweaks haha
[Nexus 5 Original Android Development] peikojose:
It was something like a test. But I didn't feel the phone slow at all.. Used first level at 99... That with the gingerbread man tweaks (I think)

Total time was 17hours.
[Nexus 5 Original Android Development] Techimplant:
Yup..It is
[Nexus 5 Original Android Development] freshiem:
Hi everyone

Hoping this is the right spot to ask, I've been running Franco since r3 with cataclysm with no problems at all. On r32 and suddenly today I cannot receive a call when LTE is preferred for mobile internet (Rogers in Canada). Both Rom & kernel are default and I've confirmed that force LTE is not on with cataclysm.

Any ideas?

Thanks!
[Nexus 5 Original Android Development] JNewms:
Probably something with your carrier.
[Nexus 5 Original Android Development] howtomen:
Guis this kernel is magic. i flashed it and all of the sudden i was able to beat my flappy bird highscore. 10/10. must recommend.

jk but franco been rock solid without hiccups since r32 good work!
[Nexus 5 Original Android Development] freshiem:
I thought so too but as soon as I dropped to 3G and it worked. I then tried in my wife's iPhone 5 (on LTE) & it worked.
[Nexus 5 Original Android Development] JNewms:
OK. It's either the ROM or your APN settings got derped
[Nexus 5 Original Android Development] freshiem:
Thanks I'll check, but would apn settings affect receiving calls?
[Nexus 5 Original Android Development] JNewms:
I am fairly sure they do. But in all honesty, I've never had that issue.
[Nexus 5 Original Android Development] rccar:
Sound quality is noticeably better on r33, more full sound not tingy like before. Love it ?
[Nexus 5 Original Android Development] ptesmoke:
if its of any value. they just lit up LTE in my area with rogers and its good 99% of the time but I've had a few days where I couldn't make calls but LTE data worked...and times when I'd drop all signal when making a call. it always ended up being rogers. I know because my wife runs a different device and different ROM and she had the exact same behavior. sometimes the iPhone aren't affected though...they're special I think and get routed differently.
[Nexus 5 Original Android Development] freshiem:
Thanks, I've had LTE in my area for a few years...I'll see if it "fixes" itself tomorrow. Thanks all!
[Nexus 5 Original Android Development] ptesmoke:
no worries! yea definitely give it a day or so. I reflashed stock before asking if my wife had issues...and it was the carrier....lol doh
[Nexus 5 Original Android Development] freshiem:
I was going to do that but way too lazy tonight!

Thx again!
[Nexus 5 Original Android Development] chw2006:
It appears my colors aren't setting on hard reboots, even after I turn the screen off/on. I'm currently on r32 with the latest beta of FKU. However, they do stick when I do a soft reboot.
[Nexus 5 Original Android Development] Aerowinder:
I'm certain I read other people having issues receiving calls and texts while on LTE. I think it's a KitKat issue?
[Nexus 5 Original Android Development] milanmania2004:
I also having issue making call on LTE, I avoid it by set a tasker profile switch to 2g every time when calling.
[Nexus 5 Original Android Development] brownrt:
The issue in fact was not your kernel. The behavior i was experienced was similar to other verified kernel experiences I've had. The problem was/is with with a titanium backup extraction from an adb backup. I forgot in my post that the issues were occurring after a reboot and not the actual kernel installation. Forgive my hasty judgement.
[Nexus 5 Original Android Development] franciscofranco:
Ok finally found out why the speaker volume is lower on r33 test, its this patch: https://github.com/franciscofranco/hammerhead/commit/b2a2b6abe3e6539fc964526b7cbd4dd308b2303e

Duly noted, thanks for the tip!

Yep, there's a couple of sound patches that improve the overall sound quality/clarity!
[Nexus 5 Original Android Development] freshiem:
The issue isn't making a call, when you make a call, the phone automatically drops to 3g as Rogers doesn't support LTE calling. The problem is receiving calls.
[Nexus 5 Original Android Development] franciscofranco:
Pushed a new r33-test http://192.241.177.15/Nexus5/4.4/tests/boot-test33.img has a couple of fixes etc. Have fun.
[Nexus 5 Original Android Development] yoyoz808:
Yup. Volume is good now. Thanks Franco.
[Nexus 5 Original Android Development] zxyz:
New PA AND test kernel?! :D.

Great weekend.
[Nexus 5 Original Android Development] dannyella:
Can i have a flashable zip of r33 plz?
[Nexus 5 Original Android Development] zukа:
Is there any place to see good settings for battery life to apply in Franco Kernel Updater?

I've searched the thread and read through 20-30 pages of content, and can't find any
[Nexus 5 Original Android Development] aavvaallooss:
Just install and forget
[Nexus 5 Original Android Development] JNewms:
Either use fastboot or flashify. These tests are not released in zips because, well because they're tests. If you don't know your way around ADB and fastboot, and something goes wrong, you could be in real trouble.
[Nexus 5 Original Android Development] blueren:
Um.. my speaker volume is at full while playing via Google play music. I'm in the latest test kernel. :( reboot doesn't fix it. I'm currently using viper fx though, would thus be a culprit?
[Nexus 5 Original Android Development] JNewms:
Only one way to find out. Uninstall it, then reboot and try your volume with play music
[Nexus 5 Original Android Development] blueren:
Apparently not. I disabled viper, disabled dsp manager, rebooted. No juice. However, if I connect earphones, volume control behaves itself. After i unplug the earphone, speakerphone volume control mysteriously starts behaving itself as well.
[Nexus 5 Original Android Development] JNewms:
Very strange. Can you get a log while repeating those steps, so that Franco can see exactly what's going on at the kernel level?
[Nexus 5 Original Android Development] blueren:
Don't want to trouble franco just yet. Interestingly, I believe this is happening only in Google play music .. I play a game and the volume behaves.
[Nexus 5 Original Android Development] jmartino5920:
Franco,

The new test r33 is great in terms of sound. Definitely different from previous test. Got my preferred color profile loaded after resetting FKU app.

No problem with Google Play Music fwiw.

Nexus 5

Stock Android 4.4.2

Franco.kernel r33test4

Tweaked color profile: not sure whose base I used but I love my colors now!

Now if I wasn't too lazy to per app mode tweak to get better battery life while playing graphically intense games...lol...I'm over it. Love the performance too much.

Thanks Franco!

Sent from my Nexus 5
[Nexus 5 Original Android Development] JNewms:
Oh, trust me, grabbing a log will not bother him. If anything, he would need it asap since he will want to officially release 33 as soon as all the bugs are worked out. I would do it, but unfortunately, I don't have my headphones with me.
[Nexus 5 Original Android Development] blueren:
Quickly downloaded other music players. This is only localized to Google play music.

I'm trying to attach a logcat.. I'm the meantime, :

EDIT - LOG - http://pastebin.com/s4BsXkKu

12:43:05.113 W/Binder (696): at com.android.server.power.PowerManagerService.updateWakeLockUids(PowerManagerService.java:839) 01-27 12:43:05.113 W/Binder (696): at android.os.IPowerManager$Stub.onTransact(IPowerManager.java:103) 01-27 12:43:05.113 W/Binder (696): at android.os.Binder.execTransact(Binder.java:404) 01-27 12:43:05.113 W/Binder (696): at dalvik.system.NativeStart.run(Native Method) 01-27 12:43:05.163 E/audio_hw_primary(226): out_set_volume: Could not get ctl for mixer cmd - Compress Playback 9 Volume 01-27 12:43:05.213 E/audio_hw_primary(226): out_set_volume: Could not get ctl for mixer cmd - Compress Playback 9 Volume 01-27 12:43:05.273 E/audio_hw_primary(226): out_set_volume: Could not get ctl for mixer cmd - Compress Playback 9 Volume 01-27 12:43:05.313 V/QcrilMsgTunnelSocket(2256): After reading offset = 0 remaining = 4 countRead = 4
[Nexus 5 Original Android Development] omvir:
Something weird that I am just noticing. That I didn't notice in previous versions. When you're on a CPU heavy app and all cores come online, keep swiping and make sure all the cores are on the touch input frequency. Quickly press the home button and keep swiping the home screens, all 4 cores will stay enabled until you stop swiping. Now stop swiping and wait for CPU 2 and 3 to come offline and now swipe through the home screens and note...stays on 2 cores with the input frequency.
[Nexus 5 Original Android Development] ironjon:
Yes I think the same but same rom, same apps , same scenario with different kernel I have no problems.

I´ll try with different rom and FK for check.

Thanks for your answer!

PD: New beta seems awesome :D
[Nexus 5 Original Android Development] JNewms:
Quick question, are you using SU or SuperSU?
[Nexus 5 Original Android Development] ironjon:
SuperSu :D

Seems that with latest beta r33 this problem is gone :D
[Nexus 5 Original Android Development] franciscofranco:
What rom are you using?

Its not weird per-se. What happens is when the cores are above X frequency (user tweakable soon) my algorithm thinks the cpu is under some kind of load and prevents it to go offline. The only way I can see for that not to happen is for me to only input boost cpu0 and cpu1 instead of boosting all online cpus at any given time.
[Nexus 5 Original Android Development] blueren:
Cm11 23rd jan. Please don't tell me I missed something that you'd mentioned about cm comparability :|
[Nexus 5 Original Android Development] franciscofranco:
Yep, CM has changed audio libs on nightly 22 I believe...
[Nexus 5 Original Android Development] JNewms:
OK.. Start running a log and then attempt to mount your system r/w. I've not had an issue mounting with any version of this kernel. It's gotta be something ROM side.

Edit: just saw your edit. Goof deal. I'm glad you got it worked out.
[Nexus 5 Original Android Development] jb0ne:
It's still in testing so you won't see one for now.

The way I flash the tests is drop it into the fku kernel backup folder, then restore it in fku.
[Nexus 5 Original Android Development] omvir:
Ah okay, thanks :). Would you also allow us to tweak which CPUs are allowed to be affected by input touch as well? Or no? Like only 0, and 1, or all cores.
[Nexus 5 Original Android Development] Bobtehblob:
Same issue on the latest vanir nightly, must be using the same cm code? Anyway to fix this Franco? (Other than change rom :D) Happens on the sound cloud app too.
[Nexus 5 Original Android Development] Kusie:
Question about ambient light sensor bug

Dear franciscofranco,

first of all thanks for your hard work and your N5 Kernel!

I´m not sure if you´re aware of the N5 ambient light sensor bug, which in special situations (and using auto brightness) boosts the brightness to 100% in dim environments. Maybe you can help solve this problem with your kernel?

Please see this post:

http://xdaforums.com/showpost.php?p=49723527&postcount=37

I´m not sure you can do anything about it, but it might be worth a shot.

Thanks,

Kusie
[Nexus 5 Original Android Development] dannyella:
After trying i think all kernels for our device, im back here again.. Never leaving.. :'>
[Nexus 5 Original Android Development] alcurtis93:
That's cute...
[Nexus 5 Original Android Development] Alfablos:
Cool! How much did you guys uc/uv. I'm 1.190 -80mv

I had managed to get -125 but the second time I tried I had a crash... (first time seemed to be ok though)

MOST IMPORTANTLY as far as I know you can't apply the same undervolt to all the clock frequencies, but I don't really know what the algorythm to scale the uv is. Can anybody help?
[Nexus 5 Original Android Development] blueren:
Onoes! Is this a cm mess up? Or will there be some sort of addition/mod at the kernel level from your end?
[Nexus 5 Original Android Development] dannyella:
Somehow viper4android fixes the audio issue in CM..
[Nexus 5 Original Android Development] linqdesires:
Thanks for raising the issue, I'm quite disappointed with ambient light sensor, but I hope we will have it fixed soon. I updated the thread there, after my post
[Nexus 5 Original Android Development] rofik_gitara:
before im so sorry for stupid question,

im from mako and new in hummerhead,

i use franco in mako and run very well but i dont know in hummerhead,

can anyone tell me experience this kernel and issue,

thanks for good respons
[Nexus 5 Original Android Development] Enddo:
its the best kernel i've tried :good:

great with stock settings, even better when you customize it to your liking
[Nexus 5 Original Android Development] k4r70ng:
Is this a normal amount of wakelocks?

https://anonfiles.com/file/33731147ee67557ad8caba5c376fb131
[Nexus 5 Original Android Development] hanschke:
i cannot boot with nightly from today from you and cm11:rolleyes:
[Nexus 5 Original Android Development] Enddo:
looks good to me
[Nexus 5 Original Android Development] armaki:
same here...
[Nexus 5 Original Android Development] rofik_gitara:
any issue?
[Nexus 5 Original Android Development] sirovai:
It's a change that cm do in kernel and configuration, both sides. I switched to purity rom to solve.
[Nexus 5 Original Android Development] Laurentyu1995:
In trying latest r33 and i had 2 reboots. It's good to know that cpu is UV. Now i cleared fku app data to see if without UV i'll have another reboots. By the way here are last_kmsg from both reboots ( i saw there kernel panic ...but I don't know what is useful ) : https://www.dropbox.com/s/ud8sm9xcr3dht9j/last_kmsg

https://www.dropbox.com/s/htjpn5dg01vn08h/last_kmsg_2
[Nexus 5 Original Android Development] whitedragonz83:
Franco said a patch he applied will cause a need for more voltage somewhere, causing 'old' undervolting values to fail. Likely you shouldn't see a problem with normal voltage values.
[Nexus 5 Original Android Development] iPsychoGeek:
So, can i use viper4android with latest r33 test kernel?
[Nexus 5 Original Android Development] jdec529:
Running latest PA beta with latest test kernel and sound issues seem to be fixed on my end. Google music, and notifications are working perfect. Thanks Franco!
[Nexus 5 Original Android Development] Molitro:
Reboot on 33v4:

http://pastie.org/8671948

Anddddd... Another 2 reboots in a row just opening FKU. Last one:

http://pastie.org/8671960
[Nexus 5 Original Android Development] xadidas4lifex:
Ya can not boot 1/27 cm and v32...
[Nexus 5 Original Android Development] Gaussiano:
Same problem here

Enviado desde mi Nexus 5
[Nexus 5 Original Android Development] vomer:
not surpirsing... it's cm... it's always a hit or miss with that ROM since they keep changing $hit every other day lol

yup
[Nexus 5 Original Android Development] Laurentyu1995:
I know that franco said that but maybe not the voltages ( UV ) was the problem and in that last_kmsg maybe he can find something useful....who knows ? I've also played Asphalt 8 to see the performance which is very good.. I hope I'll not get other reboots