yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] n82k:
Hey faux, I just have a question not sure how it fits in, but is it possible through an app like faux clock to have like profiles for the settings? I.e. when I'm on the charge I'm all out performance but when I take it off sometimes forget to change the settings back to battery-centric settings. I would definitely pay another 2-3$ for an in-app purchase with that feature. Thanks for the great kernel and all of your hard work.
[Nexus 4 Original Android Development] bfspider:
Faux, What's the deal with beta 3 not showing up in the app? Thanks.

Sent from my Glitter Phone 4
[Nexus 4 Original Android Development] Locksmith81:
Here you go homeboy..... One page back
[Nexus 4 Original Android Development] bfspider:
So, I gotta dig and follow someone's profile just to stay up to date. Makes sense! :silly:
[Nexus 4 Original Android Development] RaveOnSRV:
Hahah, just gotta trust Faux's decision. Right after he posted up the beta, some people reported problems with their screen locking. In fact, I experienced it myself, so I ended up re-flashing to 003_r2.
[Nexus 4 Original Android Development] bfspider:
True. However, that is what the beta is for! :)

I think there is even disclaimer on the first or second post...
[Nexus 4 Original Android Development] Locksmith81:
What's even sillier is how easy it was to search and find his G+ account... About the same time it takes you to post that.... You could've found it and flashed it already :p

It's 2013 and a new technology called the "internet"... you should have a look see... You may come to like it..maybe

Sent from planet Common Sense
[Nexus 4 Original Android Development] aSquard:
New beta 04 available in the app... (I hope its new and I'm not just slow...)

Enlightened with Paranoid Android on the Nexus 4 and XDA Premium
[Nexus 4 Original Android Development] jacklebott:
It's new alright, not even on his G+! :p
[Nexus 4 Original Android Development] Goog1e Phone:
are people having issues with version 003_r2 or version 004_r2? i want the most stable release, since i dont crack flash often...any thoughts? i'm on xylon's rom 4.1 and it came with faux's kernal, but i was having data issues so i went back to stock kernal but still running xylons. i dont remember which kernal version was put in xylon's rom so i dont want to repeat it. any help would be appreciated. thanks!
[Nexus 4 Original Android Development] jacklebott:
v004b4 is working fine for me (though I don't use sweep2wake)
[Nexus 4 Original Android Development] bfspider:
I already found it and flashed it already before I even posted my question.

What is silly is that I have to pay attention and read stuff out side of _this_ community and forum to keep up to date of what is going on when the link and change long can put here. What's silly is that there is an awesome app that tells you when there is a new update it wasn't even used!

My question was a honest question and however silly you find it, is on your own accord. Also, my question was directed at faux and not you or your silly ego. However, since you're an awesome forum warrior and know about these so called "internets" in the year 2013, you would have the reading comprehension to understand that.

Good day to you.
[Nexus 4 Original Android Development] faux123:
Beta 03 was HIGHLY experimental. It had Linux 3.8+ patches for Power Awareness scheduling changes. I didn't want to make it a wide beta release because it could blow up :fingers-crossed:

It was NOT a game of hide and seek, it was done on purpose to limit the number of people loading it.
[Nexus 4 Original Android Development] kwerdenker:
Edit: ignore this post
[Nexus 4 Original Android Development] Zanr Zij:
For normal usage, 004 beta 3 seem very good

Sent from my Nexus 4
[Nexus 4 Original Android Development] Tweezydak1d:
What's a good global uv setting people are using. I set mine to 200 and it was ok for a while then I stopped receiving txt measages
[Nexus 4 Original Android Development] JNewms:
You can't use your phone to tether to Xbox. It can't handle the amount if data needed. You won't be successful with any kernel for that

Sent from my Nexus 4 using Xparent Red Tapatalk 2
[Nexus 4 Original Android Development] jacklebott:
Other peoples' UV settings are irrelevant. Each processor is vastly different, even those with the same binning level. You have to find your own stable levels
[Nexus 4 Original Android Development] nexicon:
Lord, there is so much kernel porn going on this thread...it's making me sweat and my head hurt!

Sent from my Nexus 4
[Nexus 4 Original Android Development] Luk_Sch:
Battery with 4b3 has improved, but Android OS eats ~30%.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] pixiebob:
s2w works great in the last beta, cool :)
[Nexus 4 Original Android Development] expertzero1:
Beta 4 is out fyi
[Nexus 4 Original Android Development] jacklebott:
It seems that setting LMF Max Freq by script or by your app works now, but what's weird is that re-entering your app and going to the governor tab after changing the value sets it back to 1512MHz. Reinstalling your app seems to have fixed it for now, though that previously wouldn't fix it
[Nexus 4 Original Android Development] Z-Man™:
Lol I've done it many a time.
[Nexus 4 Original Android Development] Ace42:
Probably just a display issue, it will show 1.5 sometimes but, its solely cosmetic.
[Nexus 4 Original Android Development] jacklebott:
Not a display issue. 100% positive of that, as I check the actual file that gets changed

