yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] abra5umente:
Just drove for 40 minutes with bluetooth audio. It appears to be intermittent?
[Nexus 5 Original Android Development] EvgeniX:
No

I have good sound but with strange clicks every 5-10 sec when I use phone... When I do not touch phone for 5-10 min... Click stops and I have good BT audio...
[Nexus 5 Original Android Development] abra5umente:
That's not what mine does... I might have to have a look at the device drivers tonight and see what I can find. I'll post my findings.
[Nexus 5 Original Android Development] pradhyu69:
Screen flickering have gotten worst after flashing new version after applying color screen....so flashed back to r33..please fix it...I'm on kangkat ROM.
[Nexus 5 Original Android Development] harshalkatakia:
Running -50 now. No reboots yet, but strange how on r34 I can't UV so much.
[Nexus 5 Original Android Development] harshalkatakia:
Got this error, any idea what it could be? Has happened in the past also. Home screen is unclickable, only soft buttons work.
[Nexus 5 Original Android Development] 44-RON:
I had the same problem when I was on stock kernel, non rooted, locked bootloader.

So I think it's not the kernels fault, just some 4.4.2 bug.

Back then, a simple reboot solved it for me.
[Nexus 5 Original Android Development] Enddo:
this happened with r33 too if i recall correctly, had something to do with CAF commits. but if you undervolt and try to submit a bug report no one will care unless it can be replicated with stock voltages too
[Nexus 5 Original Android Development] harshalkatakia:
I'll run at stock voltages now to see if I can replicate it.How do you see from the logs what error it is? How does one know the reboot is because of undervolting?
[Nexus 5 Original Android Development] theowner997:
I am from Greece , half of the Google Services in Greece are not available, neither google play for phones neither play gift cards :/ I wish Google had paysafe payment at least, it's the only pre-paid card I can get here. Nevermind, lets stay on-topic guys :) We don't want to ruin the thread :P
[Nexus 5 Original Android Development] Enddo:
i don't, that's why i asked. franco might know certain error messages that happen from undervolting but i don't know that much about it. it's just the first line of defense when troubleshooting errors like that
[Nexus 5 Original Android Development] spyros.giotakis:
Most probably, that is why r32 is fine with me.
[Nexus 5 Original Android Development] aow1980:
You can try the free version of trickster mod from the play store. That should allow you to change some of the settings. Also check out the fku lounge forium topic. They may have more info on app you can use.
[Nexus 5 Original Android Development] blueren:
What does go_highspeed_load do? Sorry to say it but the micro stutters are still acting up on v34 :( it is absolutely unacceptable to have stutters on a nexus no matter what :(

EDIT:

Reducing go_highspeed_load from 90 to 85 brings a decent amount of butter back. I'd like to know how this affects the battery.

Sent from my Nexus 5
[Nexus 5 Original Android Development] hanschke:
much more important is cm support :p
[Nexus 5 Original Android Development] Wenzo2:
Set boostpulse duration to 1000000. Or use ART! I love it...

But probabily is only placebo... There aren't any change in r34... Only fix
[Nexus 5 Original Android Development] blueren:
Whatever context you're referring to, cm support is dead and buried

Sent from my Nexus 5
[Nexus 5 Original Android Development] gee2012:
Look here https://www.google.nl/search?q=go_h...7&sourceid=chrome&espv=210&es_sm=122&ie=UTF-8 for more info and use Google next time ;)
[Nexus 5 Original Android Development] blueren:
What is this "Google" you speak of? Is it a new iteration of toaster? :)

Sent from my Nexus 5

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

Hmm.. worth a shot. But I'm just trying to make sure decreasing go high speed thing I did now isn't another placebo. Art.. I'm willing to wait till Google is actually fully ready with it :)

Sent from my Nexus 5
[Nexus 5 Original Android Development] Wenzo2:
The hispeed freq is 1,4 GHz.. And boostpulse is 1,5 GHz.. So if you set a 1000000 instead 500000 for boostpulse duration you're phone stay at 1,5 GHz for much time... Hispeed freq probabily work only when you don't touch the screen.
[Nexus 5 Original Android Development] whoRichard:
Just auto flashed r34, damn that was fast. How is battery life running the same settings for everyone?
[Nexus 5 Original Android Development] Sygmasf:
Can someone give me a briefly update on the r34 changelog?
[Nexus 5 Original Android Development] gee2012:
Dude realy, its posted in the OP under Changelog :silly:
[Nexus 5 Original Android Development] blueren:
Bug Fix! No more display flickering after applying a color profile, but now you have to screen off/on to apply the new colors

Improvement! New feature that improves Auto-Brightness experience

Improvement! Merged a feature from upstream Linux to make the system use power efficient workqueues for several systems which will save some battery in the long run

Improvement! Other misc patches, improvements, fixes and merges - check my github
[Nexus 5 Original Android Development] ArtieQ:
I'm seeing a clear difference in battery life between r33 and r34, r34 being the better one of course.
[Nexus 5 Original Android Development] Sygmasf:
damn, i believed that in the Franco's minimal OP there was not a changelog section, pardon ^^
[Nexus 5 Original Android Development] gee2012:
Oke, go on and sin no more :D
[Nexus 5 Original Android Development] Tzfardaya:
each version of the kernel seems to have different tolerances for undervolting... either don't uv or reset and retest your uv settings with each kernel

you can tweak the kernel with scripts, tasker, trickster mod, etc etc...

Google? isn't that what gets you in trouble with the ladies? Googling them too obviously?

Lowering the go high speed thing makes it easier for the phone to ramp up the cpu freq, again a slight trade of of battery vs performance
[Nexus 5 Original Android Development] The Gingerbread Man:
In post 2 in my learner lounge thread iv explained briefly the basic functions of the interactive governor.
[Nexus 5 Original Android Development] Tzfardaya:
but but, that means people have to look for it themselves, not just sit here and wait for a spoon... :P

---------- Post added at 08:57 AM ---------- Previous post was at 08:52 AM ----------

what type of clicking, if it's what I think it is... and only when you use your phone (to send/receive data/phone calls) then it's probably just the phones radios creating interference on your vehicles speakers (those nice long speaker wires can act as antenna)
[Nexus 5 Original Android Development] amphi66:
Try Vomer's init.d script to modify Kernel settings
[Nexus 5 Original Android Development] dannyella:
Hello, all

Inside FKU>CPU Manager> Hotplug, there is no option there. I would like to enable hotplug but nothing is there..why??
[Nexus 5 Original Android Development] Tzfardaya:
iirc those tunables are only in the fku beta app atm...

hotplug is enabled anyways, it's just some more tunables that franco has opened up, in the next fku version (or current beta)
[Nexus 5 Original Android Development] blueren:
Hmm.. with 1000000, it's still there. Lurking around here n there. Especially in g+ / hangouts / app open close animations. :( this never used to be there in any of the earlier kernel versions.. think it cropped up in r33 onwards

Sent from my Nexus 5
[Nexus 5 Original Android Development] The Gingerbread Man:
In my learner longe thread iv explained about how interactive works so instead of sounding sad go and use the information provided to improve your experience and let us know how you get on later :)
[Nexus 5 Original Android Development] Tzfardaya:
stutters can be caused by to low a cpu freq, changing the length of time it's held at that speed won't help. :P

