yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] _motley:
New build 32 to be uploaded in a bit:good:

Haha, good to hear. Simpler is better is my motto as well. If I have to use more than an init.d script for my day to tday, something doesn't sit well in my world. That said, all the apps we talk about here are awesome for tuning and troubleshooting. I can't live without them for that purpose.

AFAIK, we have the same hsic fixes in place that thracemerin pushed forward in his git repo. We consult with each other from time to time and discussed these patches before we dropped them in. I poked around in his thread a bit and see that he has the same thing where a small minority of users have data drops and some attribute them to these patches. It's just hard to say whether these patches attribute to them happening at a higher frequency or not. I looked on Google's issue tracker are even there you can find folks on the stock kernel/ROM that also report this issue. It would be cool if we could come up with a test that was easy to reproduce for everyone, unfortunately I don't see that happening due to all the complexities.

Interesting, I use system tuner pro (paid version) quite a bit and haven't seen this phenomenon. I just ran a test and it doesn't spike above 1.5 when running a benchmark. Let me know how to reproduce it in System Tuner if you have to do some things first before you see it start occur.

Yes /sys/devices/system/cpu/cpu2 (or cpu3) do not have a cpufreq folder, this is just how the topology is laid out. It is the same with stock as well. CPU 0 is the policy cpu, so all others should follow accordingly.

Yes, using XZ. On a modern CPU, you will not see much difference in total boot time, maybe 100ms or so (tenth of a second). As compared to lzo, kernel load time is faster and decompression is slower. As far as boot speed, it comes out in the wash on this fast device. So, I opted for XZ since boot time almost matches lzo, but zip files use quite a bit less storage space (about 33% less).

I would call 594MHz to 1.02GHz mid-range. But most importantly on this kernel, don't UV 1.02GHz too much or you may get random reboots since it is the default boostpulse frequency for the interactive gov. Low range is 304MHz and 486 mainly. UV these too much and you may get a SOD. That said, all devices handle UV differently, even those of the same bin tag. Above 1.02GHz is the high range...UV these too much, especially your highest set frequency, and you will freeze with doing intensive operations or when throttling down freq steps from intensive operations (thermal throttle).
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Thanks motley! Yea, I kind of figured both kernels had similar patches, so it was odd to see it happen on yours but not his. I probably just didn't notice it at all when running matrix.
[Nexus 4 Original Android Development] j3di:
Thanks Motley for the explanation. It was interesting to see that the System Tuner app init.d script writes the CPU max/min settings to all four CPU folders, even if they don't exist. Guess I can delete CPU 2 & 3 from the init.d settings then. Why is there a CPU freq folder for CPU 1 though if it is not used?
[Nexus 4 Original Android Development] _motley:
Experiment build 32 posted (beta)

exp b32 has now been released (see OP for details). Let me know how it goes. Nothing earth shattering in this build, but still looking for feedback as far as smoothness, battery etc.

Yeah, System Tuner init.d script generation doesn't differentiate between different devices when it writes the script, it doesn't know any better. Since the settings don't exist for cpu 2 and 3, the script will fail to execute for these lines, but it won't hurt anything. I would still edit the file on my own script to remove the extra two lines just since I am anal that way LOL. CPU1 still has a cpufreq folder because of the way the topology is mapped out for our setup (physical id, siblings etc.). It is still used internally within the kernel.
[Nexus 4 Original Android Development] chinthekng:
just to be sure if i wan to flash r32 fresh on a new rom all i have to do is flash r31 and then r32, no more need for r17
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

yes

Sent from my Nexus 4
[Nexus 4 Original Android Development] FrankBullitt:
It's booting (exp32 over the exp31 I was using). I'm gonna try it for a while, launch a couple of games and browse a bit with it. I'll report later :)

