yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] noneabove:
Do you have his app? I think it's disabled by default in 03
[Nexus 4 Original Android Development] falconrulz:
Use this application and go to the 'Specifics' section and you'll see an option to Enable S2W, in Beta 3, Faux has disabled S2W by default.

- https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
[Nexus 4 Original Android Development] zimphishmonger:
Exact same feeling here

Sent from my Nexus 4

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

It's also an option in faux clock

Sent from my Nexus 4
[Nexus 4 Original Android Development] otariq:
The new beta just gets stuck on the Google splash screen anyone else having this problem
[Nexus 4 Original Android Development] mundixx:
Flash reset kernel from OP, then flash latest beta again..
[Nexus 4 Original Android Development] 0.0:
Did anyone check out faux's latest tweet? Can't wait for that new beta and updated app!

Sent from my Nexus 4
[Nexus 4 Original Android Development] sryche:
can u share your settings please.
[Nexus 4 Original Android Development] Bluewall:
Not a real problem but I wonder, am I the only one only see cpu0 and cpu1 online ?

The Faux app or, for exemple, System Tuner, never show me freq on cpu2 and cpu3 when I open them ?
[Nexus 4 Original Android Development] 0.0:
are you on eco mode? if so, that is the reason why
[Nexus 4 Original Android Development] Bluewall:
You mean eco mode only use two cores no matter what ?
[Nexus 4 Original Android Development] Michealtbh:
Yes
[Nexus 4 Original Android Development] jamesj999:
Having wake lock issues and battery drain with 3b03. Anybody know what this is? Shows under kernel wake locks.
[Nexus 4 Original Android Development] undercover:
Faux, will you be releasing gamma control source? Thanks.
[Nexus 4 Original Android Development] Der_Schubi:
I have noticed my device doesnt get into deep sleep as soon as I plug in the charger. Do you have the wakelock on battery?

Gesendet mit Tapatalk 2
[Nexus 4 Original Android Development] kwerdenker:
Deep sleep is a battery saving mechanism. No need for that while you are right at the source ;)

Send from my secret moonbase via space carrier pigeons
[Nexus 4 Original Android Development] Der_Schubi:
That would be OK if the N4 wouldn't turn into a boiling plate...

Gesendet mit Tapatalk 2
[Nexus 4 Original Android Development] kwerdenker:
If your phone gets hot while charging and doing nothing else, you should check for some wild running apps or services. Not going to deep sleep means the cpu always clocks with the minimum frequency but should not scale higher without any load.

Oh and also the loading of the battery itself leads to some warming up of the device. Can't skid around the physics :)

Send from my secret moonbase via space carrier pigeons
[Nexus 4 Original Android Development] Der_Schubi:
Thats OK, but in deep sleep it also would get fully charged earlier. My Galaxy Nexus also goes into deep sleep on AC, why not the N4? Is this behavior faux's kernel or stock?

Gesendet mit Tapatalk 2
[Nexus 4 Original Android Development] undercover:
Stock.
[Nexus 4 Original Android Development] arich:
In response to previous posts regarding USB fastcharge: Many cars and car stereos these days have a USB port built in, mostly for iphone connections. However, when you plug and android phone in it is identified as USB and you only get a trickle charge vs the full charge the port is capable of. That is why a USB fastcharge option is desirable.
[Nexus 4 Original Android Development] Sucalakafufu:
so. anyone else get fauxclock intermittently not recognizing the kernel correctly? the app works fine again after restarting it
[Nexus 4 Original Android Development] jamesj999:
This was on battery, yes. It's common to get more wakelocks when the device is charging.

It seems to be something to do with audio. I've closed all apps and tested in BBS. Using 002m it's only happening about 10% of the time which is fine, but before it was about 90% of the time, absolutely killing my battery!
[Nexus 4 Original Android Development] slind:
Yes - Device is being identified as Tegra 3 XXX. Restart works fine.
[Nexus 4 Original Android Development] wera750:
I just wish I could run this kernel again :mad:
[Nexus 4 Original Android Development] housry23:
If it has to do with audio, try turning off some of the sounds when touching the screen in sounds settings. I don't know what rom you're using, but usually when audio is causing wakelocks, this is the issue. Not 100% of the time, but it's definitely a good possibility.
[Nexus 4 Original Android Development] jamesj999:
Thanks for the reply! I'm running CM10 (27/12 nightly). The only sounds I usually have switched on are ringtones/notification tones, but the phone has been on vibrate for most of the day. I can't seem to find anything else on Google, but do you know of anything else that may cause this type of wakelock?
[Nexus 4 Original Android Development] brar.arsh:
What is the best AMOLED type setting for display in this kernel??

