yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] pnut22r:
Why won't the kernel reset zip work with CM roms? I know that it won't, and I've read the disclaimer, but WHY does it not work. Please explain the compatibility problem. Is it the ramdisk?

Myself and another xda member are chatting about this in another forum.

I wanted to run stock kernel on my CM Rom for a day, before returning, but I had to unpack the stock boot.img and repack the zImage with koush AnyKernel to flash it. It worked. But why? If I can flash any other custom kernel no problem, why the stock kernel have problems?

Thanks.
[Nexus 4 Original Android Development] brunini:
You have problems with reset kernel because it is made for work with Stock ROM. If you want use the stock kernel of CM, just flash CM ROM again. This will replace the old kernel.

Don't flash the 07 July CM nightly, its buggy.
[Nexus 4 Original Android Development] pnut22r:
Thanks, but I said in the first paragraph, I knew it didn't work, I'm just wondering why, technically speaking, not just "it doesn't work...because".

I want to use the stock android kernel, not the stock CM kernel.

Thoughts?
[Nexus 4 Original Android Development] brunini:
I don't know exactly but i think:

Maybe the zip file of "reset kernel" have more than stock kernel inself. They may contain some files/scripts that only work in Stock ROM structure/environment.

Perhaps these custom kernels do more than only replace the kernel as a single file.

So if they change more than a single file, make sense as a developer have a "reset kernel" to reset the changes.

Conclusion:

"stock kernel zip" != "reset kernel zip"

I don't have knowledge about this technical details, but this is what I think.

Please someone correct if I'm wrong.
[Nexus 4 Original Android Development] stab244:
CM uses a different ramdisk. Don't ask me why. They just do.
[Nexus 4 Original Android Development] aldyu:
R u from the future?

Sent from my Nexus 4
[Nexus 4 Original Android Development] pnut22r:
^^I laughed so hard at this, simple but effective^^

So their builds only works with their ramdisk? That's why I'm able to flash the kernel (the zImage, and not the ramdisk) and it works.

Then why can custom roms work? Their ramdisk works with CM? Its just that the stock ramdisk doesn't? Weird.
[Nexus 4 Original Android Development] brunini:
Yeah i come from the future!

Sorry. :eek: its 04 instead 07 July.
[Nexus 4 Original Android Development] aldyu:
Just kidding around... Have a nice day..:)

Sent from my Nexus 4
[Nexus 4 Original Android Development] JaylanPHNX:
Not the first time I've seen someone do that. It is usually kinda funny. And let's face it, if people on xda had the ability to go to the future, forget warning of impending disasters, they'd just use it to flash future builds. :D

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] housry23:
I think he was talking about toggling s2w in the app itself. It's AT&T the top and I think he was asking if the toggle can be moved to where he can reach with one hand.

I think....
[Nexus 4 Original Android Development] _Vegas:
That'll be good

来自 Nexus 4 上的 Tapatalk 4 Beta
[Nexus 4 Original Android Development] BYTeXperience:
I was talking about this: modify if it's possible the distance from the screenshot attached.

Right now it is necessary to swipe all red line, and it would be better to decreese the swipe needed to turn off the screen to the yellow line.

On dedicated TouchControl app it is simple and easy to modify that distance, maybe can be implemented on faux123 app also.

Thanks for your time.
[Nexus 4 Original Android Development] jarjar124:
When I download the kernel from your app. Where is it located?
[Nexus 4 Original Android Development] undercover:
Right. So went with display calibrator app to get as near as I can to 2.2. Red, green, cyan are success, blue us at 1.8 max, yellow about 2.4 and magenta around 2.0.

As near as I could.

Amp 0

10

7

25

The rest at default.

Don't find it saturated enough imho, but if anyone is looking for the closest possible settings to calibration, this is a good place to start. Screens differ, so you might need to move them about a notch. Also, it might be worth taking it to the separate thread.

Scratch that. Saturation is perfect. Blue really shines now, although I couldn't get it to 2.2.
[Nexus 4 Original Android Development] faux123:
under /sdcard/Download/
[Nexus 4 Original Android Development] jarjar124:
Thank you so much. The name of the file caught me off guard
[Nexus 4 Original Android Development] SIGUEL:
Can you share your settings??

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
You mean the ones you quoted? :p
[Nexus 4 Original Android Development] SIGUEL:
The color adjustments are not mentioned, sorry.

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
These are quite nice. A but over saturated, and gamma is completely off, but for amoled lovers spot on. White balance is very good. :thumbup: Edit. Maybe a bit too cold.