But anyway, it's working now like I said
[Nexus 4 Original Android Development] droidmeup:
Thanks for the app update :)
[Nexus 4 Original Android Development] ock:
Does beta 04 have the Power Awareness patches?
[Nexus 4 Original Android Development] superleeds27:
Anyone know the changes in Beta 4?
[Nexus 4 Original Android Development] MontAlbert:
Not sure whether it's the update to the app or the new beta kernel but now many of my settings in the app won't stick. Especially sweep2wake. I got it to stick using the sweep2wake widget from the play store though.

And yes I am on supersu.
[Nexus 4 Original Android Development] teh_lorax:
Just check his G+ profile...

https://plus.google.com/u/0/109078966818501160423/posts/E5JWSpJrUdB
[Nexus 4 Original Android Development] Galactic2:
I don't know if this is a ROM issue or a Kernel issue... but my phone has an ever so slight blueish hue. It's very subtle, my white and greys especially have a bluish tint.

Ive tried using the FAUX123 app to tone down the blue, but the settings won't stick....
[Nexus 4 Original Android Development] Zanr Zij:
I face same problem like you. After some test, I manage the color better. You should try:

Red: 242

Green: 250

Blue: 255

You also change slightly Red and Green upon your screen!

Sent from my Nexus 4
[Nexus 4 Original Android Development] dispatch:
Happened again, same circumstance: phone on WIFI, left house and WIFI, went to stream music via Subsonic on mobile data, data drop/reconnects until I rebooted. I did get a DMESG log this time. :)

http://pastebin.com/b41yZQ1R

still on 4b2
[Nexus 4 Original Android Development] Stryder5:
I think the latest beta (4) reverts some of the changes that caused data drops. Try checking it out to see if it helps.
[Nexus 4 Original Android Development] dispatch:
Mos def, just posting a log in case it helps Faux.
[Nexus 4 Original Android Development] kwerdenker:
I had the data stall problem with 004b4 today and pulled dmesg, logcat and logcat -b radio.

From skimming the logs, I can't really say what the problem is. Since this problem of data drops also seems to happen on stock systems (see undercovers thread) I'm beginning to suspect this might be a radio (firmware) related problem. I just can't pinpoint anything in the logs to support that claim :confused:
[Nexus 4 Original Android Development] Mash87:
same for me. If I exit the app via the bag button I'll lose my UV settings after a couple of minutes, having the app running in the backround keeps the settings in place.
[Nexus 4 Original Android Development] lookitzjohnny:
Best battery life I've had with this phone since released. Running mako 4 beta 003. Almost 2 days on 1 charge with 4 hrs 30min screen on time. Will post screen shot when i get to a computer.
[Nexus 4 Original Android Development] drdrewdown:
we believe you...
[Nexus 4 Original Android Development] lookitzjohnny:
oh do you really? ;) you sound very... very facinated!
[Nexus 4 Original Android Development] Hung0702:
So faux, big rumor going around that needs a little background so I'll start there.

I've been experiencing 3G data drops, as have a good number of users. I've verified that my apn settings are correct, both with AT&T and on these forums. I can't recall if I experienced them on stock everything and it's a tad troublesome for me to revert just to check.

