yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] UZ7:
If you're at your house and most likely just going to sleep its best to just turn off data and have wifi turn off when its at sleep/idle then you'll barely have any power drain during deep sleep.

I would only keep it on if you want updates constantly being sent to your phone while you sleep (or for some people who must reply to a notification). For me if I wake up it automatically connects back to wifi and receives all those update anyway.

Now if you're out and about and have data off but have wifi on that will constantly look for a hotspot/routerand (depending on your setting) try to connect to it, which I also disabled. I don't want the phone to connect to an open wifi while I'm driving or walking around. But most of the time I leave data on anyway as I don't mind the battery drain. Even with my ol skyrocket (has LTE) I got a full days worth while keeping LTE on.

If you're talking about wifi vs modem drain then yes modem drains more.
[Nexus 4 Original Android Development] rlaw:
You hit the nail on the head, I was referring to drain.
[Nexus 4 Original Android Development] DowntownJeffBrown:
Thank you motley for this Kernel it'd exactly wanted. I wanted to for now stay as close to stock as possible and curb some of my battery drain. I just flashed and ill see how it goes.
[Nexus 4 Original Android Development] UZ7:
So far good battery life, I'm at 16% right now close to 11PM

Day started at 8AM w/ 98% (unplugged before I went to sleep).

Watched a few youtube clips, HD, -15min ~Wifi

Talked on the phone - 30min

Went to Gym, used pandora normal quality, 1.5HR ~Data

Browsed the web - 10min ~Data

Talked on the phone -30min

Google+ video chat - 20min ~Wifi

I did run StabilityTest and Antutu for a few minutes when I was testing for stability so that took about 10%~

So roughly 15hrs, 3hr screen time, 15% left~ didnt constantly use my phone but its a normal day use so battery is pretty good, at least on my end. After a few more tweaks here and there I'm pretty sure tomorrow's day will have a longer bat time. :good:
[Nexus 4 Original Android Development] yumcax:
I'm getting some pretty impressive performance from this kernel, compared to OC kernels. Not sure if it's because of thermal throttling or what, but I had a couple games lag on faux123's kernel, while everything has been flawless (including battery drain!) here.

Now, can someone explain what mdprecision does? I understand that it f*cks with me changing frequency limits, but what pros are there to keeping it running?

Also, what is the best governor? I have been using Interactive for the freq boost when touching the screen.
[Nexus 4 Original Android Development] MatAuc12:
You cannot really turn mpdecision off with this kernel. Well you can but performance will be attrocious, nothing will be governing the interaction of your different cores. So the list of cons is full with no pro.
[Nexus 4 Original Android Development] _motley:
Build 38 posted

New alpha build 38 released (see OP for the download and details on changes). Testing thus far has shown it to be stable and there are not any open issues at this time.

Thanks again for all the feedback, let me know how it goes!
[Nexus 4 Original Android Development] DroidRC1:
Seems the download link is broken
[Nexus 4 Original Android Development] _motley:
Seems to work ok for me...just tested again. These files are hosted by XDA. Do any of the prior version downloads work for you?

Anybody else able to download OK?

Thx
[Nexus 4 Original Android Development] DroidRC1:
Got it to work by going to xda via browser besides app...thanks!
[Nexus 4 Original Android Development] yonpa:
Just installed it but my phone is very slow now and touch is unresponsive :confused:
[Nexus 4 Original Android Development] MatAuc12:
Did you reboot a couple times?
[Nexus 4 Original Android Development] richteralan:
Wipe cache?

Wipe dalvik?
[Nexus 4 Original Android Development] MatAuc12:
That is useless for kernel.
[Nexus 4 Original Android Development] 0.0:
I'm wondering, why was the 1.5 GHz frequency taken out?

Sent from my Nexus 4
[Nexus 4 Original Android Development] jazzboyrules:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

