yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] wvcadle:
I don't see any problems with using toolkits. The two out there are from very respectable developers. I do know most commands, including how to flash images and zip files, adb and fastboot commands, but I still use Wugfresh's toolkit sometimes. Nothing wrong at all with using them... well, other than they can keep one from learning how to do things manually.

Edit: And one other thing. For some reason, there has been more than just one time where downloading and installing the drivers manually just wouldn't get my phone and windows 7/8 pc to talk and get along... which I resolved via Wug's toolkit.
[Nexus 4 Original Android Development] notbrodie:
exactly! anyone flashing roms or kernels on their phone should know exactly what they are doing. while i can understand using the toolkit as a shortcut (provided you already know what you are doing), the toolkits should not be used by new flashers. [MENTION=1566190]efrant[/MENTION] wrote an excellent guide on flashing your phone completely back to stock. that is the first thing i recommend people do, as it familiarizes them with fastboot and adb without crippling them (like those toolkits do). generally, when they run into a problem, they have no idea what to do. toolkits are a horrible idea for new users.
[Nexus 4 Original Android Development] ÜBER™:
Its not that they're bad, they are quite useful once you know how they actually work. Its just a crutch, and should be used to ease users who already know the manual way. However most new users use it, and screw things up. That leads to more headache which could have been avoided if the user opted for the manual route which has much less chance of problems. Mostly because its very straight forward. Three commands.. Four at most. The toolkit is not very straight forward since it does multiple things for multiple devices.
[Nexus 4 Original Android Development] Shftup:
Ahh yes.

Well I hope that I can. The problem is the phone wont stay on for me to enter recovery and do just that.

When I get home, I will try the toolkit before doing to ADB with PC - and reflash the AOKP ROM - that should solve the issue.

Question - when using the toolkit

Open the Wugs program, plug in phone via USB, then what? Just attempt to turn it on, and program should see nexus 4, then which command?

Put back on TWRP so I can reflash rom or something else?
[Nexus 4 Original Android Development] wvcadle:
The analogy I would use in this instance is like asking a kid to read a book on Christmas morning before opening their presents. Of course, reading a book is a very good thing to do, but not right before you open presents!

Same thing with rooting and flashing roms. People want the prize now now now! Of course, that's another whole issue in itself.

But honestly, as long as someone has common sense, which I would assume most do who find XDA, can figure it out if disaster strikes. Matter of fact, there's nothing like a soft brick to force someone to learn (spoken totally from experience). I never knew any adb or fastboot commands until I bricked my phone. Within an hour or two, I knew most every command that I'd ever need!
[Nexus 4 Original Android Development] notbrodie:
I agree with you. it just seems like a lot of people who try toolkits are scared of the command line, and that is what is like to see ameliorated.
[Nexus 4 Original Android Development] Shftup:
Okay - I got this bad boy to work. I did a recovery and restored by backup. I was able to use the toolkit.

thanks all
[Nexus 4 Original Android Development] pikachukaki:
Could someone that is borring can compile faux latest with new prima...alot of kernels uses it...so maybe they are ok now!! :) until faux can decide about this!!
[Nexus 4 Original Android Development] faux123:
When you said many, who are the many? And how can you claim I don't have the new WiFi drivers?

https://github.com/faux123/mako/commit/8eca210599503d4b426ded7e5def5879469dea08

You got anything newer than this? :rolleyes:
[Nexus 4 Original Android Development] pikachukaki:
Dont get upset...im just saying..."Updated prima drivers (wifi, 3g, bluetooth) to 3.2.3.185...."

btw this is the 1st time i get notification as soon as i get on wifi..not from all apps....(g+,gmail) but from FB,fb messenger!!!
[Nexus 4 Original Android Development] acadiancrusader:
I as well would love to see this compatible with multirom. But just as you stated, i'm in no hurry and wish faux a speedy recovery

Sent from my Nexus4+Gn0m3JLS36G+Faux026MJSS
[Nexus 4 Original Android Development] arifroni:
i installed jss m version with PA 3.99 rc2. after installing the kernel phones display acting wired. its like there is no display driver. when there is an animation, things are broken. did i do something wrong?
[Nexus 4 Original Android Development] stark_br:
On PA you should use JWR version.
[Nexus 4 Original Android Development] Globespy:
Any evidence if these new Wi-Fi drivers are fixing the widespread 5ghz router band connectivity issues introduced in JB4.3?
[Nexus 4 Original Android Development] arifroni:
thnx...i just did...and it looks fine now :)
[Nexus 4 Original Android Development] pikachukaki:
Not sure about that but I'm confident about the notifications under deep sleep