I mean RGB and gamma1 gamma 2 values??
[Nexus 4 Original Android Development] Michealtbh:
https://docs.google.com/spreadsheet/lv?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E

Take your pick. I personally find the settings by Acer73 best.
[Nexus 4 Original Android Development] bfspider:
+1 for Acer's settings. The calibrator he used seems to be accurate.
[Nexus 4 Original Android Development] endiz:
Would love to see this implemented, I'll donate a case of beers if you can achieve this!

Also, not sure if this can be fixed with the kernel but the hotspot doesn't work when LTE is enabled.
[Nexus 4 Original Android Development] n82k:
Yes I have his app and enabled it

Sent from Nexus 4 - cm10 - faux kernel003 beta003

---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------

In a word, yes

Sent from Nexus 4 - cm10 - faux kernel002 beta005
[Nexus 4 Original Android Development] realfelix:
mhh, got a question bout installation instructions.. do i have to install the mainline kernel described in the op before flashing the new 03 beta? or is it ok to directly flash from cm stock to this
[Nexus 4 Original Android Development] Lownita:
Got a question here: You say "immediately press vol up + vol down." How do I press up and down at the same time, that is not possible. Or am I getting that wrong?

Thanks!
[Nexus 4 Original Android Development] undercover:
It is possible. Although button looks like a rocker, it's not really, it's too separate buttons connected in the middle.
[Nexus 4 Original Android Development] Locksmith81:
They are 2 different kernels... It's OK to flash from stock.. Backup always
[Nexus 4 Original Android Development] n82k:
Should be fine to flash the beta over cm, its complete. You would use the reset kernel if you have a problem and need to reinstall a beta. Every time you update the cm or rom ref lash the beta over it as this will reset your kernel to cms as well.

Sent from Nexus 4 - cm10 - faux kernel002 beta005
[Nexus 4 Original Android Development] evonc:
Is anyone noticing a msm_otg wakelock from 003beta3? Not sure what's causing it but it has been destroying my battery since last night.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Stryder5:
I read somewhere that someone mentioned this kernel has sweep2wake. Is this true? If so, how does it work? I'm running on kernel 003 b03.
[Nexus 4 Original Android Development] samwebbo1990:
I think that's a wake lock from when you charge your phone, nothing to worry about :)
[Nexus 4 Original Android Development] SIGUEL:
Hold both down at the same time.

Sent from my Nexus 4
[Nexus 4 Original Android Development] endiz:
You need to download FauxClock from the play store and enable sweep2wake in the MISC menu

https://play.google.com/store/apps/details?id=com.teamkang.fauxclock&hl=en

How does it work? From the bricked thread: "Sweep2wake works with IRQs (Interrupts). An interrupt can be best imagined as you doing something, like shopping at the local super market, when someone jumps in front of you and punches you into your family jewels. You will most certainly not just continue shopping. In technical terms: An Interrupt interrupts the normal operation of a program and executes "special" code instead. So if you touch your screen, an interrupt is send on which the touch driver reacts. That's it. Since we have a capacitive touchscreen you also do not need to worry about any pressure onto the screen."
[Nexus 4 Original Android Development] evonc:
You can also enable sweep2wake by using an init.d script to enable it on boot or via apps like SManager.
[Nexus 4 Original Android Development] Stryder5:
Can you please elaborate on this? What command do I need to run?
[Nexus 4 Original Android Development] faux123:
To enable or disable sweep2wake feature, simply do the following in a terminal or script:

su

echo 1 > /sys/android_touch/sweep2wake (enable)