No. I am on mobile data only during my commutes between work and home. I will test out b35 for 1 charge cycle and again switch back to the then latest 4.2.2 motley kernel and see if the battery life degrades /stays the same/improves.
[Nexus 4 Original Android Development] thracemerin:
Hmmm....there's something wrong with the .44 baseband too, I can't explain the exact problem yet, but some very very odd things seems to be happening to people using it. Not saying it's related, but it could be.
[Nexus 4 Original Android Development] ptesmoke:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

I dunno if its baseband related but my nexus decided to EFF itself last night. I ended up having to flash stock to fix it....and I'm a decent adb/fast boot warrior...there was no recovering..

went from 22%ish battery to 1% instantly. every time I rebooted recovery it'd have somewhere random between 0% and 20%.

didn't want to charge, failed flashes , md5 matches...thought I was being haunted.

seems to be OK today...
[Nexus 4 Original Android Development] thracemerin:
No, there's definitely something weird with the new radio, its the only thing I haven't eliminated as the cause for the issue I posted about in my thread.
[Nexus 4 Original Android Development] lazer155:
Did you revert your baseband/radio back to the one before .44? I haven't had any issues so far but I have never had any with this kernel. I'm worried I my have issues with something like the sleep of death with the red light. I'm considering reverting if this is an issue people are having as a preventative measure.
[Nexus 4 Original Android Development] gianton:
B38 running very smooth on CM10.1 Kang linaro builds, gamma settings can be controlled with Franco's app.

Thanks!
[Nexus 4 Original Android Development] pa.pn2:
same here with trinity toolbox...
[Nexus 4 Original Android Development] yyz71:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Loving b38 nice and smooth.

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[Nexus 4 Original Android Development] _motley:
Getting anxious to add the hsic fixes back in as I too think battery is a bit worse. People report data issues once in awhile with or without them. I really wanted to try it for a couple days to see how things would go and we have now done that.

I will leave the read-ahead at 1024 since I have heard that it can cause issues on some media players. I have not witnessed this myself, but have seen it reported. I'll look into the row scheduler and see what tuneables it has. It is a good candidate for the default scheduler. CPU cycles are also important to me when it comes to an IO schduler. NOOP would be best in that regard, but not for performance. I will so a bit of study as it is hard to pick between SIO, row, and deadline as they appear to perform nearly the same. The one using the least amount of CPU to manage requests would be the best.

I'll be looking at putting some of the upstream smp, hotplug, and scheduling patches back in very soon. After the rebase, I just wanted to see what it behaved like without all the extra patches from the start. Some are valuable I think, so they will go back in.

Yes, this very early in development, so it is best we wait this one out a bit and see what happens. If it is useful and doesn't affect general performance or usage, then it would be something I would consider adding for those that want it.

Not seen anything weird yet on my end with the new radio:fingers-crossed: Phone seems stable as before so far. Currently on 4.2.2 CFX ROM.
[Nexus 4 Original Android Development] batman368:
i'm on b38 as well, runs really smooth :) tonight i had 0.2%/h drainage, on wifi, that's pretty awesome. on b35 i sometimes got 0.1%/h, but i think b38 is really good, even without the hsic patches.

new radio and bootloader work flawless for me, didn't notice any difference at all.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Overnight I lost 7% in 7h 45min on 3G (took it off charger basically the moment it hit to test this, so it was as actually as close to 100% as it could be.), which is good, but a little worse than with the patches.

B38 in terms of data stability has been pretty much identical to pre 4.2.2, its hard to be totally sure due to the new baseband, but for me the old patch set caused no issues anyway so it would be good to have it back. (and i could reproduce the data stuck issue very quickly with the partial set).
[Nexus 4 Original Android Development] pa.pn2:
made an antutu benchmark with min/max 1512mhz-performance-row-fysnc fast

any idea why the score isnt so high?AOKP PUB rom
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Seems fine to me, most people getting 22k or more are overclocked.
[Nexus 4 Original Android Development] pa.pn2:
ok.thx for the info^^
[Nexus 4 Original Android Development] Remoteconcern:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Thanks motley. I can also confirm that I lose slightly more battery on 3g now, so those patches we had in before represented the ideal balance of no data issues and battery saving.

