yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] dashqa:
Thanks for update.

Is it me or test 4 is more laggy then test 3?
[Nexus 4 Android Development] manulemaboul:
It's you I guess :)

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Android Development] lordvj:
oh :( sorry to hear that, take care brother another door will open
[Nexus 4 Android Development] fabian.m:
Sorry for that. Same thing happened to me 2 weeks ago, hope you'll get better soon.
[Nexus 4 Android Development] gpvecchi:
I got notification delay under wifi with M3 for the first time... I tried even with stock M3 and that's the same.

I posted even on Franco thread, and they say it's a coincidence...

No problems with the one with Prima drivers...

EDIT: Test 4 shows rev 156 in phone status...
[Nexus 4 Android Development] sirxdroid:
Are kernel wakelock stats enabled in this kernel?
[Nexus 4 Android Development] ameinild:
Nice! Gonna try these soon enough...
[Nexus 4 Android Development] sNiPe78:
I have also #156 in the phone status for the M3 linaro and the test versions...

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Android Development] pnut22r:
Change scheduler to "ROW"
[Nexus 4 Android Development] dashqa:
Always ROW
[Nexus 4 Android Development] sirxdroid:
Does the scheduler really make a difference? I doubt we're talking about intensive sdcard I/O here.
[Nexus 4 Android Development] Luigiesin:
It does... But not much

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r156-Linaro T3

T-Mobile
[Nexus 4 Android Development] pnut22r:
+1

This is after flashing test 4

Although it probably just says that, because simple governor is included, and franco 156 did not have that. He added it with r666 before m3

Thoughts?
[Nexus 4 Android Development] coldhardtruth:
Go BEARS!!! You're all welcome for the relevant contribution. That is all.
[Nexus 4 Android Development] pnut22r:
Bill Swerski from SNL "Superfans"

"That's right. Da question is: Now, did God create Da Bears, and make them superior to all teams? Or is he simply a huge fan, and Ditka made them superior to all other teams?"

"Bears"
[Nexus 4 Android Development] arief347:
Nice update..thank you guys..
[Nexus 4 Android Development] LaboDJ:
It says 156 but it is M4...
[Nexus 4 Android Development] dark_ente:
I think you mean m3

Sent from my Nexus 4
[Nexus 4 Android Development] currydude:
Guys it's just a name. Probably didn't do a clean build but it's m3.
[Nexus 4 Android Development] atomic339:
So is there any problems on test4?
[Nexus 4 Android Development] pnut22r:
Negative
[Nexus 4 Android Development] sirxdroid:
[MENTION=702102]LaboDJ[/MENTION] - could you please enable kernel wakelock stats in your builds? I don't see a good reason to keep them disabled. Thanks!
[Nexus 4 Android Development] gharrrrrr:
I wonder what the good reason is for having them enabled? Has your batt life been bad? Is there a serious drain on battery that you think can only be attributed to the kernel? Or just curious to see what is there even though everything is working great?

Sent from my Nexus 4 using a flounder.
[Nexus 4 Android Development] sirxdroid:
Curiosity mainly. If it's there in the stock kernel why not just let it be? After all how else could we have found the early msm_hsic_host wakelock problems?

Also, the other day I woke up to a drained battery. I was running a setup that was giving me great battery otherwise. I looked at the kernel wakelock stats and suspend_backoff and smd_sns_dsps wakelocks were the culprits. So something went wrong overnight. Not sure what, but a reboot fixed it. Could I do something about it? Not really, but at least I had some clue of where things went wrong, otherwise I would have been left staring at a blank page instead of the kernel wakelock stats, wondering what might be behind the black wallpaper.
[Nexus 4 Android Development] gharrrrrr:
Hmmm. Valid enough points.
[Nexus 4 Android Development] hospital349:
I completely understand what you're getting at and appreciate that it's nice to see the msm_hsic_host wakelock information as Google intended.