Now, word on the street is that every kernel dev adopted some commits long ago (regarding the radio or data, for battery conservation) and that's messing with the 3G data connection for a small but unfortunate number of users. As chance would have it, I'm one of those users :(

FYI, CM has recently reverted those changes, and apparently Motley kernel never implemented them. However, I love Paranoid Android and faux kernel too much to give anyone else a second chance and also I'm a bit lazy.

All I'm asking for is that you could upload a 004bX kernel that has completely stock treatment of the radio, data, and anything related to it. I would really like to determine whether or not that rumor is accurate or not, otherwise I'll get a replacement.

Thanks a ton for your time and efforts! I understand if this request is simply too convenient for you.
[Nexus 4 Original Android Development] drewtang:
Haven't had a full cycle on beta 4 yet so can't give a full report, but she sleeps well :D
[Nexus 4 Original Android Development] lookitzjohnny:
5hrs screen off and didnt lost 1%, air plane mode? i sleep over night lost maybe 4-5%
[Nexus 4 Original Android Development] expertzero1:
The changes were reverted. Check the last few post for info out his Google plus page
[Nexus 4 Original Android Development] linelock:
From what I've read neither the 003r2 or 004b4 kernels include those patches.
[Nexus 4 Original Android Development] drdrewdown:
about to test data connection functionality here shortly (b4r4) & i'm seeing a decent wakelock from msm_hsic so yea it appears those patches were reverted successfully. wish we could find a happy medium, no wakelock & functioning data
[Nexus 4 Original Android Development] drewtang:
Haven't had a full cycle on beta 4 yet so can't give a full report, but she sleeps well :D

View attachment 1627986
[Nexus 4 Original Android Development] jassycliq:
Im guessing the build.prop line didn't fix anything for you?
[Nexus 4 Original Android Development] droidmeup:
Was using Cm10.1 7th with 003m_r2 and 004b_4 and was getting crazy Msm_hsic. Now I updated to cm 8th nightly and using 004b_4 and that wakelock is now tamed.
[Nexus 4 Original Android Development] Treatcon:
004b04 is working GREAT! Best kernel thus far. It's speedy and responsive.
[Nexus 4 Original Android Development] Zanr Zij:
My battery life with 004 beta 3

6h 30mins screen on after 1 day usage. Mixed 3G + Wifi. Low brightness ( enough ) cause almost inside house/office

Seem best battery life ever with N4.

Sent from my Nexus 4
[Nexus 4 Original Android Development] superleeds27:
How!?
[Nexus 4 Original Android Development] Zanr Zij:
How what? :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] superleeds27:
Get such god battery? Im using pretty good settings but getting nowhere near that!
[Nexus 4 Original Android Development] yym789:
Same as me. My nexus 4 dead yesterday after flash 005.img when it was running benchmark.

You only check --if you don't plug phone into USB cable and nexus4 can boot into fastboot mode ( volu down + power), that means you may save your phone. if it can not power on to fastboot mode without plug phone into USB cable, I think you know this is Physical damage on your phone. (No Battery Support)

I have used other kernel for 2 days. I tested many times benchmark just OC 1.73G without any problems.

Maybe Nexus 4 MAX safe OC is 1.73G, or Maybe this beta version has some problems and kill nexus4 (check page 9)

---------- Post added at 04:50 AM ---------- Previous post was at 04:43 AM ----------

yes, OC 1.83G and my nexus 4 dead.

If you want OC, please use other kernel. or you never try 1.83G, maybe 1.728 is max safe OC for Nexus 4.
[Nexus 4 Original Android Development] Logi_Ca1:
Interesting that OC killed the device. I thought that thermal throttling was supposed to protect the SoC from damage??
[Nexus 4 Original Android Development] sarni84:
No one knows for sure could have been a number of things. U know? Can't say it is that for sure
[Nexus 4 Original Android Development] mprziv:
If you get the red light, just connect via a USB and press power. The phone will turn on.
[Nexus 4 Original Android Development] sarni84:
U don't think I tryed that??? Lol a million times?
[Nexus 4 Original Android Development] mprziv:
It worked for me a few times. It was plugging it in and a press and hold power. Them the phone will power cycle. At least this is what worked for me when my N4 locked up on the OC kernel during benchmarks.
[Nexus 4 Original Android Development] yym789:
impossible. Under that condition, vol down + power go into fastboot mode and vol up + power go into "Download mode".

If you want try this situation, you just falsh 005 version and OC 1.83G run benchmark 3 times. You will get that. :laugh:

Just a joke, please never try it.

---------- Post added at 06:07 AM ---------- Previous post was at 05:57 AM ----------

