yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] xadidas4lifex:
here is my logcat...

i had like 4 reboots happen in a matter of 10 minutes. just listening to music and basic usage on my way home from work.
[Nexus 5 Original Android Development] sudoeste:
I'm also getting launcher redraws on the latest 33, with ram at 707 free, so maybe the problem is elsewhere?

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] sasho36:
Had the same today.

I've also a strange bug with sound: after I make or receive a call while using a bluetooth headset (or car bluetooth), the sound of the phone stops working completely (speaker or headset). It's fixed with a reboot, but comes back each time. Anyone has the same issue?

I'm on Carbon with r33 test6, but I had the same bug with test4 on Cataclysm, so I don't think is the rom.

There is no problem with r32 or with Linaro r33test3.
[Nexus 5 Original Android Development] mibtnt:
Had similar issue with my bluetooth as well. Rebooted and it helped it. But it only happened once for me. I'm on r32

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] :
I only witnessed something like this on 4.4 .

Kudos to you franco

No problems here , ram is behaving normally , no launcher withdraws ..
[Nexus 5 Original Android Development] RobbieL811:
Phone was sleeping on charger. Got a phone call and it started ringing then rebooted. Last kmsg below.

https://www.dropbox.com/s/vy3o2ptmpimypfl/last_kmsg
[Nexus 5 Original Android Development] EarlZ:
Has anyone experienced a huge battery drain on idle?

Ive been trying to fix this for the past few days and for the last 2 days it was under control and just last night I get a huge drain again. Can anyone take a look at the BBS see if its something to do with the kernel ?
[Nexus 5 Original Android Development] RobbieL811:
I too had my launcher redraw this evening with about the same RAM free. I might've even had a little more than that free.

Sent from my Nexus 7
[Nexus 5 Original Android Development] omvir:
No ram problems here on latest r33... Dunno what this launcher redraw is all about that people are getting :/
[Nexus 5 Original Android Development] abjexstallion:
Same here. Trying pastie for uploading the log but it doesn't accept .txt any options?

Straight from my franco.fied SLimHeAD... After all it's a ?NEXUS?
[Nexus 5 Original Android Development] The Gingerbread Man:
So occasionally you hit home button, after a fair while muti taking and when you press home its black for a very short time and then loads. Personally I'd blame the launcher for not being a finished product yet and goofle appears to be potentially making small steps to make it a market release. This maybe be our future, GPE phones with near enough all gaps and built in apps finding their way to the play store reducing OTAs
[Nexus 5 Original Android Development] franciscofranco:
1 - ZIP path thingy to open with the File Manager comes soon!

2 - Play games services is greyed out because I haven't finished the achievements integration. All the code is in place but I have to create the achievements etc, just some work that I'd rather use on other features. This will be the last feature I'll integrate for v11.4

Thanks for the log, something derped on the sound chip driver, and it was helpful! :)
[Nexus 5 Original Android Development] RobbieL811:
Good deal.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Ok so ahead of launching another r33 test image I'll let you sneak peak the new tunables for the Hotplug driver. There are no changes to the driver algorithm itself, I'm just exposing all these interesting tunables for users that want maximum control and I mean extremely maximum control on how my driver behaves. Feel free to ask away if any explanation is not as good as it could and I'll happy to explain! Here's my documentation:

The load_threshold = first_level, just changed the name of the text to be less ambiguous.

/*
* system load threshold to decide when online or offline cores
* from 0 to 100
*/
unsigned int load_threshold;

/*
* counter to filter online/offline calls. The load needs to be above
* load_threshold X high_load_counter times for the cores to go online
* otherwise they stay offline
*/
unsigned int high_load_counter;

/*
* max number of samples counters allowed to be counted. The higher the
* value the longer it will take the driver to offline cores after a period
* of high and continuous load
*/
unsigned int max_load_counter;

/*
* if the current CPU freq is above this limit don't offline the cores
* for a couple of extra samples
*/
unsigned int cpufreq_unplug_limit;

/*
* minimum time in seconds that a core stays online to avoid too many
* online/offline calls
*/
unsigned int min_time_cpu_online;

/*
* sample timer in seconds. The default value of 1 equals to 10 samples
* every second. The higher the value the less samples per second it runs
*/
unsigned int timer;
[Nexus 5 Original Android Development] fcisco13:
Franco do you have any recommended settings that you use with your app.

