yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Remoteconcern:
No, I haven't. Maybe you should try raising the voltages slightly, as I get camera artifacting with voltages that are too low.
[Nexus 4 Original Android Development] Hero_Guy:
Ah I didn't think of that. I'll try it after IO. Hoping there's still a 1% chance of 4.3 being shown.
[Nexus 4 Original Android Development] 3c:
Sorry if it was asked before, but how does the 6 extra values in the spreadsheet (amp 0 & 1) do correlate with the 7x3 values defined above? Asking because I'm implemented a UI for this in Android Tuner, and would like to include some presets from the spreadsheet.

By the way, who to and how do I request permission to include the presets defined in that spreadsheet into my app?

Thanks.
[Nexus 4 Original Android Development] brainbeatuk:
Yes. Just been bugging trickster to add multi governor support like your app

. been told its impossible without big.litlle Indian processor haha. So why does it work then. I gave up with reply.

I couldn't even change colours on trickster cos CPU section conflicts then with my android tuner multi core init.d setting. I borrowed tweaked 99_01cpu :/

You might be best asking Thracemerin. He has continued this kernel in Motleys absense. There is a m+ thread in android development.
[Nexus 4 Original Android Development] sirxdroid:
See whether this post helps:

http://xdaforums.com/showpost.php?p=38161821&postcount=6090

You can also install Trickster, run it, go to the app data folder and there a bunch of installed scripts there, see how those scripts process and set the values.
[Nexus 4 Original Android Development] 3c:
Not sure what a big.little indian processor is, as far as I know, it's either big or little, however I believe multi-core works only on ASMP processors (asymetrical), but it's not certain either and identifying them is very hard, so I opened the UI to all processors and in the end it mainly depends on kernel :D.

Yes, after posting just realized this thread has gone quiet and posted on m+, but for now only received a reply here ;)

Thanks, it's worse than I imagined :D So now that I saw the first easy-tab, I'm going with it and already added a dozen profiles.
[Nexus 4 Original Android Development] sirxdroid:
You may not need to use the Amp0/1 format at all depending what you are trying to do. You can use the Franco format numbers and set them on a Faux interface. I just posted the script that I use:

http://xdaforums.com/showpost.php?p=41809627&postcount=1171

Exposing the Faux interface to the end user is probably a bad idea, it's too complicated. Here's what I would do in an app:

Basic Mode: just expose one set of values that are applied to the the 3 R,G,B channels. Most profiles use the same values anyway, so there's no point entering the same numbers 2 more times. I think this is called the "old Franco" interface, you can still see it in Trinity kernels and I like it.

Advanced Mode: go wild with the Faux interface, for those who like to tweak every bit. I would not use "advanced mode" :)

I think if you do the Basic Mode it will take you very far and make a lot of users happy.
[Nexus 4 Original Android Development] 3c:
Thanks, that's exactly what I did, simple RGB ui first, then extra settings on different tabs. Also the ablity to link RGB settings together seemed much needed to configure gamma quickly ;)

Here are 2 screenshots.

EDIT: App has just been published :D
[Nexus 4 Original Android Development] patrickdo:
Is it safe to say this kernel has been abandoned?
[Nexus 4 Original Android Development] thracemerin:
Nothing wrong with the kernel, it just hasn't been updated since Mar 10, I continued it in a different thread in the Development Section.
[Nexus 4 Original Android Development] guapinoy:
He just added support for for all rooted devices to change gamma control, snake charmer (underclcoking for all cores) and vibration control according to his app change log.
[Nexus 4 Original Android Development] SleemLDJ:
Living the gamma tweaks on this kernel. Is there a native app to control it tho?
[Nexus 4 Original Android Development] 0.0:
If this saves battery, I hope it gets implemented. But I don't want the performance to be compromised

Sent from my Nexus 4
[Nexus 4 Original Android Development] Beretta93:
Same here
[Nexus 4 Original Android Development] keda:
I'm having hard time to keep it at one charge throughout the day.

Screen on time is 2hr 24min

I'm not even using it a lot, just little gaming, google music and web browsing.

What's weird is it's saying Bloomberg is taking 12% (cpu total about 30m) of the battery drain which makes no sense to me. Is anybody else using this App? I used it less than 10 min today.

Stock 4.2.1, Kernel build 48. Earlier built isn't that much different.

