yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] LiquidSolstice:
Uhh..that's not a button. That's the TapaTalk watermark that gets overlaid onto any image that's uploaded through the TapaTalk app onto a forum, as TapaTalk is the one hosting the image.
[Nexus 5 Original Android Development] bazzawhite:
Been using intellidemand with Intelliplug but have been getting laggy scrolling and long smses in hangouts make the default Google keyboard really laggy. Switched to Ondemand and it seems much better. The rest of the settings are exactly as the recommended settings.
[Nexus 5 Original Android Development] danarama:
Doesnt happen on mine:

http://xdaforums.com/showpost.php?p=48238973&postcount=1208

is it the free version you use?
[Nexus 5 Original Android Development] sterod:
Sweep2Wake Help

Guys, I'm having trouble getting Sweep2Wake to behave the way I want. Running FauxClock 1.5.6 with the V5 mainstream kernel on a Nexus 5 with 4.41, rooted of course.

I want Sweep2Wake to respond to a swipe from the bottom edge of the phone to about 1/3 of the way up.

I've gotten the approximate coordinates by enabling the pointer location in the developer options.

My settings (that don't appear to be working) are as follows:

Start Position: 1900

Mid Position: 1600

End Position: 1300

Threshold: 300 (I have no idea what this does, and explanation would be helpful)

Orientation: 1 (I assume 1 is correct, as that is what the setting is in the Vertical preset)

Suggestions?
[Nexus 5 Original Android Development] abdielol:
Exactly what he said. I dont know how would I even get a Tapatalk shortcut over there.
[Nexus 5 Original Android Development] Grondinm:
[MENTION=3332811]faux123[/MENTION] Juts had a random reboot while i was having lunch. Phone was in case not doing anything. Noticed when i got back to work and had to unlock sim card...here is last_kmsg

Running latest kernel with SlimKat beta 1.4(Android 4.4.1) and 4.4.1 modem and bootloader.
[Nexus 5 Original Android Development] show-p1984:
Android touch position != kernel touch position.

I don't exactly know if this is true on the n5, but it is on the n4. Android uses some filters that actually decrease the resolution quite a bit.
[Nexus 5 Original Android Development] mad_ady:
I'm not sure if my question is relevant to this thread, but I'm running 4.1.1 with faux kernel 05m. I noticed on calls that the speaker vibrates and resonates unpleasantly on some frequencies. I can hear it when the caller makes sounds like zazaza or zezeze (sorry for sounding childish).

Most likely it's a hardware defect - the speaker (head piece) clearly rezonates, but I wanted to know if it may be caused by some tweaks in this kernel (I haven't tested the stock kernel).

Also, if it's a hardware issue (it doesn't occur when using headphones), can it be fixed by attenuating those frequencies systemwide?

I've heard complaints about the speaker not being loud enough, but I think this is something different.

Sorry if I'm being offtopic, but at least I'm not asking if the kernel is compatible with CM :P

Thanks
[Nexus 5 Original Android Development] Globespy:
Did you experience this issue with previous Faux kernels or other kernels?

---------- Post added at 01:38 PM ---------- Previous post was at 12:42 PM ----------

Is the latest kernel compatible with 4.4.1 build? FauxSound and gamma app will all work OK?

Just want to be sure before I update to latest cataclysm.

Thanks.
[Nexus 5 Original Android Development] muyoso:
Anyone know what the best settings are for the Faux Sound app to reduce the clipping present in the Nexus 5 left channel? Anandtech recently posted an article on smartphone audio testing and exposed that the Nexus 5 clips at max volume pretty significantly in the left channel.
[Nexus 5 Original Android Development] nadrojcote:
I've always had this issue, turn the volume down a bit.
[Nexus 5 Original Android Development] raLzor:
I just got an update notification for 4.4.2, not applied it yet.... do I need to wait until faux releases an update to still use fauxclock?

I was still on 4.4 as well, never got update for 4.4.1 OTA.

Thread about 4.4.2 http://xdaforums.com/showthread.php?t=2562534
[Nexus 5 Original Android Development] nadrojcote:
I just updated to 4.4.2 and am using 005 kernel, seems to be working.

I updated without reverting to stock kernel, after I reinstalled 005 kernel and supersu
[Nexus 5 Original Android Development] raLzor:
Thanks, I'll give it a try :good:
[Nexus 5 Original Android Development] chazall1:
I just updated to 4.4.2 and am using 005 kernel, seems to be working.

