yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] eep2378:
Open browser(AOSP) tap menu----->tap settings----->tap labs----->make sure quick controls is checked off. Now when using the browser on any page hold your thumb on the right side of the screen and the quick controls will popup, then simply slide your finger to desired option(don't lift finger). :)
[Nexus 4 Original Android Development] aletto:
The left side works too.
[Nexus 4 Original Android Development] mko000:
Thanks! Not my cup of tea though ;).
[Nexus 4 Original Android Development] phewizzo:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Battery life in the latest build is amazing.
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Hey the delay you mean is a rom issue. Because of this i switched to cm. It is fixed on cm and aokp.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

No delay in phone calls here running AOKP Jan 16th build with kernel v01/16.
[Nexus 4 Original Android Development] aletto:
Yeah, right. Look for yourself; a picture is worth a thousand words and I have 3 of them!

I haven't used the phone that much, a little bit browsing, listening to music and I played UNO with some friends for about 30 minutes. I have no idea how some people get 4 hours+ screen time.
[Nexus 4 Original Android Development] eep2378:
Syncing services?

---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------

To each his own. Actually once you get used to it, its very intuitive. It's actually the one of the main reasons I don't use Chrome.
[Nexus 4 Original Android Development] themrjason:
Is your screen on full brightness? I keep everything on...syncs, gps, bluetooth, hspa etc, and at 12 hours with 2 hours and 45 minutes screen on I'm at 25% battery left.
[Nexus 4 Original Android Development] aletto:
lowest brightness, 1/3 to 1/2 outside (it's cloudy)

Syncing services shouldn't be an issue. There are no significant wakelocks as well.
[Nexus 4 Original Android Development] ctfrommn:
Maps/facebook/Google+ are notorious drainers. If you have any of them syncing that will definitely affect it. Are you undervolted at all? Android OS usage is pretty high too, I would guess there is a wakelock issue there somewhere.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

You definitely have some bad apps running. Your idle graph is not as it should be. Plain horizontal graph is ideal in deep sleep. Also you just use 3g all the time.

Definitely check for rogue apps, by your usage I thing 4h 20m should be easily manageable.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ctfrommn:
I never use WiFi and I get great battery/screen time so it is very possible to do. 5+, probably not but 4+ is very plausible.
[Nexus 4 Original Android Development] Audioboxer:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

To add to the discussion a few pages back about the frequencies in trickster, if you buy a donate key you can turn on frequency lock and set it to 384mhz.

Worth the money, its a great app.
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Idle battery drain on 01/16 kernel is awesome with AOKP Steve's Jan 17th build, lost 1% overnight in 8h all disabled.
[Nexus 4 Original Android Development] reaper000:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Thanks for this kernel - - exceptional speed evident in TiBu operations, scrolling, everything is ridiculously smooth. Even antutu benchmark agrees, a score of over 18200 on xylon 16. Based on what others have posted, I hope to join the 4hr screen club as well!
[Nexus 4 Original Android Development] Mahdi786:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Hi Harsh, do a test reduce your readahead in kernel to 128, test if pgm touch control works. I can't see why it would make a difference but it did with my cm kernel. Readahead 1024= module can't load, readahead 128= module load fine.
[Nexus 4 Original Android Development] Harsh:
Actually it should not effect on this. But yet i did a test by setting it in trickster, and it still does not work.

And friends who like interactive governor too much, Interactive governor is coming in next build....
[Nexus 4 Original Android Development] Mahdi786:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Well I'm building your kernel right now to test it, I meant in kernel by editing mm.h file, it changes a lot of things while building.
[Nexus 4 Original Android Development] cescof:
Really??? I've same rom and i've call delay really strange... Are you sure?
[Nexus 4 Original Android Development] Mahdi786:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Yes sorry I spoke too soon, it seems many thing can break the app, I have a cm kernel which has been confirmed working, I added some cherrypicks (undervolt etc...) App worked fine, then I added row and increased read ahead to 1024 and it broke the app, then I reduced readahead back to 128 and the app is working now.

I'm out of ideas :)
[Nexus 4 Original Android Development] aletto:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

I usually need the internet connection all the time, but 2G would be possible as well, I guess.

The Nexus was unplugged for 6h41min. I think that the wakelocks aren't the issue.

By the way I only sync emails, contacts and the calendar.
[Nexus 4 Original Android Development] gianton:
What exactly do you mean with call delay?

As soon as I slide to answer the phone and by the time I put it next to my ear I answer and the person on the other line responds. To me that's no call delay. Same thing happens with my Bluetooth headset.
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

@Harsh

Is this a usual scaling of 01/16 kernel? It's using only min or Max freqs (I've set min freq at 384MHz with Trickster Mod app).
[Nexus 4 Original Android Development] Harsh:
Its normal. mpdecision make 1026 as min. setting min frequency wont help.
[Nexus 4 Original Android Development] gianton:
I'm only using Trickster Mod for enabling the Sweep 2 Wake module. Could you please let me know how to enable it with the terminal or adb?

