yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] fallout0:
Just a quick question. I've got the Kernel Enhancement Project app running on my phone with Faux123 recommended settings. I noticed in the SuperSU logs that FauxClock asks for root permission every couple of hours and runs a huge script that sets up all the params again. Is it necessary to "set up" all the settings from FauxClock periodically?
[Nexus 4 Original Android Development] Bloodimirgr:
One Question, i see that Faux Clock and Fauxdisplay are pushing their color settings together, (although i havent set on boot on fauxclock) is there any way to just use one or should i put same colors on both ?
[Nexus 4 Original Android Development] 0.0:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Fauxclock will detect fauxdisplay and vice versa. For the display, the fauxdisplay will take precedence over the other app. You only have to change the colors in the display app

Sent from my Nexus 4
[Nexus 4 Original Android Development] xflowy:
AW: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

i own fauxclock and fauxdisplay. adjusted screen settings via fauxdisplay, set boot apply but the settings dont stick after rebooted. im on 007b1.

whats that?
[Nexus 4 Original Android Development] buster041284:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Sticking here I followed op steps
[Nexus 4 Original Android Development] karendar:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

You can use OTA if everything is stock (radio, kernel, ROM with no mods). After OTA is flashed, you have to flash back .33 radio
[Nexus 4 Original Android Development] Z-Man™:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

My settings stick but I have to turn the screen off and on a couple times after reboot maybe try that
[Nexus 4 Original Android Development] jhericurls:
I'm averaging 3% msm_hsic per 1 hour on mobile data? Good or bad?

Has the msm_hsic patched been applied to 007? I know that google have already applied some on 4.2.2 kernel.
[Nexus 4 Original Android Development] xflowy:
AW: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

and why is that. i mean, i paid for that app and getting such a thing working shouldnt be that hard. setting screen settings via fauxclock before always worked.
[Nexus 4 Original Android Development] nick34609:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Battery drain overnight is crazy good.
[Nexus 4 Original Android Development] farhanito:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Yeah.. Battery is good on wifi. On mobile, msm_hsic is sick.
[Nexus 4 Original Android Development] nick34609:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]
[Nexus 4 Original Android Development] azsl1326:
I am on the latest beta for 4.2.2 and noticed that my phone isn't going into deep sleep. Checking BBS, it says sns_periodic_wakelock is 81.2% of the wakelocks. I am assuming that this is why. Any one know what this is?
[Nexus 4 Original Android Development] Stryder5:
Check your partial wakelocks. Sounds like an app is keeping it awake. If you can't figure it out, take a log and post it in the BBS thread to see if someone there can assist you with it.
[Nexus 4 Original Android Development] Anrikus:
according to this threat you can choose between the following options.

Lockscreen widgets like "DashClock",

Live wallpaper or

Lockscreen replacements like "widget locker" who can cause that wakelock.

Still it seems the rootcause is unknown for the moment.
[Nexus 4 Original Android Development] Stryder5:
I have both live wallpaper and DashClock and don't get that wakelock.
[Nexus 4 Original Android Development] Bloodimirgr:
In my case Fauxclock ovrerides Fauxdisplay in a weird way, it boots normaly, colors are fine but when i turn it off/on. Then i got color mix everywhere ( i tried it with just lowering one color to check it - so i lowered blue and everything was awful - although in fauxdisplay everything is normal).

I used the same settings in both and works fine ( else it overides them or push them on top or something)

PS.

I dont have set on boot on fauxclock, only on fauxdisplay.
[Nexus 4 Original Android Development] DnickDominic:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