I also see it from Franco's perspective. I've followed his thread from the very beginning and unfortunately the wakelock complaints became vexing to say the least. The thread became overcrowded with repeating users moaning about their msm_hsic_host percentage rates and requesting stupid 'hacky' fixes that Franco just didn't want to include (with good reason not to... as there aren't any sophisticated solutions.) Thus, he removed the msm_hsic_host wakelock stats from the kernel, so that folks would spend more time enjoying their devices and less time worrying/stressing about 'irrelevant' figures.

Irrelevant why? Well, if these statistics were again made available to us, how would we take advantage of them? What difference would it make after knowing the msm_hsic_host percentage? We all know the wakelock exists on our devices. Google will perhaps fix this in due time. Unfortunately, the issue is inevitable and whether or not the numbers of this problem are made accessible to the masses, the problem remains the same and conclusively, we're still stuck with it.

I think Franco made the correct decision, all-in-all. I haven't noticed much talk of the subject since he removed the elephant from the room. I know it's difficult to ignore the drain, I for one have OCD regarding such things. However, I do find peace of mind in 'not knowing'. :)
[Nexus 4 Android Development] raptor22:
r161 out ;)
[Nexus 4 Android Development] markd0wn:
r161 out...

* Fixes a bug on the CPU load calculator

* Small code optimisations from upstream Linux Kernel

Not sure if that latest change is already in these test builds since the upstream linux kernel is merged, but worth a build anyway since there's another change besides that.
[Nexus 4 Android Development] sirxdroid:
Not sure why this is such a huge problem only for the Franco kernel. No other kernel I know of disables them and I monitor pretty much all kernel threads, I don't see people complain about kernel wakelocks left and right. Sure, there's occasional mention but it doesn't seem to be a big deal (there's currently some chatter in the Semaphore thread, but it's civil and contained, I find it instructive not annoying).

I guess I have to learn how to build the kernel myself and re-enable the stats :)
[Nexus 4 Android Development] giangi88:
I had kernel wakelocks because of .27 radio not compatible with my router... so not kernel related...kernel wakelocks stats are useful, no doubts, otherwise how could I find the cause of battery drain?maybe I would have flashed roms and kernels with no results...
[Nexus 4 Android Development] sirxdroid:
+1 this is the value I see too, it points you in the right direction, it doesn't mean the kernel is broken or there's anything you can do about it on the device side, but it may point to incompatibilities that you can solve in other ways.
[Nexus 4 Android Development] matesc:
Hint: r161 is out :thumbup:
[Nexus 4 Android Development] deltatux:
We will need to wait until LaboDJ to recompile the r161 kernel with his improvements ... and so the waiting game starts lol.

Looking forward to the release.

deltatux
[Nexus 4 Android Development] LaboDJ:
R161

Test 4 - R161

Downloads and MD5s in OP!

:good:

The difference from test 4 to normal one is upstrea, fixes from linux kernel 3.4.51, bluetooth and power fixes now are in "stable one"
[Nexus 4 Android Development] GJ123:
Thanks!

I'd like to know if you know how I could build my Cyanogenmod builds for personal use directly with your kernel?

At the moment I'm trying to learn about compiling from source et cetera and I succeeded in building the basic roms and now I'd like to start on different stuff like replacing the kernel directly while building.

Any help would be appreciated!
[Nexus 4 Android Development] jawz101:
where's the config file for this kernel? I can't do an adb pull /proc/config.gz because it says the file doesn't exist??

nm. I guess you left it in /arch/arm/configs
[Nexus 4 Android Development] jawz101:
labodj- are you using ccache to compile? I get errors saying permission denied when I try to compile

btw, I'm using ccache version 3.1.9+319_gd1b2219 (latest build off of github since it has commits referring to get it working with gcc 4.8

and linaro toolchain gcc-linaro-arm-linux-gnueabihf-4.8-2013.06_linux

and copied it to a folder under my /home/user/ directory.