Sorry if this has been discussed before.
[Nexus 4 Original Android Development] ckret:
Try

in terminal

1 ist for on and 0 for off
[Nexus 4 Original Android Development] kevinnol:
Doesnt stick after a reboot though

Aww yeah :D ty harsh
[Nexus 4 Original Android Development] gianton:
It works but it doesn't stick after a reboot. Also I tried Sweep2Wake-Widget app but it doesn't work.

Any idea?
[Nexus 4 Original Android Development] ckret:
write an addon.d shell script which echos 1 to sweep2wake after each reboot

just works if youre using cm

dont know anything else except an app which does that for you (which i dont know off)

something like

.... should also be working with init.d

not sure if its working
[Nexus 4 Original Android Development] gianton:
It would be nice if someone could make a script to place in the init.d folder. I don't know how.
[Nexus 4 Original Android Development] gianton:
I made the script attached and copied it (first deleted .txt extension) to /system/etc/init.d folder fixed permissions, rebooted but it doesn't work.

Maybe Harsh can chime in to give us an idea.
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

I thought init.d went from 0-100 or something o.O try renaming it to 99 not 900. I could and most likely am wrong.
[Nexus 4 Original Android Development] ckret:
maybe the kernel doesnt support init.d yet
[Nexus 4 Original Android Development] Harsh:
here you go. place it in init.d folder n remove extention
[Nexus 4 Original Android Development] gianton:
Working great, thank you!
[Nexus 4 Original Android Development] ckret:
is there a way to do this for vibration level?
[Nexus 4 Original Android Development] renna1992:
best battery life i've ever had with this phone, thank you so much harsh!
[Nexus 4 Original Android Development] Harsh:
Probaby yes, But i have not tested it yet. try adding below line in 99sweep file i gave.

echo 100 /sys/class/timed_output/vibrator/amp
[Nexus 4 Original Android Development] Imperticus:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-16

Which rom are you using?
[Nexus 4 Original Android Development] Harsh:
New Build Jan-18 Uploaded

Welcome back... :D

And new build Jan-18 uploaded

Changelog Build Jan-18:

Interactive Governor is now fixed

OnDemand is set as default (use trickster app to select Interactive governor).​

As always HIT Thanks button if you like it... :good:
[Nexus 4 Original Android Development] Audioboxer:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Thanks Harsh great kernel. Can I ask a question about the camera? I've read on these forums the camera is controlled at a kernel level, things like compression and quality. Is this true and can it be improved? For a phone with the same camera as an iPhone the nexus 4 sure pales the majority of the time.
[Nexus 4 Original Android Development] Harsh:
Yes camera is controlled by kernel. I have looked into it. But google have complete off implementations of camera driver.

We have SONY IMX111 camera sensor, and many other phones also have same, but google's implementations is different than those.

I try messing around with it, but cant say it would be better or worse. All inside camera driver is in HEX and that values represent everything in camera. From light to dimensions, fps to shutter speed.
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Aahaha you fixed interactive!

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] gianton:
Thanks for the update.

