yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] notbrodie:
yes
[Nexus 4 Original Android Development] trathiang:
Same issue here.
[Nexus 4 Original Android Development] BYTeXperience:
[MENTION=3332811]faux123[/MENTION] I use 026 JVR with SlimBean 4.3 BUlLD1, but i encoured a problem. This days i have buyed a new charger from Energizer 2xUSB 2.1Amp,,, I have make one USB dedicated charging cable, soldering a resistor of 200ohm to the d+ / d- acording with the official documentation, but sometimes the phone is seeing the charger as USB Charging and other times as AC plugged, "capacity source: user defined, flow source: provided by Android kernel". Something is wrong because it is charging too slowly... 3.75hours... is not normal. Have something to do with the kernel from what i see the flow source is controled by the kernel? Please give me any advice, i have read houndred of pages but nothing regarding this issue. Any help will be apreciated.

L.E. This is how i make the USB dedicated charging cable (see European USB Charging Resistor figure) is the same as Battery Charging Specification Revision 1.1 from April 15, 2009.

More info: The charger have an output of 4.80v without any load and 4.75v with the phone connected and charging. The amp mesured is 2.1A like it's specified on the charger... nothing electrical from what i have tested...
[Nexus 4 Original Android Development] faux123:
Does it only happen with my kernel or does it happen with stock kernel as well? I didn't change anything except the FastCharge hack which is a simple change of value from 500mA to 1000mA.

Another possibility is a bad solder joint from your mod... the resistor is intermittently detected, so the kernel got confused by it...
[Nexus 4 Original Android Development] faux123:
Yes, there's a soft limit.
[Nexus 4 Original Android Development] G1ForFun:
Zip fails verification for me. Works fine on the previous nightly but not the latest.
[Nexus 4 Original Android Development] BYTeXperience:
It's not a bad soldering joint for sure... I have verified this first time when i conclude that is not charging as it suppose.

I have flashed SlimBean 4.3 Kernel now, but seem to be the same... Status is changeing from Charging to Discharging on "battery monitor widget", but on the info menu is figure as AC Charger... Maybe is this tool malfunction with the Nexus 4, can you suggest me another way to correctly control the flow of charging on our device?

It's hilarious, with the 2.1A charger most of the time battery flow is with negative sign -XX mA ... I have tryed a 500mA charger and it's fine with the same cable, have +180mA on Battery flow.
[Nexus 4 Original Android Development] mammenj:
Got a green screen using 26u with 1.726 oc and -75uv, everything else on default on PA 3.99 rc1.

Attached logs.
[Nexus 4 Original Android Development] faux123:
Not a software error. Probably too much oc and/or uv
[Nexus 4 Original Android Development] mammenj:
Probably, I have reduced to -50uv.

I had used -50 for few days with no issues, so going back to 50.
[Nexus 4 Original Android Development] :
[MENTION=3332811]faux123[/MENTION]

Do you intend to make a JLS version of your kernel?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Andre_Vitto:
JLS is same as JSS.. you can use jss versions on your JLS ROM..
[Nexus 4 Original Android Development] :
Didn't realize it wasn't that big of a change..

Sent from my Nexus 4
[Nexus 4 Original Android Development] mammenj:
Would below log indicate hardware issue? I havent applied any wifi fix, except using v26u kernel?

-------------------------------lastkmsg----------------------------------------------------------------------------

[59705.457062] wlan: [2874:E :HDD] wlan_suspend: Fail wlan suspend: not in IMPS/BMPS

[59705.457062] wlan: [2874:F :HDD] hddDevSuspendHdlr: Not able to suspend wlan

[59705.457092] dpm_run_callback(): platform_pm_suspend+0x0/0x54 returns -1

[59705.457092] PM: Device wcnss_wlan.0 failed to suspend: error -1
[Nexus 4 Original Android Development] ev!denz:
Does UV save a lot of battery? Dunno if it is worth it to test it.
[Nexus 4 Original Android Development] MuertoKo:
No, and it doesn't make the device cooler as many claim... BUT on N4 we can undervolt nearly any chip over -100mV, which is a damn lot... and 100% stable, so why not trying? I mean, I've neer been a fan of it, never used it, and now I am. Worth trying -100mV in case it does save battery or does help on device coolness in a perceptible way as long as you keep device 100% stable.

