yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] hospital349:
Exactly the same issue here. At first I thought that it was only happening with LaboDJ's Linaro Kernel, but after a full day using the latest test Kernel, I can report the same audio issue.

It only happens when a certain volume level is exceeded and music will begin to clip in the right earpiece of my earphones, followed by no sound at all. Only in the right earpiece, again.

I haven't got my earphones with me right now, so I cannot reproduce, to retrieve a log. If anybody can fetch one for Franco, I'm sure he'd really appreciate it!

From what I know, this bug came to exist around the time that low notification volumes occurred and got fixed... If this helps eliminate the issue, at all.

Cheers!
[Nexus 5 Original Android Development] scissors_cut_paper:
+1 for the right headphone issue. Using headphone boost 1, and edited mixerpaths.xml l/r headphone to 20 instead of 15, if that makes a difference.
[Nexus 5 Original Android Development] jjhiza:
Headphone boost increases headset volume, speaker boost should do the same for speakerphone, and volume boost should be related to in-call volume, when not using a headset. That may be over-simplistic, but it should give you more of an understanding, so you can make relevant tweaks. :thumbup:
[Nexus 5 Original Android Development] Laggalot:
got it ! only the last one was unclear though :)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] jjhiza:
Oh ok... Well the last one is about in-call volume, coming through the built-in headset (the small, circular area at the top of the phone), instead of the speakers (on the bottom) or a headset.
[Nexus 5 Original Android Development] TrenchKato:
OK sooooooo. I won't call this a memory leak (for fear of someone coming and attacking my competency again) . But maybe somebody here can help. Evey app I exit gets killed. Notice the 0mb next to all the apps. This only happens on r33. I've clean flashed my rom and tried stock for 2 days just to see if it was an app that updated. Everything ran smoothly.

Any ideas are appreciated.
[Nexus 5 Original Android Development] franciscofranco:
No idea. Look at my shot 15h since rebooted.
[Nexus 5 Original Android Development] jjhiza:
I haven't read any of your previous posts, so I'm trying to play catch-up here... What is reported under the Show Cached Processes tab? Here's a look at my memory on yesterday's test 33:

I do have a couple of RAM management tweaks applied (minfree values and such), and I rarely have below 800MB.
[Nexus 5 Original Android Development] TrenchKato:
Ok thanks

Dang. I reboot it without taking a screenshot of the cached processes. Nothing there seemed out of the ordinary but the list was really short maybe 3 or 4 items. Chrome was there for sure.
[Nexus 5 Original Android Development] adamsweeting:
Sorry for OT

Franco - I see you have SmartConnect installed - do you have a smartwatch by any chance?
[Nexus 5 Original Android Development] Red5:
Yeah I saw that too. I have a Sony smart watch and love it. I've had no connection problems to it either.
[Nexus 5 Original Android Development] franciscofranco:
Yes, SW2.
[Nexus 5 Original Android Development] adamsweeting:
Nice... Me too :)
[Nexus 5 Original Android Development] kraven001:
My battery is dropping like 10% / h with 4G ... as far as I remembered Franco was around 5-6 % / h. I don't see any wakelocks or anything.

Any ideas ? What should I use to debug (using better battery stats so far but that seems clean with proper deep sleep for the CPU).
[Nexus 5 Original Android Development] franciscofranco:
I must've done something on my local build, after 16h my ram is sitting at 490mb used, never had it this low even when I tested stock Kernel.

Its a bit hard to debug something with so little information in a device I don't have on my hands to evaluate...
[Nexus 5 Original Android Development] omvir:
Wait.. You mean 490mb free?
[Nexus 5 Original Android Development] nerotix:
Make sure it gets to the release aswell XD
[Nexus 5 Original Android Development] kraven001:
Yeah , I know, trying to find some support on how to give back. I can survive with this but was curious and I guess is something on my device. Guess will have to factory reset or something, and try to figure it out myself.
[Nexus 5 Original Android Development] Hippoman13:
I'm pretty sure he means only 490Mb are in use. Which is really good
[Nexus 5 Original Android Development] omvir:
Oh, I just thought the way he said it sounded like its something bad LOL. So I thought why would that be a bad thing?! Then I thought maybe he meant free instead of used. But never mind lol.
[Nexus 5 Original Android Development] franciscofranco:
No, used. And I dont clear my recents E V E R.
[Nexus 5 Original Android Development] omvir:
Wow that's awesome! If you try to load up an app at the top of your recents does it reload like when you load up a closed app or is it instant? Just curious.
[Nexus 5 Original Android Development] JNewms:
Hmm... I'd like to take that local build for a little test drive.. ?
[Nexus 5 Original Android Development] sudoeste:
The ram problem is easily triggered using Chrome with 06/02 build. Open several tabs with heavy websites and the redraws begin

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] educk:
Guys, I don't usually buy apps on Play Store (last time I bought something was months ago - Greenify) and now I purchased Franco Kernel Updater.

