yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] awacker89:
Thanks guys! I'll give that a shot. I wasn't trying to be rude, I understand how much work goes into this free kernel. I still have ownership of the old Koush Bootstrap for Droid X. Buying apps for the sake of ROMing is part of the deal but you can't blame a guy for trying! ;)
[Nexus 4 Original Android Development] gho8t:
More info on sleep states if anybody is interested.

http://www.intel.com/support/processors/sb/CS-028739.htm

RATTA RATTA THUNDA CRATTA BOOM BOOM BOOM From My Nexus 4
[Nexus 4 Original Android Development] awacker89:
See above post. :) Thanks for the reply Faux, looking forward to seeing if I can make this baby zing and zong!
[Nexus 4 Original Android Development] mkamal23:
All this talk about Sleep, deep sleep, levels of sleep.... man I feel like there is some type of "Inception" stuff going on lol. Im loving it tho haha. So far so good with the new Fauxclock settings. Battery life seems legit, phone has been cool all day. No lag what so ever. No skipping with music. Im on 162 min-1.512 max. Intellidemand. Eco and Snake On. mpdecision off. -75 UV. And everything else is Battery recommendation from the OP. Thanks for everything.
[Nexus 4 Original Android Development] 0.0:
So...first it was turbo boost similar to Intel, now sleep states similar to Intel. I'm presuming more Intel-like tweaks coming later? :p

Sent from my Nexus 4
[Nexus 4 Original Android Development] gho8t:
Sleep states aren't Intel specific. They are generic forms of sleep. Apparently some were disabled on our SoC and Faux gave us the option to turn them on. That was just an explanation from Intel.

Sorry to confuse.

RATTA RATTA THUNDA CRATTA BOOM BOOM BOOM From My Nexus 4
[Nexus 4 Original Android Development] franciscofranco:
Power States were introduced for the MSM8x60 processor families in 2011: https://www.codeaurora.org/gitweb/q...it;h=3f2bc4d6eb5a4fada842462ba22bb6bbb41d00c7 and https://www.codeaurora.org/gitweb/q...it;h=dd93ecf782f7a88f5ffea62e7868254a1977797c (the other commit is too bloated) and they are present in every iteration after.

faux just exposed /sys/module/pm_8x60/modes/cpu0/ in his app and the stats for how long each CPU was in each mode. Such functionality is in stock kernel as well.
[Nexus 4 Original Android Development] 0.0:
Ah, ok. It was a small joke anyways :p

Sent from my Nexus 4
[Nexus 4 Original Android Development] Guto ViP:
So why has never been before?

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] coloxim:
And...

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] MasterJam882:
For me,using newest ES, the SoC settings do not stick. After closing the app and reopnening it the settings are deactivated again! set on boot also not working :(

Can you help me please?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Michealtbh:
Despite C3 showing off in the screenshot, I'm pretty sure it's on as the counter is going up. I also has C2 on briefly which is why the counter went up a bit.
[Nexus 4 Original Android Development] italia0101:
And ... If what Franco said is correct then we had this anyway?
[Nexus 4 Original Android Development] coloxim:
Of course...anyway...I don't listen much Franco..

;p

Anyway today while charging my phone stays at max freq

...??

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] :
mine was the whole time @ lowest frequency when i charged.. maybe its something on your end? like an app...
[Nexus 4 Original Android Development] coloxim:
I didn't touch nothing..

I had to reboot the phone...for fix it...

My phone was very hot..

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] android88:
What about when it's not charging?
[Nexus 4 Original Android Development] danslecarton:
Faux, mind to add SOC settings to the first post? Just for new guys ;)
[Nexus 4 Original Android Development] :
there are settings? thought u just turn it on or off :D i dont see any settings besides the one for turning it on and off
[Nexus 4 Original Android Development] coloxim:
The same...only reboot fix it...

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] android88:
Okay. What's your CPU governor? If it's performance, then change it to something else. Performance makes the CPU stay on the highest frequency.
[Nexus 4 Original Android Development] coloxim:
No..intellimand...

How can have the log?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] italia0101:
How are you getting below 384mhz ...

Scratch that
[Nexus 4 Original Android Development] TheDarkDefender:
Damn. The same happens with mine too. :confused:
[Nexus 4 Original Android Development] italia0101:
Btw . wanted to say thanks for the awesome colour preset on faux display ... It is the best I've come across . and I've tried them all .

Thanks a ton
[Nexus 4 Original Android Development] lloydcabraham:
Hey Faux, quick question. When I set SOC as advised with set on boot, my camera won't work at times either for face unlock or from the camera app. When it does work, it's extremely laggy. Problems go away when SOC disabled. Do I have an incorrect setting?
[Nexus 4 Original Android Development] italia0101:
Anyway we could have an option to enable all 4 cores online ?
[Nexus 4 Original Android Development] faux123:
I just tried face unlock and it's normal with soc power set. I'm not sure why you are experiencing lag
[Nexus 4 Original Android Development] android88:
At all times? There is a script you can run in the terminal emulator to enable it: echo "X" > /sys/devices/system/cpu/cpu1/online

With X being the minimum number of cores online at any time.
[Nexus 4 Original Android Development] faux123:
So you want to have four cores on all the time?

You can by using terminal or script.

Disable mpdecision and disable intelli-plug, then go to /sys/devices/system/cpu/cpux/online and set "1" to each cpux then you b will have all cores running...

Just curious why you want to do that?
[Nexus 4 Original Android Development] faux123:
Yes, C3 is during full system suspend only and so it will count up but at very slow rate. With my options, you can enter it even without full system suspend, that's the beauty of it.
[Nexus 4 Original Android Development] italia0101:
Thanks fellas .... Why ? I wanted to test out say having all cores online . but underclocked to say 1.1ghz ... See how it performed
[Nexus 4 Original Android Development] faux123:
He he, sensation Id 2.0 ;)
[Nexus 4 Original Android Development] android88:
C'mon Paul, I'm really looking forward to 013 :p.

I'm thinking about just compiling Faux kernel myself.

Are you planning on doing a code freeze anytime soon (for 013) so I know when/if I should compile it?
[Nexus 4 Original Android Development] Spec-Chum:
It's been stipulated that having all 4 cores on-line uses about the same battery as constantly bring them on-line taking them off-line etc but with the added bonus of extra snappiness :)

Can't say I notice much difference when I tried it...
[Nexus 4 Original Android Development] lloydcabraham:
Sorry faux, problem was on my end. I had set tasker to turn on screen rotation when screen off. This was what was causing the problem. Thanks for the quick reply though. Love your kernel.:cyclops:
[Nexus 4 Original Android Development] faux123:
If you have sensation 4g and running my kernel, then you would know the result (my sensation kernel with dual core active while screen on with c2 state enable while idling has better battery and performance than with hot plugging enabled :D )
[Nexus 4 Original Android Development] italia0101:
So yea . is it not worth it on the n4?
[Nexus 4 Original Android Development] Girn:
Faux, I have an issue with C3 not staying on in faux app.. Others C0 and C1 stay on fine.. I have it set on boot.. I close the app and check it again an hour or two later and C3 is off
[Nexus 4 Original Android Development] aSquard:
13 is up ^_^
[Nexus 4 Original Android Development] faux123:
Done!
[Nexus 4 Original Android Development] italia0101:
Anything changed from the 013 beta which I literally just flashed lol
[Nexus 4 Original Android Development] faux123:
no, if you like the tbm version, then it's exactly the same, I just recompiled it using my new buildbot
[Nexus 4 Original Android Development] Girn:
Noticed an update to fauxclock. But still same issue
[Nexus 4 Original Android Development] kishke:
Faux! 3rd time the charms I hope.
[Nexus 4 Original Android Development] Remoteconcern:
Seeing as no one seems to have the sysfs pathways for the new retention state, I did some digging. These would appear to be what the app does when you change the toggle :)

echo 1 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu1/retention/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu2/retention/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu3/retention/idle_enabled
[Nexus 4 Original Android Development] Banchu:
Broken WiFi, is it hardware, Kernel or ROM

Hi all,

one question, I ve been here in XDA for many years with different devices but it is the first time that happens to me :confused::

my wifi i damn broken. Impossible to turn it on, nothing happens... I ve changed ROM (back to stock), KERNEL (the same thing), factory et wipe everything in all roads but nothing, stays OUT OF ORDER :crying:. No problem with mobile 3G H+ thing, still on it, thanks god.

I ve heard in Galaxy Nexus XDA thread, the same, with back the phone to seller but what a strange thing.

I think it heated so much that the wifi thing is burned or something. Any ideas?

I ll phone Google tomorrow and bck it up here,

By the way, thanks Faux123 for all, and thank you all, for all your great advices we can get here :o
[Nexus 4 Original Android Development] Stryder5:
If you went to stock everything and it doesn't work, warranty.
[Nexus 4 Original Android Development] Aetos7:
Stable version, right?
[Nexus 4 Original Android Development] Banchu:
Indeed, I ll do that, just for information, put it in freezer!!:silly:
[Nexus 4 Original Android Development] faux123:
Same issue what?
[Nexus 4 Original Android Development] samwebbo1990:
I've just installed the latest CyanogenMod M build (M3) and have heard about the change in the ROM to do with WiFi. I want to install the latest kernel (v13) but heard it will really affect my battery with custom kernels :( Is this true because I would much prefer to be on Faux's kernel rather than CM's? :)
[Nexus 4 Original Android Development] faux123:
WiFi on android is made up of 2 parts.

Userspace drivers (proprietary) + kernel drivers.

The changes made by CM were to the userspace drivers. It should be fine with my kernel.
[Nexus 4 Original Android Development] samwebbo1990:
I was originally on Franco and heard it would drain the battery but I much prefer your kernel so wasn't sure. Thank you for the quick reply :)
[Nexus 4 Original Android Development] Aetos7:
I have just installed the latest version..

In Soc Setting, which values i have to set?

And i'have to enable C0, C1, C2, C3? All?
[Nexus 4 Original Android Development] android88:
Yup! :)
[Nexus 4 Original Android Development] samwebbo1990:
All but C2
[Nexus 4 Original Android Development] mariotme:
C3 isn't sticking for me after I restart the app :banghead:
[Nexus 4 Original Android Development] coloxim:
You have the same problem? The CPU stay at max freq?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] chrone:
I noticed each time i came from franco, did a reset kernel from faux, and flashed faux enhanced stock or the mainline kernel, my screen won't turned off when offline mode charging.

To fix this problem, i had to "fastboot flash system system.img" within fastboot bootloader mode using google factory image reset, reflashed faux kernel back, and voila, the screen now turned off when offline mode charging.

Just want to share this if you experience one. It's not faux kernel's fault. :)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Aetos7:
Ok.. why not C2?
[Nexus 4 Original Android Development] coloxim:
Now with last faux my CPU stays at 1134...

Reboot doesn't fix...

Whatsup?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] haze_nme:
The commit that was added to CM 6 days ago was already in Faux's source a month ago.

CM Mako Kernel commit from 6 days ago

https://github.com/CyanogenMod/lge-kernel-mako/commit/85ba2bc0fc741a663c094ccd84faa3b18d21e292

Faux123 Mako Kernel commit from a month ago

https://github.com/faux123/mako/commit/221d6ac6e2c0a4b6e98a1e33fb747cc064e35d31
[Nexus 4 Original Android Development] jarjar124:
Doesn't matter since you can't change it.
[Nexus 4 Original Android Development] gho8t:
This is nice because every time I would close faux clock and open it back it would say C2 and C3 were disabled again. I checked the files and they are all actually still enabled. Thanks

RATTA RATTA THUNDA CRATTA BOOM BOOM BOOM From My Nexus 4
[Nexus 4 Original Android Development] alleyezondisromo:
Anyone in her e use tasker to keep faux clock open at boot ?
[Nexus 4 Original Android Development] tanmay.01:
I have used stable v12 ... Only got assertions 3.5 to 4 hrs on screen time. Past 2 days I am on default xylon kernel. Its giving me 5hrs on screen time. Almost she apps used and the same build. Don't know the reason for this diff. Will test this new release from Sunday.. Thanks

Sent from my Nexus 4
[Nexus 4 Original Android Development] phewizzo:
13 stable is out.
[Nexus 4 Original Android Development] expertzero1:
What settings are you using? Are you using fauxclock? Have you been using your phone on wifi more / data?
[Nexus 4 Original Android Development] Ulver:
I'm using the latest 13tbu with min 162 and max at 1.5. I have intellidemand, eco off, snake charmer off, mpdecison off. When looking at the 4 cores clock speed via the faux clock app, none of the cores ever go offline no matter long I let it idle. Shouldn't it drop down to 1 core at 162 MHz eventually?

Once I switch it to eco mode all cores go offline except the one core at 162.

Is it the app just not displaying the correct numbers or is there something wrong? Thanks
[Nexus 4 Original Android Development] thebrainkafka:
Hint for soc settings.

Set c0,1,3 and tic set in Boot. Now leave APP via home button and reboot.

Now all ticed c states are stable set.
[Nexus 4 Original Android Development] mariotme:
lol that actually works! :highfive:

Thank you

PS out of thanks for the day sorry
[Nexus 4 Original Android Development] xflowy:
would you mind telling me why i shouldnet use c2?

aand: can i use the soc settings with any governor?
[Nexus 4 Original Android Development] danslecarton:
Huge thumbs up for changelog in the folder!
[Nexus 4 Original Android Development] Girn:
Didn't work for me
[Nexus 4 Original Android Development] Guto ViP:
No problem here.

Enviado de meu Nexus 4 usando o Tapatalk 2
[Nexus 4 Original Android Development] 0.0:
@faux: idk if it is an app bug or kernel bug (i say app) but when moving the cpu freq sliders, a bunch of other numbers are displayed, not the set freq numbers. for example, if i want to go from 1.512ghz to 1.242ghz, when moving the slider it shows a bunch of other numbers along the way. does that make sense? do i need a logcat for that?
[Nexus 4 Original Android Development] Locksmith81:
I believe its by design :cool:
[Nexus 4 Original Android Development] Stryder5:
Just got a kernel panic. This is on v013 beta 11_r2 though, so I'm not sure you'll even want to look at it. Just updated to v013 tbu after I got the panic so hopefully it won't happen again.

I was also undervolted around -75 or so.

View attachment last_kmsg.txt
[Nexus 4 Original Android Development] ChongoDroid:
Any particular reason why we're not enabling c2

Sent from my Nexus 4
[Nexus 4 Original Android Development] italia0101:
What sort of undervolts are people using for the lowest freq . I've been on 700 all day and its stable
[Nexus 4 Original Android Development] naveediftikhar:
any plans on releasing the enhanced stock version with soc features?
[Nexus 4 Original Android Development] Ulver:
Its all good now. Could have been some of my background processes running.
[Nexus 4 Original Android Development] djvoleur:
As mentioned a couple pages back...it's already there...
[Nexus 4 Original Android Development] faux123:
It will work with enhanced. only bug fixes will go into enhanced stock.
[Nexus 4 Original Android Development] faux123:
your GPU memory got corrupted :p Maybe use individual UV instead of global uv.. and raise the min a bit.
[Nexus 4 Original Android Development] ChongoDroid:
10char
[Nexus 4 Original Android Development] JaylanPHNX:
That's answered a few pages back. 2 and 3 are almost the same, so why put an extra step between sleep and wake?

Sent from an N4 blessed with AOKP and sanctified by Faux123!
[Nexus 4 Original Android Development] Savant:
Sent you a pm bud .
[Nexus 4 Original Android Development] Globespy:
I'm still having issues with SOC settings sticking (set on boot selected). Everything else sticks fine?
[Nexus 4 Original Android Development] faux123:
haven't' seen any...
[Nexus 4 Original Android Development] Savant:
Xda gremlins. I will send them again.

Edit: resent to you now.
[Nexus 4 Original Android Development] kishke:
Faux! 4th time trying, respond that you've seen it.
[Nexus 4 Original Android Development] sxp:
i flashed 13m kernel

162mhz to low some time laggy

a try set low frek 270mhz but only core 1 set

all 3 core set 162mhz

intelidemand and snake charmer On
[Nexus 4 Original Android Development] Globespy:
Are you saying that you can set individual frequencies for each core? I didn't think that was possible? I was only aware of setting individual voltage settings for each frequency, but that would be across all cores?
[Nexus 4 Original Android Development] faux123:
ok.. I will try to incorporate the translations soon... So much to do.. not enough time :angel:
[Nexus 4 Original Android Development] faux123:
voltage is applied to the chip always as a whole. there are NO individual core voltage control. It has always been to the SOC as a whole.
[Nexus 4 Original Android Development] Globespy:
Bump... anyone able to answer this? Thanks.
[Nexus 4 Original Android Development] faux123:
Instability usually occur at edge conditions... so > 1.5 GHz and < 384 MHz are more susceptible to issues than say 1 GHz.

My advice is to use Global voltage control first to find a stable OVERALL UV value. Then use the individual UV to experiment and push it a bit against your chips limitations ;) (Remember TO BACK UP YOUR IMPORTANT STUFF BEFORE TRYING ALL THESE!!!!)
[Nexus 4 Original Android Development] Savant:
I sent it, so I hope it doesn't get lost this time. Thanks Paul.
[Nexus 4 Original Android Development] MrPhilo:
Today I was travelling and was going to play some play some PS1 game on FPse. When I clicked on it everything frozed and my phone turned off to boot in the Nexus logo. I left it on the Nexus logo for 10 minutes but my phone was too hot which I turned off after. After trying to bootup again it failed and stayed on the Nexus logo, so I went in recovery (TWRP) and backed up and then tried flashing the ROM (CM10.1), Kernel (Faux obv), Gapps again but still stuck on the Nexus logo.