just from curiosity, are you undervolting? or lowering the gpu max freq?
[Nexus 5 Original Android Development] dannyella:
Is there a setting to have only one core online when phone idling like the way it is on cm??
[Nexus 5 Original Android Development] blueren:
No. No uc /uv whatsoever. Stock fk settings. And out of curiosity, set the min freq to 2gigz. No stutters at all. Boom! They're gone. But.. 2gigz is overkill, obviously.

Hasn't anyone noticed the stutters at all? I'm sure it can't be just me

Sent from my Nexus 5
[Nexus 5 Original Android Development] gee2012:
Yup, especialy when doing Quadrant tests when going around the corner in the `hall way`.
[Nexus 5 Original Android Development] Savant:
No and Franco wanted to leave it like stock since you get the same battery with 2 cores anyway.
[Nexus 5 Original Android Development] Wenzo2:
If you don't want try art... Try this http://xdaforums.com/showthread.php?t=2537299
[Nexus 5 Original Android Development] justibasa:
Just so everyone knows and we hopefully won't get questions, Carbon Rom has moved to caf. Time to look for a new Rom.

Don't like me.......BITE ME!!!
[Nexus 5 Original Android Development] whitedragonz83:
"2 Corz always onlinez Y? Quad core specific devices only

It is normal for 2 cores to always be online, its like that by Franco's design. It is meant to save battery in the long run as turning cores off and on again all the time is taxing on the battery according to Franco. It also helps keeps things running smoother. Cores 3 + 4 will activate when system load requirements are met."