The thing is that if I go to Google Wallet Transactions it shows me "Pending" under the current transaction and it passed like 30 minutes or so.

So, for those who purchased FKU, for how long did you guys wait for the transaction to be complete ? The app is installed on my device though.

Thanks and sorry for OT.
[Nexus 5 Original Android Development] JNewms:
It doesn't matter. It'll go through eventually. Probably once the transaction is completed through your bank.
[Nexus 5 Original Android Development] Halavus:
Hello,

I bought your app today and flashed the zip it downloaded on my nexus 5 (r32) with the last cm11 nightly. After the flash, the phone get stuck on the google screen when booting.

I did a restore and everything is good again, but I really would like to use your kernel.

Should I give a try with fastboot instead of flashing it in the recovery?

What's your advice?

Thank you.
[Nexus 5 Original Android Development] bigbiceps:
Are we stuck on 32? Been a long time since 32 was released. But why are we running tests (they can be released as 33,34,35 etc itself right or am I missing some thing?

I lost track and there are just too many posts which makes it impossible to read.

You help is immensely appreciated. Thank you.
[Nexus 5 Original Android Development] vomer:
Brah... do you even lift? :p

r33 has been in testing as franco perfects things.
[Nexus 5 Original Android Development] GeekMcLeod:
... Franco and CM are not compatible no matter how you flash it. I remember someone saying there is a file you can flash so they will work together. That would probably be found through the CM thread, I believe.

It is being tested so we don't have a whole bunch of people complaining about the same things. He wants to iron out most bugs before releasing it.

Posted from under your bed.
[Nexus 5 Original Android Development] Red5:
It's 32 bothering you? Is it negatively effecting your phone? No? Then wait till Franco releases 33.
[Nexus 5 Original Android Development] jd1639:
If I don't get r33 now my head is going to explode. And if my head explodes the janitor is going to have to clean it up. And if he has to clean it up he gets crabby and goes home and kicks his dog. And I really like that dog. So don't let his dog get kicked.
[Nexus 5 Original Android Development] milestone2mod:
[MENTION=3292224]franciscofranco[/MENTION] Wouldn't it be better if you write something like "not CM-compatible" in the OP or title to prevent yourself from getting the same question every ten posts?

I mean, it would prevent you from annoying noobish questions and would help keeping your thread clean....just guessing....
[Nexus 5 Original Android Development] bobloadmire:
Anyone got any advice on these kernel Wake locks? I have 20min screen on at 50%.
[Nexus 5 Original Android Development] 5FOOTER:
Mine did this on one of the test I flashed the newest, cleared FKU stats and rebooted a couple times. That fixed it not sure why though.

Destro warlock on WOW burnall
[Nexus 5 Original Android Development] italia0101:
What's your standby time? Those kernel wake locks seem fine
[Nexus 5 Original Android Development] bobloadmire:
About 5 hrs. On wifi.
[Nexus 5 Original Android Development] italia0101:
Check your other wakelocks, I'd bet on a rough app rather than the kernel
[Nexus 5 Original Android Development] bobloadmire:
I listened to some podcasts so this looks normal. Also I greenify most apps too. Facebook etc.
[Nexus 5 Original Android Development] jjhiza:
This is a good idea, but if new users actually read the OP (not talking about you, just making a general observation), they would find the FAQ link. In that FAQ, the following is clearly stated:

As written by The Gingerbread Man

"Cyanogen Romz

Cyanogen often makes changes in the ram disk or use different drivers than stock / aosp and ROMs based off cyanogen pull their commits from their github and sources so they don't have to work on these things them selves so those rom devs can work on their features. Cyanogen have a tendency of doing things in their own way. To my knowledge CM roms only work with their shipped kernels. As for future compatibility no one knows, Franco said he will consider adding support in the future. It depends on the changes required I guess. Franco will always make things to be compatible with stock / aosp."

While putting the CM info in the OP in big, bold letters, seems like a good idea, let's be honest - even if it's clearly stated, the questions will still continue, because reading is a lost art for many on XDA.
[Nexus 5 Original Android Development] adame09:
http://xdaforums.com/showthread.php?p=40409356 Has anyone used the init.d scripts by osmosis do they do any good?

Scripts * 950iosettings + 875mntsettings + 925vmsettings init.d scripts (all devices) [with Franco's Dev Team] - link

The scheduler tunables have already gained a bit of attention/adoption on various devices and kernels, but this is the init.d script I wrote to set the new custom scheduler tunables values as "default" by an independent loop, sleeping in the background and detecting each time the scheduler is changed. There is no effect on idle drain or deep sleep. The settings included are the growing work of the "Franco's Dev Team" (or "Team Franco") tuning collective, of which I am a member. We are striving to perfect the scheduler, vm and various other settings for the smoothest and fastest experience available. The collective is: malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres. Link points to my Dev-Host since these may still be subject to change from time to time. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask.
[Nexus 5 Original Android Development] JNewms:
Didn't realize that Franco needed to keep a release schedule. How dare he take longer than you think he should to release a kernel.

These tests are being done for a reason, he releases tests in img format in hopes that the people who know what they're doing will test and submit proper bug reports. If you searched his posts you'd see that he said he's only releasing 33 once everything is working perfectly. So just sit tight on 32 and allow the development process to run it's course.
[Nexus 5 Original Android Development] cc16177:
FRANCO! MY MAN!

I unfortunately did not have access to your beautiful work when I was using my DNA but you were my go to kernel for my Galaxy Nexus and the other 2 in my family...

This thing is AWESOME! 6 and a half hours off the charger, 25 min screen on time and 5-10 min of voice calls i'm still at 89%. Unreal!

I don't need crazy screen on time because I use my phone maybe 2 hours a day so i'm focused on idle battery consumption and you as always have delivered.

Happy to see you here!
[Nexus 5 Original Android Development] :
I don't mean to offend anyone. That isn't the point of that post. However I'm not presenting this as an opinionated point of view. Anyone who has had their time with a colorimeter and properly calibrated monitors will agree with me. The Kelvin Temperature of 6500k is a sRGB standardized format. Its not a matter of "oh I feel its too blue".

However, I don't care much for the screen calibration considering how much of a battery improvement I'm getting. I know he is going to make gamma adjustments available. Im as grateful for Franco's work as the next guy. I'm just putting my two cents in.

After all, thats one of the reasons why this thread exists in the first place?

Thanks Franco. Ive found a temp fix to change up the colors a bit via screen adjuster so im good here. I hope you didn't take it as an attack for your work. Like the guy who said on your Google+ Community page, you make the device usable now. Thanks.
[Nexus 5 Original Android Development] aeroseek:
Same thing happened to me on r10. But I just did a disconnect/connect and charged just fine after that. Weird.
[Nexus 5 Original Android Development] shamu11:
weird stuff. I hope future kernels dont do that, if they cause it at all
[Nexus 5 Original Android Development] pa.pn2:
quick question

am i doing something wrong or do my settings not stick in FKU after rebooting?cant find any option to save the settings imo.is that true?
[Nexus 5 Original Android Development] tkalli:
No problem here charging with r10.
[Nexus 5 Original Android Development] Rxpert:
Better battery stats beta releases work. Here on xda
[Nexus 5 Original Android Development] Chad_Petree:
Are you working on the nexus 5 display control app too ? :)
[Nexus 5 Original Android Development] eep2378:
If you're using FKU beta, you simply long press on each setting to enable set on boot:D
[Nexus 5 Original Android Development] rxmxsh:
yes. please read back. it's been asked and answered more than a dozen times in 24 hours.
[Nexus 5 Original Android Development] Bogusetti:
Trickster Mod shows 128kb as default setting ?!
[Nexus 5 Original Android Development] franciscofranco:
Then I forgot to change it. No big deal though.
[Nexus 5 Original Android Development] Bhonka:
Does this place even have mods?
[Nexus 5 Original Android Development] RTNDO128:
Not another one... You're attacking the wrong guy here. Again, he attempted to belittle me, not help me. Thanks though.
[Nexus 5 Original Android Development] franciscofranco:
I hope not, the less they interfere, the better.
[Nexus 5 Original Android Development] Evilv2:
I tried searching this thread. System Monitor shows CPU 1 and CPU 2 are always on (~300mHz) while with the stock kernel CPU 2 was not always on. Is everyone seeing this (is CPU 2 supposed to be always on with the franco kernel?)?
[Nexus 5 Original Android Development] STi_Fanatic:
Wow, flashed r10 last night after buying the FKU app and I have to say - it feels like I'm using a totally different phone. Just sips on the battery now. Incredible work, especially since you just got the phone yesterday. Keep it up - much obliged, Franco!
[Nexus 5 Original Android Development] itsfozzy:
Bug.

I used to be able to fry an egg on my N5 when playing Plants vs Zombies 2, but since installing the latest Franco kernel, the phone hardly heats up at all. I'm going to have to buy a saucepan now.
[Nexus 5 Original Android Development] gaurav2912:
hello, im a noob :laugh:, trying to learn what I can do with my Nexus 5 or rather what I can make my Nexus 5 do

im upgrading from a Galaxy SL i9003 and im gonna get my nexus 5 after a month from the US and I just read through a 1740 replies :p

im already excited to try this out

thanks franco.....you rock buddy
[Nexus 5 Original Android Development] SedyBenoitPeace:
I suggested some time ago to add the [NO CM] to thread's title that is even better...i think that is nothing of hard to make...and probably will clean the thread from new questions about the CM...because i don't think that franco is glad to answer the same thing over and over...
[Nexus 5 Original Android Development] gambe89:
You lost 1%/h, it seems good to me
[Nexus 5 Original Android Development] SedyBenoitPeace:
The news about bam_dmux is really great! Can't wait to next release! However the r32 is really amazing! Thanks franco!
[Nexus 5 Original Android Development] Kpoch:
Well i have CM11 Installer versión and is up to date(m2 snapshot) and works ver y well i dont hace any problem with audio/bluethooth or youtube and FKernel is working well, just stick with cm11 M2 or CM Installer versión and stop updating it simply WORKS

Nexus 5 From MEXICO !!!
[Nexus 5 Original Android Development] bobloadmire:
I lost 50% over 5hrs
[Nexus 5 Original Android Development] Peanuts.:
R33 is awesome. Getting better with each test update. Also it's been so long since my charge that my charger has collected dust!

Compared to R32 I was able to get around the same SOT, 4.5+ hrs but with almost 24hrs total battery. Now it's just wow.
[Nexus 5 Original Android Development] jjhiza:
I see what you're saying, and I agree that it would be easy enough to do, but I could make the counter augment that only kernels that SUPPORT CM, should be labeled (eg CAF compatible etc), and that every other kernel should be assumed to NOT support CM.

I think a lot of people get testy about this issue, because it appears as if CM users expect to get special consideration. Naturally, other users take umbrage with that, and can be nasty at times.

At this point (several months into kernel and ROM development) everyone should be able to get an answer to the CM question, by simply doing a thread search for it, because the question really IS asked that much. :)
[Nexus 5 Original Android Development] Aerowinder:
All of the potentially useful ones can be done with: FKU, Trickster, other kernel tweaker knockoff app, or even Tasker. No reason for the init.d scripts. The other one, the mounting one, doesn't make a noticeable difference. I've run slower devices with and without, and there was no perceivable difference.