I updated without reverting to stock kernel, after I reinstalled 005 kernel and supersu
[Nexus 5 Original Android Development] nadrojcote:
Only thing Im noticing is that my notification light is no longer working.

EDIT Nvm its working, it must have just been cause I had the screen on at the time of getting the notification.
[Nexus 5 Original Android Development] ogboot:
I installed 4.4.2 without reflashing 4.4.1 stock kernel. I'm not saying i've tested for 100% functionality, but yes the update proceeded with faux's v5 kernel and the phone booted with no issue.
[Nexus 5 Original Android Development] spray.de:
Does 4.4.2 contain a new bootlaoder and modem?
[Nexus 5 Original Android Development] graffix31:
This... Curious that because is sprint of they fixed the bad radio in 4.4,1
[Nexus 5 Original Android Development] DoesntPostAThing:
005 should work just fine as there are no kernel changes in 4.4.2. The OTA zip does not contain a boot.img.p
[Nexus 5 Original Android Development] DroidIt!:
Haven't updated myself but saw somebody who had that still had the same .23 radio number as on 4.4.1, so no don't think so.
[Nexus 5 Original Android Development] KrazyAttack:
I just flashed the 4.2.2 update with Faux already installed.

Flashed just fine, reflashed SuperSU 1.80 and 005 and good to go just like before.
[Nexus 5 Original Android Development] shadowblade330:
Seems to work on 4.2.2. And worked fine to with ota update
[Nexus 5 Original Android Development] silverdart:
Works however comma

Only working on two cores for me. 1 and 2
[Nexus 5 Original Android Development] shadowblade330:
Which version are you using I'm on kernel 5 maybe you might have to reflash supersu to gain root again.
[Nexus 5 Original Android Development] silverdart:
I'm using

5u and tested OTA before flashing and all cores were working. Probably have to wait for a kernel specific update for 4.4.2.
[Nexus 5 Original Android Development] DoesntPostAThing:
There should be no problem. As I said, there is no kernel update at all from 4.4.1 to 4.4.2.
[Nexus 5 Original Android Development] silverdart:
Nice theory

However, my reality is what it is. Please pay attention to my Avg usage. And that's after running benchmarks!
[Nexus 5 Original Android Development] DoesntPostAThing:
Try reflashing and disabling fauxclock's set on boot. Or freeze fauxclock.

---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------

It seems GPU is behaving weirdly. Often times it would idle at 320 MHz, then as soon as I do something it drops to 200 MHz. Wouldn't it make more sense for it to be the other way around? Other times it functions as normal where it would idle at 320 and go up to 450 when something is moving.
[Nexus 5 Original Android Development] silverdart:
OK!

Will do!
[Nexus 5 Original Android Development] DroidIt!:
From what I've read it's a very minor update, all software related, no new bootloader or radios or anything. So if you're using a custom ROM I'd just wait for the dev's to incorporate it into a ROM. Being that 4.4.2 is all software if you update and flash a custom ROM again afterwards, then you will lose the update.
[Nexus 5 Original Android Development] silverdart:
Yes sir!

You are right! Fauxclock was the problem as results show. I wiped dated and uninstalled so now I'm going to re-install fauxclock and post my results.
[Nexus 5 Original Android Development] silverdart:
Fauxclock!

The same thing happened once I re-installed fauxclock so that is definitely the culprit in this case.
[Nexus 5 Original Android Development] DoesntPostAThing:
Hmm, interesting. This may be causing my GPU issues too. I'll uninstall Fauxclock and see for a bit.
[Nexus 5 Original Android Development] pluGinSz:
Hi OP, any plan releasing Hybrid for Mako ?
[Nexus 5 Original Android Development] notbrodie:
take this to the mako thread. this is for hammerhead, aka nexus 5
[Nexus 5 Original Android Development] feedhead:
About to throw phone on charger... Quite impressed with battery life.
[Nexus 5 Original Android Development] DoesntPostAThing:
Hi guys, I ran some tests on the GPU issue that's been bugging me and likely others. Ever noticed your phone stutter a bit here and there? As been pointed out before, this should be no fault of the CPU as even on lower frequencies there should be more than enough power to provide a smooth experience. What's likely the issue, is the GPU. And take a look at these two graphs made by Trepn Profiler of GPU frequencies. One is on Franco Kernel, one is on Faux.

Album: http://imgur.com/a/51aY6