Edit: btw, I'm on Jellybro from Euroskank. So far it's been a great combination to use.
[Nexus 4 Original Android Development] z3r0_x:
Motley, would it be possible to upload to goo.im or Dev Host in the future? Somehow the xda servers are painfully slow...
[Nexus 4 Original Android Development] FrankBullitt:
This might be a simple placebo effect, but I was feeling some lack of responsivness from the touchscreen with build31 on top of the latest euroskank nightly, but with this build32 things look a lot more fluid.

Like I said, it might be a placebo effect, but so far I was using playerpro to listen to a couple of songs, ran antutu benchmark just to push the machine a little bit, saw an youtube video, scrolled a lot back and forth, and I haven't got a single touch on the screen that didn't respond back... The temperature of the phone is also good, no heating at all even when I was multitasking with video playing on background.

Also, scrolling through my gallery of pics just feels "snappier".

Motley, are you sure this was just a minor release? Those interactive gov tweaks seem to be perfect! ;P
[Nexus 4 Original Android Development] jhericurls:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

It feels faster cause its a new install and if your clear cache that helps.
[Nexus 4 Original Android Development] FrankBullitt:
Shouldn't be that. I have a terrible habit of cleaning the cache and the dalvik once or twice a day... got that old habit when using my old Xperia Neo and flashing a couple of roms per day :p

I'm guessing the interactive governor tweaks on this build really make a big difference from build 31.
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

@motley b32 ->holy ****
[Nexus 4 Original Android Development] Are.Two:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

I'm really loving b32. It's running extremely smooth and am getting great battery life with it thus far. Will keep testing but initial impressions are awesome.

Sent from my Nexus 4
[Nexus 4 Original Android Development] samwebbo1990:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

WOW loving #32! So smooth and looking very battery friendly! Thank you Motley :)
[Nexus 4 Original Android Development] j3di:
b32/CM10.1

If I never update my device ever again I couldn't be any happier! Great kernel, great dev! Thanks Motley.
[Nexus 4 Original Android Development] ms0chez:
Okay so motley is gonna be the first kernel I flash on my n4, I just want to make sure I have this right: Normal wiping, flash rom/gapps/etc, anykernel b31, then anykernel b32? Is that right?
[Nexus 4 Original Android Development] ltylty123:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

B31 has to be stock/cm version. Do not flash anykernel b31 but those version in your case.
[Nexus 4 Original Android Development] mko000:
ROM, gapps then kernel, that is correct.

You have to flash b31 (Stock, AOSP or CM) before b32 (anykernel).

If you already had this exact ROM flashed, you don't even have to wipe the caches.

When you update to a new version of this kernel, flashing the kernel is enough.
[Nexus 4 Original Android Development] elkhouri:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

No. B31 Init.d or CM depending on your ROM, then any kernel b32.
[Nexus 4 Original Android Development] apascual89:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Motley great work, b32 working great so far! I haven't had any data issues.

Anything in particular you want us to look out for?
[Nexus 4 Original Android Development] JeanEatsWorld:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Hello guys, I just flashed thus kernel, last update, but the color are so bad.. don't know why but the black seems dark grey and everything is more washed out then usual..

Can someone suggest me a good combination for try to correct it with faux app?
[Nexus 4 Original Android Development] ms0chez:
Got it, thanks guys! Downloading correct kernel now. One last question....what rom are most of you guys running with motley?
[Nexus 4 Original Android Development] apascual89:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

This is my setup. For me it's nice. I have it to set on boot.
[Nexus 4 Original Android Development] ogrillion:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

So I am having issues and hoping someone can assist. Love this kernel but I have data drops with it.

Basically I turn the screen on and my bars are gray and I have no data for a second. Its not a huge deal but groove IP stays disconnected till I turn the screen on.

It almost feels like I have a power save app that turns off my data, but I don't.

It happens with faux and this kernel, not with hash or stock though.

Anyone else have this and maybe fixed it aside from running stock or harsh. Thanks
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

On WiFi?
[Nexus 4 Original Android Development] ogrillion:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Yeah WiFi mostly. I don't know about mobile hardly on it.

Edit - I did check to make sure WiFi policy isnt set to sleep or whatever.
[Nexus 4 Original Android Development] thracemerin:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