I have a suspicion it's like all the build.prop tweaks that developers are still including in their ROMs, even though they have all been thoroughly debunked. Multiple times. Years ago.
[Nexus 5 Original Android Development] kirt231:
Does this support USB OTG? If so what formats?
[Nexus 5 Original Android Development] HenryDCase:
If you mean auto mount, no.

If you mean with Stickmount, yes, same as stock.

Search is your friend.

Sent from my Nexus 5
[Nexus 5 Original Android Development] kirt231:
Lol yep stick mount works
[Nexus 5 Original Android Development] Vollspacken:
I get easily 6h+ SOT on Slimkat-ROM and the build of 6h february with -50mV overall and some configured App-Ops with the same total runtime. Gnow and GPS off, but who needs it always turned on?

So this is very awesome. Can't imagine that there's a better kernel for both performance and battery life out there.
[Nexus 5 Original Android Development] The Gingerbread Man:
Most of the testing which took along time was tuning and optimizing the values for io schedulers for fastest average through put of operations tested on galaxy nexus' and old nexus 7s. The tweaks worked well on both devices but it has been along time since any further tests have been carried out. That was most of the summer 2012. It wouldn't surprise me if rom devs still include those tweaks and they are free for anyone to use. I'm not 100% certain Franco is using the tweaked values for io or not but they were used on the devices I mentioned. The mount stuff isn't really needed so much now due to trim being added to android 4.3 I think it was included. We tested all sorts of things collecting a lof of data, was good times
[Nexus 5 Original Android Development] GeekMcLeod:
Pastie.org is annoying as hell. I feel like I was deleting more than 3/4 of my last_kmsg.