What frequencies/settings do you recommend for interactive governor?
[Nexus 4 Original Android Development] renna1992:
AW: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Minco v6, all other options on stock :)
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

I never used interactive. I use ondemand. But for interactive you can reduce high load threshold to 80-85 and reduce high frequency to whatever you prefer probably 1.2 GHz.

Sent from my Nexus 4
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Thanks I'll try these settings. Rest default as ondemand?
[Nexus 4 Original Android Development] trismegistos:
AW: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Yes

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

What wasn't working with interactive governor, so that we know what's fixed?
[Nexus 4 Original Android Development] Harsh:
Everything. Interactive governor was causing phone freeze and reboot. It was unusable before.

Now it works fine, I did test it whole day on Interactive since I build it (compiled it)... working good. But I prefer Ondemand :D
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

I'll stay to Ondemand too then, you're the dev you know better.
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Interactive governor is developed by Google. So it would be good for android. But as I said I keep on using what I had before :)

Inactive can be good to control high frequency when in low load.

As for mpdecision when we touch screen frequency goes to 1 ghz, and interacting more directly jumps to 1.5 ghz (ondemand). But maybe interactive could get you good middle point until you don't have enough load on cpu.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Solarian:
I'm curious, does your kernel auto-detect the CPU and undervolt accordingly? Or do I have to download an adjustment app and tell it what CPU I have?
[Nexus 4 Original Android Development] YOUCANNOTDENY:
It's claimed that "Phones with faster binned should have better battery than slower binned phone out of box without any other configuration."

"Fast" was originally returned on my phone, but after flashing Harsh's kernel "1" was returned, so I'm not sure if it actually autodetects and adjusts accordingly.
[Nexus 4 Original Android Development] Harsh:
Yes voltages are already lowered accordingly. ability to control voltage by an app will be added in next release.

Yes it auto detects, that is already built in original codeaurora kernel source. And also in every kernel.

It autodetects for sure. But I will look why it came 1 on your phone.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
New build 1812 uploaded.

Changelog:

Added UV control (thanks Faux and motley)

Use System Tuner to control voltage.

Download link: http://d-h.st/tSX

If you got Fast or Faster binned CPU, post me screenshots from system tuner default kernel voltages showing 1512 MHz frequency voltage. Thank you.
[Nexus 4 Original Android Development] boykioy:
Mine was faster and after installing your kernel it shows 4. What is this, super fast?:laugh
[Nexus 4 Original Android Development] chemita:
I have faster
[Nexus 4 Original Android Development] Harsh:
For my kernel it works on new msm sources. And default voltage of faster frequency table is indeed being adopted very well that is 1025 mV at 1.5 Ghz.

People with fast should have 1050 mV at 1.5 Ghz.

Sent from my Nexus 4
[Nexus 4 Original Android Development] boykioy:
Could you please integrate the display mod settings into you kernel? It still seems yellowish comperate to franko kernel or Motleys one.
[Nexus 4 Original Android Development] Harsh:
Sure I try.

Also will be getting normal names back for binning of cpu.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Imperticus:
Mine said Fast, changed to 3 after flashing kernel and default voltage is at 1050mV for 1.5Mhz. Don't think the numbering system is very accurate, naming is more accurate.
[Nexus 4 Original Android Development] Harsh:
Updated new build 1912.

Naming system is back. :beer:

Colors can be changed using franco's display control app or by Tickster Kernel MOD

Link only here, will update OP when get home.

http://d-h.st/HX4

Sent from my Nexus 4
[Nexus 4 Original Android Development] Imperticus:
That's better. Now displaying fast again.
[Nexus 4 Original Android Development] YOUCANNOTDENY:
Something peculiar to report:

I'm on CM10.1, which is probably why this happens. I flashed the latest 1912 build on CM10.1, and everything seems to be working fine. I used terminal to retrieve my PVS value, which returned 1 instead of "FAST." But under System Tuner, my voltage is 1050 mV for 1.5 GHz, which corresponds to the correct "FAST" value.
[Nexus 4 Original Android Development] patsmike:
Anyone notice a significant improvement in battery life with the stock undervolt settings on this kernel?

And thanks harsh for making this nice and simple kernel :)
[Nexus 4 Original Android Development] Harsh:
Yes your voltages are correct. And if you are on latest build 1912, it should have name. Try reboot and check as soon as phone boots up. Sometimes old dmesg values just vanish up when you have lots of them.

But I see no point in checking, as you already got correct voltage table :rolleyes:

@patsmike I make it to use in my phone. I don't like reboot or dataloss(no fsync).:D

I am getting more than 4 hours of screen on with half hour of phone calls. My daily use.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
New build 2212 updated

Changelog:

Got it to current Linux version 3.4.24

Updated prima wifi drivers (thanks arcee).

Download Link in OP :D... have fun.
[Nexus 4 Original Android Development] 0.0:
By updating to 3.4.24, what does that version bring? Performance enhancements and fixes?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
It brings 1000+ commits of changes which were added in original Linux kernel. This brings same as what was implemented in there.

It includes fixes, compile speed improvement, logic changes, and may improve performance :angel:
[Nexus 4 Original Android Development] phewizzo:
Kernel is running very smooth. Thanks for the updates.
[Nexus 4 Original Android Development] themrjason:
I've noticed a small bump in battery life over the last couple of days. Really hard to tell though. Probably just me, but it seems like it charges a lot faster too. No stability problems either.

Sent from my Nexus 4
[Nexus 4 Original Android Development] baliriot:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

I'll stick OnDemand too for now, trusting Harsh's advises since p990 :)

Probably will give a try later on interactive :p
[Nexus 4 Original Android Development] undercover:
Ondemand has been the best governor for a while now for qualcomm devices imho. I've been using it since sensation. Sticking with it too. Vjan-18 is running good Harsh.
[Nexus 4 Original Android Development] gianton:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Jan 18th version running good here too with default settings. Lost 1% in 8h overnight all disabled.
[Nexus 4 Original Android Development] evie12604:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Lost 1% overnight with WiFi on, gmail sync on and scope syncing every hour

I love this kernel
[Nexus 4 Original Android Development] Skkip:
if anyone is interested in battery saving while device is in use try using interactive and setting hispeed_freq to 1026MHz :) I'm going to test these values now. They seem to offer the same smooth experience as ondemand but don't scale to 1512MHz so often. Maybe a good setting for later kernel releases, Harsh? :)
[Nexus 4 Original Android Development] Harsh:
Not much of difference actually. Ondemand increase and decrease frequency faster than Interactive. Even though it calls for 1512 MHz all the time, it reduce it to min as soon as its not required. While on other hand interactive wait for sometime to increase and decrease until it learns load values.

I prefer ondemand, so no change would be pre-set in kernel for other governors.

BTW: Guys currently building CAMERA test build.... tried improvement in photo only. Video is left alone as default.

Experimental would be in boot.img format only... senior users or those who know about fastboot only for testing :highfive:
[Nexus 4 Original Android Development] Skkip:
Only for me to understand:

Ondemand uses a sampling_rate of 50000uS=50ms and interactive a boostpulse_duration and min_sample_time of 80000uS=80ms. So if we/i/you adjust these values it should scale down as fast as ondemand and scale up not as fast?

Edit: Also for scaling down to 384MHz most of the delay seems to be caused by mpdecision and not by the governor itself

Thx in advance
[Nexus 4 Original Android Development] Harsh:
Probably yes it should do... But why bother with changing so much when you can get same battery life and smoothness on ondemand.

But I will try you 1026 MHz with bootpulse and min at 50ms. But I still want to be able to go to 1512 MHz when required, so what should I set for

And guys here are 2 sample images taken with old and new camera drivers. Do let me know which one is better.

And for unbiased view, I can not tell you which one is from old driver or new.