This is an android 4.2.x problem, its completely unrelated to kernel, the fact that it works on some and doesn't on others is random good/bad luck. There is a fix available here: http://xdaforums.com/showthread.php?p=36046900 but it may significantly reduce your WiFi battery life depending on how busy the networks you use are.
[Nexus 4 Original Android Development] mko000:
More info: http://code.google.com/p/android/issues/detail?id=40065

It also happens with Harsh and other kernels.
[Nexus 4 Original Android Development] ogrillion:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Oh OK thanks for the reply. I thought it was a general wide spread issue but then when it didn't happen on stock I was unsure.

Hate running stock since the battery life and phone temp is higher. Oh well hopefully the new update comes out and fixes stuff.

Thanks
[Nexus 4 Original Android Development] thunderger:
@motley:

Your UV values shouldn't be lowered anymore. I was able to lower by 25 mV, but another 12.5 mV resulted in freezes in games. :D

After changing screen off profile (set in setcpu) to ondemand with 304 up to 594 MHz there're nearly no more lags after waking up.

Only after boot there is ahuge lag untill I can enter SIM pin and device pin and I've to lock/unlock the device a few times.

Two questions:

- Will you merge some "upstream" changes from Linux 3.4.28 or are the "benefits" too small?

- Can you enable GPU UV and OC? I saw this in another kernel, it might be faux' kernel but I'm not sure.
[Nexus 4 Original Android Development] j3di:
See screenshot, real or indication problem?

Latest CM10.1 nightly, b32

Max 1.404/ Min 304

Interactive
[Nexus 4 Original Android Development] _motley:
Agreed, I have not been changing the built-in UV for awhile now. We seem to have a good stable platform for all the binned chips.

Does anyone else have lags on wake-up? I have tried hard to duplicate this, but I don't seem to have this problem on the stock ROM or on Rasbean Jelly. I do have some ideas that I might be able to try. I am thinking of trying two standby frequencies like showp did with 192/384, except I would use 304/384.

As far as 3.4.x upstream patches, I have studied this a bit and found that (1) Many of the patches that matter were already merged in even though Google kept us at 3.4.0, and (2) Most of the patches don't benefit us at all since they are for other ARCH's/hardware that we don't have. My approach has been to find and cherry pick patches that I think will benefit us while keeping us closer to stock as far as all the other merges to the main tree are concerned. For example, awhile back I back-ported some patches from 3.5+ for SMP that won't be found in 3.4.x. If there are particular patches that someone thinks will benefit us, please point me towards them and I will give them a look.

I think we have a perfectly capable little GPU without hacking it. I have tried experimenting with OC'ing the GPU and found little to zero benefit. My current thinking here is that "if it ain't broke, don't fix it". In my testing, I ended up with more heat, less battery, and actually had my first "red LED" experience when bench-marking. If there were games that required more clock to keep up, then it would make sense to look into it further, but I don't see anyone reporting this issue. Any lags in gaming early on were due to throttling events and we should have all those taken care of by now. If the throttle is still an issue, then I give the ability to raise it a bit if you need to.

When this was discussed a couple post back, there was a link and an app to try from chainfire. Give this a look and let me know what you think. Also, take a look at CPU times, reset and then see if the other frequencies are really being used.

Thx, just looking to see if we have make improvements with the governor (smoother UI) and that there are no side-affects to the other merged patches.