http://pastebin.com/qyL9Lfnj

This is on the latest test. Everything has been going smoothly, until I decided to try out my 1TB harddrive with stickmount. I bought the pro version, and have the media scan on mount. That is the only thing I could think of that caused it. Too many files. But after it booted back up, it's working fine.

There is also a lot of this

[ 8839.481660] Invalid frequency request Max:1036800 Min:1881600

[ 8839.551155] Invalid frequency request Max:1036800 Min:1881600

[ 8839.551302] Invalid frequency request Max:1036800 Min:1881600

[ 8839.581497] Invalid frequency request Max:1036800 Min:1881600

[ 8839.581673] Invalid frequency request Max:1036800 Min:1881600

[ 8839.652057] Invalid frequency request Max:1036800 Min:1881600

[ 8839.652205] Invalid frequency request Max:1036800 Min:1881600

My min is always 300 and my max is always 1574.
[Nexus 5 Original Android Development] Ok_Kaleidoscope5109:
Init.d scripts to control Franco kernel workings are useful because you don't need yet another app to load at startup. The fewer the better.
[Nexus 5 Original Android Development] akaHardison:
Is there any r33 zip for recovery flashing?
[Nexus 5 Original Android Development] Chochiwpg:
Nope, you can flash the IMG using the Flashify app
[Nexus 5 Original Android Development] resynx:
I don't believe so. If you don't want to use fastboot, you can use FKU to flash it :)
[Nexus 5 Original Android Development] akaHardison:
fku only has r32.I have beta version.
[Nexus 5 Original Android Development] david279:
Download the boot image and flash it with fku or flashify.
[Nexus 5 Original Android Development] mitchdickson:
If you need a tutorial, perhaps test kernels are not for you.