Sent from my Nexus 4
[Nexus 4 Original Android Development] cocchiararo:
i just noticed that the sweep/knock to wake/lock on the N7 2013 is way different (and betteR :P) than in this device.

is that other version or portable to this one ? :P
[Nexus 4 Original Android Development] Oops...:
Based on tests without any mods in the ini file respectively additional apps? Would be great...
[Nexus 4 Original Android Development] ziddey:
.84 radio seems to have 5ghz issues. Reverting to .54 resolves this at the expense of ARP offloading

Sent from my phone. Please forgive typos and brevity.
[Nexus 4 Original Android Development] Cuzz1369:
And [MENTION=3332811]faux123[/MENTION] suddenly reappears. (Golf clap) Welcome back. Hope everything is going well for you.
[Nexus 4 Original Android Development] RonnieRuff:
I am using carbon on my N4 and they say to use JWR but I am getting crashes that send me to the boot loader. Any ideas?
[Nexus 4 Original Android Development] 21plays:
Thanks faux! Proof!
[Nexus 4 Original Android Development] pikachukaki:
im getting 20hours SOT by having my phone min/max 384mhz and leave my screen on ;)
[Nexus 4 Original Android Development] soumoks:
I see that you've not shown the battery graph for a reason :D :D
[Nexus 4 Original Android Development] mor_1228:
this is so damn fake. this guy is charging his device frequently if not then show us the graph in both ways expanded and normal
[Nexus 4 Original Android Development] BLADESMAN1889:
Or another analogy:-

My parents wouldn't buy me a digital watch until I had learned to tell the time with a 'ticking' watch with fingers & hands :)

[Traditional parents]

Sent from NEXUS⁴ via XDA Prem [AOKP 4:3:1]​
[Nexus 4 Original Android Development] Globespy:
+1000!

There is no way in hell that data is genuine 1 charge use, unless he has retrofitted a car battery to power his phone that he drags around behind him on a radio flyer cart. :laugh:

I think the most I've ever seen was about 6 hours, and it was genuine with all the screens to prove it - and this person must have had the best built battery that LG have ever made, and ran his screen at the lowest possible brightness setting all day in a dark room.

I have got 5 hours once but the average is 4 and that's considered good by many.
[Nexus 4 Original Android Development] 21plays:
Everyone just calm the funk down. It was a joke okay. You got me! :) BS aside, this kernel is awesome.

---------- Post added at 11:24 PM ---------- Previous post was at 11:23 PM ----------

I laughed... Hard. Thanks!
[Nexus 4 Original Android Development] Globespy:
LOL - me too as I was writing it! What a visual to see, the car battery on the radio flyer. Maybe someone has the time to steal their kids cart and do a mock video of this for shizzles. :laugh:
[Nexus 4 Original Android Development] ciprianruse88:
Best laugh I got today :)
[Nexus 4 Original Android Development] zimphishmonger:
I've done searches but can't find an exact match but someone has to have had this issue.

Using aokp Oct 1 (from whitehawkx but nothing different than main branch) 26m works perfectly. For some reason, any version past that has blue lines immediately after the Google logo on boot. Tried jwr and jss even tho it should work with jss. Stranger, I flash one of the color fixes intended to correct a lib conflict (something about caf vs non caf implementation), and it boots but shows opposite colors (yellow for blue etc).

Anyone mind helping me out? Just been hanging out on the October 1st build of Aokp until I can figure this issue out.

Thanks!
[Nexus 4 Original Android Development] DontPushButtons:
Doesn't seem like the colorfix took properly. You're still having the same CAF problems. I would say try reflashing the fix and making sure to wipe dalvik/cache after, if you didn't already.