Always remember, a single reboot costs you more than what UV can save, that's for sure. So don't UV if you are risking your device to reboot, otherwise... it's worth the try, just in case it works :P

PS: Before anyone clearly states it does help, it does keep device cooler and so on I'd say "bring me some evidence". I tried myself on many devices yet to check UV, and even if I tried the most accurate test I could... well, results weren't stathistically significant, so nothing worth mentioning. "I feel my device cooler" it's NO evidence btw.
[Nexus 4 Original Android Development] kwerdenker:
Is physics a good enough evidence for you? ;) Plugged straight from Wikipedia, this is the formula for the power consumption of a CPU core:

P = C*V²*f (where C is capacitance, f is frequency and V is voltage)

As you can see voltage is a squared factor, so any reduction in it does have quite a significant impact. Using less energy means less waste heat produces thus keeping the chip cooler.

Now, if this impact is really noticeable in day to day operations is another matter (micro vs. macro scale) and probably very dependent on usage/environment/etc.
[Nexus 4 Original Android Development] MuertoKo:
Sadly it's not, I'm industrial Engineer so kinda know how this works, still ty for saving me the googling (me and many others, most appreciated).

What I ment was specifically related to a device, blind test, real tests. I know it should work as you stated up here, it's physics, sadly we're speaking of transistor switching and core voltages and body voltages... well, kinda hard to calculate when it comes to frequency switching...

Anyway, that's not enough to reflect a significant increase in battery life at all. Let's put it this way, you UV by -100mV a freq, what was expected is to have a % decrease in consume in same conditions running that freq. and I've not seen a single properly run test proving that with some stathistical significance. I even tried myself to run 2 blind test controling as much paramethers as I could (fresh boot, same temp in and out of device, same timings between operations, plane-mode active, running the same video at the same brightness with freq's locked to run at same freq with and without UV... which I really consider a pretty good test... and results were UV saved me around 3% battery which coming from a full charge it's not stathistically significant... (tried to run the same test some times, 3% was an average result etc).

Id' like to try that on N4 (all was done with a Sensation, pretty different device and pretty different UV capabilities) to see if it's significant enough to have some kind of a real "study" to show whoever asks about it. I'll try myself when I have a full day to test and the will, as it's quite hard really... or perhaps someone of those who can UV by -175 or so could test (the higher the better to test)...

Otherwise as I said before, I know it should work, and physics say it does, but coming to real-life improvement it's the area where I wanna know :P (gaining 1m battery would be ok to physics, but really not worth trying it all all for example).

Thanks for a nice answer though, too used to answers like "this sh*t makes my device as cool as in fridge and grants me 8h SoT for troll other thread" and such things... Most apprecited, really.

Hope I managed to explain myself properly this time :P
[Nexus 4 Original Android Development] kwerdenker:
Like I said, macro scale impact is a bit hard to determine. Especially since in a screen-on scenario, those four small cores are not the biggest power consumer by far in the device ;). But judging from your data, 3% more battery would be nearly an hour more running time for me, based on my average per hour battery consumption. As you pointed out though, this was on another device and isn't automatically applicable to our Nexus 4.

We could have a whole other discussion just about how testing it on one device would still not be enough evidence for or against it, even if it's done with the greatest care. Too many variables, most of which are out of our control. To properly test this we would probably have to build a special test-board with a lot of extra sensors to properly monitor temperature and power intake of the processor while conducting the tests. Also a temperature controlled test chamber would be nice to exclude deviations through ambient factors. Then the whole thing would have to be automated, so we remove any subjective influence and can run the 1000+ tests needed to get any meaningful statistical representation of how the different parameter factor into the power consumption.

On the other hand: if UV is stable and the user is happy, why argue :p

If my workplace ever gets the temperature control chamber my boss is aiming for, I might have to just get a dev-board for a snapdragon or whatever is used then and go nuts with it...