http://xdaforums.com/showthread.php?t=2532422
[Nexus 5 Original Android Development] Enddo:
i've heard CM kernel beats out franco for battery life. either due to more CAF commits or because of the 1 core vs 2 core setup.
[Nexus 5 Original Android Development] Savant:
I tried cm kernel before and to me if its laggy compared to Franco and elemental. I tried hells kernel and yielded better results than cm kernel. It may be the commits or the cores but, either way wasn't a fan of stock cm kernel.
[Nexus 5 Original Android Development] Tzfardaya:
of course they're gone at 2ghz, because at that point the cpu freq is up enough to compensate... since you seem to notice them most prominently, why not run a few tests for us..

set min/max freq to the same, (starting at 2ghz) check for stutters, step both min/max down one, check for stutters again, keep stepping down until you find where the stutters start.

Then set the input boost and high speed freq to that and check for stutters again, if they're still gone let us know what freq you found.
[Nexus 5 Original Android Development] dannyella:
No it isn't..CM kernel was great for me...best so far...let me see how franco kernel performs.
[Nexus 5 Original Android Development] Tzfardaya:
I'm confused...

If a rom works for you , why wander off looking for others?
[Nexus 5 Original Android Development] zubsz:
usb otg issue

I don't know how to report this, but r34 seems to stop my usb otg working. Reverted back to r33 and it's working fine.
[Nexus 5 Original Android Development] Tzfardaya:
not working with mice, keyboard, or mass storage?

which rom? I was having issues with otg on the various test 33's but it was because my rom was messed up, I did a clean reflash and now no more issues with otg on r33 or r34
[Nexus 5 Original Android Development] dannyella:
Kernel worked for me..Not ROM..:p
[Nexus 5 Original Android Development] BTT8:
Anyone here still use cataclysm? I feel like with every update to Franco, the kernel becomes less compatible with cataclysm due to cataclysm not being updated in a while...
[Nexus 5 Original Android Development] ArtieQ:
I do, and I've noticed that Chrome crashes alot (just closes down) after installing r34, somehow my device feels slower as well.
[Nexus 5 Original Android Development] vomer:
I don't think its becoming "less compatible". Try another ROM though since that one seems to have stalled development.

Sent from my Nexus 7
[Nexus 5 Original Android Development] BTT8:
Same here actually...

I think it may be time to leave cataclysm... :(
[Nexus 5 Original Android Development] granets:
Guys, anyone got a solution to the right channel clipping? I can't up volume on my phone above what should be stock. everything more that that results in skipping or muting of the right channel. Can someone please help? issue is present on r33 and r34.
[Nexus 5 Original Android Development] Tzfardaya:
only solution so far is to NOT RAISE THE VOLUME... :P Like your own post said...
[Nexus 5 Original Android Development] granets:
that defeats the purpose of having a custom kernel with volume boost. anything else I can do?
[Nexus 5 Original Android Development] Tzfardaya:
as I said... that's the only solution found so far...
[Nexus 5 Original Android Development] granets:
any idea if franco is looking into the issue?
[Nexus 5 Original Android Development] Tzfardaya:
well, we know he's not looking into it this weekend... he's out making time with his gf.

he knows about it, but as to any possible solutions, he's been silent so far.
[Nexus 5 Original Android Development] benthian89:
I jumped ship from cataclysm to slimkat because I needed the FLAC fix.

And I chose slimkat because it's compatible with franco =)

Oh and trust me, you will love the implementation of recents in slimkat
[Nexus 5 Original Android Development] Spl4tt:
I don't have any problems with r33 on cataclysm.. I don't think r34 would change that
[Nexus 5 Original Android Development] Tzfardaya:
then don't change... if others find it lacking, let them make the change... :P
[Nexus 5 Original Android Development] benthian89:
The FLAC issue is in the FLAC libraries used by Android, nothing to do with kernel.
[Nexus 5 Original Android Development] caalca:
Best gamma profile I have seen. Try it. If somebody knows another good profile please make me know :)
[Nexus 5 Original Android Development] ArtieQ:
I may as well ask here, is it difficult changing ROMs? Does a backup in recovery save everything such as apps installed, settings and more? I would hate going through the hazzle of installing and setting everything up again..
[Nexus 5 Original Android Development] harshalkatakia:
Try increasing headphone gain and decrease the volume level by 2 levels. See if that works.
[Nexus 5 Original Android Development] bigmem:
The only thing you can really do is revert to stock or use r32, its the newest kernel that franco didn't incorporate audio and media patches me such. The extra additions for me are what messed up the kernel for redraws, sound issues and reboots when disconnecting from casting. R32 by ear the most stable and usable all round with amazing battery life.
[Nexus 5 Original Android Development] blueren:
That makes perfect sense. :)
[Nexus 5 Original Android Development] harshalkatakia:
The phone seems to be warming up with r34. CPU stats show Deep sleep and 300MHz mainly. Max set by me is 960Mhz.
[Nexus 5 Original Android Development] zubsz:
Stock rom.
[Nexus 5 Original Android Development] blueren:
Nice! This is new to me. Gonna give this a shot in sometime. Although, just wanted to confirm, does PA (the latest one) have these bionic patches?
[Nexus 5 Original Android Development] Wenzo2:
Yep... If you're on pa install only dalvik optimised
[Nexus 5 Original Android Development] yorici:
Hi,