Whatchu talking bout willis!
[Nexus 5 Original Android Development] franciscofranco:
I use the defaults I ship the Kernel with. If for some rare ocasion I know that I ain't charging my device for a long time I underclock to 1,5GHz and use PerAppModes for apps I know that need more juice.
[Nexus 5 Original Android Development] Dungeon47:
Franco, do you disable emmc entropy by default?
[Nexus 5 Original Android Development] evonc:
Is it possible for you to do a short write-up explaining how the kernel would react to processes starting/finishing (ie. how do the cores/frequency scale for example when a process ends? Does the frequency ramp down slowly before the cores go offline or does the kernel simply take cores offline directly before ramping down frequencies? Also lets say a new load is applied and additional cores are brought online, do they follow the governor guidelines for frequency increase or do they come online at the same frequency the other core is operating at?)
[Nexus 5 Original Android Development] Smallsmx3:
What about the low touch screen sounds?
[Nexus 5 Original Android Development] Tzfardaya:
What about them?
[Nexus 5 Original Android Development] Smallsmx3:
Any idea what's causing them in the latest test
[Nexus 5 Original Android Development] franciscofranco:
No?

Good question, I have absolutely no idea. Either the governor cpu node saves the last target_freq and when the core comes online it starts with that freq, or it starts from 384MHz (min)... I wish I had a better answer, but I don't know because these cores are async. In a synchronous cpus arch I could answer you that the new core would come online in the same freq as the other online cpu was at that exact time. In this async cpus arch I have no idea. Sorry :(

"Does the frequency ramp down slowly before the cores go offline or does the kernel simply take cores offline directly before ramping down frequencies?"

The core just dies regardless of what frequency it was running. The whole process involving an offline of a core is pretty brutal. Its much halved with some changes I've merged from upstream from the kthread subsystem and workqueue subsystem, but its still pretty brutal in what happens down there in the lower layers.
[Nexus 5 Original Android Development] evonc:
Thanks for the reply. Always wondered on how the entire process works and from the core offline process, it almost seems better to try to setup the governor in a race to idle setup since there isn't really a huge drawback to bringing cores online/ramping up frequency because the cores would go offline once the process is complete. I'll try to setup a test keeping as many variables the same when I get a few days off to see if it actually improves battery in comparison to underclocking.
[Nexus 5 Original Android Development] Dungeon47:
Might be worth looking into. As I understand it, the phone uses the emmc to generate a pool of random numbers that the OS uses for various tasks requiring randomness. Disabling the emmc contribution to this entropy is supposed to reduce lag and save some battery life by omitting the operation to generate the randomness. In my experience, it has been a perceptible difference, especially over time. Faux has a setting for it. Thanks for your work and responses all the same.
[Nexus 5 Original Android Development] sordna:
Disabling it could have security implications though. Any known downsides ?
[Nexus 5 Original Android Development] Dungeon47:
I can't verify from my own knowledge, but I've heard other people say that the contribution of entropy from flash storage is poor in the first place. There may be other sources that sufficiently contribute on their own. I'll see if I can do more research on the matter.
[Nexus 5 Original Android Development] evonc:
IIRC wasn't there an app that came out in the JB days that was supposed to fix the "lag" issues with Nexus 7 2012 by changing something related to entropy pool and it was soon declared as placebo by a few developers?
[Nexus 5 Original Android Development] Dungeon47:
You might be thinking of the Seeder app, which was superseded (lol) by adjusting it in the kernel settings. If it has no measurable effect and it's just my imagination, so be it. Frankly it's one less thing to need to worry about adjusting. If it does, however, make improvements, it would be nice to know/have.
[Nexus 5 Original Android Development] P.Mobile:
cant wait!! r33 gonna be killer!!:victory: i dont have any $$ on my bank card rite now but i can buy an app and bill it to my sprint account.. i already have paid FKU.. and cpu monitor.. is there any other app i can buy to show some love??
[Nexus 5 Original Android Development] vomer:
Guess I will have some testing to do to add some more things to my custom tunable profile as well :)

Sent from my Nexus 7
[Nexus 5 Original Android Development] 5FOOTER:
Could be crossbreeder or Exit only's killjoy I ran them on my gs3 and it took all the lags away.