P.S.: If it isn't obvious by now, I'm an engineer too. Embedded Systems :D
[Nexus 4 Original Android Development] PJcastaldo:
Its funny.. I know a few engineers in the real world.. Your about as annoying as architects. If it doesn't work on paper for you then it doesn't work at all.. Point being on an everyday basis UVing has shown minimal battery savings but quite a bit less heat transferred through the back glass.. Now you may see that as my opinion or even as placebo.. But I would call it practical application.
[Nexus 4 Original Android Development] kwerdenker:
I think you misread our argument a bit. We are saying it works on paper but we are not 100% convinced it's that noticeable* in the real world. We are also not arguing that a user might not notice improvements. We're just not sure if this is really down to just UV. There is not enough real scientific test data to properly draw a conclusion, that's all we are saying.

Also I don't know what kind of engineers you know but the way I learned it, it's all about practical application. You just have to have data to support your decisions and why option A is better than option B. Next time you drive a car, board a train or get on an airplane think about how this would work, if we weren't trained and wired this annoying way. Just saying ;)

*noticeable as in "the gain is worth the risk of having an unstable device"

P.S.: Really not trying to hijack the thread. I just think that the UV topic is one that is worth discussing in relationship to the kernel and the more information the user has, the better.
[Nexus 4 Original Android Development] faux123:
I welcome geeky debates.. on or off topic ;)
[Nexus 4 Original Android Development] ansontyl96:
Anyone facing data drop with slimbean rom? As I think it's the problem if kernel.Anyone can confirm this?

sent from my nexus 4 with slimbean rom and faux kernel
[Nexus 4 Original Android Development] JaylanPHNX:
I think the take-away from the UV debate is that everyone agrees there may be some small, but really difficult to quantify, advantage to UV, but certainly not enough to risk instability for. If you can without introducing problems, then by all means, since it can't hurt, but don't freak out about how little or how much you can cause it's not that big a deal.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] morganmf:
Could not find info whether it is ment to work with cm10.2 or not?
[Nexus 4 Original Android Development] t0ph0id:
I'm running this with 26m JSS had a couple of AP watchdog barks. Been fine today though.
[Nexus 4 Original Android Development] Oops...:
That's exactly the point - reproducible (test) data is real evidence, not Wikipedia.

Just 2cts from another engineer :)
[Nexus 4 Original Android Development] Matt Devo:
I had one today that caused a boot loop/failure after the lockup. Rebooted to recovery and cleared cache etc, and then it froze on 'starting apps.' Wiped system and reloaded CM10.2 9/17 nightly, same problem. Had to wipe data to be able to boot again =/
[Nexus 4 Original Android Development] kwerdenker:
In my defense, I did make the limitation about the impact being big enough to be noticeable. And as for quoting Wikipedia: it was the fastest way to find it and I was lazy efficient ;)
[Nexus 4 Original Android Development] chadalu:
Im using cm 10.1 rc2

Whats is the latest version of faux for 4.2.2

Since the new versions are for jss and jwr
[Nexus 4 Original Android Development] t0ph0id:
From memory I think it was 16
[Nexus 4 Original Android Development] JaylanPHNX:
Actually it was 17b2, which was very stable even though it never made it out of beta (because Faux123 moved on to 4.3).

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] readon1:
Quick question: what's the stock PA lcd preset? Is it PA half breed?
[Nexus 4 Original Android Development] odavans:
yes
[Nexus 4 Original Android Development] MuertoKo:
Exactly my point of view really, will try to do myself some tests on N4 some day and share results, just for the sake of trying... xD As you said, too hard to control so many variables but.. I'll try my best! All depends on how patient I am during test procedure and how itchy I am with number of samples... :P

Nice geeky-chat btw ^^

Real Life evidence >>> Paper evidence, oh we stubborn engineers xD

+1000

That's a good way to sum-up a good and general opinion :) I'm running the -100mV just... for the "why not as long as it's 100% stable"
[Nexus 4 Original Android Development] Hali666:
Hi All,

Im using AOKP Milestone 2 and would like to use Faux's last 4.2.2 kernel can anyone tell me what that one was and provide a working link to download it please.

All help is appreciated.