Could it be the spotty cell connection that's causing it?
[Nexus 4 Original Android Development] keda:
I'm also seeing some slightly frame drop for this video. Stock Kernel Setting.
[Nexus 4 Original Android Development] siberian85:
I figure out is set it up right out of box but BTW what is safest voltage so far?
[Nexus 4 Original Android Development] keda:
At 1.5G 1000mV, it crashed once for me while playing game. I think it's best to leave it at stock 1050mV.
[Nexus 4 Original Android Development] ctfrommn:
Stock is actually 1200mV.
[Nexus 4 Original Android Development] whittikins:
Very interesting. I have fast I guess. So comparing the 3, the fast will be stable at lower voltages than nominal and slow?

I might have misunderstood... :)
[Nexus 4 Original Android Development] cmikeh2:
I'm getting really low stable voltages if you are really patient with the undervolting. To get done if then this low I did have done reboots but as long as you don't make it set on boot then you're good.
[Nexus 4 Original Android Development] jacklebott:
Yay I have a "fast" SoC!
[Nexus 4 Original Android Development] _motley:
One of the lucky ones I see;) The fast binned chips are running 1150mV@1.5Ghz in the stock kernel while the nominal and slow chips are running 1200mV and 1250mV respectively. So, yes you are correct, the fast chips can handle the lower voltages better. There is also a freq table slated for a "faster" chip, but the kernel is not yet finished yet to support that, probably none were binned that way from the factory yet, but they added some room just in case.

Again, this is commonly done in this industry, so hopefully folks don't go freaking out because they have a nominal chip like I do:). It's probably good for a dev to have a nominal chip so we understand the limits. We'll just have to make sure we honor these diffs as devs. One some devices once we find the norm that most devices can handle, we can forge the kernel to be generic, i.e. force all chips to be treated the same way. As long as we understand, I don't see any reason to do this since we can scale like my custom kernel freq tables are shown in that prior post. It is cool to know by looking at the base voltages as to what chip you have.

A little more reading on this for those that are interested in what it all means.

http://en.wikipedia.org/wiki/Product_binning
[Nexus 4 Original Android Development] _motley:
Another lucky one...rub it in LOL.
[Nexus 4 Original Android Development] jacklebott:
Too lucky, it's bound to run out soon, eh?
[Nexus 4 Original Android Development] _motley:
LOL. Keep being good and things should keep rolling for you:angel:

P.S. I have updated all this info the 2nd post since this is important information and folks will be asking about it again I'm sure. Just direct them here:D

http://xdaforums.com/showpost.php?p=34825979&postcount=2
[Nexus 4 Original Android Development] ptesmoke:
<-----this guy here ....is also "faster" :D
[Nexus 4 Original Android Development] jacklebott:
Oooh that's super lucky to get a "faster"
[Nexus 4 Original Android Development] ptesmoke:
heh...I'm assuming I found the right line..

0.374057] acpuclk-8064 acpuclk-8064: ACPU PVS: Faster
[Nexus 4 Original Android Development] 3c:
And it's definitely worth checking, here is the continued m+ kernel thread that's definitely worth checking as it offers everything one would want in a custom kernel. Too bad we can't update OP to link both threads.
[Nexus 4 Original Android Development] :
Hi guys,

Oh no!!!! no news from _motley :confused::crying::(

So just a little hello to trillo69, copi, ctfrommn, chrone (hey mate ;)), Kocai, azrash, IAmAN00bie,Remoteconcern, etc.. (and people I forgot :crying:) :cool::);)

I saw the thread from thracemerin , great mate :cool:;)

_motley, we lost you, sincerely...

I still have my Nexus 4 but I have not flashed anything since my last post here (OMG!!!) I'm still running _motley kernel with a (very very very) old AOKP PUB build :eek:, all is fine with this setup...

And I use mostly my HTC One for day to day..., I don't have enough time to follow the two devices :crying:

Maybe it's the time to come back to the nexus 4 stuff... :D

A+ guys and I hope all goes well for everyone :cool:;) (maybe see you soon).
[Nexus 4 Original Android Development] chrone:
Haha hello nice to see you again. Yeah it's been along time. Gave up on 4.2.2 and hope for the best on this week update. Wish 4.3 will delivery smooth animation and scrolling, also better battery life. *finger crossed

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
Hey :),

Chrone, happy to see you here ;)

Yes I saw this there is a 4.3 leak for now, right? Apparently, in benchmark, the new 4.3 + the new Adreno drivers works great... In fact maybe in the general UI that will be improved...

But unfortunately, I think, we will not see a _motley kernel for the 4.3... :crying:, unless thracemerin continues its work :)