I'm on Arch Linux and then run commands:

cp /home/user/repos/mako-linaro/arch/arm/configs/franco_defconfig /home/user/repos/mako-linaro/.config

cd /home/user/repos/mako-linaro

make ARCH=arm CROSS_COMPILE=/home/user/gcc-linaro-arm-linux-gnueabihf-4.8-2013.06_linux/bin/arm-linux-gnueabihf- -j4

the error I get is:

ccache: error: execv of /home/user/gcc-linaro-arm-linux-gnueabihf-4.8-2013.06_linux/bin/arm-linux-gnueabihf-gcc failed: Permission denied

My guess is either you might've not been using ccache, ccache isn't working for linaro 4.8.x or I'm not using the right toolchain?

I'm leaning towards me not using the right toolchain because I haven't done kernel compiling in about 2 years. I figured I'd brush up with yours as a great starting point :fingers-crossed:
[Nexus 4 Android Development] deltatux:
Is it me or the Test kernels seem to have audio skipping issues when using it with PowerAMP? I've been using all 4 tests and PowerAMP keeps skipping (at random points, as if it's having a hard time keeping the buffer full, I'm not running anything excessive)... Works fine on the non-Linaro franco.Kernel.

deltatux
[Nexus 4 Android Development] sirxdroid:
When I read about this issue in the past it was due to the I/O scheduler and/or the read-ahead buffer size. Are you using the same values for both the regular Franco and this Linaro build?
[Nexus 4 Android Development] deltatux:
I set my franco.Kernel Updater to use default values and all I've only tweaked was using row instead of deadline and underclocked the CPU to 1350 MHz.

If the values aren't default somehow, can you please let me know what they are?

Thanks,

deltatux
[Nexus 4 Android Development] sirxdroid:
That's probably where you want to look. The defaults for Franco are deadline and 512 buffer. Not sure whether underclocking would affect it too, why don't you try all defaults and make one tweak at a time and see which one causes it. If you find it, please post.

Edit: noop is a very simple I/O scheduler you may want to try. When you play music it's probably all reads from the sdcard anyway. I think there were problems when people tried to increase the buffer size. Try 512, 256 or the stock kernel default 128. Btw, the stock kernel default is cfq/128.
[Nexus 4 Android Development] deltatux:
Deadline was causing more problems than row, that's why I went with row. I'll try no-op. The read ahead value on my ROM is 2048. The Dalvik cache is set to 512M. My SD card buffer is set to 2M (2048kb).

I tried stock 1512 MHz, did nothing in terms of fixing the audio gap.

deltatux
[Nexus 4 Android Development] sirxdroid:
2048 read-ahead is too much, start with 128, then bump it to 256, 512, 1024, etc. See if it fixes the problem and where the problem starts.
[Nexus 4 Android Development] deltatux:
changed it back to deadline and using 512 for read-ahead. 256 was meh, 512 is better. Preliminary testing shows promise. Will see how it'll hold up during more testing.

Thanks.

deltatux
[Nexus 4 Android Development] arief347:
Any chance for r161 can be use for miui?
[Nexus 4 Android Development] LaboDJ:
Sorry I have no time to explain how... I'm preparing an exam...

I never compiled ROM, they are different things

You can't extract it from /proc/config.gz, it's in my github (see op) under arch/arm/franco_defconfig

Don't know.. i'm using ccache and gcc installed using apt-get (ubuntu 13.04)

i'm using this toolchain: https://launchpad.net/linaro-toolch...arm-linux-gnueabihf-4.8-2013.06_linux.tar.bz2

i put the toolchain in /opt/toolchains not in /home, dont know if it changes anything

It works on miui... now MIUI will work with normal version, try it!
[Nexus 4 Android Development] rikmer:
162 is out.
[Nexus 4 Android Development] LaboDJ:
R162

Test 4 - R162