007b1 not up anymore;(
[Nexus 4 Original Android Development] kwerdenker:
This link still works for me http://faux.androidro.ms/mako/beta/mako-jb-kernel-007b01.zip
[Nexus 4 Original Android Development] xflowy:
AW: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

would be appropriate if faux says sth about that. i just found out, that also a couple of locks (without reboot) change my settings. this sucks. i paid for this app not for only using fauxclock again.
[Nexus 4 Original Android Development] azsl1326:
So, it looks like it was lightflow that was keeping it awake. I have disabled it and now the phone is getting deep sleep.

Thanks!
[Nexus 4 Original Android Development] Logi_Ca1:
Hi faux123, I'm just wondering, how do I go about lowering the minimum voltage threshold to below 800mv? Judging by how much time the CPU spends in 384mhz, it's a pity that we can't lower the voltage for 384mhz to below 800mv. :(
[Nexus 4 Original Android Development] DnickDominic:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Hm weird. It was hidden on the directory
[Nexus 4 Original Android Development] ghost_og:
Missing values above 119?

Faux,

I've been trying to make sense of how your display app interacts with the gamma interface. Using the stock Google values found here, it seems like your app uses hex values. Here is my understanding of how the app translates the values (I've ordered them according to the source code, not how they appear in your app):

0 [B]1 2 3 4 5 6 7 8 9[/B]
p_gamma_r_setting[10] = {0xD0, [B]0x40, 0x44, 0x76, 0x01, 0x00, 0x00, 0x30, 0x20, 0x01[/B]};
n_gamma_r_setting[10] = {0xD1, 0x40, 0x44, 0x76, 0x01, 0x00, 0x00, 0x30, 0x20, 0x01};
p_gamma_g_setting[10] = {0xD2, [B]0x40, 0x44, 0x76, 0x01, 0x00, 0x00, 0x30, 0x20, 0x01[/B]};
n_gamma_g_setting[10] = {0xD3, 0x40, 0x44, 0x76, 0x01, 0x00, 0x00, 0x30, 0x20, 0x01};
p_gamma_b_setting[10] = {0xD4, [B]0x20, 0x23, 0x74, 0x00, 0x1F, 0x10, 0x50, 0x33, 0x03[/B]};
n_gamma_b_setting[10] = {0xD5, 0x20, 0x23, 0x74, 0x00, 0x1F, 0x10, 0x50, 0x33, 0x03};

Gamma Fine

1. (0x40, 0x40, 0x20)

Gray 08~15: 0 0 0

Gray 16~23: 4 4 2

2. (0x44, 0x44, 0x23)

Gray24~31: 4 4 3

Gray32~39: 4 4 2

3. (0x76, 0x76, 0x74)

Gray 40~47: 6 6 4

Gray 48~55: 7 7 7

Gamma Grad

4. (0x01, 0x01, 0x00)

Grad Lower: 1 1 0

Grad Upper: 0 0 0

Gamma Amp 0

5. (0x00, 0x00, 0x1F)

RGB: 0 0 31

Gamma Amp 1

6. (0x00, 0x00, 0x10)

RGB: 0 0 16

Gamma Grad

7. (0x30, 0x30, 0x50)

Top Half 1: 0 0 0

Top Half 2: 3 3 5

8. (0x20, 0x20, 0x33)

Bottom Half 1: 0 0 3

Bottom Half 2: 2 2 3

9. (0x01, 0x01, 0x03)

Mid Point: 1 1 3

If this is the case, how can we enter values that go above 0x77 (119). From what I can tell, the naming system floating around for each of these columns is consistent with your table (i.e. whites, mids, blacks, contrast, brightness, grays). So when trying out values posted around the forums we hit a wall. I've seen blacks as high as 255 (0xFF), but the corresponding fields in your app (Gray 40~55) max out at 119 (0x77).

Is there a reason you placed limitations on these fields? I've been able to replicate others' settings to a degree, but the lack of hex values above 7 makes it hard to match them exactly.

P.S. I did notice the Gamma Amp 0 (Contrast?) and Gamma Amp1 (Brightness?) do go up to 31 (0x1F), but that seems to be the highest possible value.
[Nexus 4 Original Android Development] cbutters:
This works pretty good for those who like dark blacks...

With these settings I'm getting about 2.5 Grey, 2.0 red, 2.2 green, 2.1 blue, 2.4 yellow, 2.3 cyan 1.8 magenta.. this is about the closest I've seen to good gamma values on the colors and still pretty close grey gamma levels... (usually if the color gamma numbers are right around 2.2, the grey level suffers.) I think I'll run these settings for a while and see how it goes.

Edit: also... very little banding on these settings vs. the PA colors.
[Nexus 4 Original Android Development] anwedr:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Hi faux, this should be a proper last kmsg log. I received another random reboot. These reboots are becoming more frequent.

