yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] adrain:
Thank you so much.... :) I will stay in Ultra then :) I really do have a good battery life... only thing is I got low score in antutu benchmark.. but my nexus runs very well . it dosnt matter about the antutu score... (19934 score)
[Nexus 7 (2013) Original Android Development] :
When using enhanced stock or mainline, do I need to tweak every setting with trickster or is are they optimal out of the box?
[Nexus 7 (2013) Original Android Development] jhuff83:
Just got a ton of force closes while using the Internet. Could this be kernel related.
[Nexus 7 (2013) Original Android Development] kecinzer:
Hi [MENTION=3332811]faux123[/MENTION]

I'm trying to compile faux kernel and I can't get to finish it.

Can you please help me little bit.

Defconfig is here - https://dl.dropboxusercontent.com/u/3406794/faux_keci_defconfig

Error:

drivers/media/platform/msm/camera_v1/gemini/msm_gemini_dev.c:27:17: fatal error: msm.h: No such file or directory
#include "msm.h"
^
compilation terminated.
[Nexus 7 (2013) Original Android Development] DroidIt!:
You'll need to tweak. Trickster only hits some of the options as well, to take full advantage of the faux series, you'll want to grab faux clock. :good:

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

In my experience, this is rom related. You would have to ask a rom dev for the particualrs, but I know DJ (CMKanged rom) has talked about it in his thread before. :good:
[Nexus 7 (2013) Original Android Development] Crwolv:
Actually you need both apk,s to be able to tweak all you can. Trickster does sound boost very well but I purchased faux sound to support dev.

---------- Post added at 06:38 AM ---------- Previous post was at 06:32 AM ----------

Indeed you are absolutely right it is happening to me on asylum rom.
[Nexus 7 (2013) Original Android Development] DroidIt!:
You are correct :) I was just referring to the CPU, etc. tweaks. :thumbup:

from my Viped out one x
[Nexus 7 (2013) Original Android Development] stfudude:
Faux, can you include one more gpu clock speed: stock (400)?

I only use 450 Mhz speed in certain demanding games, and for other apps I chose 320 Mhz. But the UI is not smooth with that speed... Could you maybe include the stock clock speed? Pretty please. :)
[Nexus 7 (2013) Original Android Development] xfrancis14:
Ever since the faux123 app update my tablets been hot doing anything. And it seems as if all cores are almost always on when I check in the app
[Nexus 7 (2013) Original Android Development] DroidIt!:
That's strange. I just checked mine and all is normal and the per app settings are awesome. Maybe try reflashing the kernel :confused:
[Nexus 7 (2013) Original Android Development] Krowbarr:
That's strange. Not doing that on mine. Faux clock not even showing up in battery usage.

Sent From My Nexus 7 2013/Pacman Rom/faux mainline kernel 006 r2!
[Nexus 7 (2013) Original Android Development] xfrancis14:
I'll try reflashing..

---------- Post added at 05:43 PM ---------- Previous post was at 05:38 PM ----------

Reboot seemed to have fix it
[Nexus 7 (2013) Original Android Development] jhuff83:
I'm on stock rom and I got those force closes. I'm also seeing where sometimes my tablet will turn off by itself when running this kernel. Any idea why?
[Nexus 7 (2013) Original Android Development] DroidIt!:
What's your oc value set at? Might be a bit too high or your low end a little too low.
[Nexus 7 (2013) Original Android Development] jhuff83:
1.5/384 with intellidemand
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hmmm, ok seems like a reasonable spread. Which version of the kernel did you flash? CAF or AOSP? If CAF probably want to flash AOSP. Being a stock ROM (one of scroslers?) there shouldn't be any compatability issues, but try flashing the ROM without faux, run it and see if you get the same issues or not. If you don't, then there's probably a compatability issue.
[Nexus 7 (2013) Original Android Development] konradsa:
I have tried to find some good answers, but was not able to, maybe faux can explain: Does sleep2wake or doubletap2wake have a significant battery impact? Some people say no, it's similar to hardware buttons being pushed due to the use of interrupts. Others say yes, since it prevents the tablet from going to deep sleep and touch screen needs to be kept active.

Also, is there any difference between sleep2wake and doubletap2wake, where one would be better than the other with respect to battery?
[Nexus 7 (2013) Original Android Development] jhuff83:
006 enhanced stock. I'm not even running scroslers. I just rooted and left bone stock on here.
[Nexus 7 (2013) Original Android Development] DroidIt!:
I'm not a kernel dev or anything, kind of have limited knowledge on the particulars, but don't think you can run a custom kernel on purs stock rom. I believe init.d support needs to be in place for a custom kernel to work, and with stock in place I don't think that's the case. Also, you need to install busybox for the faux kernels to work correctly which you can't do on a stock rom either. If you want to stick to stock, I would go with one of scrosler's roms: they are stock with some cleaning and optimizations and have everything in place to be able to run custom kernels.