This is still the best kernel for me. I have Franco's app and use it for color adjustment because I don't know how to make an init script for my settings, which is the only thing preventing me from just using your kernel at the defaults because I think its that good.
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

It would be great if someone could help me make an init.d script with the color settings as the screenshots.
[Nexus 4 Original Android Development] :
Hi,

It's what I have, same rom:

304 Mhz-1.51 Ghz / Ondemand governor / FIOPS i/o scheduler / F-sync off:

Not bad but a bit low, maybe you have been thermal throttled? I set my thermal throttled temperature to 75 °C...

It's your 3D score that is "low"...

Test with min CPU freq at 304 or 486 Mhz for see and with Ondemand or Interactive governor. Wait your phone runs cooler before running a bench, don't do 2 or 3 benchs in a row.

:)
[Nexus 4 Original Android Development] pa.pn2:
AW: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Great settings wohowww
[Nexus 4 Original Android Development] veyka:
http://www.veyka.co.uk/other/91giantofranco

:)
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Thanks!

Running with no app to control the kernel now.
[Nexus 4 Original Android Development] AnTrans:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

I'm from Canada and currently use LTE on Rogers network. Just wondering if I can upgrade to 4.2.2 but keep the old radio and use b38 kernel and still be able to use LTE.

I understand I may have to use custom Rom package to avoid getting the new radio, or perhaps there is a way to down grade the radio after ota update.
[Nexus 4 Original Android Development] thracemerin:
You can use the old modem without issue, just flash the modem via fastboot or recovery, there are lots of packages available. I've been doing it on CM10.1 (4.2.2) with motley b38, no issues that I can see.
[Nexus 4 Original Android Development] AnTrans:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Thanks. Would it be best to not upgrade the baseband or would downgrading be same thing. I made the mistake of upgrading my iPhone 4 baseband and got screwed. No longer able to unlock it
[Nexus 4 Original Android Development] thracemerin:
You can downgrade it just as easily as upgrading.
[Nexus 4 Original Android Development] Armin_van_buuren:
Good kernel :good:

Unofficial AOKP JB 4.2.2 Builds [PUB] Rom
[Nexus 4 Original Android Development] starscream92:
Looking to stop using apps like Trickster to control the kernel, and want to start using init.d scripts.

What's the general format of a init.d script to tweak voltages?
[Nexus 4 Original Android Development] thracemerin:
there are a few examples in the thread, i think i posted one a few pages back.
[Nexus 4 Original Android Development] j3di:
Use System Tuner to tweak voltages and save as an init.d script.
[Nexus 4 Original Android Development] starscream92:
Thanks. Found it! Link for future reference: http://xdaforums.com/showpost.php?p=37926586&postcount=1767

Also, where do I echo values to tune TCP congestion algorithms, I/O scheduler, and read-ahead buffer size?

Edit:

Found the TCP congestion algorithm config path:

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

but no clue about I/O scheduler and read-ahead buffer config paths.
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

@motley hate to bug, but next release would be great if you can grab the newer version of Francos interface for gamma as it fixes the bootloop issue with init scripts without a sleep statement (only use that interface due to the amount of presets around based on it and I am to lazy to convert atm)

Cheers!

I have also noticed that battery life is suffering on 3G, i got "only" 3h 30min of battery life this time around ;)
[Nexus 4 Original Android Development] thracemerin:
Do me a favor veyka, jump to my thread, grab the v4 test and see if you can reproduce the data drop. Since you're the only person I know of that can actually do it at will, I'd like to know if you can.
[Nexus 4 Original Android Development] IAmAN00bie:
I have the paths to change the I/O Scheduler and the read-ahead buffer in my script attached:
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

On it! Also hotfiles is awful, you should use Dev host or something ;)
[Nexus 4 Original Android Development] thracemerin:
I know, but I'm too lazy to move them :p
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 17][b38] _motley kernel for the N4 (4.2.2 support added)