http://db.tt/BGS0LIq5 -- Kmsg

http://db.tt/LJogbS37 -- last kmsg
[Nexus 4 Original Android Development] faux123:
use beta 7 release 2
[Nexus 4 Original Android Development] faux123:
Yes, you have it decoded correctly. Franco's interface is completely wrong. many registers have maximum values (those can be found in my display app), when he expose them from 0~255, there will be HUGE jumps in the gamma curve and settings will not work properly.
[Nexus 4 Original Android Development] xflowy:
AW: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

@ faux. please a short statement on the issue mentioned a few posts before.
[Nexus 4 Original Android Development] granduke:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Does faux's 4.2.2 kernel retain swipe2wake?
[Nexus 4 Original Android Development] Ace42:
Yay 007b2 is out.
[Nexus 4 Original Android Development] expl0it4:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Sitting at 1day 15hours 30% left. 10 hours of that off wifi. Enhanced stock seems to be a winner.
[Nexus 4 Original Android Development] simms22:
francos interface is different, not wrong.

edit.. nevermind, francos interface is wrong.
[Nexus 4 Original Android Development] faux123:
Sigh... it is WRONG. It merges different registers into 1 and that's not how it works :( This is a pure technical discussion. I don't want to get into any flame wars. I simply stating the FACTS.... Ask other advanced users who knows about the interface and they will tell you the same thing.
[Nexus 4 Original Android Development] franciscofranco:
Yes, I think you're right, a user called oblivion been researching that and he came to the same conclusion as you did. Good job finding the values for yourself, I couldn't do that. In case someone thinks I'm being sarcastic, I'm not.
[Nexus 4 Original Android Development] simms22:
when youre right, youre right :angel:
[Nexus 4 Original Android Development] jhericurls:
Just installed 007b02.

I noticed that I can only use this kernel in eco mode, if not the CPU would spike like crazy when idle. This also happens when with motley kernel too. Don't know about others as I haven't used any other kernel for months.
[Nexus 4 Original Android Development] xflowy:
AW: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

which tool are u using man?
[Nexus 4 Original Android Development] ghost_og:
A few more questions...

Thanks for the clarification. Before buying your app I was adjusting these values with scripts. I've since been trying to port the numbers from molesarecoming's calibration thread, and then the ones from visceralpyche here and here to your app, but was unaware of the maximums.

But is there a reason for not being able to adjust values into the 8-F (8-15) ranges up to 0x77 (119)? This would mean there are corresponding gaps for each register up to the 119 (0x77) maximum: 56~63, 72~79, 88~95, 104~111. Do these values not get recognized?

I did notice the title for every other Gamma Fine field alludes to the 8-F values we can't input manually: Gray 8~15, Gray 24~31, Gray 40~47, but wasn't sure how exactly these relate to the other missing ranges.
[Nexus 4 Original Android Development] jhericurls:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

System Tuner Pro
[Nexus 4 Original Android Development] arvonn:
I'm on 007b1 - haven't tried 007b2 yet (installing shortly)

-but I'm getting PowerManagerServce.WirelessChargerDetector eating my batter to the tune of 2% per hour (on top of normal ~1% per hour everything telse)

I don't know if this is a Faux Problem - I'm thinking it is more a 4.2.2 problem..

But it started right after I got the Orb..

Anyone else having problems with Orb + this kernel?
[Nexus 4 Original Android Development] faux123:
The reason you can't use 0x8~0xf is pure hardware. The hardware has only 7 bit resolution. so anything higher is meaningless to them.

Software can have any range but it is the hardware that's the limiting factor.
[Nexus 4 Original Android Development] tyea:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

007b2+02/18 paranoid android

Working fine. Its nice to have touch to wake working on a 4.22 ROM. Thanks.

Occam, Tapatalk
[Nexus 4 Original Android Development] faux123:
Quick change log for 007 beta 2:

Tweaked Intelli_plug to work better with benchmark apps (artificial loads will now trigger > 2 core operations after certain thresholds)