Thank you.
[Nexus 4 Original Android Development] qwahchees:
Is this kernel stable with PA? I've had issues with this and had to move back to 4.2
[Nexus 4 Original Android Development] Somairotevoli:
Just a warning. Got the blinking red light of death after flashing Monday morning. Had 90 % charge. I have recovered many times before from it by just simulating a battery pull with volume up and power for 60 seconds. Not working this time. Would just get the battery icon for a sec and then back to blinking red. Decided to plug into USB and same thing. Left it plugged in for awhile and when I went back to check on it, it was completely dead. So had to do a manually battery pull. That worked and phone booted it up at 85%. Ultimate kernel working great! Got it clocked at 1728 interactive with hispeed set at 1350. No issues, no heat. Just a little scared getting there.

Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
[Nexus 4 Original Android Development] Face1ess:
http://faux.androidro.ms/mako/ last stable 016m, last beta 017b02
[Nexus 4 Original Android Development] partylikeaninjastar:
Faux, would you consider adding USB fast charge to the stock plus kernel?
[Nexus 4 Original Android Development] WiwiPouPou:
Hi, sorry, it probably have been answered before, but I'm on xda app and can't find... It understand that stock+ is based on stock, and mainline and ultimate on AOSP (??).. I wonder, which one is stabler? What are the others differences? I mean besides missing features, the under the hood differences?

Sorry, I'm new to nexus 4,a whole new world! :)

Edit : voltage table seems different?
[Nexus 4 Original Android Development] steve385:
I installed JWR SP and my phone didn't boot. I waited for about five minutes and all I got was "Google" when device powered up. Curently running PA 3.99. Any suggestion would bi nice.

And one more thing.. I managed to download kernel from OP's link in first page but it paused a few times (but I flashed kernel normally, got the install from SD complete message) .. Maybe that is the problem?
[Nexus 4 Original Android Development] beren:
[MENTION=3332811]faux123[/MENTION]

any chance to see DoubleTap2Wake option in fauxclock app? shouldn't take a lot of time...
[Nexus 4 Original Android Development] linelock:
They are both based on aosp. Stock+ is just that. Stock plus a few tweaks, but nothing that could make it unstable. You can't undervolt as much. Stock governors. Stock thermald and mpdecision. It includes gamma and sound adjustment.

The mainline and ultimate kernels include all of faux123's features. Mainline is stock frequencies, ultimate includes Overclocking.

Check faux123's git linked in the OP for more detailed changes.

---------- Post added at 07:12 AM ---------- Previous post was at 07:07 AM ----------

It could be a bad download. I would download it again. Wipe cache and dalvik cache. Dirty flash the ROM and gapps(if required by the ROM), flash the kernel.
[Nexus 4 Original Android Development] nixie2121:
I know this has been asked before, so please bear with me...

I have had some issues (weird screen issues, freezing, flickering) trying FAUX in the past and really would like to give it a go again. Right now I am on the latest PA rom with the latest Franco kernel and francos paid app. (I know I can use trickster for FAUX).

I just downloaded JWR Mainline 4.3 Kernel from the OP. <---Correct I assume!!!

What steps do I need to take to install this Kernel? (coming from Franco)

Again I am sorry as I know this has been answered, but I have had issues and I want to give FAUX a shot here and want to make sure I do everything correctly.

I also have no clue what OTG is!!??

Thanks so much in advance.
[Nexus 4 Original Android Development] notbrodie:
re-flash PA (to flash rom's stock kernel and ramdisk), then faux kernel, then whatever else may have been wiped by the PA flash. wipes caches, reboot

---------- Post added at 07:12 AM ---------- Previous post was at 07:12 AM ----------

faux has stated multiple times that it is unstable and will NOT be added to the stock+ kernel
[Nexus 4 Original Android Development] partylikeaninjastar:
I was just thinking the same thing. The included kernel with my N7 ROM has this feature and it's a lot more cool than I would have thought since the buttons aren't exactly easy to access on the N7 unless you're holding it landscape. Maybe I'll try sweep2wake, but I'm worried about killing my battery in my pocket.

Thanks. I used to follow this thread religiously, but stopped checking back as often around the time of 4.3 being released. I went ahead and re-installed the mainline kernel because that's a really useful feature for when I'm at my work desk. Do you happen to remember in what way it is unstable? Just wondering what kind of wonky behavior I can expect from my phone. I don't even remember him saying anything about it being unstable, but I do remember him ranting how he hates the name "USB fast charge" because it's misleading to some people.
[Nexus 4 Original Android Development] snak3ater:
Double tap to wake option is good for a Tab but for our phone it's no good..I tried enabling it from TC & my phone was waking up again & again while inside pocket.So i had to disable that option..
[Nexus 4 Original Android Development] bhanumagotra:
sweep2wake not working properly !!

i just installed faux 026 and enabled Sweep2Wake (s2w+s2s) ... the screen is sleeping perfectly when swept right to left .. but it is not waking up when swept from right to left everytime ... sometimes it does after 5-6 tries but sometimes it just dont ..

any reason why this is happening ?? and the possible solution ??

EDIT : i m using trickster mod to activate the function
[Nexus 4 Original Android Development] notbrodie:
i had the same issue. dt2w has the potential to be useful, just not on pocketable phones/devices
[Nexus 4 Original Android Development] cammel:
Hi, sorry if this been asked before But I'm new with the nexus 4 and I want to calibrate the screen colors and gamma. I'm actually running cm10.2 with stock kernel, and I bought the advanced color and gamma control app from the play store, but when I change any of the values and the app tells me to turn off and on the screen to apply those changes it automatically reset them to the stock values, so... Do I have to change to faux kernel in order to use this app? Cause apparently it doesn't work with CM stock kernel... (which has gamma control on the rom, but I don't like it)