Yes they are.

Amp 0

10

7

25

The rest at default.
[Nexus 4 Original Android Development] afbengochea:
Anyone having issues with faux app closing? I'm on aokp

Edit: might that supersu needed to update binaries. Just did. Well report back if anything
[Nexus 4 Original Android Development] undercover:
Yes, now and again.
[Nexus 4 Original Android Development] SIGUEL:
Ohh sorry, didn't get the “rest at default” part. Thanks.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Locksmith81:
I'm connected to my car charger now and it reads charging AC..... I'm missing something?
[Nexus 4 Original Android Development] undercover:
Different chargers supply different voltage. Some will be seen as usb, others as ac.
[Nexus 4 Original Android Development] jarjar124:
Sorry if this was mentioned but is it possible to change the haptic feedback strength? I was using Franco kernel and loved the haptic feedback on the thing and got really used to it. If its possible,how do I do it?
[Nexus 4 Original Android Development] jhericurls:
Goto

Sys/class/timed_output/vibrator and change the amp file to 100.
[Nexus 4 Original Android Development] Locksmith81:
Of it wasn't..... It wouldn't show ac?
[Nexus 4 Original Android Development] teknhard:
This looks quite good. Thanks
[Nexus 4 Original Android Development] undercover:
I think it shows usb. But it's been a while since I modified mine, so not sure. Best way to check is to install battery monitor widget and to look how much it supplies. AC charger hovers at about 800+ until it reaches about 80% charge. If it's less, then you are not getting AC like charge.
[Nexus 4 Original Android Development] mesasone:
Minor nitpick, but it's current that varies between chargers, not voltage. Voltage should be ~5V and if it's not your charger is broken.
[Nexus 4 Original Android Development] undercover:
My bad.
[Nexus 4 Original Android Development] den_breacker:
Ok, we all should post our logs in the carbon thread so they can fix the problem !
[Nexus 4 Original Android Development] PianoJazz:
Anyone else having this problem?
[Nexus 4 Original Android Development] housry23:
Ah..gotcha. Faux123 isn't the developer of sweep 2 wake. He has just implemented into his kernel. Not sure if he'd be willing to change anything. Maybe you could ask the dev of S2W.
[Nexus 4 Original Android Development] BYTeXperience:
I have already contacted the creator of S2W some days ago, and i have asked him if can help faux123 with this sugestion... No answer for the moment. I will wait, maybe it will help faux123.
[Nexus 4 Original Android Development] masterg0g0:
Interesting story: since couple of weeks my phone was running pretty stable with no radio dumps or data corruption. Yesterday when i was returning from work in the airport my phone through the x ray machine and wala green screen after rebooting there was data corruption and restore from the rom backup up :) lost 5 days of app activities but that's life.
[Nexus 4 Original Android Development] notbrodie:
if the phone reboots, i can't get a log cat, and carbon dev doesn't care about last_kmsg for a different kernel
[Nexus 4 Original Android Development] den_breacker:
You can use adb logcat.
[Nexus 4 Original Android Development] MasterJam882:
[MENTION=3332811]faux123[/MENTION]

Any news for ES mate? The stepchild feels lonely and unbeloved^^

greetz

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] JaylanPHNX:
Part of the point of ES is to not have a lot going on with it. Unless there's some new patch/fix for an issue, or the kernel source changes (4.3?), then there really isn't much to be done. It's supposed to stay as close to stock as possible.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] Jake-CT:
My phone also died following a trip through the x ray scanner yesterday - been a nightmare to restore in another country. Surely just a coincidence but is best advice to remove carbon and not use c2 state?
[Nexus 4 Original Android Development] ak:
Do you use carbon nightly?

Carbon is a fantastic rom, try to use stable version.

I dont use c2 state and my phone sleep like a baby.
[Nexus 4 Original Android Development] Jake-CT:
Ah I thought carbon meant the backup tool (renamed to helium). On Paranoid Android ROM. I was using C2 and have swapped to C3 now.
[Nexus 4 Original Android Development] ak:
:D Thanks a lot .. i have confused two things.
[Nexus 4 Original Android Development] MrPhilo:
Your screen protector is the cause of the issue. Is it covering the left side sensor at top? It was a known issue couple of month ago as some screen protector didnt have a cut for the sensor.
[Nexus 4 Original Android Development] PianoJazz:
No, that's not it. My screen protector has the proper cutouts, and nothing's covering the proximity sensor.

