yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] rlaw:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

You can always turn cfx settings off for a full stock experience with the performance improvements cfx brings.
[Nexus 4 Original Android Development] PoisonWolf:
Surprisingly, even with dual core, it doesn't feel all too different at all. I can't personally even tell any difference.
[Nexus 4 Original Android Development] Voltor46:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Motley you have done really a great job. Y have tried Franco and Faux, but your's is THE ONE (b31). Smooth, switching between apps with recent apps menu is much more faster than in other kernels. And Battery performance is awesome too, I can't even believe how it sleeps, it seems to have 0% of drain while sleeping. It has gamma control too and OC <3.

Your's is the only one kernel that really gives a good boost to the stock one. Congrats! AND THANK YOU VERY VERY MUCH!

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] air2k57:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Yes, but even with cfx off you get blue icon vs stock grey. See, look at the hspa icon, that's with cfx disabled.
[Nexus 4 Original Android Development] Redmed427:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Flashed exp last night and again during lunch. Not getting notification sounds or vibrations. This happened on a fresh install of a xy ROM

Sent from my Nexus 4
[Nexus 4 Original Android Development] thracemerin:
Did you flash b17 before b31?
[Nexus 4 Original Android Development] _motley:
Not sure if you saw it, but I updated the OP with a full version of b31 and marked it as stable. No more b17 pre-flashes:good:

Redmed, I have never seen this type of issue reported before, so I am not sure what is going on. Like thracemerin says,it is best to try the full version of b31, not just the AnyKernel update of b31 to be sure. If that doesn't work, do a full wipe and try again.
[Nexus 4 Original Android Development] lazer155:
B31 is running great for me with undervolting. I also can't tell the difference with 2 cores disabled. It seems the same as 4 cores in terms of ui speed.
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

How about if playing games?
[Nexus 4 Original Android Development] jazzboyrules:
I can play Temple Run 2 fine and Epic Citadel benchmark ended up with 60fps on an avg.

UPDATE: Nevermind, I read too fast. I am on b31 but I haven't limited to just 2 cores.
[Nexus 4 Original Android Development] j3di:
Where do you check which TCP Congestion Control is currently set? Many thanks!
[Nexus 4 Original Android Development] tengen:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Trickster MOD should allow you to see and set it (under general )
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

With temple run 2, have you noticed there's micro lags once the game starts getting faster?
[Nexus 4 Original Android Development] lazer155:
I haven't tried an games yet just web browsing, gmail, and other minor things (calling, texting with stock app ect.). I switched back to 4 cores already but will try 2 again with some games and let you know. I was worried something would happen and I would get stuck in a bootloop since it sets the 2 cores on boot. I'm waiting for trickster mod to support changing the number of cores so on a reboot it will default back to 4 in case something goes wrong (unless of course you tell it to set your settings on boot). Ptesmoke said that it is a feature that will come in the next update since it is in the test version he has now with gamma control. I wish system tuner pro would update their options with number of core settings.
[Nexus 4 Original Android Development] HKPolice:
Init.d is not working right now in B31.

I made this script to do some simple changes:

#!/system/bin/sh

#Init.d tweak

echo 80 > /sys/module/msm_thermal/parameters/throttle_temp

echo 400 > /sys/module/auto_hotplug/parameters/enable_all_load_threshold

echo 60 > /sys/class/timed_output/vibrator/amp

copied it into /system/etc/init.d/ and set permissions to allow execute, the settings never stick after reboot.
[Nexus 4 Original Android Development] IAmAN00bie:
No wonder my init.d scripts weren't working... I just boot then copy paste all the lines at once into Terminal Emulator meanwhile.

edit: also does anyone know the path to modify the TCP Congestion using a script?
[Nexus 4 Original Android Development] PoisonWolf:
The microlags you see are a function of the game. I got the same lags regardless if it's 4 cores or 2 cores.

So I've done a full drain of the battery with heavy use today. I used 2-cores throughout, FSync on throughout. Nothing else was changed from motley's stock settings. WIFI for 90% of the time, 10% on data. Time since off charger is about 10 hours.