Not only is the graph from Faux kernel all over the place, I noticed this: It would idle at 320, but as soon as I did something it dropped to 200. What Franco does is it idles at 200, and when you did something it jumps up to 320 and then back down when it's idle again. 450 isn't even needed. Faux, perhaps you could take a look into this? Btw, if anyone wants to test Trepn is a Qualcomm app for developers. Search for it and it should ask you to create a Qualcomm developer ID. It's completely free. After that just download the apk and profile away. In both tests all I did was swipe around between app drawer and homescreen in Nova Launcher, then open a few apps like G+ or XDA. The Faux test was ran on Simple with 5 and 6, Franco test was on default settings.
[Nexus 5 Original Android Development] shadowblade330:
Delete
[Nexus 5 Original Android Development] MasterfullDON:
Silly question, but I am unable to understand from the posts. I have upgraded to the 4.4.2 odexed stock rom, working fine with stock kernel. Can I use this 005u kernel on the Nexus 5 with 4.4.2 KOT49H build?

BTW when I installed 005U on the 4.4.1 KOT49E it didnt work for me....
[Nexus 5 Original Android Development] nadrojcote:
You can use it on 4.4.1 and 4.4.2, maybe youre doing something wrong?

---------- Post added at 03:58 PM ---------- Previous post was at 03:55 PM ----------

I dont notice stutter, when using faux kernel make sure to set the gpu governor to simple and use recommended settings.

Edit, I am noticing it idling at 320 and not dropping to 200 unless I do something that should make it ramp up. Very odd.
[Nexus 5 Original Android Development] DoesntPostAThing:
Exactly, the behavior is reversed. It is also jumping between frequencies too much.

Sent from my Nexus 5
[Nexus 5 Original Android Development] afazel:
I noticed the behavior as well on the ondemand governor. It idles at 320 and ramps "up" to 200. With simple it idles at 320 and ramps up correctly.
[Nexus 5 Original Android Development] DoesntPostAThing:
I tested with all three governors as well as playing with parameters for simple. It seems like this: ondemand constantly ramps "up" to 200. Simple would sometimes ramp up correctly, other times go down to 200. If you slide either slider to the ends it goes "up" to 200 more often. Even when it ramps up correctly it still produces the messy graph. If you look closely you can see that for every time it ramps up correctly, it first dips down to 200. After the load has been processed it will dip all the way down to 200 a few times before settling at 320. Whatever it does, it still jumps to 200 intermittently.

And whether you notice the stutters or not, I think we can all agree that this is a bug.

Sent from my Nexus 5
[Nexus 5 Original Android Development] HKPolice:
Just confirmed everything you said, with simple gov the gpu freq bounces around like crazy. ondemand gov idles at 320, sometimes 200 but it always drops down to 200 when scrolling apps, it never scales when needed. Downloaded the trepn app and running overlay. Going to test on the nexus 7 2013 next....

Update: nexus7 better, it instantly boosts to 450mhz when swiping screens. The idling is still a bit weird. With a live wallpaper (phase beam) it idles at 128/200Mhz, but with a static wallpaper it idles at 300Mhz!
[Nexus 5 Original Android Development] RealSlimShadyMC:
Issue exists on Nexus 4 as well. Doesn't go below 450MHz (30u) on demand, but only ever goes to 320MHz on simple.
[Nexus 5 Original Android Development] Phazmos:
What happens with force gpu rendering enabled in dev settings?
[Nexus 5 Original Android Development] DroidIt!:
Believe that your gpu then takes the load of, oh how to say it, loading the different pages of whatever launcher you are using instead of the cpu. Not sure my terminology is right, kind of hard to describe, but I've tried that option before and really found no advantage of forcing gpu rendering. Supposedly it can speed up your launcher with faster scrolling etc. but I think we have such a good processor it makes no difference.

Oh, and personally I've always kind of shied away from it myself. You're forcing some of the load the cpu takes onto the gpu. I don't know if that impacts the lifespan of the gpu at all, but kind of makes sense if you think about it.
[Nexus 5 Original Android Development] lolpok:
it should only affect 2d programmed apps, but however rendering with GPU would be a good thing, android already rendering with GPU but not so much as it should IMO.

---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------

I used franco kernel before this one, and i must say faux kernel is much more smoother. Thanks faux!
[Nexus 5 Original Android Development] Phazmos:
I know what it does, I mean how do the graphs look with this enabled.

Theory - some gui is rendered on cpu, and some on gpu. Graph may show that switching. With more of the gui being rendered on gpu, you may not see that behavior, or as much of it.

Just thought it would be interesting to see.

---------- Post added at 02:28 PM ---------- Previous post was at 02:22 PM ----------

