yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] 0.0:
To add on to my previous bug report post (and to make it clearer), when sliding down the min freq slider all the way to the left, "###" appears then goes back to 162mhz. Just reporting, and hopefully it can be fixed

It's only a minor bug

Sent from my Nexus 4
[Nexus 4 Original Android Development] AdamUpNorth:
Anyone else setting frequent reboots with 013m? Seems to happen more often when using keyboard (Swype). 012m was solid.

Flashed 013 this afternoon and have had 3 reboots so far.

Using 384,1.5

Snake charmer and eco off

Gpu @487

No UV

All for SOC states active

Stock Rom

Intellidemand with Faux recommended settings
[Nexus 4 Original Android Development] resynx:
Provide your last_kmsg, will be easier for Faux to deduce the problem ;)
[Nexus 4 Original Android Development] faux123:
Log or they didn't happen ;)
[Nexus 4 Original Android Development] justanut:
Disable SOC C2 maybe and see if it's better..
[Nexus 4 Original Android Development] tonie972:
Someone please! I'm currently running Franco's kernel and the instruction says to "Flash Reset Kernel First" what does that mean and how do I do it? Thanks
[Nexus 4 Original Android Development] JeanEatsWorld:
Mini-micro- tutorial on how to apply this instruction? Should I create a txt file? I have no clue....... sorry........
[Nexus 4 Original Android Development] DirgeExtinction:
There's a reset kernel in the first post. Flash the one for your android version. Then flash this kernel.

Sent from my Nexus 4 on T-Mobile
[Nexus 4 Original Android Development] El Nino1977:
I don't think the reset kernel is necessary anymore...
[Nexus 4 Original Android Development] raidrom:
been using 13 r2 for a few days and love it so far . the 164 or whatever low clock is super sweet and I am able to under clock -50mv with no reboots so kudos . I always thought motley kernel was the only good kernel out there cause my phone never overheated until I learned about mp decision and project butter .which we don't need since we all have quad core phones and 2gb of ram . anyways I had purchased your faux clock and also have faux speaker which I love .but after every reboot both of those apps have a 1-2 min superuser toast request at the bottom of the screen. so it could take 4 mins before my other super awesome superuser apps start getting in action .ohh and been using your kernel for a year or so .had a HTC raider and a HTC one s .but the hardware kept braking and it got old tearing it apart and finding parts .

I'm rambling .good kernel by the way .cheers
[Nexus 4 Original Android Development] Girn:
Did faux remove the 3 second delay for sound increase with fauxspeaker? Seems it's gone now
[Nexus 4 Original Android Development] AdamUpNorth:
Here you go.

View attachment last_kmsg.txt
[Nexus 4 Original Android Development] faux123:
Try disable C3 and use C2 instead... if you continue to have issues, disable both C2 and C3... it is interesting that your phone has issues entering deeper sleep states...
[Nexus 4 Original Android Development] jassycliq:
I think I saw a commit somewhere that fixed a rare circumstance that would cause issues entering deep sleep state. Been going through a ton of commits today so I'll try and find it tomorrow hopefully it'll help :)
[Nexus 4 Original Android Development] hhyong99:
Hi, can anyone teach me how to disable snake charmer by using script?

Thanks.

EDIT: Nvm, I've figured out. Thanks.
[Nexus 4 Original Android Development] Locksmith81:
Been on 13b11r2 may try 13tbu tomorrow but beta has been so good... Worth the jump??
[Nexus 4 Original Android Development] kara mustafa:
Faux why your app show that second, third and fourth core is at 162 MHz although my min is set to 384?

Wysyłane z mojego Nexus 4 za pomocą Tapatalk 2
[Nexus 4 Original Android Development] domii666:
013...great :)
[Nexus 4 Original Android Development] Sucalakafufu:
recently FauxClock has been fcing more often. ill try to grab a log at some point but it seems pretty random. anyone else?
[Nexus 4 Original Android Development] coloxim:
Faux...I've a problem...while charging my phone stuck at 113400 freq...

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] 0.0:
strange...no FCs for me
[Nexus 4 Original Android Development] GNEXc:
Just flashed 013-tbm, Is the audio mod removed ? The volume for my calls are very soft now

Edit: reverted back to r13 beta.
[Nexus 4 Original Android Development] :
For me the same: SOC2 and SOC3 are not sticking at "ON" (set on boot selected). Any hint?