I need to come back to the Nexus 4 stuff, I'm a little lost for now (there are some new stuffs, rom's and kernel's as I see) :p. I'll test thracemerin's kernel and I need to find a new rom...

No micro-stutters or lags with my One, never had a single one... :D

:)
[Nexus 4 Original Android Development] chrone:
Yeah the leaked is out there. It has better battery life and more responsive touch input and scrolling, but again animation stuttering is still there on stock launcher, lesser on custom launcher.

Me too wonders where is _motley. Hope all is well with him in real life. :)

Whoa nice to hear htc one runs well. Trickster mod team also confirmed that htc one was less stutter than nexus 4.

I suppose the improvement in s600 instruction per cycle and power management did the trick. Full neon, bigger floating point unit and such as pointed out in this following article.

http://www.anandtech.com/show/6971/exploring-the-floating-point-performance-of-modern-arm-processors

I read S800 will also bring new level on krait performance.

http://www.anandtech.com/show/7082/...ce-preview-qualcomm-mobile-development-tablet

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
Re,

Yep, my Nexus 4 seems old in comparison to my One plus HTC did an awesome work with Sense 5, in general a stock Android device is less "lagger" than a device with a constructor overlay... Here it's not the case...

And yes the s600 is a beast I also expect the s800 in a new device (no, not in the SIV... :D).

A very good CPU (the S4 Pro is very good too) and a software part very well optimized did the trick... In the Nexus 4 it's not the CPU / GPU part (both devices have the same GPU and the S4 pro is not a lower end CPU) but the software part where is something "wrong" (don't get me wrong here, the Nexus 4 is not a SIV for example LOL! Some lags/stutters sometimes here and there for the Nexus 4 but it's not a "laggy" device), how HTC optimized this part and not directly Google on a Nexus device?... I don't know...

I love my Nexus 4 but since there are some Google Edition's rom for the "classic" One... It's hard to compare now :confused:

Thanks for the links, interesting ;)

:)

EDIT: what kind of rom are you using for now?

This thread will turn in Off Topic, sorry my fault :angel::cool:

:D
[Nexus 4 Original Android Development] chrone:
I'm using cm 10.1.2 stable right now, coming from stock 4.2.2 since February. Hehe

[MENTION=4311174]Kocai[/MENTION] suggested me to try pure speed experience rom for speed junkies. Will try it later once 4.3 not deliver. :P

Sent from my Nexus 4
[Nexus 4 Original Android Development] :
After that I stop the OT, it's friendly I post these benchs from my One :angel::cool::)

All with custom rom/kernel, running at 1.56 Ghz (the closest to the Nexus 4 CPU's frequency, I' ve not 1.51 Ghz step...):

Tweaked Ondemand governor (as always not for battery life, you know me), Mpedicison is off (in the Ramdisk) replaced by Franciscofranco's hotplug stuff (he began its own hotplug stuff with the Nexus 4, I'm not too OT LOL), tweaked thermal settings , FIOPS i/o scheduler, no undervolt, I think that's all from the kernel I use...:

Ok, Ok, sorry mods and guys for the Off Topic (it's about an HTC One :cool::angel:)... Hello to all, hope is fine for everyone :cool::cool::cool::angel::angel::angel:

The next time I come back here it's to talk about The Nexus 4... I don't want to troll (and i'm serious ;), it was just for fun... ;))

A+ all the guys I thanked, all the guys who helped me, answered, with whom I could discuss, etc ... :angel::cool::);)

;)
[Nexus 4 Original Android Development] :
Hi,

Maybe "déjà vu" (arf, no time to check the general section so I post here, my apologies), I found this googling "Nexus 4 Android 4.3" and it sounds interesting: http://www.nextpowerup.com/news/187...-the-nexus-4-reveal-improved-performance.html

:)

PS: I edited my previous post, less "agressive" with the screenshots :D

I saw the "pure speed experience rom" from simms22 on Google+ and ctfrommn posted in morfic's kernel thread, maybe I'll give it a try :)

Thanks to them ;)
[Nexus 4 Original Android Development] :
Re, hi, :D

Almost everyone is in front of the Google event :D, it's quiet here on XDA :confused::D

;)
[Nexus 4 Original Android Development] chrone:
yeah! 4.3 did deliver! as it was like coming from ics 4.0.4 to jb 4.1. hahaha very satisfied with the ui rendering performance in android 4.3. just flashed this morning and it flies 'till now. lol :good:

note that some apps still behave sluggish such the scrolling performance in archived notes in google keep app, and yahoo messenger. i find myself amazed, there's stuttering sometimes but not that frequent as it was on 4.2.2. all i can say the overall experience for this last 13 hours of 4.3 usage is 95% buttery smooth. more responsive, faster animation, smooth transition, you name it.