added an experimental patch to remove idle balance... (jury is still out for this one... supposedly, huge core performance increase for certain benchmarks but it's hard to say in real life since benchmarks are by nature synthetic).
[Nexus 4 Original Android Development] ghost_og:
Why are Amp 0 and Amp 1 able to use the full range of values including 8-15 (0x08-0x0F) and 24-31 (0x18-0x1F)? Wouldn't these be meaningless? Not clear on why these two fields can accept those 8-F values, but others can't if the hardware is the limiting factor.

If it only applies to the value for the 1st digit after the 'x' (0x80-0xF0), then shouldn't we be able to use 8-F in the second position after the 'x' (0x#8-0x#F) like we are doing with Amp 0 and Amp 1?
[Nexus 4 Original Android Development] faux123:
The amp0/1 values are 5 bits 0~31. They are different from all other registers, and it was the reason I picked them for fauxclock if you look at the charts I drew. They have the MOST influence overall. all others are localized. Look at my Guitar String analogy.

http://xdaforums.com/showpost.php?p=38134041&postcount=666
[Nexus 4 Original Android Development] superleeds27:
Might hold out until B3, nothing in the changelog effects me really.

Cheers for the update though
[Nexus 4 Original Android Development] deezid:
Is the display app (or fauxclock) finally stable? I always had the problem that RGB changes were back to its defaults after a few minutes... :(
[Nexus 4 Original Android Development] faux123:
yes, it should be. Everything is working.. just turn screen on/off for settings and they will stick.
[Nexus 4 Original Android Development] Confused_Cheese:
I'm been using CM for a while now, but I wanted to try to sort the colours out on the screen. I've installed the latest 4.2.2 kernel and purchased FauxDisplay and have configured the colours nicely, but I've noticed after a reboot it takes ages for the cLock widget to load. It also seems to refuse to load any apps for maybe 30 seconds or so after its booted.

Is this normal? Flashed back the latest nightly kernel from CM and the delay is only about 2-3 seconds for the clock widget to load.
[Nexus 4 Original Android Development] xflowy:
AW: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

nope. as stated before. they do not stick for me either. they even change without a reboot.
[Nexus 4 Original Android Development] .A.J.:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Has anyone been able to back up their settings in the latest FauxClock and FauxDisplay apps?

Either mine just won't do it or the file is being stored somewhere besides where it always has been.

Mine says it backs then up but I can't actually find them anywhere whereas they used to be on the root of my SD card.

Any help is appreciated.
[Nexus 4 Original Android Development] El Nino1977:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

faux_xxx_backup.tar.gz

Saved to sd storage
[Nexus 4 Original Android Development] .A.J.:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Yeah, that's what I've always gotten in the past but now I get nothing. Can you, or anyone, please try moving that file somewhere else (a folder) and see if a new one is actually created when you click the backup settings button. I would greatly appreciate it.
[Nexus 4 Original Android Development] Girn:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Faux or anyone knowledgeable... What settings in gamma gradient or fine should br changed go bring down JUST cyan and yellow gamma?
[Nexus 4 Original Android Development] masterchung89:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

At first I was having the problem where they did not stick, but the values stuck after a restore and an on-off screen.
[Nexus 4 Original Android Development] arvonn:
I disabled 'Day Dream' and solved my own problem.

Be that a warning to ye - day dream runs the PowerManagerServce.WirelessChargerDetector kernel wakelock and prevents deepsleep.

I'm sorry if I implied in anyway that Faux was responsible.. 007b2 kernel is mighty fine! :)
[Nexus 4 Original Android Development] randomnoob83:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Only complaint is screen isn't as responsive should make screen more responsive
[Nexus 4 Original Android Development] Ace42:
http://xdaforums.com/showthread.php?t=2027476

Maybe use that one? Personally I don't see any issues, the N4 has zero-gap screen tech so it should be plenty responsive.
[Nexus 4 Original Android Development] anwedr:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

On 007b02 and received my first random reboot. Another last kmsg uploaded.:(

http://db.tt/LJogbS37
[Nexus 4 Original Android Development] mrimage:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Can someone share kernel reset zip
[Nexus 4 Original Android Development] faux123:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

I don't know what is going on with your setup. You keep timing out according to your logs. Meaning you have something holding the keeping the kernel busy. Maybe you should backup and nuke the ROM and start from scratch
[Nexus 4 Original Android Development] anwedr:
I certainly will after that comment.

BTW, am I doing this correctly?

- install PA3

- flash faux 007b02.

or is it;

-install PA3

-flash faux's reset kernel

-flash faux kernel?

I came from flashing 4.2.2 clean as per efrant's guide and proceeded with your kernel without a reset.
[Nexus 4 Original Android Development] droidmeup:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

PA3

Gapps

Wipe cache and davlik

Faux kernel

Sent from my Nexus 4
[Nexus 4 Original Android Development] .A.J.:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Please see above quotes. Thank you.

Stock 4.2.2 ROM

Faux stock enhanced kernel

Latest FauxClock & FauxDisplay.
[Nexus 4 Original Android Development] shankesh:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

I'm running rooted stock ROM and sick kernel 4.2.2 with secure boot.... can I install this kernel in my phone... Because in the boot loader it shows that I'm having secure boot image... will there be any problem with secure boot for installing this kernel

Sent from my Nexus 4
[Nexus 4 Original Android Development] faux123:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Take my reset kernel for 422, extract the boot.img and do 'fastboot flash boot boot.img', then you can use cwm to flash my latest beta.
[Nexus 4 Original Android Development] shankesh:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Thanks faux !!....
[Nexus 4 Original Android Development] brian88:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Hi, I intend to download your kernel for my phone but I cant see any link to download for 4.2.2, could you show me how to download it, thanks
[Nexus 4 Original Android Development] Kid_droid:
I am trying to get hold of the mainline 4.2.2 kernel but there no link to that any help on the latest this would be my first try of this kernel thanks. im runnning rootbox 4.2.2 right now.
[Nexus 4 Original Android Development] :
AW: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

It's under the beta kernels. Check the links in the first post
[Nexus 4 Original Android Development] CerB:
i have been looking and looking, only found 005 under beta
[Nexus 4 Original Android Development] danslecarton:
Did you use this link?
[Nexus 4 Original Android Development] Nathtech:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Thanks, I needed this as well.
[Nexus 4 Original Android Development] mkamal23:
Got 4 hours of screen time today which im pretty happy about on its first run on 007b2 and thats without messing around with any values. I just flashed it over the newest PA ROM. Yes... i was on WIfi for the most part, but still i thought that was impressive. The speed, responsiveness, and scrolling was all perfectly fine for me. I also bought the Nexus 4 Advanced Gamma control app which is working perfectly and all the values stick. Just wanted to say thanks.
[Nexus 4 Original Android Development] strapped365:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Was wondering if anyone else has seen this.

Fresh flash of paranoid android 3+ PA Gapps and faux 007b01 kernel.

Mpdecision-off

Snakecharmer-on

Governor-intellidemand

Max freq-1.3

Global undervolt -150mV

eMMC read ahead-2048

The problem I had yesterday was out of nowhere my phone shut down and would not boot back up at all. It would just stick on the boot animation. So I wiped cache and dalvik and it made it past the boot ani but after it optimized all my apps it stuck at starting applications.

The only 2 apps I had downloaded was fauxs apps, both would force close on every entry into the apps so I just chalked it.

My questions are, is it safe to shut cores down and step away from mpdecision? Did I botch setup?

I've been around android for a while now, and even have kernels and ROMs for other devices. But I have never had an issue like yesterday

Sent From a Freaked out Nexus 4
[Nexus 4 Original Android Development] droidmeup:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Its pretty safe. Ive never know anyone had this issue before. Perhaps do a proper clean install? Format everything except sd card.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Ace42:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

Significant battery drain over night in latest beta. Has anyone else experienced this? Went to bed with 90% woke up with 75%.
[Nexus 4 Original Android Development] strapped365:
Re: [Kernel] (version 006) Mako (UV Control/CPU/GPU OC/Hybrid Linux 3.4+) [Feb-16]

A proper clean install.......yeah that's what the whole fresh flash line meant. Like I said, I have kernels and ROMs for other devices, so none of this is new to me. Only the issues with both faux apps and the kernel.

Maybe faux should answer on what's safe and not safe as he is the kernel Dev.

Sent From a Freaked out Nexus 4