Can anyone perform some tests for me? I need to know if some things are general or display specific.

Steps to do:

Get the Faux App

Unzip zip file from attachments with a file browser. (For example: ES File Explorer)

Open up the image (from attachments) with QuickPic

Change White Point with Faux App to 20

Adjust values 8,11,14 in such a way that they match the background of the image

Note values

Change White Point with Faux App to 40

Adjust values 8,11,14 in such a way that they match the background of the image

Note values

Change White Point with Faux App to 60

Adjust values 8,11,14 in such a way that they match the background of the image

Note values

So you end up with 3x3 noted values. Please report your values to me. It would help me creating a method to calibrate every screen:)

Thank you very much!

(I'm currently busy deciphering the connection between White Point and the register)
[Nexus 5 Original Android Development] Tzfardaya:
recovery backup saves everything, including the rom...

okay, now the other question I asked? what part of otg isn't working? mouse, keyboard, mass storage, other?
[Nexus 5 Original Android Development] blueren:
Aww shucks. bootloopie loop. Let's rewind and retry. Only the dalvic this time.

Actually, dalvic patch was the culprit.

Anyway. I've diverted from the kernel thread and it's not fair. Another day, another time. Ler's see what r35 has in store for us.
[Nexus 5 Original Android Development] zubsz:
I'm not sure I know what you're talking about, but this is the otg I bought: http://www.ebay.co.uk/itm/221350918124?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
[Nexus 5 Original Android Development] Tzfardaya:
does a mouse work when plugged in via otg?

does a keyboard work when plugged in via otg?

does a usb stick work when plugged in via otg?

edit: Ah, you just bought a card reader....
[Nexus 5 Original Android Development] Silentbob999:
Yes

Yes

Yes

Tapatalked with SlimKat NexusFive
[Nexus 5 Original Android Development] Tzfardaya:
silly, I know it does, That was directed to someone who is having issues with otg, I was trying to help narrow down the problem...
[Nexus 5 Original Android Development] Silentbob999:
But not the one linked. It's a microSd expansion. If you are using a usb port otg yes everything works

Tapatalked with SlimKat NexusFive
[Nexus 5 Original Android Development] Tzfardaya:
this is my preferred style otg

let's me connect whatever usb device I want to my phone...
[Nexus 5 Original Android Development] EvgeniX:
No I did try this dongle at home and it the same. Click definitely from phone itself... and since I have them on full stock phone looks like problem not in kernel but in kitkat. since other phone works fine...

so still hoping some one can find this problem or google will do something....
[Nexus 5 Original Android Development] kkazakov:
Problems with r33 and r34

I'm having this weird problem with r33 and r44 that I don't have with r32 ... When after install the screen goes off, I cannot turn it on. I need to hold down the power key until it reboots. If the screen goes off afterwards, then I cannot turn it on again.

When I revert to r32, everything works perfectly ... please, help! Could not find anything on this :(
[Nexus 5 Original Android Development] Aerowinder:
Are you undervolting?
[Nexus 5 Original Android Development] zubsz:
Thanks, Sorry for he confusion lol
[Nexus 5 Original Android Development] Tzfardaya:
first question, do you undervolt?

second question, are you running stock franco, or have you made any tweaks?

---------- Post added at 12:29 PM ---------- Previous post was at 12:24 PM ----------

no worries, if you've the time, try a clean flash of the stock rom and see if that helps with your otg issue... I'm on stock too and that's what mine needed.. I was having all sorts of otg problems before. reboots on disconnect, mass storage not working..
[Nexus 5 Original Android Development] kkazakov:
I am on stock 4.4.2, Stock franco from FK updater and no, I'm not undervolting or touching anything ...
[Nexus 5 Original Android Development] Tzfardaya:
that's interesting then... sleep of death (screen off death) usually hits the n5 when undervolting too much...

stock 4.4.2, r34 with no custom tunes?

grab a last_kmesg next time and post that here to see if there's something for us to find in it...

alternatively, you could try reflashing stock and the kernel and reconfiguring your phone.. see if that helps any.
[Nexus 5 Original Android Development] kkazakov:
Okay ... I think it fixed itself, when I opened FKU, reset all it's data and restarted the phone ... for now seems this have fixed it. I'm pretty sure I've never undervolted it manually or anything else ... It's a brand new N5.

EDIT: Seems it's not fixed after all :( I'll try to get some log

---------- Post added at 06:58 PM ---------- Previous post was at 06:46 PM ----------

It looks like it's actually not dead, but the screen just does not turn on.
[Nexus 5 Original Android Development] gee2012:
Just reflash the stock rom to fix your issues, there are also pre-rooted odexed and deodexed stock ones available here on XDA which you can flash in recovery. Backup files first though.
[Nexus 5 Original Android Development] Silentbob999:
Oups sorry, I read some post way to fast :P

Tapatalked with SlimKat NexusFive
[Nexus 5 Original Android Development] Tzfardaya:
no worries, I've done it myself before.. :P
[Nexus 5 Original Android Development] floepie:
I can't seem to change this value. I use the terminal emulator with root permission (su), and it still won't change. I've also tried with Antek Explorer with root permissions. In either case, the file's value changes from 'Y' to 'N', but after a reboot, the value is restored to 'Y', indicating that at boot the file is reverted to its default state. Has anyone verified that after changing this value, it persists following a reboot?
[Nexus 5 Original Android Development] Tzfardaya:
it's not supposed to persist across reboot, you need to use something to make the change each reboot.

like vomer's init.d setup or tasker or the like.
[Nexus 5 Original Android Development] floepie:
OK thanks. For the love of god though I really hate this now. Please revert and let everyone use Lux the way people have done for generations now. Thanks.
[Nexus 5 Original Android Development] Tzfardaya:
why would this affect how you use lux? just means you need to adjust your lux settings
[Nexus 5 Original Android Development] floepie:
I don't use lux. That's the point. Some people did, now they don't.
[Nexus 5 Original Android Development] Tzfardaya:
I happen to a) not use lux, and b) like the new brightness levels on auto. Yes, If I set the brightness manually to the lowest level, my backlight is off entierly, but so what, I don't set it manually... (or, the rare time I do, don't set it to the min level...)