job well done, google! the future looks bright for Android. :_)
[Nexus 4 Original Android Development] 3c:
Yes indeed, job well done Google! And I read next version will be even smoother to handle low-end devices! Can't wait to have 4.3 on all my devices ;)

I also experienced this scrolling issue a few times, but couldn't find a real culprit. It happened in my app at some point after first boot and quickly disappeared after a few minutes. It seems very hard to track down. For now, I'm suspecting the developer option to force GPU rendering or a background process blocking IO somehow. It hasn't reproduced since.
[Nexus 4 Original Android Development] chrone:
I've read they will make the overdraw process more efficient to improve overall smoothness. Hope it will deliver.

4.3 is great, the stutter is there, but much lesser than 4.2.2. You can check it via gpu profile rendering in dev option. Whenever an action hit the green line which is over 16ms time window, the display stutter not reaching 60fps. :)

Spoiler content hidden.
[Nexus 4 Original Android Development] Irthu:
I havent tweaked around with a kernel much. I wanted to know which governor and i/o scheduler i should use for better battery performance.

And is there some way i can reduce it below 304Mhz?
[Nexus 4 Original Android Development] ziovelvet:
Any news about the _motley kernel?
[Nexus 4 Original Android Development] azrash:
Until motley comes back, thracemerin is keeping the legacy running with his _m+ kernel. The latest version is here, for Android 4.4

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

[Kernel][GPL][4.4.1][Dec 6][0.1.0] m_plus kernel for mako

If you are running 4.3 or 4.2.2, he also have kernel built for those versions. Check his profile and look for his other threads
[Nexus 4 Original Android Development] karanrajpal14:
Since development is being continued on another thread and motlely hasn't been online since April don't you guys think the thread should be locked? At least until if/when he comes back? Really hope he's fine though. Really nice guy!
[Nexus 4 Original Android Development] Kelvino9:
+1

That would make absolute sense to me.
[Nexus 4 Original Android Development] thracemerin:
Feel free to report the post and ask a Mod to lock it, talking about it just bumps the thread and results in people thinking it's active again.
[Nexus 4 Original Android Development] jacklebott:
Yep, that's the one. I do wonder what the ratio is for people owning each bin level though...
[Nexus 4 Original Android Development] ptesmoke:
so does that mean there's a.."slower" as well? guess I should go read Motleys link...this is all new to me.
[Nexus 4 Original Android Development] jacklebott:
AFAIK, the levels are "Faster", "Fast", "Nominal", and "Slow". No "Slower". Slower is probably too cruddy to use
[Nexus 4 Original Android Development] ptesmoke:
hah...interesting. from what I've read over clocking isn't really the gain. the amount of voltage it can run on is the main difference. of course if it'll work on a little less voltage in theory...you might get a tad more oc out of it.

I re read Motleys post...I'm the first faster! time to build a faster table too!!! hahah just playing with ya. looking forward to your thoughts motley.

edit* hrmmm its late..I'm not making much sense..time to catch 5 hours zzzzz lol
[Nexus 4 Original Android Development] jacklebott:
Just don't drop it ;)

EDIT: What's your default voltage table? _motley's 2nd post says that the table wasn't finished for "faster" because it's likely none were actually binned that way, so I'm curious if it actually has lower voltages or not
[Nexus 4 Original Android Development] bamsbamx:
Motley, i think that you havent read this yet ;)

http://xdaforums.com/showpost.php?p=35415842&postcount=306
[Nexus 4 Original Android Development] Stryder5:
Can someone please tell me how to check dmesg?
[Nexus 4 Original Android Development] jacklebott:
adb shell dmesg | grep PVS
[Nexus 4 Original Android Development] bamsbamx:
Easier way, just after boot open terminal emulator:

dmesg > /sdcard/dmesg.txt

Then check at sdcard a file called dmesg.txt. Open it and search for 'acpuclk', it should appear ;)

MINE IS FAST!!!! :D
[Nexus 4 Original Android Development] Stryder5:
Ran dmesg | grep acpuclk from terminal emulator. Mine says fast :)
[Nexus 4 Original Android Development] UZ7:
Build 48, this is 100% -> 0% and had to plug the phone to turn it back on. So roughly 15+hr and the last 5 hr messaging was pretty much on wakelock and thats prolly what drained the last 10%? Average day, used XDA/fb/instagram/browser, 2hr pandora, played a few games (diamond dash, tennis) and watched a few youtube videos. Good none the less! :good:
[Nexus 4 Original Android Development] undercover:
Heh, faster here. I still can't go lower than 1000mV on faux.