Any other ideas? I could try the factory kernel and see if I still have the problem.

Thanks.
[Nexus 4 Original Android Development] rmead01:
Any update on ideal zram setups?
[Nexus 4 Original Android Development] FrozenLord:
After having experienced this problem several times I've turned my back on Carbon and switched to Revolt.

So far there have not been any more crashes / data corruptions and I have yet to find a missing a feature.

I am now using Revolt 4.4.
[Nexus 4 Original Android Development] faux123:
recommended settings updated :D

here's the snippet for z-control

Z-Control

Set On Boot - On for both

ZRAM Disk size - 150~200 Megabytes (or 50 MB when disabled)

ZRAM Enable/Disable - Enable if you mult-task often

Clear VFS Cache After Boot - On

Auto FS Writeback Delay Mode - On

Swappiness - 100% if ZRAM enabled, 0% if disabled

VFS Cache Pressure - 100% if ZRAM enabled, 150% if disabled

Dirty Ratio - 20% for both

Dirty Background Ratio - 5% for both

check the OP for complete setings
[Nexus 4 Original Android Development] KerryWood34:
Thanks faux!
[Nexus 4 Original Android Development] ak:
Thanks faux ... zram statistics with cakes is a wonderful thing. :D
[Nexus 4 Original Android Development] cocchiararo:
exact same as the ones you recomend for the n7, which has half the ram and all the other notable differences.

I find that weird :P
[Nexus 4 Original Android Development] qwahchees:
Any recommended settings for simple GPU settings for battery + performance when needed?

CPU is 270 - 1.512, intellidemand, eco, snake charmer
[Nexus 4 Original Android Development] notbrodie:
this has already been established. stock gpu settings already give you this
[Nexus 4 Original Android Development] kairi_zeroblade:
ok so have been reading back lately..and found out that some of you guys disable the C2 power states..now my DUMB question would be since all of you purchased the app..how to i tinker with this via the sysfs??i want to add it on my init.d script..

Again TIA for someone who can help..
[Nexus 4 Original Android Development] omer7:
I've been trying different kernels on my phone and so far found Faux123 to be one of the best. Quite smooth and responsive. I've searched this thread, but couldn't really find an answer to my question.

How does throttling works in faux123?

I'm using this kernel with default settings and it shows MP-Decision "ON". My question is at what battery/CPU temperature throttling starts? Like in stock Nexus 4 kernel, (what I know), throttling starts when battery temperature hits 37C. In some other custom kernels, they use Thermal Throttling which see CPU temperature instead of battery temperature.

So, can anyone please tell me how throttling works in faux123? :)
[Nexus 4 Original Android Development] kairi_zeroblade:
if i do remember things right faux said he edited the thermald.conf file found in the zip file to allow higher thresholds than the stock one..you can review that file inside his zip file for answers on your query regarding when does the throttling starts..if i also remeber the throttling starts around 40'ish..some do correct me if i am wrong..
[Nexus 4 Original Android Development] omer7:
Thanks for ur response.

And can u plz tell me what does intelli-plug option do? Does it also look at battery temperature?
[Nexus 4 Original Android Development] omer7:
Ok, so I've checked the thermald.conf file. I'm not an expert at reading it, but I think throttling starts at 41C (battery temperature) and what I've understood from that file is, it doesn't throttle GPU (if it is true, then its quite good I think) :)

Attached is the last portion of thermald.conf file.
[Nexus 4 Original Android Development] kairi_zeroblade:
it overrides the built-in mpdecision(make-poor decision) hotplug binary with faux's own(intelli-plug) which is more efficient and more battery friendly hotplug driver..it does not have anything to do with battery..

and yup that's it..41c.. :D and yes it will not throttle GPU..

also would like to ask my previous post..if anyone can shed me some light..lolz

if i am mistaken you can correct me anytime guys..its just none was answering.. :D
[Nexus 4 Original Android Development] Michealtbh:
Is zram even necessary on our device? We already have plenty of ram
[Nexus 4 Original Android Development] 0.0:
I've been reading, and it looks like we don't need it right now. However, it is a nice option to have. Maybe future Android versions may require more RAM, so that's when zram will go into play
[Nexus 4 Original Android Development] trumanwu:
Hi, Guys, I am not sure if this has been discussed before.