I got into the habit of always enabling it. It always made the gui a lot smoother. Not as noticeable on a high horsepower device like this, but it still seems to make a little difference, to me anyway. After all, what we see is a gui - graphical user interface - and a gpu is geared to render graphics. Seems like a good match.
[Nexus 5 Original Android Development] DroidIt!:
:) If you try it and it seems to work better for you then by all means do it, that's the only way to know for sure. Don't think it'll change the appearance of anything though, that is all set by how themes, icon packs, app interfaces, etc. are coded to look. So, switching to gpu rendering won't suddenly change the look of things, just MIGHT have an impact on performance is all. Just curious now, if you do try it if you could let us know if you see any difference that'd be cool. I wonder how it would affect the settings in faux clock though, if at all...
[Nexus 5 Original Android Development] silverdart:
After tinkering around

I have determined that the Eco mode (which I had enabled) actually turned off two processors. The description says "Special power savings mode Optimized for 2 cores". I don't know if that was meant to mean turn off 2 cores but that is fine. If I go out for a long time now I know how to turn off 2 cores and conserve battery life. Other than that fauxclock is fine.
[Nexus 5 Original Android Development] faux123:
It's more than just turning off the 2 cores. It also changes the behavior of how the loading are calculated and how the cores should ramp up and down. Simple turning off 2 cores will not be a good idea since everything else is expecting a quadcore.
[Nexus 5 Original Android Development] parkson:
Also seeing GPU scaling issues on my device
[Nexus 5 Original Android Development] Chughes13x:
+1
[Nexus 5 Original Android Development] faux123:
Don't worry about the GPU scaling issues.

This is a classic sampling theory issue.

You see, most control apps out there samples the CPU/GPU frequencies @ once per second, for me I sampled @ 2x per second. This will give more accurate readings (higher sampling rate == closer to reflect the real time status). Unfortunately, sampling the frequencies also causes the frequencies to jump as well. By observing it, you are changing its behavior as well (Quantum uncertainty principle here ;) ).
[Nexus 5 Original Android Development] nadrojcote:
Why is it that its ramping down when it should be ramping up? Idling at 320 and going to 200 when under load?
[Nexus 5 Original Android Development] silverdart:
Understand!

That is a great option to have in fauxclock. Thanks!:good:
[Nexus 5 Original Android Development] Phazmos:
You may have missed the point.

It's not a matter of how it looks, but how it's processed.
[Nexus 5 Original Android Development] Reevine:
So after updating to 005 I tested the undervolting. On previous versions I was not able to apply a global undervolt but if I did individual frequencies it would work.

With 005 I have tested different voltages and the max seems to be -75mV on 4.4

With individual frequencies the max was -150mV.

I will test 4.4.1 once I get it updated and do some further tests for global voltage for those interested.

Edit: I still can't get Eco Mode to work with any undervolting. I'm thinking this is because it shutting off two cores? With Snake Charmer on I'm able to max out at a global -50mV.
[Nexus 5 Original Android Development] nadrojcote:
I have never been able to undervolt more than 50mv globally, this is what I am currently running at with 4.4.2 and 005 kernel.
[Nexus 5 Original Android Development] DroidIt!:
Ah, ok. :) I got your point now. When you said "graphs" in your earlier post, I thought you did a typo and meant graphics. :silly: But you actually mean performance scores, ok now we're on the same page. :o I know we're lucky and we have one hell of a cpu and also a bad a$$ gpu, so yeah, agreed, that would be interesting to see which outperforms the other with gpu rendering turned on. Never thought of that, nice thinking. Maybe time to turn on the option and try some benchmarks. :D
[Nexus 5 Original Android Development] MrPhilo:
I never noticed that the last clockspeeds has same voltage!

I did the same thing as you and just decrease them by one minus each :)

Cheers dawg
[Nexus 5 Original Android Development] Reevine:
Most people can't undervolt more than -50mV on 4.4.1

I'm running 4.4 right now. I have not upgraded to 4.4.1 yet, hence the global -75mV max.

I'll be testing 4.4.1 once I upgrade :)
[Nexus 5 Original Android Development] Phazmos:
It used to give a bump in benchmarks, but again, this processor is a beast, and can handle it just as well as the gpu. I don't see any improvement in benchmarks with that enabled or disabled. I just notice some things are smoother with it enabled.

Used to be a way to save some battery too, but that may not be true now with a beastly gpu. At least I haven't seen a diff in battery life one way or the other.