What screen on times are you guys getting in general?
[Nexus 4 Original Android Development] UZ7:
I get 3 on average, 4 if I don't browse heavy sites or play games.
[Nexus 4 Original Android Development] Stryder5:
I usually get at least 2, maybe 3 on average. Poor reception usually kills most of my battery though.
[Nexus 4 Original Android Development] _motley:
This was implemented in build 48. I went from 500 to 200, not quite as aggressive as franco and faux123.

Thanks. I did, but I wasn't exactly sure if they meant using my kernel with the stock gov, io sched, and freqs etc.. Anyhow, I tried the vid on the stock kernel and then on my latest build and I saw the same performance with both kernels. Are you in agreement that the stock kernel also exhibits this issue? If so, we should be fine.

I have updated the 2nd post since we now know that there are "Faster" also chips out there. Losers...lol.:p

Yeah, this can be a killer for sure. Have you tried using "GSM auto (PRL)" instead of the default "WCDMA preferred"? You can use the app "Phone Info" to change it, but it doesn't survive a reboot. I haven't researched on how to edit the settings yet to make it permanent. I keep trying to remember to research, but then never do...grrr. This is supposed to help, but I haven't done it religiously to see how much.

WCDMA preferred - The GSM phone is capable of using both 2G and 3G data communication and when signal strength is low 3G is favored more.

GSM auto (PRL) - The GSM phone is capable of using both 2G and 3G data communication and when signal strength is low 2G is favored more. This one is a bit confusing to me since PRL is associated mostly with CDMA technology and not GSM technology.​

Also, if you are on WiFi all the time, you can check your build.prop to see what the wifi scan interval is. I have mine set as below permanently, but I can't recall what stock is. It should also help with battery. System Tuner will also allow you to set it.

wifi.supplicant_scan_interval=180​
[Nexus 4 Original Android Development] exadeci:
Great kernel but there is a strange issue, sometimes while my phone is screen off in idle the screen turns on for no reason, no notification, no app waking up the screen and I don't remember having this with my rom stock kernel
[Nexus 4 Original Android Development] _motley:
I'll keep an eye on it, but I haven't see or had this issue reported before. If you figure out how to duplicate it, please do let us know. Which ROM are you on? Has it changed?
[Nexus 4 Original Android Development] Shaky156:
Helloooo motley :)

Edit: my bad thatll be the faster chips
[Nexus 4 Original Android Development] bamsbamx:
Motley i tried the video with stock kernel... It has almost the same performance... Tried with cfq and deadline... What does this mean? For example the video with francokernel has no frameskips...
[Nexus 4 Original Android Development] Stryder5:
Actually, there is a really handy app for this on XDA called Toggle2G: http://xdaforums.com/showthread.php?t=739530

It can switch to 2G when sleeping, when low battery, when wifi is disabled, when data is off, when charging, and so forth. Also comes with a plugin for Tasker for expanded usage. Sticks on reboot since the app reapplies the settings everytime. Works like a charm so far and has helped me get better reception when I'm at home. My complex has poor reception and improves when using 2G.
[Nexus 4 Original Android Development] robto:
Mmmmm.... Not in my n4 with stck rom...:confused:

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] _motley:
Cool, I'll give that a try when I get a chance. Thx.

Download MX Player, turn on hw decoding on under settings and let me know if it skips or not. It works fine for me on my kernel in MX Player using hw decoding, but not software decoding (default). The stock Gallery app must also be using software decoding. Haven't tried anything in developer settings yet to force the GPU rendering etc., but that might work too...not sure how the Gallery app responds to that setting. MX Player and some others are much better than the stock player in this regard.
[Nexus 4 Original Android Development] jacklebott:
Surprisingly, MX Player Pro still hiccups on the video for me (though I'm on Faux's kernel, so maybe moot point?). Even with HW or HW+ decoding
[Nexus 4 Original Android Development] Stryder5:
Try VLC? http://xdaforums.com/showthread.php?t=2035229
[Nexus 4 Original Android Development] jacklebott:
Stutters more than MX
[Nexus 4 Original Android Development] rlaw:
I only have a "fast" binned chipset but I can safely under volt to 1000mV max (I guess mpdecision won't let me go any lower?) for 1.5GHz and a min of 700mV for 304MHz.

I tested by running benchmarks to see how my device handled the under volt.