See OP
[Nexus 4 Android Development] mesarabi:
is it support miui v5?
[Nexus 4 Android Development] Taebom:
Yes
[Nexus 4 Android Development] mangomonkey00:
is this already undervolted or is at stock values

how much can i undervolt i have a faster chip(for eg -100 or -150) on this kernel
[Nexus 4 Android Development] Pilatus47:
It´s not undervolted.

You can try by undervolting -25 and see if the device doesn´t shut down.

I´ve undervolted -100 all the steps and all is working good. I have a FAST chip.

Saludos
[Nexus 4 Android Development] yethz:
I have Faster Bin chip rev11, but I dont undervolt lower than -50...

IMO, hardware in our Nexus 4 needs those power to perform tasks we do in our N4..

• Sent from Nexus 4 via Tapatalk

• Rom: AXI0M (6/18) / Kernel: Franco #162
[Nexus 4 Android Development] manulemaboul:
Power is not measured in volts, my fast bin is happy with at least -100mV with less heat and a little less drain :)

Envoyé depuis mon Nexus 4 en utilisant Tapatalk 4 Beta
[Nexus 4 Android Development] alen1901:
If you ask me, best read ahead value is half of RAM available, so, 1024, or 896. Everything more from that is a waste.

Sent from Sparkling Nexus 4
[Nexus 4 Android Development] sir*mez:
[MENTION=702102]LaboDJ[/MENTION]

I was looking on your git and franco's, I saw you merged too early. Your arch/arm/kernel/load_stats.c doesn't match franco's. For example, his line 74 doesn't match your line 75.
[Nexus 4 Android Development] sirxdroid:
You do realize the N4 has 2GB of RAM while the read-ahead buffer is set in KB? You do not want 1GB read-ahead buffer.
[Nexus 4 Android Development] gpvecchi:
I tested stock Franco, Franco+Prima, Franco+Linaro and Franco Test 4 with Antutu (just CPU+mem); all results are similar, around 2100/2300, except with test 4: more than 4000!

There's something wrong or result is just amazing?

Oh, I make my phone cold before every test, to avoid thermal throttling.
[Nexus 4 Android Development] alen1901:
You do realize that i didnt put MB there after my numbers? I said, half of ram of phone, and its 1024. But ofcourse, read ahead is set in KB, so, go figure.

Sent from Sparkling Nexus 4
[Nexus 4 Android Development] sirxdroid:
Given that the RAM size is 3 or 6 orders of magnitude (depending on how you quote it) bigger than the read-ahead buffer size, I'm not sure I understand why read-ahead buffer is a function of the RAM size. It has a lot more to do with the characteristics of the flash, scheduler, etc.
[Nexus 4 Android Development] alen1901:
Because read ahead uses ram to save "data", and if read ahead value is too big, there would be too much of data which phone probably wont use, so its a waste of memory.

Sent from Sparkling Nexus 4
[Nexus 4 Android Development] sirxdroid:
I'd buy that if we had 10 MB of RAM on our phones, but with 2048 MB, RAM is really the last thing to worry about on the N4. Looking at mine, I seem to constantly have at least 1GB free. Even on my GNex that has about 150MB RAM free, I would have no problem giving 2MB to the read-ahead buffer. Read-ahead buffer should not be a function of RAM on any device. In spite of what many people may think, a bigger read-ahead buffer does not help in practice (it just makes synthetic benchmarks look good), in fact it hurts music playback for example, there are many reports of it.
[Nexus 4 Android Development] ctfrommn:
Indeed.... There's a reason Google choose 128kb.... I do think 256 or 512 is the upper limit for a good user experience.

Sent from my blazing bionic Nexus 4
[Nexus 4 Android Development] cannibalcollier:
I know you don't need it but figure I'd ask if you had any idea when you're going to put a test build out with faux sound driver?
[Nexus 4 Android Development] logicmd:
Hey LaboDJ

Have u ever consider using goomanager to maintain the kernel auto update ?