You just "N4 locked up on the OC kernel during benchmarks", but for us ---N4 auto shutdown on the OC kernel during benchmarks and it never power on again without USB cable.
[Nexus 4 Original Android Development] Beretta93:
I don't give a **** about Google. They have billions.
[Nexus 4 Original Android Development] Shaky156:
Its funny how noobs are damaging their own devices and blaming others for it, grow the f%&* up n accept responsibility, YOU broke it end of. Buy another one n dont make stupid mistakes or quit complaining
[Nexus 4 Original Android Development] benjamin.j.goodwin:
Guys, I ran this and many others have for days. Read the thread before flashing. It's clear that OC'ing it or running a benchmark whilst OC'ing is causing some issue as that appears to be when there is an issue. I am not saying this is a definitive reason but it seems to be the most common symptom. You don't need to install a kernel and start running benchmarks all the time. It means jack ****, just bloody use it and if it feels quicker and appears so then it properly is. Just like if the battery life seems to last longer, chances are it is.

I personally UV'd mine as this device doesn't need OC'ing and didn't even bother with benchmarks. I don't use a phone to see how it benchmarks I use it to call, text, network and sometimes play games and shot pictures. If it does these things smoother on a different kernel then I would say that it's working better.

The device isn't easy to come by so why the hell would you not pay a little more attention.
[Nexus 4 Original Android Development] kabauterman:
can someone explain me why every Custom Kernel I've tried is so much slower then the Stock Kernel?

I'd run different benchmarks to compare and still the Stock Kernel is the fastest in the Benchmarks, even with this Kernel in OC Version it makes no difference, still slower than stock!

can someone explain this?

And another question... this Kernel have UV? But how to use it, SetCPU doesn't show it and I really don't want another 'Kernelapp' on my Phone.
[Nexus 4 Original Android Development] nic85:
question about color control....

default colors are 100% 100% 100%? so we can only decrase them? :crying: no possibility to have more vivid colors?
[Nexus 4 Original Android Development] Antzor:
I'm assuming that later on there will probably be more adjustments as well, gamma for example. (Which I assume will likely make the biggest difference on this phone)
[Nexus 4 Original Android Development] mastibeta:
I think Gamma is exclusive to ammoled.
[Nexus 4 Original Android Development] ctfrommn:
You can adjust gamma on an LCD computer screen so it is technologically possible for sure.
[Nexus 4 Original Android Development] sarni84:
Who's complaining just looking out for the community and why does everybody have to be a noob? Lol nobody is blaming anybody I don't know where you got that laptop gangster smh..... it has happened to 5 people so far and it is going to happen to more people you watch only trying to get the word out to be careful
[Nexus 4 Original Android Development] faux123:
Gamma control is possible but will take some time to get it working. The gamma table isn't exposed to user space with the stock kernel source. I need to write a gamma interface for the kernel first, then I need to write the algorithm to adjust the gamma. This is a two step process, please be patient. I'm only by myself on this and I need some time to think about this and write the code for kernel and the app.
[Nexus 4 Original Android Development] faux123:
Regarding overclocking bricks, I feel bad for those who can't recover from the red led situation. It seemed the phone is designed right on the edge of instability. Overclocking + benchmarks seemed stressed some weak component within the phone causing permanent damage for some people. I have removed the overclocking versions from my servers to prevent other people from damaging their phones.

The phone manufacturer usually build their phones with some tolerance but not always, and also this is a first run devices, the quality control may be rushed due to initial demands.

My kernel source for CPU overclocking is available for all to examine. The code has been used on all my Qualcomm devices, this is the first time I've heard major issues with it.
[Nexus 4 Original Android Development] sarni84:
Faux I don't want u to go to that extreme I feel that if u flash the software you are responsible.... Right? But people should be aware this is happening and no one knows for sure exactly what it is for sure. I have been using 005 oc to 1.6 and have had no problems. Will I benchmark tho like last time no! That is when it happened. Benchmarks are stupid but cool to see what the phone can achieve. I think u should leave them up people just should not oc and bench because that seems as tho it did it. Like I said 005 for two days at 1.6 and things been great
[Nexus 4 Original Android Development] chlehqls:
So besides all the talk, is OCing currently broken for most people or are there people who are safely OC'd as a daily driver?

I don't care about OCing since it's a waste of potential battery life, but if the components are as cheap as you make it out to be, then I really blame Google for rushing these out but at the same time.
[Nexus 4 Original Android Development] malavi:
my thoughts...

tryin since release b4 and its more "responsive" for wakin up with S2W... :good: (some times I have to sweep twice, but it happens less than with other ver.)