Sent from my Nexus 5
[Nexus 5 Original Android Development] keith.mcintyre26:
I just downloaded the test 33 image, renamed it boot.img and replaced the boot.img in the 32 zip.
[Nexus 5 Original Android Development] akaHardison:
I have fku beta version11.4b

I come from faux kernel.
[Nexus 5 Original Android Development] b_rangel29:
Download the .img on your phone then do to downloads in the FKU app, tap on the .img file, tap "flash .img", then reboot. Then clear cache and data for FKU app under settings> apps. Works good.
[Nexus 5 Original Android Development] RobbieL811:
Why not just do it the right way? Search, read, & learn how to setup & use fastboot. It's the best way to flash it. If someone can't figure out how to use fastboot, they don't need to be flashing test kernels.

Sent from my Nexus 5
[Nexus 5 Original Android Development] keith.mcintyre26:
I'm a full time software engineer. I did it on my phone in the car before I went into the office.
[Nexus 5 Original Android Development] pikachu01:
I think I know what triggers the extreme slowdowns on screen off. It's due to thermal throttling. When I was listening to music last night, the phone was charging and doing nothing but just Spotify on.

Since the last few test builds, I've noticed that the phone heats up randomly (even when charging, or just doing light work). Not sure if anyone encounters this.
[Nexus 5 Original Android Development] franciscofranco:
My device doesn't even heat up while playing Kingdom Rush Frontiers :'(
[Nexus 5 Original Android Development] RobbieL811:
Yeah but not everyone on here is. I wouldn't advise anyone to do it that way. If something were to go wrong, & someone doesn't know how to use fastboot that would lead to "Oh no, I bricked my phone. Someone please help" posts. I'm just saying... I think that people should definitely learn to use fastboot if they want to flash .img files. That's how it's done properly.

Sent from my Nexus 5
[Nexus 5 Original Android Development] b_rangel29:
Why are you quoting me? Is this the wrong way to do it? I was telling him a way to do it without using fastboot, turned out he was in his car so it was appropriate.
[Nexus 5 Original Android Development] pikachu01:
Might be related to the SELinux error I've encountered a few posts back. Unrelated to any apps or games.