Hiss! If you really want, drop me a pm and i can give you some space on my server :p /ot
[Nexus 4 Original Android Development] thracemerin:
@_motley:

Based on some reasonably extensive testing, I'm fairly sure that there are no unintended consequences to adding the hsic_host patches in. I've had a limited number of odd things reported, but none of them are absolutely 100% the kernel, and none were easily reproduced, so I'm reasonably confident in blaming mobile networks, location or other issues related to the users situation that are not specific to the phone or kernel.
[Nexus 4 Original Android Development] _motley:
OK, got the hsic fixes back in. Will post an AnyKernel update in a bit:good:

@veyka, it looks like I have that commit already for the franco interface. If using init.d, I would really recommend using my interface since it won't have that issue on boot. I think he needs to make the screen refresh a separate method and only call it from his app when settings are being adjusted (like my refresh_screen) and not include it in the methods where the colors are set. Separating this logic would fix the problem. No need to call this for each color set on startup because it happens already within the driver.
[Nexus 4 Original Android Development] _motley:
Build 39 posted

b39 is now live. Let me know how it goes! If this goes well, next up will be merging some of the upstream smp and sched patches back in that I had in 4.2.1. I like to do it a bit at at time so I can observe at least a normal day of usage before moving forward.
[Nexus 4 Original Android Development] BrandoHD:
I was on b38, which meant I had to flash b37, then anykernel b38, now I have to flash 37 again, or can I go straight to 39?
[Nexus 4 Original Android Development] thracemerin:
Straight to 39, 37 just makes sure you have the right ramdisk, you only need to go 37->39 if you come from another kernel.
[Nexus 4 Original Android Development] starscream92:
Alright. Finally got home from work and stuff. Got around putting all my kernel tunings into init.d scripts. Tested them out. And they all work fine.

FInally! I can now start participating in testing Motley's kernels (B35 didn't work too well with Trickster). Feels good to get rid of that app. Phone is less cluttered :)
[Nexus 4 Original Android Development] thracemerin:
I've always preferred scripts when possible, apps often only allow you to adjust things the author thinks you might want to adjust which is generally want they want to adjust, not that this is a bad thing if you're unsure what you're doing it gives you a little safety in terms of potential damage you could do to your device, but it also limits what you can do if you do have a good idea of what you're doing.
[Nexus 4 Original Android Development] zapford:
Fellow Trini ))) And i was thinking i was the only Trini with an N4 ;)

I hope you are in warm, beautiful Trinidad, i am freezing my a$$ off in Siberia, Russia right now ))) :laugh:
[Nexus 4 Original Android Development] BrandoHD:
Yes I am in Trinidad, and it is warm, and I know of 3 other Trinis with the N4, there could be more
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][Feb 20][b39] _motley kernel for the N4 (hsic patches back for 4.2.2)

Please share them?
[Nexus 4 Original Android Development] Underworld79:
Awesome update!
[Nexus 4 Original Android Development] :
Hi,

Wich rom? PA?

In fact nice score at this CPU freq :D

Thanks ;)
[Nexus 4 Original Android Development] Underworld79:
Yup yup. PA 3.0
[Nexus 4 Original Android Development] Neotelos_com:
I like your kernels, but I kept wondering why my phone gets warm with intense bruising even though I'm severely underclocked.

I found out the interactive governor is allowing cores 2-4 to go beyond the max CPU speed I've set.
[Nexus 4 Original Android Development] sideeffects:
Re: [KERNEL][Feb 20][b39] _motley kernel for the N4 (hsic patches back for 4.2.2)

The higher CPU states show no usage for me with interactive. I think the above Max CPU bug Is caused by left over's from other kernels. Try using the reset kernel before flashing Motleys.

Edit - interestingly though with my ROM (PA3) there is no scaling_max_freq set for cores 2 or 3 in /sys/devices/system/cpu

How come?
[Nexus 4 Original Android Development] bljy:
Re: [KERNEL][Feb 20][b39] _motley kernel for the N4 (hsic patches back for 4.2.2)