This is the one I've been using and have had good results. https://db.tt/rIvSxynq
[Nexus 4 Original Android Development] krispuniq:
Is this kernel compatible with multi Rom? With Ubuntu release around the corner, I want to use multi Rom with faux kernel in primary Rom...but looks like only Franco kernel works now... [MENTION=3332811]faux123[/MENTION] can you merge the changes for multi Rom in your kernel plz ?
[Nexus 4 Original Android Development] skinzy98:
So I know this sounds stupid but I can't seem to find the 4.3 link am I just missing it?
[Nexus 4 Original Android Development] evonc:
Every release after 17b2 is 4.3 only.
[Nexus 4 Original Android Development] skinzy98:
Yes but I can't seem to find a link. I've went through the op multiple times. Maybe I should try web view hold on a sec
[Nexus 4 Original Android Development] evonc:
http://faux.androidro.ms/mako/jb43/
[Nexus 4 Original Android Development] martindar:
Faux, nice to see you back, hope you are ok, heard you'd had a smash up?? so good to see your alright
[Nexus 4 Original Android Development] skinzy98:
Just found it on web view when you posted. That. For some reason the links weren't showing up through the xda app
[Nexus 4 Original Android Development] JaylanPHNX:
Are you using 26m, or 26u? U is overclocked, which some phones just can't handle. If you're not using 26m, try that one.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] alcurtis93:
Which kernel works with cm10.2?
[Nexus 4 Original Android Development] RoliSoft:
Out of the box? Neither.

Use JSS and get the color fix zip from this thread. That should work, however there are some ROMs lately on which it doesn't.

Swyped from my Nexus 4
[Nexus 4 Original Android Development] kenkiller:
Hmmm....using the term "out of the box" when it comes to kernels that you have to root to flash seems kinda...inappropriate. :D
[Nexus 4 Original Android Development] stevew84:
I hate to be "that guy", but what is the Faux kernel to be used with AOKP 4.2.2? I always have a hard time hunting down Faux's database with all the kernels.
[Nexus 4 Original Android Development] kurniawan77:
One page back....

---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------

See
[Nexus 4 Original Android Development] stevew84:
Downloading 16m, what's the difference between the suffixed kernels and non suffixed? Both have same upload date.

Actually tbu and tbm also.
[Nexus 4 Original Android Development] pikachukaki:
latest kecinzer aokp has faux 26u with new prima drivers if anyone wants to flash it...remember you can't get only the kernel cause it need some files on /system too....
[Nexus 4 Original Android Development] DontPushButtons:
U = ultimate (all governors/customizations/overclock available).

M = mainline (all governors/customizations/no overclock)

Rudimentary description, you can find more details in the OP

Edit: or maybe not.. I believe tbu and tbm were from 4.2. From the OP:

For 4.3, i believe my previous description holds true about overclock/non overclock. With 4.3 the cpu got much more finicky with clock speeds.
[Nexus 4 Original Android Development] stevew84:
I'm looking for 4.2
[Nexus 4 Original Android Development] DontPushButtons:
Then just read the part I quoted from the OP? Or do you mean you're looking for a download link? (pretty sure that's also in the OP)
[Nexus 4 Original Android Development] stevew84:
No no I'm good, that's all I needed. Thanks.
[Nexus 4 Original Android Development] DontPushButtons:
Cool, happy flashin
[Nexus 4 Original Android Development] JaylanPHNX:
Use 17b2. Even though the b2 is a beta designation, it ran very stably for a long time for me.

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

---------- Post added at 05:37 PM ---------- Previous post was at 04:59 PM ----------

17b02? There is a 0 in there somewhere and its for 4.2? What's the correct method of flashing.
[Nexus 4 Original Android Development] kurniawan77:
Always flash kernel after you done the ROM.... Is that what u meant?
[Nexus 4 Original Android Development] Coumodo:
I'm trying to use Faux 26m JSS with the latest cm 10.2 nightly. Everything runs fine so far, but i've get strange coloursettings and glitches (looks like sepia-effect).

I've tryed to reset all settings to default, or adjust the colouroptions but still get freaky images.

any surgestions?

...WTF?! I take a screenshot to show it to you, want to upload it to the attechments via dropbox --> in the screenshot the colour are perfect! :eek:

the first is the screenshot, second how it actually look like on the screen...
[Nexus 4 Original Android Development] JaylanPHNX:
Do some searching, you'll find a lot about the color issues because of CAF. But the screenshot being prefect is kinda funny.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] kwerdenker:
Actually, it's quite simple why the screenshot looks right: making a screenshot is not done by reading the pixels on the display. Instead you take what is currently in the systems image buffer and dump it into a file. This is the data the systems passes to the screen controller which drives the actual pixels on the display. If the color problems are on the controller side (probably incompatible driver access for CAF versions or something along those lines), then the data that is dumped into the screenshot is correct but what's displayed is not.
[Nexus 4 Original Android Development] JaylanPHNX:
That's what I figured. I meant funny as in ha ha. :p

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] yoyoz808:
Anyone got link to a mirror for the latest faux kernel the m version because the links in the op aren't working.
[Nexus 4 Original Android Development] wvcadle:
Working fine for me.
[Nexus 4 Original Android Development] Flashmaniac:
It's not. The software is configured properly but the display acts different. The software doesn't recognize the way the hardware displays it.
[Nexus 4 Original Android Development] yoyoz808:
Nvm. For some reason my mobile Internet doesn't work for those links but when i use wifi it works. Thanks.
[Nexus 4 Original Android Development] matchqq:
Do you need to buy faux clock from Play Store to set min/max freq? I use Trickster to set min to 384 but it keeps reverting back to 1026? Or do I need to turn off MP decision?

I'm on Carbon ROM by the way.
[Nexus 4 Original Android Development] saint_cow:
Turn off mp decision
[Nexus 4 Original Android Development] hooliganx:
did it, but don't change. only 384...

N4*Slim.b1.8.JLS.4.3.1*Faux.026m.JWR-JWR*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] Rycon33:
imo, you'd be better off using the FauxClock app, it's well worth it anyway and tons of tweaks are inside it

or maybe just make a simple script to control the CPU min/max
[Nexus 4 Original Android Development] hooliganx:
Ivm using Faux app...

and MP decision is off, but min 384 don't change

N4*Slim.b1.8.JLS.4.3.1*Faux.026m-JWR*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] C4SCA:
Faux kernel doesnt have any frequency lower than the stock 384mhz..

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Original Android Development] Rycon33:
Oops, my previous reply should have been for [MENTION=4289554]matchqq[/MENTION] where he said he can't get to 384. Apologies for the confusion hehehe. :D

Tapatalked from my N4
[Nexus 4 Original Android Development] saranyan:
I just flashed the O26M version of faux kernel. I am using the recommended intelliplug + Intellidemand settings with Eco mode turned off, However beach buggy blitz is extremely choppy for me. Not as smooth as stock

Can someone suggest some nice general settings for games?
[Nexus 4 Original Android Development] b00bs:
Just set mpdecision on and change governor to intellidemand. Smooth as ondemand but more battery. Because clock speed stay at 1024.

I like mpdecision because it tried to stay @2 cores when screen touched.
[Nexus 4 Original Android Development] hooliganx:
which version of touch control works with faux 026m?

native s2w don't work so well. sometimes screen don't turn on, no matter what I done.

great kernel!

this problem with s2w, I have in every kernel that I used :(

EDIT: Find! thanks everyone that help me in this search! :D

N4*Slim.b1.8.JLS.4.3.1*Faux.026m-JWR*TWRP.2.6*Radio.0.84
[Nexus 4 Original Android Development] mikelee28:
You can't use jss kernal with pa
[Nexus 4 Original Android Development] csunny95:
I am using miui with 016 tbm , I have adjusted some setting in the faux clock app, but after reboot, the settings have gone. I have selected Set as Boot. How can i keep those setting even after reboot ?
[Nexus 4 Original Android Development] hellsgod:
MIUI also have issues with Trickster. Settings won't stick. Try to give fauxClock permissions in the Autostart App. Maybe thats the solution...

hells
[Nexus 4 Original Android Development] Oops...:
Search for faux123's posts with echo in the text. You will find init.d script fragments for all the settings. Put the file in /etc/init.d and give proper permissions. That's all you need..

See http://chromloop.com/2013/07/how-to-control-faux-kernel-for-nexus-4-by-scripts-guide/ as basis

Edit: however you should buy faux 's apps to support this great dev :)
[Nexus 4 Original Android Development] C4SCA:
Clock speed stays at 1024mhz only for a set amount of time after u touch the screen, its called touch boost and its control by the hotplug driver wich in stock is mpdecision.

After that time it goes back to 384mhz

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Original Android Development] b00bs:
Correct. What I mean is the difference between ondemand=more at 1512Mhz, intellidemand=more at 1024Mhz which is more efficient.
[Nexus 4 Original Android Development] C4SCA:
Not exactly since when u touch tge acreen ita at 1024 and apps rarely use 1.5ghz (only games and crappy facebook for example). So at 1024 mhz the load needs to be quite a lot so that the governor decides to rank up the frequency to 1.5 and if it ranks up to that, it doesnt stay there for long... Use cpu spy and u will see, 1.5 ghz is not very used (even less when u game but thats cuz of the heat who triggers throttling)

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Original Android Development] Coumodo:
is there some kind of work around against colorfails with the latest Kernel and the official cyanogenmod 10.2?
[Nexus 4 Original Android Development] notbrodie:
try searching the thread for "colorfix"