Thx for this great kernel
[Nexus 4 Original Android Development] tanmay.01:
This kernel does not play well on xylon.. I thought at least the new version would.. But very high temps after only using XDA app and gsam battery monitor...
[Nexus 4 Original Android Development] AdamUpNorth:
First off thanks for the feedback and since I hadn't said it before..a kick ass kernel with the support to match.

Will try your suggestion today and see if it comes up.

This is the first time I've had reboot issues on any of your kernel versions. The only thing I've done differently was that I didn't wipe cache and dalvic before flashing. I know I don't need to but I normally just do it as a precaution. If I continue to have issues today maybe I'll give it a try.

Not sure if it's a placebo but I swear 013 has made the ui smoother. Love it.
[Nexus 4 Original Android Development] MarcoPolo78:
Wake lock

Anyone else getting msm_hsic_host wake lock ?? I'm using 013 tbm
[Nexus 4 Original Android Development] italia0101:
Is there anything I can do to get the freqs to stop jumping around so much ... I had prefmon open and didn't touch the screen .it kept jumping around
[Nexus 4 Original Android Development] Adnan008:
benchmark problem

hey faux123, what is wrong with your kernel? im getting ultra low cpu scores... im waiting opening "hill climb racing", im not waiting on matr1x kernel, the results taken on performance governor, gpu 487mhz, 8apr paranoidandroid
[Nexus 4 Original Android Development] chrone:
Update my report about the screen wouldn't turned off on offline mode charging. Came from faux 13m, flashed faux reset kernel and then flashed tfaux enhanced stock, triggered this bug. Seems the culprit is the reset kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] raidrom:
I am on xylon as well.with the new linaro stuff he put in you really have to under clock or under volt .but when you turn off mp decision all is good over here
[Nexus 4 Original Android Development] Traxex_:
This version is not running smooth for me, even with the recommended performance settings.

Paranoid stock kernel and Matrix are much smoother.
[Nexus 4 Original Android Development] Dungeon47:
Running Stable 13. Contrary to a few above, turning off MPDecision kills my CPU performance. Memory, GPU, I/O are fine, but CPU takes a nosedive in benchmarks and perceived performance. Turning MPDecision back on puts it back to "holy crap this is fast" mode. The rest of my settings are recommended in the OP.

As long as leaving MPDecision on isn't potentially problematic, I'm not worried about it, but which i have the behaviour reproduceable in front of me: is there anything I can provide that would be useful with this? I'm not getting reboots or anything, so I don't know if a logcat would be much use.
[Nexus 4 Original Android Development] Locksmith81:
Just to clarify las test stable release is the same as 13b11_r2?
[Nexus 4 Original Android Development] azsl1326:
Running 13m with mpdecision set to off, eco-mode on, snake charmer on using Intellidemand. Any idea as to why all 4 cores would be active? This occurred immediately after a reboot. Also noticed that despite have many settings set to boot, they were reverted to the original settings.

Only way to fix the core issue was to reboot.

Thanks.
[Nexus 4 Original Android Development] android88:
Yes.
[Nexus 4 Original Android Development] Klikerko:
Hi guys,

Last night I flashed my and wife's Nexus 4 with this kernel. I've done that because of battery drain problem with stock when not on Wifi. Before flashing with new kernel both phones where stock and just rooted. Unfortunately I'm getting worse results now than with stock kernel. After just over 4 hours on battery my phone is down to 75% with only 22 minutes of screen time. My wife's phone is down to 65% with 5 hours on battery and almost no screen time. She has just few apps installed while I have many, but I set synchronization only for emails and calendar.

Have I missed something, or this is normal? Are there any settings I was suppose to play with after flashing, or there's something wrong with kernel as others reported.

Thanks
[Nexus 4 Original Android Development] faux123:
Check logcat to see if you have powerHal error or not. It's very easy to see if you do.
[Nexus 4 Original Android Development] Dungeon47:
No, the only error I have is W/InputEventReceiver( 9934).
[Nexus 4 Original Android Development] faux123:
I did a quick test and here's my result. Tbm with 400 GPU
[Nexus 4 Original Android Development] italia0101:
Was this intellidemand ? I thought it was set up to not work well with benches
[Nexus 4 Original Android Development] faux123:
Yes. Intellidemand
[Nexus 4 Original Android Development] Caner092:
With recommended settings?
[Nexus 4 Original Android Development] faux123:
Yes with 400 GPU instead
[Nexus 4 Original Android Development] Caner092:
Here is my score with 13TBU mp,snake,eco off intellidemand 1.9ghz, gpu 400ghz, deadline 512, -150mv