how many times have these questions been asked?
[Nexus 5 Original Android Development] Cheater912:
When the phone doesn't wake, requiring you to hold down the power button to reboot it. My voltages are stock. I even tried overvolting.
[Nexus 5 Original Android Development] carlese:
Is the low volume fixed in the latest r33?
[Nexus 5 Original Android Development] :
So anyway got a new router today. Doesn't kill my battery anymore, so that's good.
[Nexus 5 Original Android Development] EarlZ:
How does a router affect that ?
[Nexus 5 Original Android Development] P.Mobile:
dont think there was a new r33 test released just yet?
[Nexus 5 Original Android Development] RobbieL811:
Some routers are said to create wakelocks.
[Nexus 5 Original Android Development] :
This.

:good:
[Nexus 5 Original Android Development] RobbieL811:
What router did you get? I just got an Asus RT-N66R about a month ago and it helped me out alot.
[Nexus 5 Original Android Development] :
Asus rt n56u I think it was I love it but now it keeps giving me an error saying no connection on gmail and Google play -,- any ideas how to fix that? Love the router otherwise. And I have connection to it cause if I hit retry a few times it works... @,@
[Nexus 5 Original Android Development] RobbieL811:
I'll send you a PM. I don't wanna clutter up the thread with OT.
[Nexus 5 Original Android Development] .Gibson.:
TL;DR long winded excuse to steal the hard work of other, smarter individuals, in order to save 1-3 bucks.

Sent from my Nexus 5
[Nexus 5 Original Android Development] linqdesires:
I was guessing if google localization service should be responsible for those wakelocks. they use wifi to localize you :confused:
[Nexus 5 Original Android Development] Stylez Ray.:
I also have memory leak and redraws on latest test. Tried several other kernels and they all work fine. Don't know what the problem is...
[Nexus 5 Original Android Development] big_adventure:
No memleak issues here - 1d11h on the latest test, and I've still got apps running in the background taking mem like they are supposed to, no launcher redraws, no issues at all. I've also not seen any fail-to-wake issues.

I just noticed that my phone seems to have spent all it's time out of deep sleep since yesterday night, so I'll check into that, but that's likely a userspace issue. I left a couple of games running that might be misbehaving.

EDIT: Yup, it was an app. The kernel is behaving beautifully.

I did notice a low-volume notification yesterday, seconding what some others have said, but I'll need to look further into that. I leave most notifications on vibrate all the time anyway.
[Nexus 5 Original Android Development] armyboy11b:
Their shouldn't be a mem leak on latest test build.
[Nexus 5 Original Android Development] Laurentyu1995:
After 39h of runtime with a lot of using and multitasking i don't see any kind of problem with ram( i have 0.9-1 gb free). Good job Franco ! Thank you for this awesome kernel !
[Nexus 5 Original Android Development] myfluxi:
Funny sidenote how many things come together sometimes. I was playing with the mdss FB thread while trying to prevent flicker when resetting the panel controller. Then I played with BFS again, just for the laughs. Then Steve pointed out the high MSM iowait. Then I was playing with mainline workqueues and exterminated the cpu-boost thread (didn't you do this as well?) only to discover the beauty of thread migration. A pity we do not make use of current kernel development, even MSM-3.10 does not use it, so I'm still looking at the iowait stuff. And everything is now connected.
[Nexus 5 Original Android Development] Technecium:
Will these be accessible from play version of fku or just betas for now?

Sent from AOSP koeMod 4.4.2 w/ Franco kernel
[Nexus 5 Original Android Development] bobby janow:
How do you do that? I rebooted last night after spending 24 hours at around 500 free. Went up to 1.1 GB on the reboot then dropped to 600 almost immediately and has stayed there all night. That's fine but how do you maintain 1gb free?
[Nexus 5 Original Android Development] ivan08v:
I had two random reboots last 30 minutes

http://pastebin.com/CFw5iDYE

http://pastebin.com/1KBB567P

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] snives:
Short reply from somebody who admits they didn't read it and would rather make blind assumptions than act intelligently when the post talks about spending more, not saving money.
[Nexus 5 Original Android Development] G-DannY:
Apart from low sound, for me latest r33 test is perfect

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] aldyu:
Hmm.. wondering why this kernel is also experiencing memory leak as cm does. :angel:
[Nexus 5 Original Android Development] P.Mobile:
yea thats the only prob i have also... other then that its beast!:good:
[Nexus 5 Original Android Development] big_adventure:
The cute little angel smily doesn't cover up for three things:

1. This kernel doesn't experience a memory leak in the released version.

2. This kernel no longer experiences a leak in the test version.

3. At least 10% of the last 1000 or so posts of the thread deal with this in extreme depth, so reading would have covered it for you.
[Nexus 5 Original Android Development] snives:
We obviously don't agree and beyond monitoring yourself there is no way to know how each individual acts, but I appreciate that you but both the care and thought into a reply. Rather than clogging this thread up anymore I'll end my talk on the subject by saying that I do not actively run the service because it is only every several months at shortest I see a need for it. Thanks again for not being part of the caustic degeneration that plagues the internet.
[Nexus 5 Original Android Development] aldyu:
I was referring to the previous test kernel and that's why I wondered because I read the comments. I looked at the github and found out that most of the commits were cm commits also. Got my answer already buddy. ;)
[Nexus 5 Original Android Development] Smallsmx3:
Its because of the same CAF patches present in both Kernels
[Nexus 5 Original Android Development] big_adventure:
Like I said, I've got no horse in this race and really don't care one way or the other what you do with your phone. It's just the presentation that bugs me.

---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------

Two things there:

1. Since a new test kernel had already been launched (more than a day and a half before), and you didn't mention where you saw a memory leak, you're fluffing up the thread with things GUARANTEED to be misinterpreted by casual readers and which no longer apply.

2. Since you didn't mention either your motivation of the post or the fact that you'd found an answer to your question, you invited a response giving you that information.
[Nexus 5 Original Android Development] Rxpert:
At home on wifi I've gotten 7 hours SOT and 19 hours off standby with 10-15% battery remaining on my N5.

Environmental factors can play a huge role though
[Nexus 5 Original Android Development] franciscofranco:
I never used that cpu-boost driver, I implemented the thread migration code on interactive and never made use of any different thread. I get along the ride of interactive's speedchange thread and it takes care of the thread migration boost. It works great, never had any problems.

What iowait stuff are you looking at?
[Nexus 5 Original Android Development] franciscofranco:
Pushed a new r33-test (hopefully the last) which fixes the notification sound derp, has a couple of merges with fixes and introduces all those new Hotplug driver tunables. Take note that FKU won't show you any tunables because I have yet to update the app to support them. The path is /sys/class/misc/mako_hotplug_control/ the documentation of each tunable is on my github in the top commit and I posted it a couple pages ago. Have fun http://192.241.177.15/Nexus5/4.4/tests/boot-test33.img
[Nexus 5 Original Android Development] hanschke:
anyone test the new beta of today with cm?
[Nexus 5 Original Android Development] vomer:
Flashed! Time for some action :D

Sent from my Nexus 5
[Nexus 5 Original Android Development] baedaa:
unfortunately not fixed here :(
[Nexus 5 Original Android Development] vomer:
Stop making cm happen... It's not going to happen.

Sent from my Nexus 5
[Nexus 5 Original Android Development] carlese:
Really? Anyone can confirm? I was about to flash :(
[Nexus 5 Original Android Development] yukkio:
Yes, same here, lowest notifications sound
[Nexus 5 Original Android Development] baedaa:
you tell me, flashing just takes one reboot ;)
[Nexus 5 Original Android Development] asm19:
+1
[Nexus 5 Original Android Development] franciscofranco:
Weird it sounds normal on my device... crap :crying::crying::crying:
[Nexus 5 Original Android Development] Techimplant:
Yup..low nofication sound for me too..I was wondering whether I flashed it properly or not..coz the name is still r33 in settings..so couldnt tell if it was the new one..

Bit still ..I too have low notification sounds
[Nexus 5 Original Android Development] baedaa:
you can see the build date in phone info, mine says feb6 03:00:55
[Nexus 5 Original Android Development] franciscofranco:
Its still r33 but you can see the date of when it was compiled .......
[Nexus 5 Original Android Development] Techimplant:
Ya thanks..its Feb 6 only..so its the new one..
[Nexus 5 Original Android Development] carlese:
I have no idea what I'm saying but [MENTION=3292224]franciscofranco[/MENTION] isn't it possible to copy paste the sound related things from r32 to r33? So we can all have the goodies from r33 and the sound from r32..
[Nexus 5 Original Android Development] micr0g:
Seems that the latest beta version of this kernel

is smoother than r32,i mean on scrolling.

True or placebo?:P

Also i have one random reboot when i tried to use Geekbench app
[Nexus 5 Original Android Development] blueren:
I see what you did there! ;)
[Nexus 5 Original Android Development] franciscofranco:
Lol no, doesn't work like that...
[Nexus 5 Original Android Development] Bobtehblob:
Had two reboots within the last 15 minutes Franco. Didn't get the log in time for the first reboot but here's the second one!