Sent from my Nexus 4
[Nexus 4 Original Android Development] leader288:
Hey I've been trying this kernel out the last couple of weeks. Was wondering if anyone could explain the tunables under CPU governor eg ignore_nice_load, two_phase_freq etc…

Thanks!
[Nexus 4 Original Android Development] sxp:
Last fauxclock FC always

Previous version only reboot FC

Rom aokp 4.2.2

Only change this app

2 version previous not problem

Last 2 version not good :(

Ui change not comfortable :(
[Nexus 4 Original Android Development] Rycon33:
Don't use it on CAF'd ones(e.g. AOKP, CM). But if you really want those ROMs, be sure to use their workaround fix there.

Faux kernel is solid on PA and stock-based ROMs.

Edit: Not sure about 4.2.2 aokp though.

Tapatalked from my N4
[Nexus 4 Original Android Development] Gustave17:
[MENTION=350276]faux[/MENTION], love your kernel thanks for your hard work.

is it possible to re-activate swipe in your app for navigate between tabs ?

Perhaps just an option in fauxclock settings...
[Nexus 4 Original Android Development] Subrad5446@aol.com:
OTG Zip

[MENTION=237687]Craxx[/MENTION]- Can you do me a favor and reupload the zip you flashed with rom and gapps to make otg work on slimbean? I misplaced it somewhere and it seems you deleted it from your dropbox account. Or you could tell me how you made it....

Thanks man
[Nexus 4 Original Android Development] Craxx:
https://copy.com/6CgxL

Best regards ;)

Craxx

Send from my Nexus 4 with Tapatalk HD
[Nexus 4 Original Android Development] itpromike:
So here is a question, actually 2... If all I'm interested in is the display /color control portion of this ROM, then all I have to do is flash the desired kernel, not mess with anything except the display control and everything else should pretty much be similar to stock settings right? 2nd question is, when coming from PA I should be able to flash this without any special steps right? Thanks in advanced for taking the time to respond.
[Nexus 4 Original Android Development] JaylanPHNX:
For you first question, yes, get the gamma control app and you should be able to just leave everything else alone. Don't know about the second one.

Edit: The XDA app has smoked a big crack rock and quoted the wrong post for me.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] DontPushButtons:
Stock enhanced kernel is probably what you want, for just additional gamma (also sound options) but stock settings, otherwise.

Else, JWR (if the desired kernel specifies) should be the only other thing to keep in mind. Since PA is still on JWR base as far as I'm aware.

Quoted the wrong post methinks?
[Nexus 4 Original Android Development] c_86:
People keep saying to use the colorfix which BTW does not work with the latest CM Oct 19 build.

With the latest cm10.2 oct19. And flashing any kernel like faux or Franco, the colorfix doesnt work...

Unless I am missing something. I have tried everything. Nothing will work. It either boots with the messed up colors. Or flashing the fix make it not boot at all
[Nexus 4 Original Android Development] Sliverpfa:
It's not kernel issue. Try another rom like carbon.

Inviato dal mio Nexus 4 con Tapatalk
[Nexus 4 Original Android Development] nadiros:
This was the expected outcome of CM becoming CAF-inated. The more of it they add will render the fixes useless. Seriously, as soon as I realized this path they decided to take, I chose not to chase it and instead use ROMs and developments that are open and compatible giving the user more choice instead of less. They are (CM) a business now so it's their buisness, however Android is fun for me so good riddance :p
[Nexus 4 Original Android Development] stab244:
Blame CM for changing stuff again. Faux needs to make some changes to his kernel I think for it to work. No easy fix this time.
[Nexus 4 Original Android Development] itpromike:
[Kernel] (ver 026) Mako JB 4.3 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [Sep-14]

On most stock kernels (if not all) as far as I knew used Google/Aosp stock colors though? And not the LG/retail stock colors...? Am I incorrect about that? I'm looking to get the retail stock just bought it from the store colors. The AOSP colors are off to my eyes. The reason I was looking at faux is because there is an LG stock preset in the display settings. If I wrong about that which enhanced stock kernel would you suggest?