Oh, graphs, I meant graphs like in plotted data. Previous posts have more info.
[Nexus 5 Original Android Development] DoesntPostAThing:
What about the idle and "ramp up" frequencies being "reversed"?

Sent from my Nexus 5
[Nexus 5 Original Android Development] muyoso:
Your post is interesting and raises the question of what the better option is for battery savings. Turning eco mode and snake charmer off and getting a better undervolt across the board, or turning both of those features on and undervolting as much as you can. . . . .?
[Nexus 5 Original Android Development] DoesntPostAThing:
I reverted to 004m and did a test, this time using ondemand. No crazy jumps, HOWEVER: It show the exact opposite graph as Franco's, which I currently assume to be "correct" as it makes the most sense to me. On 004m, it would be flat at 320, and as soon as there was something moving on the screen it dips down to 200. Very predictable. The only issue here being, the frequencies seem inverted to me. I then went back to 005m and tested it again. The jumpy behavior was only with simple. I'm not sure how correct that is, but it seems rather smooth. It could just be the extra sampling Faux talked about. However, ondemand is the same inverted. Then I fired up Riptide. 389 and 450 seem to function just fine, only 320 and 200 are mixed up. Forcing GPU rendering does not make a difference. Judging by how 320 and 200 are switched, I think there's another explanation why the graph for Simple looks all over the map.

What the GPU thinks it's doing: 200, 320, 389, 450, 389, 450, 389, 320, 200. All in increasing order to begin with, a slight bit of variation at the top, then in descending order when coming down.

However, due to the mix up, here's what every single test I've ran shows me: 320, 200, 389, 450, 389, 450, 389, 200, 320. This would explain why the frequency shoots down before going up, and would always overshoot the idling frequency down before idling again.

At this point I'm not doubting the "messy" graph of Simple, as Faux explained it's just sampling more often for more accurate results. However, the inversion of 320 and 200 should be looked into.

Tl;dr: 320 MHz and 200 MHz reversed.

Temporary workaround: To prevent it from staying at 200 when you're doing something, either lock it to 320 using performance governor (performance seems to be unaffected by this) or use Simple. Simple tends to stay very little at 200 (what it thinks to be 320) and goes up to 389 and 450 more. So yes, there will be slight periods at 200, but due to the limited duration of it it shouldn't be too noticeable. I'm just going to stick with performance [MENTION=2539186]320[/MENTION] for now and increase it to 450 if I'm playing a game.
[Nexus 5 Original Android Development] Reevine:
Yeah that's what I've been trying to figure out. I see better battery life to be honest when I'm using a larger undervolt than when I was using Eco Mode and Snake Charmer.

For some reason on the Nexus 5 kernel undervolting does not work well with those two features. Even if I use a small undervoltage I still end up getting CPU crashes eventually.

The one thing I'm trying to find out is what the differences are between the Snapdragon 800 and the Snapdragon S4 Pro (found on the Nexus 4). With Faux's kernel for the Nexus 4 I was able to use both features and undervolt -100mV which gave me amazing battery life under moderate to heavy usage.

I know both kernels are compiled differently because of the differences between the devices but I really don't think that there is a big enough difference to warrant the CPU to not support undervolting.

[MENTION=3332811]faux123[/MENTION] you have both sources for the kernel up correct? Might you also provide some more insight and why this could be happening?
[Nexus 5 Original Android Development] nadrojcote:
For some reason I cut off 2.26ghz in my picture but its at 950000uV

---------- Post added at 03:14 AM ---------- Previous post was at 03:11 AM ----------

I wasn't able to under volt more than -50 on 4.4 and I'm using the same settings on 4.4.2 as I was on on 4.4.1 and 4.4. Also I am using snake charmer to and eco mode. Max Cpu clock is at 1.7ghz

---------- Post added at 03:20 AM ---------- Previous post was at 03:14 AM ----------

They are two completely different CPU's one will under volt better than the other. Also you could have twp 800's and one can do -100 and the other could only do -25. Silicon lottery.
[Nexus 5 Original Android Development] muyoso:
Every day I have at least an hour of wakelock from Wlan_rx_wake and other wifi wakelocks as well, sometimes up to 3 hours. Does faux have these mythical wifi patches that Franco kernel supposedly has? This is the last issue plaguing my phone, and I have tried just about everything to fix it including static IPs, disabling IPv6 and various services on Windows PC's, etc. Its just the router constantly waking up my phone at this point.
[Nexus 5 Original Android Development] KrazyAttack:
What is everyone using for their I/O scheduler? Just the default CFQ?