So I don't understand your complaints... sure, it's something new to adjust to, but it's not that hard to adjust...
[Nexus 5 Original Android Development] Ivixmax:
Is this nomal,guys?

Stock + Xposed + R34

Initaly the ram is normal between 500 or 700 mb of use.But the ram increase a lot of through the day...
[Nexus 5 Original Android Development] floepie:
If by adjust you mean adjusting your eyes, then that doesn't seem to be working. I simply can't read the text when there is low level ambient light (not completely dark).

If by adjust you mean creating a script to run at boot, then I suppose it would be indeed easy. Now, to go and research how to go about doing this.
[Nexus 5 Original Android Development] Tzfardaya:
first question I have for that screenshot is...

have you cleared your recent apps, or did you never open any since boot?

apps get cached in ram even after you've swiped them (even though the processes have been closed/killed) for faster reloading...

The mem leaks from the test 33's seem to have been taken care of.

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

earlier this thread vomer gave steps on how to set up an init.d script for those who don't have fku (or access to paid apps) and want to tweak anyways... same technique would work to echo the new backlight system off.
[Nexus 5 Original Android Development] FlorinXstyle:
Hello Franco.Thanks for this wonderful kernel.I used your kennel on Nexus 4 too and now i moved to Nexus 5.

I think the autobrightnes is a litlle to low on places with no light. Ca you readjust a little bit hight ?
[Nexus 5 Original Android Development] Tzfardaya:
*sigh*

he's already given us a command to disable it, but needs to be re-applied every reboot, this is what [MENTION=284716]floepie[/MENTION] and I were talking about right above your post...
[Nexus 5 Original Android Development] FlorinXstyle:
Oh.. Ok now i see it.

Hope to aplly the patch on next kernel update.