Has anyone compared this with faux kernel?
[Nexus 4 Original Android Development] BrandoHD:
Have you ever used any Scripts?
[Nexus 4 Original Android Development] mko000:
Even when I play demanding games for half an hour or longer the phone gets warm but not hot. My experience is that temperature management is perfect for me on this kernel.
[Nexus 4 Original Android Development] brainbeatuk:
Re: [KERNEL][Feb 20][b39] _motley kernel for the N4 (hsic patches back for 4.2.2)

Is this a bug. When i enable Bluetooth my WiFi gets interference. Slow standstill transfer rate. Thought it may of been ipega gamepad but noticed it does same when pad off not connected. Been like this since 4.2.1 though it was bug that was to be fixed by Google.
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][Feb 20][b39] _motley kernel for the N4 (hsic patches back for 4.2.2)

That's a Google bug, I have the same. When on WiFi I have to disable BT. Also when WiFi is enabled I can't make a call through my BT headset.
[Nexus 4 Original Android Development] _motley:
LOL, that's what I love about XDA. Seeing and chatting with so many people from different corners of the world. Stay warm or cool, whatever applies haha. At moment, for me, it's stay warm :(

I'll take a closer look to be sure there is not a problem, but I don't think I was scaling past my max 1.5 yesterday. This is typically caused by a ROM or app startup frequency or an init.d script. We just rebased on 4.2.2, so I will definitely take a look.

It is normal to have not have scaling_max_freq set for cores 2 or 3 in /sys/devices/system/cpu. This is the same on the stock kernel as well, They works as siblings with cores 0 and 1 on the cpu policies.

Very nice score at 1458:good:
[Nexus 4 Original Android Development] jazzboyrules:
Thanks for the update motley. I am sporting b39 right now. Will keep you updated. Thanks for your awesome work! :)
[Nexus 4 Original Android Development] veyka:
Re: [KERNEL][Feb 20][b39] _motley kernel for the N4 (hsic patches back for 4.2.2)

Cheers for the info, I should have actually looked at your git hehe.

I was mainly using his while trawling though presets, lots of them refer to his and unless I know it's any good I'm to lazy to convert, still just sticking to LG atm as my screen seems to dislike most presets say gives them 2.2's for gamma hehe.
[Nexus 4 Original Android Development] :
Hi,

Have you seen this?: https://plus.google.com/109078966818501160423/posts/Us6pFjVqegW (Turbo Boost):D

And this: http://xdaforums.com/showthread.php?t=2159076 (About video quality based on your kernel).

@ _motley thanks for your PM, appreciated, it's OK ;)

:)
[Nexus 4 Original Android Development] starscream92:
It's nothing fancy. I didn't even modify the gamma/color multipliers because I like the coolness of the stock IPS display :) But I still really appreciate having the choice of modifying them. As for the voltages, this is I think as low as I can go while maintaining perfect stability. My CPU is fast-binned. Might still try and lower them further.

What's the best way of testing undervolting when using scripts? Do it manually through shell without putting them in the init.d/ folder to prevent bootloops?

FSYNC:

echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled

TCP and I/O:

echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control
echo row > /sys/block/mmcblk0/queue/scheduler
echo 2048 > /sys/block/mmcblk0/queue/read_ahead_kb

Voltages:

# Undervolt by -37500 (from _motley's defaults) across all frequencies
echo "304000 687500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "486000 837500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "594000 862500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "702000 887500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "810000 900000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "918000 912500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1026000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1134000 937500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1242000 950000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1296000 987500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1350000 997500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1404000 1000000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1458000 1002500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1512000 1012500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1566000 1030000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1620000 1037500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
echo "1674000 1062500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels;
[Nexus 4 Original Android Development] IAmAN00bie:
Re: [KERNEL][Feb 20][b39] _motley kernel for the N4 (hsic patches back for 4.2.2)

I wouldn't test using shell, I would use an app like Trickster and write down the voltages somewhere and then when you are done put them into the script. That's what I did. Use the scaling stability test in StabilityTest to see if your voltages are stable.