---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------

I haven't ever noticed any real difference. How many services you have running in the background, how often your accounts refresh, screen brightness, etc. all have a much bigger impact in my experience on battery than dt2w or s2w do.
[Nexus 7 (2013) Original Android Development] jhuff83:
I have busybox on the stock rom right now. I used the toolkit to root also. Was not having issues up until a couple days ago.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Did you flash a Rom in recovery?

from my Viped out OneX
[Nexus 7 (2013) Original Android Development] jhuff83:
Yup, TWRP
[Nexus 7 (2013) Original Android Development] DroidIt!:
Which Rom?

from my Viped out OneX
[Nexus 7 (2013) Original Android Development] jhuff83:
As soon as I got tablet I used the toolkit to root and it gave me the option to flash a custom recovery. Never flashed a rom. Sonoma rooted and have busy box without using any other rom.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well, I would back up your current Rom, download one of scrosler's and try that with a faux kernel. You have a 95% better chance of a custom kernel working then. :) And if you don't like it you can revert back. I've tried scrosler's Rom though with faux, it is a supercharged stock experience. :thumbup:

from my Viped out OneX
[Nexus 7 (2013) Original Android Development] jhuff83:
Yea I used his back in my HTC days.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Thanks for another update on your app there faux, everything in it works great. Only one thing I noticed is that if you tell it to back up app settings and then go to do a restore later, it just has a brain fart and doesn't restore the settings. Not too big of a deal, it really doesn't take much effort to set up, just thought I'd let us know. :)

from my Viped out OneX
[Nexus 7 (2013) Original Android Development] banny7000:
Which kernel for pa?
[Nexus 7 (2013) Original Android Development] poondog:
Both AOSP (non-CAF)
[Nexus 7 (2013) Original Android Development] xfrancis14:
I've been using the non CAF for PA and haven't ran into any issues, there may be a random reboot sometimes but that's it, should I bother flashing the CAF version?
[Nexus 7 (2013) Original Android Development] poondog:
Ooops see my edit haha, realized I made a mistake :P

PA is not CAF idk why I thought it was

CAF one should cause problems
[Nexus 7 (2013) Original Android Development] konradsa:
I am back to stock kernel now. I like the features of this kernel, but for some reason I experience occasional lag with this kernel that I don't have with stock. Anybody else having the same experience?
[Nexus 7 (2013) Original Android Development] jhericurls:
No issues here. Make sure you use MP-Decision. Get amazing battery life, over 1 screen time and still on 95%.
[Nexus 7 (2013) Original Android Development] NovaSlim:
Really? I thought Faux said MP-Decision should be turned off and IntelliPlug should be used instead if you want better battery life.

Faux on MP-Decision vs IntelliPlug

On post# 2
[Nexus 7 (2013) Original Android Development] DroidIt!:
I've never had any problem with intelliplug....actually never seen any lag at all. What does make the difference though is the Rom you're using. Some have varying degrees of compatibitliy with faux kernels. I will say though that usually I pick whatever Rom I like and look for a good kernel afterwards. But with the faux kernel for the first time ever I actually switched roms so I could keep using the faux kernel. Sooo, your personal choice, try a different Rom with faux or keep trying different variations of the faux kernels with different settings and see what works fir you. Yeah, never had any lag before though. :thumbup:

from my Viped out OneX
[Nexus 7 (2013) Original Android Development] NovaSlim:
I personally don't have any lags, [MENTION=5138965]konradsa[/MENTION] is the one talking about lags with faux.

I was responding to [MENTION=1950715]jhericurls[/MENTION] about MP-Decision vs Intelliplug in term about battery life, the discussion was not about lags.
[Nexus 7 (2013) Original Android Development] jhericurls:
Well the proof is in the pudding, after 6 hours I'm still on 88%. I was on IntelliPlug yesterday and my battery was much worst.

My settings
[Nexus 7 (2013) Original Android Development] ÜBER™:
Your readahead is WAY too high. Turn that down... At most it should be 1024.
[Nexus 7 (2013) Original Android Development] NovaSlim:
Opposite results from me, MP Decision off and IntelliPlug on give better battery life. I hope faux would come in on this issue and explain whether he still recommend Intelliplug over MP Decision, but based on what he had said & what he stated on post #2 it seems he advocates having MPDecision off.