BTW Mediafire is unaccessible in china,

would you please maintain you kernel another mirror like goo.im?

goo.im could be more statble worldwide
[Nexus 4 Android Development] jtwlbz:
I am against goo since that's hell slow
[Nexus 4 Android Development] jsauder2:
ya, it'd take forever to download that whole 6mb file...

I agree with you on roms that area few hundred mb's, but this shouldn't make a difference. and even if there was a speed discrepancy, it would be offset by being able to use goo manager to get update notifications.

Sent from my Nexus 4
[Nexus 4 Android Development] Fobz:
What provided? I'm able to on China telecom, even on Unicom 3g.

Sent from my Nexus 4
[Nexus 4 Android Development] logicmd:
agreed. 6mb is small. Moreover Goo provide you update notification.

---------- Post added at 03:15 PM ---------- Previous post was at 03:10 PM ----------

Unicom 3g is okay. But Mediafire is reset in China Unicom as well as CERNET.

I suggest using more mirrors other than Mediafire to provide higher accessibility worldwide.

If LaboDJ could include your update address in Franco updater that would be the best.

Otherwise Goo is an good option. It has a native app to provide you instant update notification.
[Nexus 4 Android Development] bigroof:
I can post a mirror on Google Drive if OP is cool with that.
[Nexus 4 Android Development] momomok:
my phone didn't wake up this morning

not really sure if it is app/ROM/kernel issue though...

last_kmsg attached:

https://dl.dropboxusercontent.com/u/23739553/last_kmsg
[Nexus 4 Android Development] drakexpl:
UV?

Wysłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Android Development] momomok:
not sure if you are asking me... but no

no UV

no OC
[Nexus 4 Android Development] yethz:
Thats the best practice to test a kernel and help the developer to fix what the kernel offers.

And when it hits the stable version then play with what u want and never expect support from devs lol..

• Sent from Nexus 4 via Tapatalk

• Rom: AOKP_PUB (6/25) / Kernel: Franco #162
[Nexus 4 Android Development] RaydenEris:
After the new quadrant release the true power of the Nexus is revealed?!?! I normally don't post benchmark screenshots but.....
[Nexus 4 Android Development] markd0wn:
r163 out:

* Two security patches from Codeaurora to prevent illegal access into memory

* Add a security patch from upstream

* Add a patch from Codeaurora that improves performance of the GLUpdator thread in the video framebuffer for performance improvements
[Nexus 4 Android Development] Luigiesin:
Nice! Hey DJ, could you please include the supercharge (fast charge) option if you compile 163? That option is a life saver!

Thanks for your work brother!

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco 162 - Linaro T4

T-Mobile
[Nexus 4 Android Development] phillysnexus:
Holy smokes what ROM and kernel are you running? I assume Franco linaro but what number and what ROM :)
[Nexus 4 Android Development] LaboDJ:
R163

Test 5 - R163

- Kernel 3.4.52

Downloads and MD5s in OP.
[Nexus 4 Android Development] Guzanni:
My N4 running like a beast thanks to this kernel with Aliendroid 3.0 :)
[Nexus 4 Android Development] arief347:
We have the same rom and kernel..the best combo i ever tried :D
[Nexus 4 Android Development] :
Any way you could include the prima drivers?
[Nexus 4 Android Development] Luigiesin:
Oh man.. Please don't... Those drivers are known to cause more issues than good... Especially wifi battery draining.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r163

T-Mobile
[Nexus 4 Android Development] lsv-1:
I've been using Franco Kernel with the latest prima driver and Faux sound with no issues at all. No battery drain / phone reachable during deepsleep.
[Nexus 4 Android Development] sNoxious:
+1. No battery drain for me as well, matter of fact it gives me good WiFi speeds. But that's the OP's decision, it's up to him if he wants to add it or not and it's stated in the OP. :good:
[Nexus 4 Android Development] Luigiesin:
You're lucky... A lot of us experience problems with those drivers... That's why a lot of devs rather not use them.

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.60