If you check out post #2, there is a link to a spreadsheet for a bunch of settings to try. It's really hard to come up with a color default since it is so subjective. There is also an example in post #2 with some values to try. That one seems pretty good to me. I have tried many values that others seem to love and find them to be too dark, or too blue etc. It is very likely that our screens (and definitely our eyes) aren't the same. Before we had gamma, I made an RGB tweak that most seemed to like and then I switched over to LG presets (a partial revert of a Google commit). This is the same base as several other kernels here on this site. It would be nice to find a default that most like, but I am not sure we have found anything that most would agree upon. The good thing is that it can now be changed:good:
[Nexus 4 Original Android Development] apascual89:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Thanks for keeping us in the loop. I haven't seen any negative issues with b32. Sleeps like a baby and responsive ui. No lags for me at all.
[Nexus 4 Original Android Development] j3di:
Hi Motley, this was with the Chainfiire app! CPU times show zero against anything above 1.4 but the Perf Monitor app shows different.
[Nexus 4 Original Android Development] shadow071506:
I'm getting around 38-39C Temperature... is this normal with the latest build(32)? my binning is nominal if that helps... and im in xylon's latest stable rom...
[Nexus 4 Original Android Development] jazzboyrules:
Is that the temp while your phone is idle? If so, it's high for that case. My idle temp is close to 21 C (of course while I am at work in a temperature controlled env). My binning is fast and I am running b32 at its default settings (no Trickster, no init.d).
[Nexus 4 Original Android Development] shadow071506:
yup..phone at idle or just basic task like swiping through homescreens and stuff... i wonder whats causing it...
[Nexus 4 Original Android Development] azrash:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

with b31, I am normally at around 32-34 C. Using CM + no other changes in kernel settings. Fast binned CPU too. I am assuming this is normal too.

Sent from my Nexus 4
[Nexus 4 Original Android Development] lazer155:
I'm getting closer to 36C as my idle temperature. I have 2 cores disabled and a fast binned cpu. I'm on b32. I think b31 was closer to 30C but I wasn't disabling any cores at that time. Maybe running only 2 cores increases heat since those 2 have to work harder rather than distributing the load.
[Nexus 4 Original Android Development] PoisonWolf:
This assumes that the os itself is intelligently distributing the load.
[Nexus 4 Original Android Development] starscream92:
Hey Motley, just wanna drop by to say thanks for all your work. I'm loving your kernel! I'm running B31 right now, further UV'd your voltages by -50 mV (fast binned chip) and my phone's been running really cool, no stability issues whatsoever. I can't seem to find any problems with your kernel. No data drops, msm_hsic_host wake lock seems to be very low (BBS says it's always the 4th highest kernel wakelock, amazing! I'm always on HSPA by the way).

I was running CM10.1 nightlies before but experienced a really bad drain due to Android System (userspace, so I don't think it has anything to do with your kernel). Just temporarily switched to MiNCO, I'll see if I get the same amount of drain. Then I'll test your kernel some more!

Once again, thanks!
[Nexus 4 Original Android Development] lazer155:
Checked again, my temperatures are now around 30-32C so that's more normal. Not sure why it was hanging around 36C for awhile. I hadn't done anything with it for about 2 hours and nothing was syncing/running in the background, wifi was off and 3g was off.

B32 works great by the way. It still seems to be the most responsive out of all the other kernels I tried and the battery life is great.
[Nexus 4 Original Android Development] Franklin Bernard:
Hi Motley,

Greetings !!!

I am using your Kernel and its very good.

I just left a note on Touch Control thread . Touch Control is not working with Exp32 build. I getting reboot after set all the values to true. Let me know if you need any logs and how to take it :) I can provide it.

Thanks
[Nexus 4 Original Android Development] ceejay83:
touch control is working fine for me on exp 32. try uninstalling touch control, reboot, and reinstall
[Nexus 4 Original Android Development] joeshmoe08:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Is anyone having super high android os after flashing this ROM? See attached pictures. Its B32 with xylon ROM if it matters.
[Nexus 4 Original Android Development] starscream92:
I don't have a high Android OS drain. And I'm assuming you meant "kernel" instead of ROM. What kernel did you use before? How did that work out? Try wiping using TWRP, I find it to work better than CWM's wipe feature.

I have a big Android System drain. But that's different, Android OS is definitely kernel related, Android System is all userspace.
[Nexus 4 Original Android Development] joeshmoe08:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Ya I meant kernel. I was using Franco and it had very low usage, nothing significant. I'll try wiping and reflashing thanks.