30 minutes for Temple Run 2, 30 minutes of Arcane Legends 2 (setting was moved to battery saving mode), and about 15 minutes of Dragonvale.

I am now at 4 hours and 20 minutes of screen on time with 10% battery left.

It isn't too bad and there is literally no difference in terms of usability of being on 2 cores.

Hope this helps someone who is using this kernel with similar questions.
[Nexus 4 Original Android Development] HKPolice:
What I don't understand is that an init.d test script is working fine:

After every a reboot, test.log exists but nothing else sticks.
[Nexus 4 Original Android Development] PoisonWolf:
Just found a possible bug? I just plugged my charger in and my phone just went from 10% to charged completely. Is this normal or kernel related? After a reboot it went back to 7%.
[Nexus 4 Original Android Development] thracemerin:
The chip that monitors the battery is flaky on occasion, I'm not sure this is kernel related, I've seen things like it drop from 100-95 in 10 seconds under no load and then take hours to drop another 1%, I think it's sort of a hardware "defect".
[Nexus 4 Original Android Development] PoisonWolf:
Is it an indicator of a hardware problem in the long run (i.e., I would hate if my battery died within the next few months because of improper reading/reporting/charging/etc)?

I was wondering whether static might have jumped onto the usb port when I was plugging it in and whether that had anything to do with it.

If the chip or whatever it is that is monitoring the battery is flaky...this could also point towards improper reading in actual battery capacity, I assume?
[Nexus 4 Original Android Development] thracemerin:
I doubt it, the I9100 which I used to use as my daily phone had all types of problems with the chips that monitored the battery but after 2 years it still functions and charges fine, that's why I hesitate to say it's a defect. It's just a quirk of the chip that monitors the battery that it gives some strange readings occasionally, I don't think you should be worried, you could RMA it but chances are the chips are all the same.
[Nexus 4 Original Android Development] PoisonWolf:
Thanks mate. You have quelled some of my worries. I initially started going down a list of whether messing with the max number of CPU-cores could have glitched the battery reading, etc. I even tried turning on full brightness, etc, and it was draining the battery at usual. (After 5 minutes it only went down to 99% from charged). I was hoping it would drop from Charged (100%) instantly to 10% or something.

I also started wondering whether I shorted the USB by accident....lol.

But thanks for explaining the situation.

Now, back to testing 4-cores for the next day and see if I could hit 4 hours and 20 minutes of screen on time.

PS. I've attached a screenshot to show what happened after reboot from 100% to 7% or so.
[Nexus 4 Original Android Development] _motley:
Here is some info to hopefully help with the init.d setup. If your ROM doesn't have support for it working out of the box, then it can be kind of a pain when you first set it up. If you are flashing nightlies that remove it each time, it is even more of a pain.

----

CM10 - if I recall correctly, CM has a "user" init.d implementation, so you will need to find that folder and put your scripts there. I think it is in /data so it isn't lost on flashing a new nightly. I play no role in init.d or user init.d on CM as I just use their ramdisk.

AOSP - if a ROM doesn't have busybox pre-installed and working, it can be a little tricky. For example, for RasbeanJelly, I make sure I follow all his installation notes in his OP. busybox is not included in the ROM, but he tells you to install it.

1) Install busybox to /system/xbin - I typically use the stericson busybox installer in the app store.

In my experimental kernel zip for AOSP, I alter the ramdisk and add the following to init.rc to enable init.d support. Note the location of busybox below in the script. You have the install busybox into /system/xbin or it will not work. This is the recommend spot for installing it.

init.rc:

service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
class late_start
user root
group root

2) Make sure your scripts are properly placed in /system/etc/init.d/, are formatted correctly, and have exec permissions.

Note: beware, when you edit scripts with some editors (ES File Explorer is one), they will place a file.bak file in the same folder after the file is edited. If the busybox script picks up the .bak file, it will also be executed AFTER your newest live version. It can be confusing because it will revert back to your original changes and you may not realize what is going on (been there, done that!).