After the latest Fauxclock update (yesterday?), I cannot open the application any more. It says "busybox is not installed, please install it from Google Play". I have busybox installed. Anyway, I updated the busybox from Google play this morning. But I still got the same message from Fauxclock. Before yesterday, it was running perfectly.

Anyone else got the same problem? How should I fix it?

thanks.
[Nexus 4 Original Android Development] ak:
Have you tried to clear data/cache and force closing into system/app tab?
[Nexus 4 Original Android Development] musashihatred:
What about Gamma Colors ?:D

i would really love to have faux editable gamma settings, saturation etc :)

everything else: flies! ^_^

Use it, Rocket High.

Screen of, Baby's Sleep

PS: Hi Anarkia :D joined the n4 club recently, cant resist.
[Nexus 4 Original Android Development] PJcastaldo:
So I got a black screen that said kernel crash at the top. Looked a lot like the green/yellow screen but no mention of modem. I was using the recommended settings in faux clock. The only thing new I tried was the zram set up, but I used the recommended settings for that also. After a reboot It pretty much booted to the green screen. Then again the black kernel crash screen. I reflashed my ROM and kernel and left the zram stuff alone and it hasn't happened again.

Running latest AOKP nightly and you b17 kernel.
[Nexus 4 Original Android Development] trumanwu:
I tried just now. But no luck...

Could you help me and tell me how to install busybox?

I was using WugFresh to root my device and busybox was installed at the same time.

This time I just go to Google Play and "update" the busybox (acturally "Busybox Free"). Is this the right one and the right way?

Thank you.
[Nexus 4 Original Android Development] JaylanPHNX:
You could try uninstalling FauxClock and rebooting, then reinstalling it.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] kishke:
You gotta go into the busybox app and update it from there, the app itself is only the installer.
[Nexus 4 Original Android Development] mumbhai55:
Gsam battery monitor showing kernel using almost 25% battery, is this normal? I'm on 016m and cm10.1.0.
[Nexus 4 Original Android Development] trumanwu:
Thank you both.

I updated busybox from inside. Now it is 1.21.0.

I also tried to uninstall and re-install FauxClock.

Still the same problem...

I really appreciate if anyone can give me any more help...
[Nexus 4 Original Android Development] kishke:
Try removing busybox from within the app and applying it again.
[Nexus 4 Original Android Development] trumanwu:
Thank you to all the guys above who helped me.

It turned out to be my fault...

Since the error message appeared after the update ( I still do not know why), my busybox is not installed somehow. Every time I entered busybox, actually I did not install it, but load the smart installer (?). Until I tried to remove the busybox as Kishke mentioned, I found out the uninstall button is greyed out.

After I install the busybox, FauxClock works well.

Thank you all again. Sorry to waste your time...
[Nexus 4 Original Android Development] ak:
+1 Another fantastic guy into the N4 family ... how are you my friend? :D
[Nexus 4 Original Android Development] saint_cow:
I am running the tbm stable kernel and have turned off mpdecision and lowered the minimum clock but have noticed that from within the app it looks like all cpu cores are active and jumping around all over the place. Is this normal? I also noticed that when I turned mpdecision off the minimum clock was set fairly high by default, should I have just left it at that or is lowering it to the minimum ok?
[Nexus 4 Original Android Development] saint_cow:
It jumps from minimum to random clock settings on all cores.
[Nexus 4 Original Android Development] musashihatred:
Im fine buddy. Jumping from faux to yours and vice versa :)

:cheers:

Sent from my Nexus 4
[Nexus 4 Original Android Development] KerryWood34:
Have you tried anarkia's ak/faux hybrid kernel?... Pretty awesome!!! :rock:
[Nexus 4 Original Android Development] ak:
MP off but do you have activate intelli? mp off = 4 core online

You can use cpu snake charmer ... max freq is capped to a specific value. :good:

Min clock is related to soc, for some phones is good for others no .. try and buy!
[Nexus 4 Original Android Development] saint_cow:
Intelliplug is on. I just used the recommended settings in the second post, are they up to date? I had to just go back to the mainline kernel as I was getting reboots with both the turbo boost ones. Might have just been that the clock settings are to high for my phone. What is the main benefit of the turbo boost?
[Nexus 4 Original Android Development] omer7:
What does "Read Ahead Buffer Size" mean? And what does its value mean?

Higher value mean higher performance?
[Nexus 4 Original Android Development] alxdadev:
Which ROM works best with this kernel?

Currently I use Carbon nightly but every time when I update fauxclock I get a reboot and yesterday the bootloop :(

After a full wipe and titanium backup restore I got back a working device but I was not so funny.

Thanks for your suggestions.
[Nexus 4 Original Android Development] alcurtis93:
Just use stock or cm10.1

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

Just use stock or cm10.1
[Nexus 4 Original Android Development] black_bottom:
after reading all posts regarding the simple gpu gov in this thread (i hope i didn't missed some ..) - I miss an explanation what this gov really does - in 3 oder 4 sentences and perhaps 1 or 2 examples. is there anybody who want to do this?

a lot of people describe the simple gpu gov as there favorite but in the OP there is still suggested ondemand .. hmm.

thank you ;)
[Nexus 4 Original Android Development] senthilrameshjv:
Guys,

I started to use this Kernel with Carbon ROM from today and Im so far liking the combinnation. However, no matter what CPU Max Clock i set in this Faux123 App, it sets itself to 1512 mhz. I even used Franco's app to change the settings and come back to Faux and see that it is set to 1512 mhz. Not sure why the CPU clock settings doesn't stick.
[Nexus 4 Original Android Development] den_breacker:
Post your log and last_kmsg in the Carbon thread (or in this thread) and hopefully they will fix this.
[Nexus 4 Original Android Development] ak:
I dont have problem ... for me max freq works ....

Do you use mpdecision?

Do you have a modified power lib into rom or stock?

---------- Post added at 02:17 PM ---------- Previous post was at 02:15 PM ----------

If you have proble of softreboot you can post a logcat to carbon thread ... last_kmsg is related to kernel problem.

Probably something is in conflict with faux app.
[Nexus 4 Original Android Development] alxdadev:
Well I was not near by a computer to gather the data and wanted to be unreachable.

I'm not sure if it's worth to reproduce this error and then no one take a look into this issue or it's starting to ping pong from room to kernel and app.

I will take a look into asylum with this kernel.

The reason why I want to stick to this kernel is faux sound:D
[Nexus 4 Original Android Development] JaylanPHNX:
Are you trying to overclock or underclock? Cause only the tb versions will OC.

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] drms12:
Any of the users here actually use the 600mhz gpu overclock?

Our device isn't the coolest phone available... The extra heart could damage the phone. Btw I'm not sure if all of the devices chip could handle that much oc.

By the way simple governor doesn't so anything for 16u version. When I installed the 17 beta 1 I could see the difference of the gpu clock in seconds.
[Nexus 4 Original Android Development] FrozenLord:
The boot loop is a known problem with Carbon.

I experienced that problem over several nightlies and tried different kernels, with the same results.

So I would recommend to abandon Carbon and switch ROM.

I am on Revolt (4.4) at the moment and, coming from Carbon, am not missing anything.

So far there have been neither freezes nor boot loops :)
[Nexus 4 Original Android Development] lazer155:
Is it normal that when intelliplug is enabled (mpdecision is disabled) (on the stock mainline version of the kernel, not either of the turboboost versions) the cpu minimum speed changes to 1.026ghz?

This is on the latest CM and I am using the fauxclock app to make adjustments. Snakecharmer is turned on along with eco mode and intellidemand. Undervolted globally -175mv on a fast binned chip.

Edit: I lowered the minimum frequency to 162mhz and it seems to work okay. I was just wondering if the default is 1.026ghz.

Does changing the I/O scheduler ever save battery life? I haven't read that it does throughout this thread or elsewhere but no one has ever said that it decreases life either.
[Nexus 4 Original Android Development] senthilrameshjv:
Sorry Anarkia i dont even know how to use modified powerlib. I'm using carbon ROM. I turned off Mpdecision and turned on Intelli plug. I am using Turbo Boost ultimate version 16 Faux kernel.

Jaylan, I am just trying to underclock at 700-900 mhz but it keep on going to 1.5 ghz.
[Nexus 4 Original Android Development] brunini:
Today I buy another Nexus 4. I unlock bootloader, install recovery and flash the latest beta kernel. 17b1.

The stock voltages are 50mv higher in the new device. Why this happen? Each device has a different voltage tab?