xda upload is scaling those images down, so if anyone interested, I also uploaded it to my dev host account.

Image1

Image2
[Nexus 4 Original Android Development] Skkip:
1512 MHz is still used when needed - see above_hispeed_delay. right now I'm using a (non-working-on-boot :P) init.d script with these values:

#!/system/bin/sh

echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor;
echo "1026000" > sys/devices/system/cpu/cpufreq/interactive/hispeed_freq;

maybe u can give it a try... as for scaling down. 384MHz delay is definitely caused by mpdecision and does not change with governor timings that much
[Nexus 4 Original Android Development] cescof:
I've tried the 16th aok but i the issue is still here ...maybe i could try ciano
[Nexus 4 Original Android Development] ckret:
image 1 looks better to me

looks more detailed
[Nexus 4 Original Android Development] zyonee:
+1
[Nexus 4 Original Android Development] Audioboxer:
Image 1 has the larger file size, and I *think* it is more detailed. Quite hard to tell.

A macro shot of the same thing would probably be easier to examine for compression.
[Nexus 4 Original Android Development] Harsh:
I am now giving you all people to decide... here is new test-kernel boot.img for you all.

Suggestions on how to do test :D..

1. Download test kernel boot.img
2. plug your phone, adb reboot-bootloader
3. fastboot boot boot.img
4. Decide a place and position your phone to take a photo (new kernel)
5. Reboot phone at same place and position and take another photo. (old kernel)
6. Compare results.

Here is link to CAMERA test boot.img..... do not re-upload or link it anywhere else.

If possible compare in various light condition and create thread in General section to compare your images and vote on OLD vs NEW CAMERA DRIVER

CWM updater ZIP of CAMERA test kernel is here...

Thank you.
[Nexus 4 Original Android Development] ckret:
im not new to fastboot (since ive used it with my old htc desire)

but after booting with the new kernel im getting "com.android.process" error

=/ something changed in the new kernel, so i should flash the kernel after flashing the rom again?
[Nexus 4 Original Android Development] Harsh:
I am getting no error like this. Boot.img is for stock ROM. So if you are running CM or CM based roms it would create problems.
[Nexus 4 Original Android Development] ckret:
ok thats it :) im running cyanogenmod

waiting for the other ppls test results :D
[Nexus 4 Original Android Development] zyonee:
Are the changes in the ramdisk or in the zkernel image? If the latter, could you please provide the zkernel image (or a flashable zip using Koush's AnyKernel updater method)? I'm also running CM10.1 and would like to test it out.
[Nexus 4 Original Android Development] Harsh:
Okay uploading AnyKernel zip right now. :D

I did boot.img as it would be easy to check both side by side just by one reboot....

But as many of you are on CM rom, here is CWM updater zip
[Nexus 4 Original Android Development] Audioboxer:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

Thanks for giving us the chance to experiment with camera settings in the kernel, I believe you are the first dev to do so ?

Can't flash boot.IMG on my phone right now as I'm not near a PC but I will later.
[Nexus 4 Original Android Development] Mahdi786:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

One thing good I've noticed about mpdecision is that it idles better than auto-hotplug by ezekeel, mpdecision stay at 384, while auto-hotplug and interactive are too jumpy, that must impact battery life.
[Nexus 4 Original Android Development] zhuozhi211:
Re: [KERNEL][UV][Linux 3.4.25] Harsh Kernel build Jan-18 - Interactive Gov now fixed

R: Photo... I can't tell. If there is any difference it is not very apparent?
[Nexus 4 Original Android Development] ckret:
its really hard to tell

https://www.dropbox.com/sh/01g7egou0muta6z/MaNpZygfit/compare
[Nexus 4 Original Android Development] zyonee:
I also can't really tell any great difference. Seems that the sharpness has increased, but the notorious graininess is still apparent in not extremely well lit areas of the picture.
[Nexus 4 Original Android Development] ckret:
the new driver seem to be sharper

its hard to make 2 photos from the same angle and position