I haven't changed anything in the kernel or the init scripts related to battery levels. I have seen this mentioned one other time somewhere on the N4 forums, but I have never witnessed it myself. It is probably just a re-calibration event of some sort where the level is not reported properly.

You should be able to do it like this:

echo "reno" > /proc/sys/net/ipv4/tcp_congestion_control

echo "veno" > /proc/sys/net/ipv4/tcp_congestion_control

echo "vegas" > /proc/sys/net/ipv4/tcp_congestion_control

echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control
[Nexus 4 Original Android Development] xdaShex:
Is it normal for the phone to idle at 1ghz with one core active especially when charging it ?
[Nexus 4 Original Android Development] thracemerin:
USB charge or AC charge?
[Nexus 4 Original Android Development] xdaShex:
USB.
[Nexus 4 Original Android Development] thracemerin:
If you're charging it while connected to your PC it will be awake because it's connected by MTP or adb so it's waiting for commands, that might explain it.
[Nexus 4 Original Android Development] xdaShex:
ah ye!, sorry for the trouble

thanks for the fast reply.
[Nexus 4 Original Android Development] whittikins:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Motley, is there an upper limit for bootpulse duration? Could it be up to 3 or 4 seconds if we wanted? Just curious, thanks!
[Nexus 4 Original Android Development] shadowcaster31:
quick question from a newbie here -

Coming from CM10.1 and currently using franco's kernel, do i have to do a "dirty flash" of a CM10.1 nightly first or can i just flash b31 straight away?

sorry i didnt really understand the OP fully.
[Nexus 4 Original Android Development] j3di:
shadowcaster31: Yeah, dirty flash CM and then b31 kernel before rebooting.
[Nexus 4 Original Android Development] thunderger:
@motley:

In b31 I tested some UV&OC with a loop of citadel demo and playing babel rising for a long time. My SoC is binned as 'fast'.

At the moment I use the following seetings

1.512 GHz 1.0V

1.566 GHz 1.0175 V

1.62 GHz 1.025 V

1.674 GHz 1.05 V

Next I'll try to lower voltages by another 75 mV. Perhaps other people can try low voltages, too. :)
[Nexus 4 Original Android Development] z3r0_x:
AW: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

I run these voltages just fine, also underclocked to 1,35 Ghz with a fast binned chip.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

If you use the full zip of b31 you don't need to flash anything else first, if you use the any kernel zip, you need to flash b17 first.
[Nexus 4 Original Android Development] j3di:
He's coming from the Franko kernel so needs to dirty flash before switching to the b31 kernel from Motley.
[Nexus 4 Original Android Development] lopez1_de:
Hi, anyone had success mounting a cifs? I'm using CM10.1 + motley kernel + CIFS Manager. But I can't mount a share. "Invalid Argument". The File Manager App can browse the smb share without a problem. Thanks for help.
[Nexus 4 Original Android Development] _motley:
Yes, the value is in microseconds, so you should be able to set the boostpulse_duration to 1000000 for each second of duration (1 million microseconds = 1 second). The internal data type is "int" in the governor, so there is plenty of room to set it up to 2 or 3 million if you want to try it.

Hi, it very likely could be too much UV in part of the voltage curve. There is already a healthy amount of UV applied throughout the curve in this kernel out of the box and all chips are different. Depending on what you were doing when it rebooted can help you determine where to fatten up the curve. If you were navigating around the UI when it happened check the midrange freqs in your voltage table and fatten it up a bit (+25 and then try it). If it was something intensive, benchmark or game, then I would look at the highest freqs and fatten them up. If it happened during sleep, then I would look at the low end. Most random reboot issues reported due to low voltage seem to be in the midrange, especially around 1024 where the boostpulse occurs.