Both cases are MX Player 720p video playback with H/W+ accleration, set 16:10 ratio, maximum brightness

With MP Decision

With IntelliPlug

Settings
[Nexus 7 (2013) Original Android Development] ÜBER™:
Was eco mode on for both? And why eco mode, no one, at least I would hope not, uses eco mode all the time. Just a waste of cores if you're running only dual cores.

Intelliplug might be better with playback, but that's only because MPdecision defaults to a min frequency of 1026 with any CPU threshold. So that whole time I bet you it was at 1026 which means intelliplug was not really any better since its min is whatever you set it.

Playback is not very accurate to begin with, anandtechs use of browser refreshing intervals seems more appropriate. It taxes both the CPU/GPU more accurately than just playing back which isn't very demanding.
[Nexus 7 (2013) Original Android Development] NovaSlim:
It is used for both. I use playback because video playback is my primary tablet usage. Eco mode were used because faux said it should used for better battery life on post#2.

Mind you Anandtech tests video playback battery lifeas well as internet broswing when they review tablets, despite your claim that it is "not very accurate" .
[Nexus 7 (2013) Original Android Development] ÜBER™:
Its not a very accurate test.... to determine typical usage. Its accurate, for well... only for video playback, in which case if that's all you do and I doubt that's many of us, intelliplug is good for that. And only because as I said MPdecision ups the min frequency to 1026. If you want to retest and level the playing field change the min for both to 1026 and see which comes out on top.
[Nexus 7 (2013) Original Android Development] NovaSlim:
If MPDecision is indeed superior, I would love to see better organized test that prove it beyond a doubt. I am just stating what my usage shows and also what Faux himself said about MPDecision vs IntelliPlug.

What is "typical" usage differs from person to person, and no forum poster have authority to claim what is relevant for "many of us". What is clear is that Browsing & Video Playback are both tested by Anandtech in their reviews, showing both are relevant tablet usage scenarios worth testing.
[Nexus 7 (2013) Original Android Development] DroidIt!:
It's pretty simple really. If you get better performance/battery with mpdecision, use that...if you don't use intellidemand. :)
[Nexus 7 (2013) Original Android Development] NovaSlim:
Intellidemand isn't good with mpdecision? Can you explain in more detail?

Can you explain in more detail why though?
[Nexus 7 (2013) Original Android Development] :
Droid probably meant Intelliplug.

Intellidemand is a governor.
[Nexus 7 (2013) Original Android Development] jhuff83:
Using the enhanced stock on clean rom 1.7. My tablet randomly shuts down after closing case sometimes. This also happened with stock rom and this kernel. Anyone know why?
[Nexus 7 (2013) Original Android Development] DroidIt!:
That's what I meant....sorry mixed up my words :angel:

---------- Post added at 11:28 AM ---------- Previous post was at 11:21 AM ----------