echo 0 > /sys/android_touch/sweep2wake (disable)
[Nexus 4 Original Android Development] MontAlbert:
This is the only time I will need it and why I'd like to see it implemented too. It's annoying plugging the phone into car stereo and having the battery still drop even though it is "charging"...
[Nexus 4 Original Android Development] faux123:
Again, this will ONLY work if your car audio USB can supply > 500 mA of current... If not, then this option will NOT do anything. :p
[Nexus 4 Original Android Development] DroidRC1:
So how soon till we get our hands on beta5 :D
[Nexus 4 Original Android Development] arich:
Which mine can (and isn't it all about me??) :p
[Nexus 4 Original Android Development] faux123:
Very soon :D I will just leave this here!
[Nexus 4 Original Android Development] 0.0:
Will the app have profiles like setcpu anytime soon? That'll be awesome! :D

Sent from my Nexus 4
[Nexus 4 Original Android Development] pnut22r:
Also, it would be wonderful of the app had a set on boot delay.

P.S. I used a lot of your recommenced settings you posted awhile back. When my phone boots, the touch screen doesn't work. All of the hardware buttons work, and it odds fully booted, but no touchscreen. If I wipe and reflash the kernel, its fine. What would be causing this? Thoughts?

Disclaimer: I am a Noob, forgive me
[Nexus 4 Original Android Development] Sucalakafufu:
such a tease >_<
[Nexus 4 Original Android Development] evonc:
It's live

Sent from my Nexus 7
[Nexus 4 Original Android Development] faux123:
Kernel 003 Open Beta 5 is out!!!!

Complete details here:

https://plus.google.com/u/0/109078966818501160423/posts/Jnri9bH3fRG
[Nexus 4 Original Android Development] alienmind:
Bootloop on v3b5. Can't get past Google splash screen, no adb logs available

I'm on a CM10.1 kanged on 25/11/2012, no extra mods

Thanks

EDIT: Reflashed and everything OK

EDIT2: After 3 minutes, sudden reboot. last_kmsg below

https://www.dropbox.com/sh/p4gvur9u0j00oaa/BgbCDOSXYk/last_kmsg-20121229.txt
[Nexus 4 Original Android Development] faux123:
reflash CM 10.1 ROM, then load my kernel again. If you come from Franco's kernel, you MUST do this every time because of his modified ramdisk issues.
[Nexus 4 Original Android Development] Sucalakafufu:
looking good ;)
[Nexus 4 Original Android Development] faux123:
can't access your dbox :(
[Nexus 4 Original Android Development] alienmind:
Thanks, I figured it out. I reported another sudden reboot, it was while playing around with faux app with the color presets. If I manage to reproduce it will report back.

Another question... How is implemented intelli_plug over mpdecision. Is the binary overwritten? It doesn't look so.I would also appreciate clarification about which governors are affected, I guess all of them? In the app every governor has set "Use mpdecision" as "on", does it mean I'm using the new binary?

Sorry if it has been answered before, I've been using Franco's for a while and last time I checked only intellidemand had mpdecision set to off as preferred...

Many thanks for the kernel btw

EDIT: Updated last_kmsg link here https://www.dropbox.com/sh/p4gvur9u0j00oaa/BgbCDOSXYk/last_kmsg-20121229.txt
[Nexus 4 Original Android Development] lightningstalon:
I was becoming convinced that switching to Brick kernel was a good move...then you release this beta 5. Looks awesome thanks Paul - the only thing I wish it had was a min frequency of 192 MHz. I've been using it and there's absolutely no lag in bricked. Got better undervolting on bricked but once we have custom voltage for each frequency, should be about the same.

By the way, faux, do you suggest using intellidemand or ondemand for better battery life?
[Nexus 4 Original Android Development] faux123:
EXT4-fs (mmcblk0p22): recovery complete

EXT4-fs (mmcblk0p23): recovery complete