But beta 3 was best kernel for battery ! :cool:
[Nexus 4 Original Android Development] Zanr Zij:
Yes! Real life usage :). When do not need, I change 3G to 2G + turn of data. The main reason for that very good screen on : low brightness + the way using. Café is a VNese news app can loads ( wifi ) and read later ( offline )

Sent from my Nexus 4
[Nexus 4 Original Android Development] DroidRC1:
Wow!
[Nexus 4 Original Android Development] drdrewdown:
it's hard to say, i used it yesterday successfully but since i've updated cm10 & the kernel so i'm without it now & b4r4 worked fine in my hour of playing ingress just now
[Nexus 4 Original Android Development] Hrithan2020:
Hi,

The kernel doesn't seem to be working with trickster mod. Basically the settings [such as UV, s2w enable] which I apply and set it to bootable values still don't stick when I reboot. Any idea what the issue could be? I tried searching and didn't find any indication that it doesn't work with trickster mod.

EDIT: The problem seems to be with excessive UVing? I had tried -175 mv all across the board. [having a "faster" binned cpu] which I think the kernel doesn't support?
[Nexus 4 Original Android Development] Hung0702:
Well then, it seems I'm SOL. Guess I'll have to get a replacement :(

Hope it's got the fast binning!
[Nexus 4 Original Android Development] Bluewall:
Alright i've tried many times, no way to UC to 1.35Ghz it's always bumped to 1.5Ghz no matter what
[Nexus 4 Original Android Development] Treatcon:
Usage so far on 004b04. No too shabby! :)
[Nexus 4 Original Android Development] SleemLDJ:
Had to go back from b3 to 003r2 coz of data drops.

But now with the revert in changes, might test out b4 too

Swagged out of my Paranoid NeXus⁴

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

Did you turn on "snake charmer" after setting the limits?

Swagged out of my Paranoid NeXus⁴
[Nexus 4 Original Android Development] disq:
I hit a reboot about 1 hour or so after switching to 004b04. I had the cpu undervolted -100mV, it was stable with 004b02 for a few days now.

After the kernel panic, I just set the undervolt to -50mV, will report if I have more issues (and then set it to 0 :) )

Kernel settings: The recommended settings "for battery", but clocked @ 1.512 ghz and with 1512000 LMF.

I also flashed today's CM nightly a few hours ago, it might be related. My previous nightly was the 31st December build.

Attached /proc/last_kmsg ("L1 / TLB Error detected on CPU 0!")
[Nexus 4 Original Android Development] basshamster:
No data loss today with beta4! :cool: :thumbup:
[Nexus 4 Original Android Development] smoki3:
Which Rom do you use

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Locksmith81:
Never had data loss with any kernel.. PA on TMO
[Nexus 4 Original Android Development] drdrewdown:
same here, working great
[Nexus 4 Original Android Development] faux123:
you got a memory error.. this is rare!

[ 1601.742285] L1 / TLB Error detected on CPU 0!

This is straight from CAF!

Certain CPU designs may be able to automatically recover from certain

kinds of L1 cache errors, even though the L1 cache itself may not

support error correction. These errors should not result in any kind

of corruption, but their presence is nevertheless an indication of

poor system health.
[Nexus 4 Original Android Development] dispatch:
Issue occurred just now on 4b4... This time I actually turned WIFI off instead of just walking out of range, using the XDA app. I did see the post a few pages back about it possibly happening across all kernels, but here is the dmesg log in case it's helpful.

http://pastebin.com/REzgyF5j
[Nexus 4 Original Android Development] warfexion:
Is UV really that effective for battery life? I just want somebodies opinion.
[Nexus 4 Original Android Development] faux123:
I don't see any data drop issues from your log. This time it may be a real radio issue rather than caused by kernel. When it was caused by kernel, there would be very specific errors pop up in the dmesg log, but yours is clean which means it wasn't caused by the kernel at all.
[Nexus 4 Original Android Development] Locksmith81:
Yes! It also seems to run cooler... Even while charging and streaming

FWIW... didn't know the word silly could mess someone's day.. :confused:

Sent from planet Common Sense
[Nexus 4 Original Android Development] jacklebott:
Dunno about battery life, but it helps massively with temperature
[Nexus 4 Original Android Development] undercover:
And subsequently with battery drain and overall battery life (doesn't degrade as quick).

Sent from my fridge. Make:LG Model:N4