And one more thing, if I flash faux kernel and I want to go back to stock CM kernel, do I have to use the faux reset kernel before flashing CM again to get back the stock kernel or it isn't necessary if I perform a full wipe before flashing cm again?

Thanks a lot in advance for the help!

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] stab244:
He said he needs to update the app to work with the CM version of his interface. He's a bit busy now with HTC One and N7 gamma control now.
[Nexus 4 Original Android Development] tvisforme:
No worries, we were all new to this at one time!

From my experience, you do not need to do a full wipe; if you reflash CM without adding Faux's kernel, you are by default on the standard CM kernel. If I understand it correctly, the reset is for transitioning from certain other custom kernels that make changes to areas which are not reverted by a normal reflash.
[Nexus 4 Original Android Development] cammel:
Awesome! Thanks you both for the help!! :D:D

Enviado desde mi Nexus 4 usando Tapatalk
[Nexus 4 Original Android Development] JaylanPHNX:
I would recommend flashing Faux's kernel just because it's so damn good.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] Flav106:
Hello,

I have installed the last version (mako-jb-kernel-026u-JWR.zip) and OTG is not working... I tried with ziddey's kernel and it worked well.

Any clues ?

By the way, do you know if USB Audio works with this kernel ?

Thanks !
[Nexus 4 Original Android Development] 0.0:
Is there a terminal code to turn on and off OTG? And is there code for SOC? Also for zram?

sent from my Nexus 4
[Nexus 4 Original Android Development] samuelrf:
it's normal that when trying to change the configuration of the kernel in trickster mod ( in specific window) the phone freezes and it reboots into a green screen?(watch dog or something like that I have read) psx with latest ultimate version

Speedy answer by Pure Speed
[Nexus 4 Original Android Development] 0.0:
[MENTION=3332811]faux123[/MENTION] I found a bug with fauxclock. I am using a kernel based off your code. The dev (anarkia) took out the laziness portion of your Simple GPU governor. Now fauxclock doesn't show the Simple governor as an option. With trickster, it shows (but I really don't like trickster, I love your app). That's all, hope it can get fixed :)

sent from my Nexus 4
[Nexus 4 Original Android Development] Stryder5:
For SOC

http://xdaforums.com/showthread.php?p=40343162#post40343162

For OTG (from the OP):

echo 1 > /sys/module/msm_otg/parameters/otg_hack_enable

For zram:

http://xdaforums.com/showthread.php?p=42460734#post42460734

You've been around long enough that you should know how the search feature works. And in case you didn't, most commands use the "echo" command so searching for "echo" + whatever feature usually gets you good results ;)
[Nexus 4 Original Android Development] omkar3409:
Can any one help me figure out major difference between mainline/ultimate/stockplus kernel ?

Thnks in advance :)
[Nexus 4 Original Android Development] Craxx:
Yes, all is written in op.

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] El Nino1977:
Post #1 is usually a good start my friend but TBH the major differences are the OC speeds of the CPU really.
[Nexus 4 Original Android Development] ak:
Before changes ... Set intelli plug cap freq and max oc to 1512 ... Than try again.

After these steps if your phone is stable change the others options