Your file system had data corruptions :( You better backup your important data and you may need to nuke your device and reformat everything if you continue to experience these random reboots :(

Did you disable fsync using his kernel? if you did, you could have higer chance of data corruptions.
[Nexus 4 Original Android Development] Hereisphilly:
Thanks for the update! Man this thing flies now!

Just to confirm, if I have intellidemand selected as the governor, with mpdecision and eco mode off, intelli_plug is still at work?
[Nexus 4 Original Android Development] faux123:
192 MHz is not really important. If CPU has nothing to do, then it should/would go into deep sleep, so minimum frequencies do NOT matter in those cases. Qualcomm removed 192 MHz from their Krait CPUs for a reason. I doubt they do it to increase battery drain :p
[Nexus 4 Original Android Development] faux123:
Intelli_plug is running as soon as mpdecision is disabled.
[Nexus 4 Original Android Development] Der_Schubi:
Intelli_plug is active as soon as mpdecission is off.

Gesendet mit Tapatalk 2
[Nexus 4 Original Android Development] meangreenie:
Do we need the app to use intelliplug then?
[Nexus 4 Original Android Development] 3bs11:
I've never used fast charge before. Are there any negative impacts to using it? Worse battery life in the long run or overheating or something?
[Nexus 4 Original Android Development] droidmeup:
I feel that you have more feature on your kernel and app than any others and its delivering fantastically amazing. A big thank you for your development :)
[Nexus 4 Original Android Development] faux123:
only works with USB chargers with > 500 mA current output but were mis-identified as normal USB chargers.

TBH, I don't know the long time side-effect of it could/would be. I don't use it personally because I have proper chargers and they all identify as AC chargers when used.
[Nexus 4 Original Android Development] faux123:
App is NOT necessary or mandatory to use intelli_plug.

simply do this in terminal or script:

"stop mpdecision"

intelli_plug is automatically active.
[Nexus 4 Original Android Development] DJMartini:
Faux,

Franco says he fixed the man_hsic wakelock issue. Have you looked into it?

http://xdaforums.com/showpost.php?p=36014982&postcount=3363[/QUOTE]
[Nexus 4 Original Android Development] jacklebott:
Intelli_plug doesn't automatically activate/deactivate when I disable/enable mpdecision via script. It only works that way using your app

When I enable mpdecision via script, it shows it as running (and has the signature 1026MHz touch boost) while "/sys/module/intelli_plug/parameters/intelli_plug_active" simultaneously has a value of 1
[Nexus 4 Original Android Development] faux123:
Intelli_plug is running all the time, so you need to stop mpdecision from clobbering it. The app just make it automatic, but not necessary.
[Nexus 4 Original Android Development] noizy1234:


+1 would love to know this as well
[Nexus 4 Original Android Development] jacklebott:
Ah so they do both run at the same time when mpdecision is enabled
[Nexus 4 Original Android Development] faux123:
Yes!
[Nexus 4 Original Android Development] jacklebott:
Just really confused me because you said Intelli_plug was a replacement for mpdecision, so I figured it'd stop mpdecision while running
[Nexus 4 Original Android Development] meangreenie:
Why not just rename mpdecision ? Like the bricked kernel
[Nexus 4 Original Android Development] jacklebott:
Because I don't want to get rid of mpdecision (it's still the fastest for gaming), I just misunderstood how Faux described Intelli_plug
[Nexus 4 Original Android Development] lightningstalon:
Is there a reason why there is no longer a mpdecision toggle in FauxClock?

Also, will there eventually be an option to UV under 80000?

EDIT: in bricked kernel, it renames mpdecision with a _bck appended and even the reset kernel will not fix it. Use ES Explorer to undo the renaming.
[Nexus 4 Original Android Development] jacklebott:
It's there for me. Did you do anything to the mpdecision binary?
[Nexus 4 Original Android Development] droidmeup:
Update your app and kernel.
[Nexus 4 Original Android Development] SeaSeeC:
Well he said that he changed USB EHCI drivers so that should help with the msm_hsic_wakelock.[1]
[Nexus 4 Original Android Development] jacklebott:
So what happened to v3beta4 anyway? Though v3beta5 was truly a big enough update to warrant the jump I suppose
[Nexus 4 Original Android Development] lightningstalon:
I have updated both to the latest versions.
[Nexus 4 Original Android Development] n82k:
If you aren't using intellidemand mpdecision would be on rendering intelli_plug "clobbered".

Sent from Nexus 4 - cm10 - faux kernel00³ beta005

---------- Post added at 02:18 AM ---------- Previous post was at 02:18 AM ----------

Or so that's how I understand it

Sent from Nexus 4 - cm10 - faux kernel00³ beta005
[Nexus 4 Original Android Development] Sucalakafufu:
he didnt release b4 cuz b5 is "MOAR FUN" :P check his twitter lol
[Nexus 4 Original Android Development] 0.0:
with the faux app, i set the max freq to 1.5ghz. but when i reopen the faux app, sometimes the max ends up being 1.2ghz. i would have to move the slider back to 1.5ghz again.

is that because of the thermal restriction thing, or is that just a bug in the app? if its a bug, could that be fixed? thanks. loving the app and kernel so far!

edit: another bug, dealing with the voltage. the app basically sometimes subtracts volts straight from where you are instead of taking it from the default values. thus if i got lower or higher voltage, it gives inaccurate readings. especially lowering the voltage, where it reboots my phone when my phone can actually run it at that voltage.
[Nexus 4 Original Android Development] iFalcon:
Love the kernel.

I have been running cm10. Does anyone know why it takes about 30 - 45 seconds for the faux kernel tuner tool to launch? It sits at setting proper permissions and superuser issues multiple granted permission messages. It launches instantly when using faux kernel with other ROMs?

Thanks
[Nexus 4 Original Android Development] faux123:
Minimum single core is set to 702mhz, this is done by design. It's called minimum performance lock. When in multi-core mode, minimum for all cores will be 384 MHz.
[Nexus 4 Original Android Development] Imppy:
How is 005 compared to 004?
[Nexus 4 Original Android Development] ceroglu:
Thanks man, that is what I thought. Awesome work for the kernel, it seems to be runing pretty good so far!