I couldn't do nothing since I was stuck on the train so I had to wipe everything and start a fresh CM10.1. After 5-6hour I got home and just pulled the last_kmsg. I don't think its faux kernel related as everything was working fine. But I was wondering if you know what the problem is?

It be awesome if I could solve the problem, I backup every month but my last backup wasn't really recent and I dont want to lose certain stuff.
[Nexus 4 Original Android Development] sniperfox47:
kernel branches

What are your source branches?

I'm trying to build your kernel with ext2/3/4 and tmpfs security tags enabled (required for a fedora chroot). However when I build the main branch (enhanced_stock) with the config from your turbo boost ultimate /proc/config.gz a lot of features such as intellidemand, intelli_plug, and eco mode are disabled.

I'm assuming this is because those features are built from a different source branch so which do I need to use?

Any help you can provide would be greatly appreciated. Thank you in advance.
[Nexus 4 Original Android Development] faux123:
The log you posted is unfortunately not tied to your original issue.

From your description, FPse crashed hard, corrupted some important system data which caused it stay in the boot logo (whenever you see the forever logo, the kernel is actually booted already and running. You can verify this by using ADB and you will see kernel is happy and alive. It's Android that refused to complete its initialization because some of the critical system Database or settings got corrupted :( ).

Of course without the original log, I couldn't help you or the FPse author to figure what crashed hard.... Usually low level emulation software use Android NDK interface to gain performance to bypass the Dalvik VM, but the bad side-effect of using NDK is that by directly accessing the hardware, when it crashes, it's less protected than Dalvik's Force Close interface.

I hope you backed up your important data on a regular basis (ie, using Titanium backup with scheduled backups).
[Nexus 4 Original Android Development] faux123:
this is the mainline branch https://github.com/faux123/mako/tree/rb_jb_mr1.1
[Nexus 4 Original Android Development] MrPhilo:
I fixed it :), I just deleted the fpse apk (.asec) in the tar backup file and it booted fine after :) happy me haha! Time to backup :), cheers for replying though!
[Nexus 4 Original Android Development] JeanEatsWorld:
Is there a way to turn on/off the c0, c1, c2, c3.. without the faux app?
[Nexus 4 Original Android Development] Ace42:
Look on page 990.
[Nexus 4 Original Android Development] JeanEatsWorld:
Thanks but I can't find the answer..

Btw I'm very new to scripts..
[Nexus 4 Original Android Development] tanmay.01:
Yes WiFi most of the time. But then used it on both kernels. Governor was on demand for both , scheduler was also the same. Intact some times I enabled eco on faux kernel. The default xylon one had 4 cores running. I guess they are using sabermod kernel.

But will report after using this never version.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Charles_l:
try this script. it works for me. c0, c1, c3 enabled.

# Soc on
echo 1 > /sys/module/pm_8x60/modes/cpu0/wfi/idle_enabled
echo 1 > /sys/module/pm_8x60/modes/cpu1/wfi/idle_enabled
echo 1 > /sys/module/pm_8x60/modes/cpu2/wfi/idle_enabled
echo 1 > /sys/module/pm_8x60/modes/cpu3/wfi/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu0/retention/idle_enabled
echo 1 > /sys/module/pm_8x60/modes/cpu1/retention/idle_enabled
echo 1 > /sys/module/pm_8x60/modes/cpu2/retention/idle_enabled
echo 1 > /sys/module/pm_8x60/modes/cpu3/retention/idle_enabled

echo 1 > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
[Nexus 4 Original Android Development] resynx:
Using 013-tbu, this is the smoothest I've ever seen my device! :D
[Nexus 4 Original Android Development] sniperfox47:
Ahh thank you for the help. I figured it would probably be one of the mr ones, but I didn't want to guess if there was even the slightest chance that messing up could damage my device.

[edit] Dur! I'm an idiot xD I just looked at the graph and realized that's the only branch that's been updated in like half a month. Sorry for my stupidity, and thanks again for the help.
[Nexus 4 Original Android Development] aSquard:
Yes, 013-tbu is awesome and the SoC options REALLY help with the battery life. After a full days' work and weak 3G, I still had 60% battery instead of 25-30%!

Nexus⁴ Enlightened with ParanoidAndroid and XDA Premium
[Nexus 4 Original Android Development] resynx:
Wow your battery really jumped up by that much? Amazing! :eek:

What was your screen on time if I may ask?
[Nexus 4 Original Android Development] wera750:
I can also see a difference in battery with the new soc options! Great job Paul!