Kernel: Franco r163

T-Mobile
[Nexus 4 Android Development] jtwlbz:
I don't like that kernel with prima stuff.
[Nexus 4 Android Development] fatjoejr2001:
Prima drivers work perfect for me and definitely increase my WIFI speeds.

Tap, tap says the wicked NeXus⁴
[Nexus 4 Android Development] pitjago74:
There is all ready a post with franco+prima drivers:thumbup:

Here. http://xdaforums.com/showthread.php?t=2272140

I prefer with out primadrivers:D

N4 Revolution&Demolition&NBK
[Nexus 4 Android Development] gharrrrrr:
http://xdaforums.com/showthread.php?t=2300873

This thread works well for me. I haven't tried the prima driver kernels myself because I was also afraid of the wakelock issues vs slower speeds and driver bugs which would lead to re-flashing rom or reset kernel. I've read great results within both threads. Worth a look and I'm still open to incorporating prima drivers if they are stable don't contain some of the wakelock bugs that have been mentioned. Cheers. 2¢

Sent from my Nexus 4 using a waffle iron.
[Nexus 4 Android Development] occtec:
Hey guys can I get clarification please. I've been told we cannot use faux sound or display with Franco kernel. Is it possible with this modified Linaro Franco version?
[Nexus 4 Android Development] murph187:
Oh my goodness this kernel is so damn fast on linaro ROMs. Using it on latest carbon nightly and its so much snappier. Although I have to admit the delayed notifications are bothersome enough that I am forced to switch back to the Franco kernel with prima drivers. I know Devs all hate requests, but please please include prima drivers with this incredible kernel! Thanks again for your great work :)
[Nexus 4 Android Development] occtec:
Can someone please clarify, should I be downloading kernel from test folder or zip folder from download site? I presume it would be from zip folder and download r163-linaro.zip

Please correct me if I'm wrong. Also can I just flash this over the top of Franco's kernel or do I need to flash stock kernel first.

Thanks in advance.
[Nexus 4 Android Development] szucsgf:
Just flash over franco.

Differences in test kernel:

- Upstream merge with linux 3.4.y kernel

- Latest code from Franco (newer than nightly one if it exists)

That's from OP.
[Nexus 4 Android Development] occtec:
Thanks for your reply, which is best to use? I'd like to flash this kernel over Aliendroid 3.0
[Nexus 4 Android Development] szucsgf:
I hate to give this kind of advice but it's really the best I can do for your question: try both (and the regular Franco kernel too) and see which gives you the best results, based on your own goals.

I personally find the regular Linaro build gives me the best performance, but I wouldn't use my experience, with very different setup and usage, as a very reliable guide.
[Nexus 4 Android Development] roilosh11:
Hey all,

I read the OP but for a noob like me it's kind of difficult to understand, what's different in this supercharged franco kernel than the original one? Better battery, performance boost (the linaro O3 optimization)? And is this kernel compatible with every ROM like the original franco kernel? Thanks in advance and sorry if my question has already been asked! :)
[Nexus 4 Android Development] Taebom:
Compatible with all ROMs original Franco works on. And as far as I know supercharged versions have been discontinued for the latest nightlies.
[Nexus 4 Android Development] ZuLa:
Working great with latest miui,

Thanks!!
[Nexus 4 Android Development] roilosh11:
Running great on my phone but i was under the impression that it would support touch control like the original franco :confused:
[Nexus 4 Android Development] :
What's touch control?
[Nexus 4 Android Development] Taebom:
http://xdaforums.com/showthread.php?t=2101488
[Nexus 4 Android Development] Federico_96:
I was thinking to give it a try but i would like to use touchcontrol...are you sure that it's not working ? maybe [MENTION=702102]LaboDJ[/MENTION] can explain us how to enable it or add support ;)