I have a question, did you have a chance to look at Optimus G kernel to compare with N4? I am curious to know why the same chip and hardware has much better battery life on Optimus G? thanks.
[Nexus 4 Original Android Development] cmikeh2:
Both feel extremely responsive to me. Benchmark wise the (and remember this coming from no OC to OC) I've gone from 2000 to 2300 in Geekbench.
[Nexus 4 Original Android Development] IAmAN00bie:
I'm loving the new kernel. Has anyone come up with some good color control settings yet?
[Nexus 4 Original Android Development] Imppy:
What program do you use to set UV?
[Nexus 4 Original Android Development] Prod1702:
I am using 200,200,255 for color with faux's app its a little more blue on the whites but it feels more like my galaxy nexus screen.
[Nexus 4 Original Android Development] danielsf:
May I ask if you could increase the touch boost for intellidemand to ~1ghz? As I have two nexus 4's on stock the other on 005 and running intellidemand. The stock was smoother on heavier web pages and apps when tracking your finger. After messing around, if I set the min freq to 1ghz then the smoothness difference was none existent between the two nexi even-though the stock was scaling all the way to 1.5ghz when screen was being touched. What do you think please?
[Nexus 4 Original Android Development] cmikeh2:
I don't know about free options but Faux's own program supports undervolting to up to .1 V and it's always nice to support the dev. another option I know of is system tuner which provides a greater range of options. Regardless, use only one app for this sort of thing out you'll have problems.
[Nexus 4 Original Android Development] faux123:
Once I create a powerHal for intellidemand 4.0, the touch response will be better. Remember this is without project butter enhancements :p
[Nexus 4 Original Android Development] djkinetic:
Wow, the kernel is already pretty damn smooth.
[Nexus 4 Original Android Development] 0.0:
the 005 kernel seems to have the color of the screen have a faded yellowish color. the screen looks somewhat washed out. i went back to the jellytime kernel, and the yellowish color disappeared. it could just be my phone. anyone else experiencing this? look in "settings" to see the color
[Nexus 4 Original Android Development] loscassapalle:
for me also in built 5, the clock speed go back to the default one after some seconds
[Nexus 4 Original Android Development] Letitflow:
Its not just you, i experienced exactly the same thing.
[Nexus 4 Original Android Development] Prod1702:
No problems here. Also you can change the colors using faux's app. This has helped with the color a lot for me.
[Nexus 4 Original Android Development] faux123:
I didn't touch the colors

at all. That's weird.
[Nexus 4 Original Android Development] undercover:
Hey Faux. Quick question. Kernel (stock and custom) seems to be using 1ghz as stop over before jumping to full 1.5. What is causing this? And wouldn't less aggressive scaling at top values and no "stop over" at 1ghz perform better? I've monitored cpu for a bit, and it looks like it hardly uses anything in between 1 and 1.5 ghz. I much prefer how Sensation handles it utilising full range of the table. I'm talking about ondemand for both instances.

Any thoughts?
[Nexus 4 Original Android Development] faux123:
1 word, powerHal. Project butter (aka jellybean) uses powerHal to control CPU behaviors from the ROM, but most of the implementations are crappy because they hard coded the frequency jumps and aren't flexible and/or too aggressive (in our case). Until I hack my own powerHal to replace the default one, this is normal stock behavior.
[Nexus 4 Original Android Development] mastibeta:
So, i definitely am not getting deep sleep with intellidemand governor, any ideas?
[Nexus 4 Original Android Development] ctfrommn:
Did you wipe cache/Dalvik prior to flashing? Definitely is sleeping for me.
[Nexus 4 Original Android Development] gknnn':
I Got a problem with b5, notifications (like WhatsApp) comes to late when screen is off. When its on i Got no problems.

Some One know how to fix it? I use fauxs ernergy saving settings.

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Michealtbh:
Switch to SuperSU
[Nexus 4 Original Android Development] droidmeup:
Use SuperSU by chainfire
[Nexus 4 Original Android Development] iFalcon:
Much appreciated!
[Nexus 4 Original Android Development] Michealtbh:
Snake Charmer doesn't seem work in the latest beta, 1.5GHz is still used despite max being set at 1.35. Running great and very smooth otherwise
[Nexus 4 Original Android Development] trismegistos:
Is it normal that i can swipe on the whole screen and wake up the phone?

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] Der_Schubi:
Yes, as long as you do a complete left to right swipe it will wake up, even if you do this on the top.

Gesendet mit Tapatalk 2