Why my physics test score is low? :)
[Nexus 4 Original Android Development] faux123:
I got into many red LED situations, I was able to come out of it everytime by using the procedure I posted above (that post was from pure experience I had).

red led bootloop unbrick procedure

1. plug phone into USB cable connected to computer

2. wait for it to go into charge animation

3. unplug, then press power button to boot, immediately press vol up + vol down.

4. hopefully you booted into bootloader mode (rinse and repeat steps 1~4 if you can't get to this point)

5. chose recovery (if your recovery is corrupted, repeat steps 1~4 and do fastboot flash recovery cwmxxx.img)

6. from recovery choose restart system

if you can't get to step 2, because N4 has a bug with battery capacity, plug your phone into AC charge and let it charge for a few mins. then restart from step 1...
[Nexus 4 Original Android Development] raycaster3:
Hmm I have not used fastboot once though I've been making flashables for all of the betas I've flashed and had no problems.

Thanks for the instructions faux. That oughtta help some pretty freaked out folks get back into the game. :D

DARKSIDE
[Nexus 4 Original Android Development] cmikeh2:
I'm getting a 404 error when trying to download the kernel. It doesn't appear to matter what browser or method I use to try and download. Is anyone else seeing this problem?
[Nexus 4 Original Android Development] abnormalreply:
Steps 1-3 do not work to get into the bootloader. However, I can get in by just doing vol down + power. Selecting recovery causes a reboot but it does not boot into recovery, it just loops the Google logo after the reboot. With some help from another user, I deduced that this is a problem with the battery not supplying the CPU or motherboard with current. This is confirmed by: 1. Unplugging the charger while it's in the bootloader, shuts the phone off, and 2. Doing "fastboot getvar battery-voltage" does not give an output, meaning my overclocking (to 1.6Ghz) fried something involved in the battery communicating with the motherboard. Furthermore, I cannot boot up into Android because the charger doesn't supply power to the phone through the entire boot process--the battery -must- be able to supply at least a little bit of power before the ROM can boot up. So, during the boot process, when the phone tries to use power from the battery, it automatically shuts off and loops because the battery is not able to supply any power.
[Nexus 4 Original Android Development] JPOKeefe:
Can someone please post the stock kernel/boot.img?

also the links for your kernel arent working.
[Nexus 4 Original Android Development] sarni84:
Yea but that was Samsung not lg I have gotten into those situations too. Thing is it wouldn't even show a charging animation at all. I got into fast boot by holding power. Plugging phone in then holding the normal fast boot button combo.....then if I unplugged it in anyway fast boot would go off . it not supposed to do that. Only time I seen blinking red light was when phone was on charger or hooked up to comp....reminds me of the Xbox red light of death. There is something more to this and this situation I was not able to get out of. Basically putting the phone to 1.8 in CPU master free then hitting apply caused it screen flashed for a sec then nothing. Usually phone will reboot when something like that happens...idk could have been the oc app could have been anything. But I will say I tried your procedure and every other one available. The fact that that I got into fast boot the way I did was weird . it wouldn't do it the normal way (power and volume down
[Nexus 4 Original Android Development] raycaster3:
That's scary ****. Weird too since I've been running mine at 1.8 with faux's app and have been just fine. Hmm strange indeed. We may need to be a lot more careful with this device than others. I had a weird situation where I hit reboot with quickboot and the splash screen showed then faded away into a blood red screen with a faded black strip in the middle it was faint and holding power and vol down got me out of it but I **** myself to be sure.

DARKSIDE
[Nexus 4 Original Android Development] mobilehavoc:
Download the images from Google and use the boot.IMG from that
[Nexus 4 Original Android Development] raycaster3:
My apologies for the profanity. Some good news to report is I've been running 003 all day and had nothing but smooth flowing battery friendly goodness. :D

DARKSIDE
[Nexus 4 Original Android Development] abnormalreply:
The phone will rarely ever stay at 1.8 for a significant amount of time, but if you try to run a benchmark software (which most of us do), it pins the processor at 1.8 which can lead to disastrous results. That said, even if you're not running a benchmark, you never know when a random app will decide to start eating up processor speed and you will have unsuspectingly be pinning your phone at 1.8 anyways. So, that's something to watch out for I guess.
[Nexus 4 Original Android Development] raycaster3:
Indeed. I never run benchmarks unless a dev specifically asks me to. Hence I have not run one on this kernel as of yet and well I'm not on too big of a hurry. Besides we're about to see an update worth intellidemand shortly according to @faux123 on Twitter.

DARKSIDE
[Nexus 4 Original Android Development] JPOKeefe:
Can you upload a mirror for the 003 image? The link he provided doesn't work for me.
[Nexus 4 Original Android Development] BravoMotorola:
If nobody does by the next half hour I will since I'll be home by then. BTW wow, F that mod! He's pathetic and immature! Just another looser trying to control people on the internet. Probably neglected in real life...
[Nexus 4 Original Android Development] sarni84:
Yes I had a bad few days myself he gave me an infraction because I was defending myself Cuz everyone jumped on me when explaining my situation granted I did use profanity a few times tho so I guess I deserved it . oh well new phones here so raycaster u running aokp with fauxs newest and his oc app and everything is good? Kind of scared:
[Nexus 4 Original Android Development] willybarca:
.

image004 link is broken .. any other links guys
[Nexus 4 Original Android Development] raycaster3:
Yep. Been running it all day. Perfectly fine.

DARKSIDE

---------- Post added at 03:43 AM ---------- Previous post was at 03:41 AM ----------

Check pm.

DARKSIDE
[Nexus 4 Original Android Development] lookitzjohnny:
Off topic but raycaster from ogden, what about damian lillard? :D
[Nexus 4 Original Android Development] willybarca:
would u please send me the link for the 003 too i gave up on trying to get the 004

thanx
[Nexus 4 Original Android Development] d4mi3n:
Can I get a link for 003 or 004 also? :)
[Nexus 4 Original Android Development] raycaster3:
No idea lol

DARKSIDE

---------- Post added at 04:16 AM ---------- Previous post was at 04:15 AM ----------

I really don't know how @faux123 would feel about it. Check my tweets. @raycaster3 ☺☺☺

DARKSIDE
[Nexus 4 Original Android Development] Audioboxer:
Wonder if Faux will start editing the thermald.conf? Hasn't it already been changed?
[Nexus 4 Original Android Development] undercover:
That is wrong. Heat is only a by product of excessive power use. It's the drain that causes heat, not otherwise.

Phone staying cooler is only an indication that drain is lower, which is obviously good. If battery gets too hot, it degrades quicker, so it's good to have it run cooler (obviously).

Faux, is 37-41c normal CPU temperature when using the phone to type (ie touching screen) on stock kernel? Just trying to build some reference point.

Thanks.
[Nexus 4 Original Android Development] Logi_Ca1:
Actually... Take a look at this article

http://www.techpowerup.com/mobile/reviews/Zotac/GeForce_GTX_480_Amp_Edition/27.html

Obviously its talking about GPUs and we can't apply what it says to our phones 1 to 1, but in general increased heat causes more current leakage. I asked an engineer friend of mine and he says a simple explanation is that because the atoms are vibrating faster when they are subject to more heat, it takes more energy to push electrons around.

So, undervolting actually produces two benefits. Firstly you are using lesser energy to do the same amount of work. Secondly, by keeping the CPU cooler you reduce current leakage.
[Nexus 4 Original Android Development] mzanette:
What's the difference between setting the min/max cpu speeds and undervolting? Do they work in conjunction with each other? I'm trying to learn all this on the go and its like trying to drink water from a firehose lol
[Nexus 4 Original Android Development] Jur1nator:
Brian Klug from AnandTech just posted this on his twitter..

could maybe be a help for faux? :
[Nexus 4 Original Android Development] lightningstalon:
Setting the min/max speeds of the CPU just sets the lower and upper bounds of CPU clock speed spectrum. More simply, the min and max of how "fast" (cycles) the CPU is.

Undervolting is basically lowering the voltage delivered from the battery to power the CPU. Each "step" of the CPU clock speeds can be set to a different voltage, the higher clock speeds needing more voltage than the lower ones. Essentially, undervolting is reducing the amount of power the CPU gets to operate, which can potentially save battery life. However, undervolting too much can cause a shortage to the CPU, which will cause the phone to reboot.

I think this could definitely be something to look at because the Droid DNA seems to get much higher benchmark scores with the same SoC.
[Nexus 4 Original Android Development] Audioboxer:
Interesting indeed, hopefully helps faux :good:
[Nexus 4 Original Android Development] faux123:
yes and no.. thermald can be customized by Qualcomm priority customers such as HTC, so they may have customized their own thermald (for Droid DNA) further from stock Qualcomm thermald (Nexus 4).
[Nexus 4 Original Android Development] rootuser11:
I wonder if we can blindly copy paste the thermald.conf from droid to n4.
[Nexus 4 Original Android Development] faux123:
not all features will be available from the stock Qualcomm thermald and also be careful, not all sensors are assigned the same way. You can reference the Droid DNA thermald.conf, but would be UNWISE to copy and paste.
[Nexus 4 Original Android Development] rootuser11:
Yes i agree. I am more curious about optimusg's thermal.cong which i would think more closely matched if not identical.
[Nexus 4 Original Android Development] lightningstalon:
Hey faux,

Is there any reason why you don't utilize deep sleep - not even with the default ondemand as the governor?
[Nexus 4 Original Android Development] bongostl:
Anyone know what snake charmer is? Faux referenced it on Twitter s being a new feature
[Nexus 4 Original Android Development] faux123:
? my ALL of my kernels deep sleeps well... If you have issues with deep sleep, load my reset kernel here:

http://faux.androidro.ms/mako/mako_421_reset_kernel.zip then reflash my latest kernel again (if you are on Stock or stock derivative ROMs, for CM simply reflash the nightly and reflash my kernel again).
[Nexus 4 Original Android Development] faux123:
it's my code name for my CPU max frequency limiter that I wrote ;) with snake charmer, you can control Qualcomm's Kraits (deadly snake!) :highfive:
[Nexus 4 Original Android Development] jacklebott:
I have a problem with the max frequency often resetting to 1134MHz while using Intellidemand, whether I'm using eco mode or not. It doesn't happen from battery temperature throttling, as it's been around 33°C. I have to manually set it back to 1.5GHz to get it to go past 1.1GHz (or reboot). Mpdecision is turned off as well. It seems to happen most often when the CPU gets stressed (but also happens more randomly), as it happens within 30 seconds into a stress test. Any idea?

EDIT: Tried v2beta4, it doesn't fix it. I don't know if Snake Charmer's supposed to help, but it doesn't for me. Maybe I'm doing something wrong, I dunno. It's past 4am so I'll test more later (seems like maybe it's working now, but who knows)
[Nexus 4 Original Android Development] faux123:
Beta 4 is out!!! Check 3rd post... Goodnight ALL.. I am feeling a bit sick...
[Nexus 4 Original Android Development] rootuser11:
I wonder which one is better