Also my android system is fine if that helps with your problem. Its like 6% with 10 min CPU total, 15 min keep awake
[Nexus 4 Original Android Development] direwolf1:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

I've had this issue before after flashing a new ROM and kernel (though not specifically after flashing b32), and I use xylon too. For me this problem has always sorted itself out after a charge cycle. Keep using the phone, recharge the battery when it gets low, and see if the problem disappears.

Sent from my Nexus 4
[Nexus 4 Original Android Development] _motley:
Glad to hear things are going well with b32. Thanks for the feedback!

I just checked mine and after 8h31m off the charger, Android OS is at 4% (CPU total 1m57s, Keep awake 1m 31s)

Franklin, are you on v1.4 of Touch Control? Mine is working OK too on b32, however, I just noticed that I am still using touch control v1.3 and not v1.4. I'll have to backup 1.3 and try 1.4 later. Hopefully we don't have an issue with 1.4. Doing what ceejay83 suggests can definitely help sometimes. Any other feedback would be great.

None of the above temps are out of the ordinary. Temps are going to depend on several factors (ambient temp, insulated bumper or case, in pocket vs. on desk, how much cpu/gpu has been used recently, plugged/uplugged etc.). I just looked at mine and it is around 29-31C when resting on my desk doing background syncs. Temps are a bit higher if I have it in my pocket for awhile and it is doing the same.
[Nexus 4 Original Android Development] jhericurls:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

When you have high OS usage, it sometime helps if you clear the cache of android framework.
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Hi been using your kernel since exp 10. I can now post.

This latest experimental is great I did a stability test at 1026 MHz with high speed set to 702000 everything else default.

Substantially better than stock

Image 1 MY TEST

Image 2. Source antutu.com

My nexus 4 is undervolted to 675mv at 1026mhz btw
[Nexus 4 Original Android Development] dark_ente:
mine is undervolt to 600mv @1026 mhz and no crash, stability test same as yours
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

600 wish I could. I think 650 is OK on mine it crashes at 625 so I'm playing safe.
[Nexus 4 Original Android Development] apascual89:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

Hi motley are the changes that you made for b32 pushed to github? Do you normally wait for a stable release before pushing?
[Nexus 4 Original Android Development] _motley:
Sorry, I thought I had pushed it yesterday, but I came home today and found it waiting on the confirmation screen in Eclipse because forgot to click OK the second time :( A little multi-tasking fail LOL. If I post something on XDA, I always push at the same time, whether it is tagged as stable or not. The only exception to this for me would be if I am trying something with a few users within the thread trying to get something to work. Anyhow, I just pushed it an hour or so ago: https://github.com/motley-git/kernel-Nexus4/commits/exp
[Nexus 4 Original Android Development] apascual89:
Re: [KERNEL][Feb 3][Linaro]Exp:b32/Main:b57 _motley kernel for the N4

No worries man, I'm just new to github and trying to learn from the best! :thumbup:
[Nexus 4 Original Android Development] joeshmoe08:
Thanks everyone for the responses on Android OS usage. I just reflashed kernel and cleared cache well see how it goes. Btw Motley, do you notice any significant battery loss when using touch control?
[Nexus 4 Original Android Development] dark_ente:
Don't worry, there's almost no different between 650 and 600
[Nexus 4 Original Android Development] thunderger:
@motley:

First, I've to thank you for your quick and detailled answer.

Scond, you asked for changes in newer Linux kernel that we want to see if possible. TCP/IP optimizations from kernel 3.5 and 3.6 would be nice to have. Ext 4 filesystem optimizations from 3.5, 3.6 & 3.8 should be looked at. Perhaps you can build an experimental kernel that uses the new f2fs that will be introduced in kernel 3.8.

I saw a lot of arm related commits in kernel 3.7, perhaps there are some interesting ones for you. :)

EDIT:

Is it possible that you implement FIOS scheduler? I saw this in antoher kernel but no read/write speed tests with this "new" scheduler, compared to ROW and SIO. Wanna test this thing.