http://pastebin.com/pmwa2p9F
[Nexus 5 Original Android Development] hanschke:
whats the problem? I dont have read that the support will not be added. other people cry for other custom rom support too and from the past all work and no one wrote that this is a stock only kernel now :eek:
[Nexus 5 Original Android Development] franciscofranco:
Re-uploaded test-33 image, now speaker sound is back to normal.

No idea, something in the display driver blown up. Using the latest test 33 image?
[Nexus 5 Original Android Development] hellsgod:
Then you haven't read enough. CM won't happen. Clearly stated, multiple times.

hells

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] baedaa:
thats how we like it :D It's working! Huge thx
[Nexus 5 Original Android Development] Techimplant:
+1 ..its done..its time to change the name of the thread to r33 :D ..thanks

And for r34 can we introduce a patch that increases the flappy bird score ..My best is a pathetic 24 :rolleyes:
[Nexus 5 Original Android Development] baedaa:
I've deleted this app in rage about 6-7 times and reinstalled it when I calmed down. you call 24 pathetic? 14. :rolleyes::rolleyes::rolleyes:
[Nexus 5 Original Android Development] imablackhat:
I flapped to 82. Trying for 100.
[Nexus 5 Original Android Development] Techimplant:
Oops ..then I will treat myself with a pat on the back and a beer ..I have deleted the app many times too..irritates me like anything.. So keep trying harder..all the best..
[Nexus 5 Original Android Development] MaxNXS:
Not to be a party pooper, but can we keep the Flappy Bird talk out of this thread? Nothing personal, but It's kind of annoying, seeing the same "in the next version can you add [random nonsense about Flappy Bird]?" joke in every other thread.
[Nexus 5 Original Android Development] cavolo:
Hi franco, yesterday I've had a random reboot, but no time to post it here, so it comes. With the "last" r33 (not from the one from today, but the last before ;p )

http://pastebin.com/rNZ7BR3n

I was just checking time (screen on then screen off), some sec later it rebooted.

e: build: Tue Feb 4 16:41:36
[Nexus 5 Original Android Development] thesebastian:
About Audio issues:

Just to summarize, 2 builds were compiled today.

- In the build compiled at 03:00:55 WET I found audio issues.

- In the build compiled at 16:14:33 WET I think there are no audio issues. At least the volume level seems to be the same as of the r32 build.

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] omvir:
You obviously haven't played flappy bird.
[Nexus 5 Original Android Development] vomer:
:D :angel:
[Nexus 5 Original Android Development] franciscofranco:
Yep its fixed now. I had to read back to Google's merges for 4.4.1 to understand what was going on with the low latency playback. Some audio patches I merged added support for Ultra Low Latency playback which makes some audio with small buffer sizes to not get post-processed in the DSP, which according to one of the patches merged by Google the speaker audio needs to go through the DSP or it gets really bad quality. Reverted the ultra low latency patches and all is golden again.
[Nexus 5 Original Android Development] fugn:
Thank you for the quick fix Franco. I'm running stock rom, stock fku setting so I rarely have any crashes to report...unfortunately.
[Nexus 5 Original Android Development] abjexstallion:
That patch made the speaker sound clearer, but really low imho.

Straight from my franco.fied SLimHeAD... After all it's a ?NEXUS?
[Nexus 5 Original Android Development] r.suchil2:
new r33 uploaded on 2-6 contains the fix to the audio?
[Nexus 5 Original Android Development] OMGBEES:
Just flashed it. Audio still quiet for me.

Edit: Oops. Missed Franco's post about re-uploading. Going to grab again and test. Others have reported it being fixed so I'm hopeful.