What veyka says should work too for exp since I provide an entire boot.img for the exp kernel. As far as stuff that may have been added or renamed in /system by another dev, I also provide my own PowerHAL and the exp builds don't depend on the mpdecicion or thermald binaries that are renamed or replaced by some devs. So, I see no issues with just flashing the zip for the exp kernel. For the mainline, I would go with the dirty flash since I only provide the AnyKernel zip.

That said, I hate to confuse with all the different combinations and transitions from the different kernels. Some that understand the nittly gritty details may take some shortcuts;) Dirty flashing always gets you back home safely too, so this is often the best thing to recommend.
[Nexus 4 Original Android Development] j3di:
Motley,

There doesn't appear to be fsynccontrol/fsync_enabled within /sys/class/misc/ and infact the /misc folder is empty. Help!
[Nexus 4 Original Android Development] _motley:
You must have some sort of root access issue. It is definitely there or many things would not be working correctly if at all. I can see this part of the virtual file system just fine using ES File Explorer with root access turned on. Can you see the fsync option and change it with Trickster MOD?
[Nexus 4 Original Android Development] j3di:
Thanks Motley, just as you described! The CM explorer, even with root access couldn't mount it so used root explorer and it was OK!

:)
[Nexus 4 Original Android Development] xdaShex:
Just an update to my last question, I was looking at my CPU usage with "CPU spy, and notice when my screens off it goes into deep sleep, but when its idling with the screen on( during battery usage not charging) it it never touches other frequencies other than 1 GHz and 1.5 GHz. is this normal ?
[Nexus 4 Original Android Development] eRajesh:
What's the UV amount by default on this kernel on a 'nominal' binned chip?
[Nexus 4 Original Android Development] lazer155:
Which frequencies are considered midrange?
[Nexus 4 Original Android Development] antih3ro:
No that is not normal. It should go to 304 MHz when its idling.
[Nexus 4 Original Android Development] IAmAN00bie:
Yeah, that's just the way it is. A lot of the intermediate frequencies rarely ever get touched. I think that's why Franco got rid of so many of them.
[Nexus 4 Original Android Development] xdaShex:
Any way to fix that ? or when a re flash suffice ?

---------- Post added at 04:04 PM ---------- Previous post was at 04:03 PM ----------

Oh so its normal for it not to ever touch 304 MHz ? when idling ?
[Nexus 4 Original Android Development] grisha1:
AW: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

No, this is NOT normal. Even when using the phone it should use mostly 304.

by N4 via Tapatalk
[Nexus 4 Original Android Development] antih3ro:
AW: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

For me it looks like that.
[Nexus 4 Original Android Development] grisha1:
AW: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Yep

by N4 via Tapatalk
[Nexus 4 Original Android Development] PoisonWolf:
That looks right.
[Nexus 4 Original Android Development] z3r0_x:
_motley, could you remove some of them as well as they're almost never used?
[Nexus 4 Original Android Development] -Asskicker-:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

What are the recommended settings for battery life? Currently have interactive with Max of 1242000.
[Nexus 4 Original Android Development] jhericurls:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Ondemand and flashing the powerhal on the OP should provide the best battery life. But I personally not notice that much difference to interactive.

I spend most my working day on 3G and that drains the battery. Switching to 2G helps massively.
[Nexus 4 Original Android Development] xdaShex:
This is how mine looks currently, I have yet to see it idle at 300 MHz

Any advice would be appreciated.
[Nexus 4 Original Android Development] meangreenie:
Why? What of someone wants to use a different governor which does go through the frequencies like 'conservative' ?
[Nexus 4 Original Android Development] ctfrommn:
What is your cpu minimum set at?
[Nexus 4 Original Android Development] xdaShex:
Under TricksterMod it says min 1026000, but initially thought this had to do with "Project butter" or is this the cause of the problem ?
[Nexus 4 Original Android Development] grisha1:
AW: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Sure that's the problem. No butter in motley kernel, so the min you set is going to stick. Just set it to 304 and you'll be fine :thumbup:

by N4 via Tapatalk
[Nexus 4 Original Android Development] popophobia:
Re: [KERNEL][Jan-19][Linaro]Exp:b22/Main:b57 _motley kernel for the N4

You should unchecked the boost option in interactive governor. It keeps the CPU at boost speed all the time.
[Nexus 4 Original Android Development] xdaShex:
Thanks I had no clue I had to do that after flashing the kernel, should I also switch it to interactive as well ?
[Nexus 4 Original Android Development] _motley:
Yeah, I don't think removing them is the right idea. All of them are used at times and they are used more in some configurations and usage scenarios than others.

Glad you got it sorted. You shouldn't need to do anything after flashing the kernel. The default min freq is 304MHz, so something must have accidentally been changed (boost option toggled for permanent boost on or min freq raised like the others suggested). Or, perhaps you were on another kernel and had an app that was set to persist some settings on boot and you didn't realize it. Interactive should already be the default after you flash (or if you reboot). If it isn't, then you have an app, ROM performance setting or a script changing it. Interactive is what I recommend for the best overall experience since it provides a great blend of performance and battery savings. Other combinations of settings can work good as well.
[Nexus 4 Original Android Development] xdaShex:
Ye your right, at the moment it's fine but I wasn't to sure what was loading the alternate settings, since I am currently on Cm 10.1, I unchecked restore settings at boot and have yet to reboot to see if that was the culprit but I am sure it was!

Thank you for the help BTW. much appreciated
[Nexus 4 Original Android Development] lopez1_de:
Sry for double post, but it drives me crazy:

Anyone had success mounting a cifs? I'm using CM10.1 + motley kernel + CIFS Manager. But I can't mount a share. "Invalid Argument". The File Manager App can browse the smb share without a problem. Thanks for help. :angel:
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Jan-28][Linaro]Exp:b31/Main:b57 _motley kernel for the N4

Motley, is there anything you've learnt from the nexus 4 kernel that could be applied to the n7? I'm getting flash withdrawal on that device?

I know nothing about kernels so was just curious really. Thanks for everything.
[Nexus 4 Original Android Development] _motley:
Been looking into this. From what I have read, Android 4.2 broke external mounts. CM 10.1 then came out with what we thought was a proper fix. However, it looks like they have since reverted that patch due to some side effects :(

http://xdaforums.com/showthread.php?t=2099312

I think you can still mount MS shares using ES File Explorer. Might want to try that as a workaround.

As soon as time allows, I will be going back and working on the N7 kernel. I am thinking about giving auto_hotplug a run on the N7 to see how it works vs tegra hotplug. It would be nice to have all of those tuning options on that device.
[Nexus 4 Original Android Development] lopez1_de:
I CAN mount with current CM10.1 (LUKS Manger for example). But I can't use cifs.
[Nexus 4 Original Android Development] PoisonWolf:
More FYIs.....running a dual-core setup results in about an additional hour of screen on time relative to a quad-core setup. There is also no noticeable difference in day-to-day activities.
[Nexus 4 Original Android Development] _motley:
LUKS would be loop devices, so I am not sure those would fall into the set of issues. I am assuming cifs and nfs access. I'll do more research on the patches so I can understand what CM is doing etc. I also saw faux post at one point that said there was also a CM dev kernel hack for this as well. However, he wasn't keen on implementing that to fix AOSP since some would still be on CM where they were implementing a more proper fix in Android (if you had both patches, then it wouldn't be good). However, if they have now reverted the patch in CM due to the side effect issues, perhaps the kernel hack may again have some relevance. Need to find that hack if I can so I can study it.

Good to hear. I am sure the overall benefit will depend on usage patterns (apps used, screen-on time etc.). I have also noticed a slight bump in battery life when I run with only 2 cores, but I haven't done enough research to quantify it.
[Nexus 4 Original Android Development] PoisonWolf:
That's true. One additional benefit is that there's less heat on the back. These are some of the things I've noticed.
[Nexus 4 Original Android Development] -Asskicker-:
What configuration would you use to only use 2 cores? I'd like to give that a try.