1.1ghz + no eco

1.4ghz + eco

Hmm
[Nexus 4 Original Android Development] MatAuc12:
1.1ghz + Eco.

Personally I use 1.2ghz, but S4 pro is so overpowered that you don't need that.. At all.
[Nexus 4 Original Android Development] rootuser11:
At the moment i am just on 1.2 + eco too. Nfs most wanted slight lags but bearable and temp is good!
[Nexus 4 Original Android Development] ajanu:
@Klikerko

You should buy better battery stats, or get the xda version. Android os should be low, you have a wake lock issue most likely. BBS will help you find that.

When I am at work, I turn off data and lose around well under 1% per hour. In 6 hours today I have 79% left after 45 minutes of screen time and 15mins of calling. Leave your phone with data off for an hour, it shouldn't lose more than a percent, if it does it isn't sleeping properly and you need to find what is stopping that.
[Nexus 4 Original Android Development] Girn:
Because ur phone got hot and down clocked the CPU
[Nexus 4 Original Android Development] droidkevlar:
i dont belive in tests, but what app you guys using for these scores?
[Nexus 4 Original Android Development] android88:
3DMark. It's available in the Play Store.
[Nexus 4 Original Android Development] faux123:
yeah.. the benchmark should only be used under controlled environment.

Posting benchmark scores is really almost pointless.

Unlike desktop CPUs, our phones are PASSIVELY cooled, so we are at the mercy of the CPU and Ambient temperature (ie, if the CPU heats up, we have NO OTHER WAYS to cool it except force it to run at lower frequencies where as on desktop, with active cooling, the fans/coolant can go faster to carry away more heat keeping the CPUs at a constant operating temperature).

To make benchmark really meaning full, you will need to operate under the following conditions:

1. Run in airplane mode

2. disable all background operations

3. Note the ambient temperature of the ROOM or environment

4. Cool the phone to a known operating temperature

5. Run the benchmark and observe if thermal throttling kicked in or not and for how long

repeat the same benchmark several times UNDER THE SAME EXACT conditions from steps 1~5

then take the average scores in order to really use the benchmark to judge performance...

Unless you work for Toms Hardware or Anantech, it's really time consuming and lot of preparation required to do a "simple" benchmark and make their results MEANINGFUL :angel: