yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] NYZack:
Interesting. I saw the new recommendation in the OP for C0, C1, and C2 to be enabled. I'll try your advice though. Just had another miserable bootloop while checking notifications. Even lost some data.
[Nexus 4 Original Android Development] zubin111:
Is it me or why this latest beta is hotter? I get constantly temp reading between 48-52 on web surfing... i think on 04 i used to get around 40-45... I have eco mode on and snake charmer on with intellidemand, 162/1.35...
[Nexus 4 Original Android Development] Ace42:
Foot battery temp or CPU temp?
[Nexus 4 Original Android Development] zubin111:
CPU temp... For Sure!!!
[Nexus 4 Original Android Development] PJcastaldo:
Haven't seen any issues caused by the last 16 beta. In fact its been pretty smooth.. And... Correct me if I'm wrong but I think this is pretty good..
[Nexus 4 Original Android Development] Globespy:
Both, but most notably battery.

Earlier beta builds were never above 34C and I've seen 44C on 16_06 and I'm running 162/1512 MHz with snake charmer and UV.

The phone is significantly warmer and actuallya little uncomfortable to hold when making calls sometimes.

I'm tempted to start under clocking CPU as I don't like these increasingly hot temps.

Also still getting the occasional reboot.

---------- Post added at 12:28 AM ---------- Previous post was at 12:25 AM ----------

2 hours screen time is awful bud - that's like the crud battery life when the N4 was first released.

Most faux kernels give me 4+ hours screen time - 16_02 actually gave me just over 5 hours - I think that was the one where faux made the min clock 512mhz!
[Nexus 4 Original Android Development] saint_cow:
Can someone please confirm what each of the headphone gain controls do?
[Nexus 4 Original Android Development] PJcastaldo:
Really..? Even after 20+ hours and several minutes of voice calls.. Plus the other use.. That's bad?

Like I've posted in the battery life thread.. I've seen 3 1/2 hours of SoT but it was with a 12 hour battery life..
[Nexus 4 Original Android Development] Andrew025:
Right now I'm sitting at 2 hours 15 mins SoT with 59% left.
[Nexus 4 Original Android Development] JaylanPHNX:
It really depends on usage. There are plenty of battery intensive tasks that don't require the screen to be on (audio streaming, for one). If a lot of these activities went on, then yes, I'd go by total unplugged time. If it was mostly browsing, news reading, etc, then screen on time is king. If you're satisfied with your phone's performance, that's the most important measurement there is.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] PJcastaldo:
But how many hours have you been off the charger.. ?
[Nexus 4 Original Android Development] Andrew025:
12 hours

Forgot to mention that part :)
[Nexus 4 Original Android Development] j.llorente:
What's de recommended SOC configuration? At the second post said all ON but I have some reboots with all ON. This configuration has not changed in months and I guess now it will be another.

Thanks!
[Nexus 4 Original Android Development] rmead01:
try turning on c0 c1 and c3 leaving c2 off.
[Nexus 4 Original Android Development] j.llorente:
Thanks! I'll try it. I'm really using C0 C1 ON and C2 C3 OFF and I don't have many reboots. All reboots that I have now are when I'm writing with swiftkey and the app suffers a "data reset" and I must configure it again.
[Nexus 4 Original Android Development] willybarca:
cpu overheats so much with 16b6, mine was near 65 degrees ,
[Nexus 4 Original Android Development] brunini:
Yeah this last beta make my device a little more warming...
[Nexus 4 Original Android Development] Ace42:
Hmm I wonder why you guys are having heat issues all of a sudden. My max is 1.3 eco and I UV -125, so I'm assuming that's part of why I'm not having temperature issues.
[Nexus 4 Original Android Development] rmead01:
Not to sound like a complaint, but I always noticed the heat with this kernel. Not from my personal usage so much, but my son plays games on my phone during car rides. So comparing a few different kernels after a 30 min ride or so, the phone always felt warmer after his usage with this kernel.

Again, just an observation because I hate saying anything "negative" about the fantastic work that devs do.
[Nexus 4 Original Android Development] PJcastaldo:
B.s.
[Nexus 4 Original Android Development] Andrew025:
This is on a fresh ROM flash and I flashed b6 a few hours after boot. I expect it to be better tomorrow.

Not sure why it's listing phone calls so high though.
[Nexus 4 Original Android Development] FrozenLord:
I'm currently using the latest beta (16b6) and am experiencing strange behavior when using WhatsApp or other apps.

The device will randomly freeze and needs to be rebooted.

However, I have no clue as to why it does this or when - sometimes it takes several hours and it might freeze after 10 minutes.

I've ruled out overclocking and undervolting and think that either my phone has some issues or that there might be something wrong with this kernel.

Could you please help me out?

I've gathered this through Logcat Extreme

My log basically gets flooded with those denied boostpulse requests.

Could you please tell me how to fix this?

I'm running Carbon nightly 18/6, but had similar problems on earlier nightlies and on Paranoid as well...
[Nexus 4 Original Android Development] Ace42:
Do you have the issue where your deice shuts off completely or the power button cannot wake, so you have to hold it to reboot?
[Nexus 4 Original Android Development] FrozenLord:
Neither.

Most of the time it freezes during usage (screen on, me poking around on the touchscrewn) and restarts on its own after some seconds of frozen awesomeness.

Today, while playing a song from Spotify, it did no longer respond to any input (neither touchscreen nor power button) and didn't refresh the screen but kept on playing the playlist just fine.

Everything was back to normal after a power cycle...
[Nexus 4 Original Android Development] PJcastaldo:
That sounds like what happens when the frequency is too high for your chip set or the voltage is too low for it.. Not saying that's your issue just that it sounds that way..
[Nexus 4 Original Android Development] rmead01:
This has happened to me a number of times using this kernel, stock voltages and recommended settings. Still haven't figured out what it is
[Nexus 4 Original Android Development] 350d:
CPU temp is hot on 16b6 than b5..., 3~5 degrees higher...

( 3 days experience, same phone, same status).

Tapatalk via nexus 4.
[Nexus 4 Original Android Development] NYZack:
I was having similar grief, and I was advised not to have C2 enabled under SOC. Once I disabled that, I've had no more instability (granted, it's only been 24 hours).
[Nexus 4 Original Android Development] Ace42:
Can you guys they disabling C3 and C2 and see if you get any more reboots?
[Nexus 4 Original Android Development] ponczoszek:
hmm one of my apps locked processor at 1.8 ghz for 4.5 h ( while it was in my pocket). It was media server or something like that, never happened to me before... drain was unbelievable. I've changed this most fluid kernel to something slower and cooler (temp) and I'm patiently waiting for next beta release.

edit:

stock settings of the kernel, only uv'ed to 725uv at 162 mhz and so on
[Nexus 4 Original Android Development] yopet:
Wtf just happened?

I am using the kernel for 3 days and I have set the parameters according to the instructions in the first posts of this thread. In the meantime I realized that sleeps higher than C0 are causing the phone to reboot. It is not a "normal" reboot however, it's some kind of boot loop. I still have to turn it off and on by holding the power button.

I saw here people mentioning similar behavior and that the remediation would be to turn-off certain sleep states. For me, not a problem. Just to see how the device behaves, I turned off C1, C2 and C3 and turned off also the option to activate it on boot. If I'm not mistaken, that pretty much sets the SoC state to stock. Right? OK.

I also stopped trying to undervolt the phone, to check if the instabilities were gone. They seemed to be gone. That's why I have undervolted the phone for 100mV. The phone worked properly several hours while I have been using it occasionally.

Yesterday I have let my phone to discharge down to 6%, before I placed it on charger in the evening. The phone has been taken of the charger (still undervolted) about 3 hours before I went to bed. I used it for half an hour during that time period.

This morning (7 hours after I went to sleep, and 10 hours after the phone has been fully charged) I looked at the phone and saw that it doesn't respond (only yellow/white led was blinking; the rest of the screen dead). I had to keep the power button long enough to make it reboot. What shocked me was that the battery level was at 32%!!! I tried to find out what happened, but no last_kmsg exists in the proc directory.

Please take a look at the attached image and advise me or give me a hint what in the hell could have happened?!? Wtf is that drop in the battery capacity doing there? Are there any tools (for troubleshooting, debugging, or any thing similar) I could use to have any useful traceable data if this happens again?

I intend not to touch undervolting for some time; to exclude the possibility that this happened because of it. Other than that, I don't have ideas.

BTW, I am using kernel from the first post of this thread mako-jb-kernel-015m.zip.

Thank you very much in advance!
[Nexus 4 Original Android Development] kwerdenker:
You said it yourself: it's an app problem, not a kernel problem.

Mediaserver is androids media library (music, videos, pictures) and it periodically or on change scans your memory devices for new content. Sometimes bad formatted content can throw it into a loop and thus never let the device sleep. In most cases it's enough to wipe mediaserver's data and let it run again to get rid of the problem. If it persists you should check the media on your memory devices if something got corrupted.
[Nexus 4 Original Android Development] pixiebob:
i read lot of complaint about cpu high temperature. with beta 6 i don't have any issue about that, and no reboot.when watching movie my cpu is less hot than if i use franco kernel. c0,c1,c2 enabled. i use this settings so that's maybe the reason.

governor: ondemand

up_threshold:99

sampling_rate: 100000

min_freq:384mhz

max:1.24ghz

eco_mode_active:1

intelli_plug_active:1

vdd_levels:-50000

max_gpuclk:200mhz

optimal_freq:384000

sync_freq:384000
[Nexus 4 Original Android Development] italia0101:
Are you getting reboots on c2 ? I was :(

Also you compared to Franco but from your settings youve under clocked majorally ... CPU and GPU and only 2 cores .... Did you give Franco the same settings ..
[Nexus 4 Original Android Development] pixiebob:
no, with franco it's not the same hotplug so eco_mode_active and intelli_plug_active not exist.

with franco i use this settings for max battery savings:

echo 99 > /sys/devices/virtual/misc/mako_hotplug_control/first_level

other settings are same.i like to switch between these two 2 kernel each time updating :D

edit: i always use C2 , don't remenber to have reboot ;)
[Nexus 4 Original Android Development] italia0101:
Ok thanks for the input :)
[Nexus 4 Original Android Development] buster041284:
i get reboot's with c2 but some how its not rebooting with them settings so far:good:
[Nexus 4 Original Android Development] pixiebob:
good to hear.

if it's good for me it's good for you too ;)
[Nexus 4 Original Android Development] willybarca:
c2 stutters music playback big time, back to c3 and its all good now
[Nexus 4 Original Android Development] FrozenLord:
I don't know yet if it's too early to say, but so far the phone didn't reboot.

So maybe there is something wrong with the implementation of C3 and C2 states?

Edit: 27 hours without a random reboot / freeze and still counting.

Edit: 33 hours without random crazyness, so I guess that C2 is in fact the culprit.
[Nexus 4 Original Android Development] Ace42:
It was okay when they were first implemented, but now they're buggy for whatever reason. Anyway disabling them shouldn't do too much harm to battery life.
[Nexus 4 Original Android Development] brunini:
Here i don't have any problem with C0, C1 and C3.

---------- Post added at 11:40 AM ---------- Previous post was at 11:34 AM ----------

Sometimes my Bluetooth can't turn on unless I do a reboot, but I don't know why this issue happen.
[Nexus 4 Original Android Development] cocchiararo:
I bet that is an ANDROID issue that has been there since nexus 1 times...

I had it on that phone, and on EVERY phone i had afterwards (Nexus One, Galaxy S1, HTC Inspire, Galaxy S2, Galaxy Nexus and now on the Nexus 4).

I had profiles for auto turning bt on and off on many conditions, but i eventually decided to leave it ON all the time.

It's like after "x" on/off cicles something gets borked. Or maybe after "x" connect/disconect cicles, if you turn BT off, it gets borked too (might be unrelated to on/off, but once it triggers, you can't turn it on if you disable it).

This happens on most official or unofficial roms or kernels for me.
[Nexus 4 Original Android Development] PJcastaldo:
I've had almost the same list of phone as you just listed.. And I can say I have never.. Nor do I now have Bluetooth issues.. Turn it on off connect disconnect never an issue..

Also xda app should have an unthanks button for when you thank on accident..
[Nexus 4 Original Android Development] NYZack:
I totally have that Bluetooth problem. After turning it on and off a few times, it won't go on without a reboot. No matter what kernel. Stock ROM.
[Nexus 4 Original Android Development] cocchiararo:
How often do you reboot ?

How often did/do you turn bt on/off and/or connect/disconect ?

This does not arrise depending how often i did the connect/disconnect or on/off cycle before rebooting (because of BT issue or for another reason).

In any case, it was never a kernel issue for me.

ps: I had the milestone before the Nexus One, don't remember having this issue on that phone, but i did not have tasker either :P

You could try leaving it on for a few days (connecting and disconnecting whatever your bt device is), and then try turning it off and on again. The only time i tried that on my N4, the bug appeared.
[Nexus 4 Original Android Development] XxVcVxX:
Where is this reset kernel?
[Nexus 4 Original Android Development] beats4x:
After a few days use, I'm seeing activity on higher frequencies, with snake charmer and eco mode on. Set to 1512-162, seeing activity at 1836. If you need any more info, just let me know
[Nexus 4 Original Android Development] njankit:
Officer, this "reset kernel" was last seen hanging out with the "op". You may Ctrl-F him there :angel:
[Nexus 4 Original Android Development] notbrodie:
the phone uses 1836 on bootup, before snakecharmer activates. how much time/percentage is being spent at that freq?
[Nexus 4 Original Android Development] XxVcVxX:
I'm on the xda app and I don't see the download link O.o
[Nexus 4 Original Android Development] njankit:
There you go http://faux.androidro.ms/mako/mako_422_reset_kernel.zip :highfive:
[Nexus 4 Original Android Development] beats4x:
Yeah I read that, but its well over 5 minutes, that's what's throwing me off
[Nexus 4 Original Android Development] .A.J.:
Faux,

On16b6 the GPU clock resets to 487 MHz on boot despite my setting (400). Also when trying to charge while powered off, the phone remains on the static charge screen without ever going to the animated charge screen & then the screen turning off like it usually would.

Aside from these 2 things the beta is working pretty well for me.
[Nexus 4 Original Android Development] xsrcivic:
I can confirm the same problem with GPU clock.
[Nexus 4 Original Android Development] brunini:
Here the same bug with the GPU Clock.
[Nexus 4 Original Android Development] meangreenie:
Edit.. Delete
[Nexus 4 Original Android Development] wera750:
Couldn't help but notice the update to Fauxcock.... Changelog says added support for simple gpu governor... New beta incoming? :D
[Nexus 4 Original Android Development] jassycliq:
Last time I checked fauxs kernel had

128, 200, 400, 487
[Nexus 4 Original Android Development] meangreenie:
Woops, I'll edit my post.
[Nexus 4 Original Android Development] yopet:
I would appreciate if someone could help me.

It happened again to me to have the phone in a semi-dead state. It is not rebooted but it is acting like it is turned-off. I have to hold the power button for many seconds before I manage to turn it on by pressing the power button again.

I can not afford to have unreliable phone at the moment. Since I am currently at version 15, could you please help me by confirming or suggesting otherwise, which steps should I take for the following two scenarios?

a) To upgrade to version 16b6, is it enough just to simply flash the zip over my current installation or should I go through cache/dalvik cache wiping? Is it maybe also needed to deal with kernel reset (or something similar, mentioned in the previous posts)?

b) If the phone continues to hang, I will have to switch back to stock. How can I go back to stock kernel (ROM reflashing is not an option at this moment)? I know that there are files in the first post of this thread, I just need to ask for a simple and short instructions. Please...

Thank you very much!
[Nexus 4 Original Android Development] FrozenLord:
Have you installed any custom ROM?

I used the mainline of version 15 for several days and never had any semi-dead states.

Well, it did reboot randomly but never turned dead...

So my guess is that you are either using faulty settings (too much oc/uv?) or you have a faulty custom ROM installed.

For exactly those reasons I am not sure that flashing the latest beta will stop those semi-dead states.

But to answer your question:

I usually flash the new kernel and, while still in recovery, wipe Dalvik and cache (not data!), and that's it.

If you would like to return to the standard kernel, then flash the reset kernel from the op - AFAIK it is exactly what you want.

(And do a Dalvik+cache wipe afterwards)
[Nexus 4 Original Android Development] faux123:
Kernel 016 is official!

https://plus.google.com/u/0/109078966818501160423/posts/diPqz8LCQWJ

Enjoy!
[Nexus 4 Original Android Development] zimphishmonger:
What is this simple gpu gov?
[Nexus 4 Original Android Development] KerryWood34:
Its like turbo boost for the GPU if i understood faux's g+ post correctly.
[Nexus 4 Original Android Development] kwerdenker:
It's a new governor for the gpu frequency scaling. It will allow a more fine grained control over how the gpu scales up and down then the previous ones. This means either more performance or more battery savings :thumbup:

Sent from my secret moonbase via space carrier pigeons
[Nexus 4 Original Android Development] sMtt:
Is simple gpu gov is a new governor or optimised version of an existing gpu governor? Because I couldn't find it in either fauxclock or trickster. I still see only ondemand and performance governors.
[Nexus 4 Original Android Development] faux123:
update fauxclock and load the latest official release.
[Nexus 4 Original Android Development] kara mustafa:
If I have now franco, I need to:

1. Format system.

2. Flash CM 10.1

3. Flash faux kernel ?

Everything shoud be fine then?
[Nexus 4 Original Android Development] 0.0:
Flash faux reset kernel then faux's kernel. You're good to go :good:

Edit: or you can flash a cm nightly, then the faux kernel

Sent from my Nexus 4
[Nexus 4 Original Android Development] aldyu:
This should be fine. No need to flash the reset kernel.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ponczoszek:
personally I find this kernel a little worse then 16b6 and it's choppier in games (zen HD pinball for ex. ) Just to mention I'm using same settings like before. To set the kernel i use trickster mod.
[Nexus 4 Original Android Development] italia0101:
Have you set the GPU to 600?
[Nexus 4 Original Android Development] ponczoszek:
yes ondemand at 600
[Nexus 4 Original Android Development] italia0101:
Use the new simple gov ?
[Nexus 4 Original Android Development] ponczoszek:
trickster doesn't support simple gov atm. and afaik ondemand should give the best performance ( not talking about battery)
[Nexus 4 Original Android Development] italia0101:
I'm just wondering if using on demand is causing it to use 600mhz too much and therefore causing throttle and downclock .... =slow
[Nexus 4 Original Android Development] Joloxx9:
I have 16b6 latest faux control and still see only ondemand and performance in GPU, latest aokp nightly

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] casonswag:
Cause you still on the beta update it
[Nexus 4 Original Android Development] ponczoszek:
perhaps u are right, I don't know how fast it's downclocking and at what frequency it's getting this choppy...
[Nexus 4 Original Android Development] Joloxx9:
Lol I didnt notice that there is new release

Wysłane z mojego Nexus 4 za pomocą Tapatalk 4
[Nexus 4 Original Android Development] hughfollett:
Don't quote the whole op please :)
[Nexus 4 Original Android Development] italia0101:
I haven't actually tried out the GPU over clock to 600mhz yet .. Is anyone noticing a difference ?
[Nexus 4 Original Android Development] giajp:
sorry, where is the download for the 16 release? thank u
[Nexus 4 Original Android Development] alen1901:
Damn, edit your post and delete that quote. Never quote whole OP!

Sent from Sparkling Nexus 4
[Nexus 4 Original Android Development] Tylog:
Tapatalk Nexus 4

---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------

In the thread opener, page 1 post 1 :)

Tapatalk Nexus 4
[Nexus 4 Original Android Development] UgoBoss:
Can someone tell us more explanations on simple GPU governor please ?

Thanks :)
[Nexus 4 Original Android Development] italia0101:
I just use the faux app
[Nexus 4 Original Android Development] 350d:
Hi, I got this when I launch NFS most wanted on nexus 4.

Rom: unofficial AOKP (bigxie)

Kernel: 16tbm

Intellidemand (gov as OP‘s 1st post)

Max:1512

Min:162

-100mV

GPU Simple Governor 600 mhz

Laziness:6

Ram Threshold:4

so,???

Tapatalk via nexus 4.
[Nexus 4 Original Android Development] clsmn:
Mh got the same as i activated the c2 on soc. Did a normal reboot then
[Nexus 4 Original Android Development] 350d:
C2 is off, always keep c0,c1,c3 on…

Second time, got in that game successfully, but quality is poor! Please check the sky…

Tapatalk via nexus 4.
[Nexus 4 Original Android Development] STIawdFTW:
Ahh my bad that's awesome :).

---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------

I'm using 2048.
[Nexus 4 Original Android Development] remydlc:
i had the last beta with the recommended settigns, and unplugged my phone and 4 hours later it only used 2 percent. really? .5% per hour? that's insane. First time i see that in any phone!!!! you are the man Faux!!!

my other phone, SG3 ATT, in the same time, used 9%, just to give you an idea.
[Nexus 4 Original Android Development] IAmAN00bie:
Performance is great. Those settings are actually Faux's recommended settings on his Google + page. Little to no noticeable heat generation either.
[Nexus 4 Original Android Development] Webstarr:
Sorry if this is a dumb question but what are you referring to for eco mode and snake charmer?

EDIT: Nevermind!!! didn't update to b5

Also where on his google+ page did you find his recommended settings?
[Nexus 4 Original Android Development] STIawdFTW:
Enable intellidemand for your governor under CPU Control and turn off mpdecision and turn on snake charmer right below mpdecision. Then go to intellidemand governor control and turn on Eco mode its at the bottom of the screen.

---------- Post added at 10:00 AM ---------- Previous post was at 09:57 AM ----------

You got it now?

Heres the link to the google page.

https://plus.google.com/u/0/109078966818501160423/posts/QKJi9Ypxw8b
[Nexus 4 Original Android Development] MatAuc12:
What is that theme? Looks fantastic.