I have a case with magnets on it to put tab to sleep when closed and wake when opened. Think this is really a rom dependent thing and it's really kind of hit or miss. I have always used the faux ultra since he put out his first kernel for the N7 and the kernel itself seems to make no difference on how this particular feature performs. I've tried somewhere in the neighborhood of 70% of the roms and sometimes it works properly and sometimes it doesn't. I would say that you might want to ask in the rom thread and see what other's experiences are there. As far as I know (at least I haven't seen it mentioned) none of the faux kernels touch the smart wake/sleep feature. :good:
[Nexus 7 (2013) Original Android Development] malukiz:
Hey, Someone have try caf with CM, is it stable ? Last time, I can't boot (logo google) and the only thing that save me was factory reset :(
[Nexus 7 (2013) Original Android Development] DroidIt!:
Depends on the Rom you're trying to use. What Rom are you trying with?

from my Viped out OneX
[Nexus 7 (2013) Original Android Development] malukiz:
I use the last CM nightly 10-22-2013
[Nexus 7 (2013) Original Android Development] waz675:
Sweet, Brought a N7 flo today and see faux123 kernel. Always a great thing to see for one's device!
[Nexus 7 (2013) Original Android Development] faux123:
Kernel 007 is official!
[Nexus 7 (2013) Original Android Development] BDR456:
Downloaded what i thought was 007u and when i flashed it says 007uCAF under kernel version in settings. Is it supposed to be like that on CleanROM?
[Nexus 7 (2013) Original Android Development] JaceAlvejetti:
Hey faux, does this (007) include the multirom patch?
[Nexus 7 (2013) Original Android Development] faux123:
Ugh... ignore all 007 releases :(

I screwed up majorly... been away from kernel building for a while and messed up everything :(

_r2 coming up...
[Nexus 7 (2013) Original Android Development] Cuzz1369:
We've waited long enough!!!!!

(Sarcasm)
[Nexus 7 (2013) Original Android Development] sk8trix:
I get back my nexus 7 friday from repairs so glad to know that a new kernel is coming just in time to pick back up. XD
[Nexus 7 (2013) Original Android Development] BDR456:
All is well again, much appreciated. ;)
[Nexus 7 (2013) Original Android Development] jhuff83:
So 007 is good to go now?
[Nexus 7 (2013) Original Android Development] BDR456:
Downloaded 007u-r2 and all looks right and is running as this kernel always does! :thumbup::thumbup:
[Nexus 7 (2013) Original Android Development] sonofevil77:
My tab is not booting and I can't access twrp after flashing 007 mainline. Uh oh.

Sent from my VZW GALAXY note 2
[Nexus 7 (2013) Original Android Development] DJLamontagneIII:
007 r2 mainline running great for me
[Nexus 7 (2013) Original Android Development] sonofevil77:
Dj it's odd because the same thing happened on 006 after a long time of running it. I am on your CM10.2 9-18 Kang build. Maybe I got a bad download but Idk because it's happening with 006 now also.

Just tried es after I restored backup and still the same except the tablet powers off. I am correct in flashing the caf version on your rom right?

Sent from my VZW GALAXY note 2
[Nexus 7 (2013) Original Android Development] poondog:
you make sure to flash CAF?
[Nexus 7 (2013) Original Android Development] sonofevil77:
Yes, OK good, I just edited my post to make sure I was supposed to use caf.

Sent from my VZW GALAXY note 2

---------- Post added at 09:23 PM ---------- Previous post was at 09:16 PM ----------

I just realized that I am on TWRP 2.6.0.0 would that do something? Why would that revert lol I was on 2.6.3.0

Sent from my VZW GALAXY note 2
[Nexus 7 (2013) Original Android Development] DJLamontagneIII:
Yea you need faux's CAF version for that build there's also a 10/4 rom build i posted that has all the CAF stuff removed to make it compatible with faux's regular AOSP builds.
[Nexus 7 (2013) Original Android Development] sonofevil77:
Damn, I'm using the caf kernel. Idk what happened. Everything was good and then out of the blue it's not working anymore. I am trying to remember if I installed a new app or something just before it happened the first time.

Sent from my VZW GALAXY note 2
[Nexus 7 (2013) Original Android Development] konradsa:
I installed 007es-r2 and now the tablet gets stuck on boot while showing the boot animation. Any way to get back again? I even tried sideloading a 006 kernel, but still won't work. Can only access ClockworkMod recovery. Help please.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Having an issue with the latest faux clock and 007es-r2 kernel. Whenever I first boot the tablet its perfectly fine. Colors apply and superuser is granted etc. Then I turn off the screen, come back to it and turn it back on, it shows for a quick second then goes to a blank grey color. Can't turn off the screen and am forced to hold the power button to reboot. Stops as soon as I uninstall faux clock. However I noticed, when I uninstalled and reinstalled it stopped, and showed faux clock being granted SU permissions every other time I turned the screen on. But I rebooted, and it started all over -.-.
[Nexus 7 (2013) Original Android Development] SuperSync:
+1 same exact issue on 006m_r2 running SlimBean with FauxClock which updated itself today. Tried to restore FauxClock from a 10/20 backup but problem still persists.
[Nexus 7 (2013) Original Android Development] stab244:
I think faux updated the CAF base used for the CAF kernel. I couldn't boot on the 9/27 nightly of CM but flashing the 19th worked.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Glad I'm not the only one. Guess its an issue with faux clock and colors, or Superuser with Fauxclock.
[Nexus 7 (2013) Original Android Development] stab244:
Yup same here. Was just about to post that. I'm on the beta fauxclock though. Nit sure about you guys.

Never mind it's not the beta version.

Odd also happening on version 1.3.2 of the app and 006u.
[Nexus 7 (2013) Original Android Development] faux123:
Emergency FauxClock fix coming soon :p
[Nexus 7 (2013) Original Android Development] ÜBER™:
Woot :). Can finally turn my tablet back on.
[Nexus 7 (2013) Original Android Development] Krowbarr:
Luckily I made a nandroid just before updating Fauxclock. Reverted back until fix:p

Sent From My Nexus 7 2013/Pacman Rom/faux mainline kernel 006 r2!
[Nexus 7 (2013) Original Android Development] FaeLLe:
Really looking forward to this and I just bought your application so I can use r_007!
[Nexus 7 (2013) Original Android Development] mohammed510:
The screen goes blue sometimes,

Had to force reboot twice, anyone has the same?

Edit: looks like a known issue.. Sorry
[Nexus 7 (2013) Original Android Development] Krowbarr:
Fauxclock update is up on Google Play, all seems well now. Thanks faux:D

Sent From My Nexus 7 2013/Pacman Rom/faux mainline kernel 007 r2!
[Nexus 7 (2013) Original Android Development] kecinzer:
New version is out but still with no czech transation :)
[Nexus 7 (2013) Original Android Development] ÜBER™:
+1 Tablet is working great now :)

Side note:

[MENTION=3332811]faux123[/MENTION] have you considering taking requests for Icon design for Faux Clock? I know i sent you one already... but just wondering if you even want one.
[Nexus 7 (2013) Original Android Development] konradsa:
Learned my lesson the hard way this time that doing a Nandroid backup is advisable before installing a custom kernel. 007r2 kernel made my tablet unbootable, and no matter what I tried (even side loading different kernel zip didn't work), couldn't get it back to life. I ended up factory restoring my Nexus 7, since the last backup I had was quite old and I wanted to rather start fresh at that point.

Not complaining about the faux kernel here, I understand the risks that are involved when doing such "hacking" to your device. Just reporting here so it can serve as a lesson to others.
[Nexus 7 (2013) Original Android Development] PiggySmalls:
A few of us had problems with it, the new FauxClock fixed it for me. Running AOSP 007_r2u
[Nexus 7 (2013) Original Android Development] SuperSync:
Still having the frozen grey/blue screen after about a 1/2 second of the lock screen appearing. Requires a press and hold to cold boot to get the tablet back.

This is on FauxClock 1.3.7 and 007m_r2 on SlimBean with SuperSU. I can rollback to FauxClock 1.2.8 and it works flawlessly. I guess I'll have to turn off Play Store auto updates until I can sort it out...
[Nexus 7 (2013) Original Android Development] faux123:
For those of you experiencing issues with Gamma control join my Beta group to help me fix this...

https://plus.google.com/u/0/communities/115233212982351984859

Currently I have a beta 138 build out there. This should fix it, but I need users verifying this for me since I can only test on my own machine with sample of 1 :p
[Nexus 7 (2013) Original Android Development] vagelis:
Good to know that I'm not the only one experiencing this.

Do we have any way of reverting to an older version of FauxClock? My titanium backup is 1.3.6 and still had the issue.

Thank you in advance.
[Nexus 7 (2013) Original Android Development] DJLamontagneIII:
Been using Beta build 138 of faux clock and haven't had the issue anymore :)
[Nexus 7 (2013) Original Android Development] sonofevil77:
I still can't get my tablet to boot after flashing this kernel on any rom. I'd wtf. I never had a problem like this before. Clean installs and all. Download the kernel from fauxclock still nothing.

Sent from my VZW GALAXY note 2
[Nexus 7 (2013) Original Android Development] luisvilla1993:
Same thing happened to me. It wouldn't boot up. Luckily, i had everything backed up and was able to restore.
[Nexus 7 (2013) Original Android Development] sonofevil77:
Yeah me too thank god,I finally got it to work on AICP ROM.

2013 N7 Kang Banged!
[Nexus 7 (2013) Original Android Development] DroidIt!:
Well, booted for me, was a little funky though. Installed the latest ultra on slimbean weekly 1293. Went to recovery, wiped cache and dalvic, flashed faux, wiped cache and dalvic again and rebooted. It did the standard android is upgrading thing, got to the end, hung for a second, auto rebooted to boot animation and then booted up. All appears to be working ok so far though.

from my Viped out OneX

---------- Post added at 02:35 PM ---------- Previous post was at 02:25 PM ----------

Yeah, just rebooted to see what would happen. Everything working good and faux clock settings stuck. Was thinking about doing an experiment and I can do it later if nobody else can (at work right now) but was just wondering if for some reason you need to have the latest faux clock installed BEFORE flashing his latest kernel. Just a hunch, but if somebody with a non-booting device wouldn't mind doing it that would be cool. Like I said just a hunch, it's booting for some and not for others. I know one person said it wouldn't boot off a full wipe and clean install, so just thinking if the latest faux clock is installed first there might be a goofy issue there that might make it work.

from my Viped out OneX