yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] OttoDeFe:
Trying 006_r2 and my N7 will boot, I can see the color settings apply then the screen goes to a solid color and locks (as far as I can tell) forcing me to hold down the power button. I tried to roll back to 005 and it had the black screen. I ended up rolling back to 004 to get my unit usable. I installed by downloading from fauxclock, rebooting into TWRP, wiping cache and Dalvik, installing, wiping cache and Dalvik again, then rebooting and letting TWRP fix permissions (it tells me root was lost).

Any ideas?

**edit**

Running stock.
[Nexus 7 (2013) Original Android Development] Tysovwik:
One more thing about sweep to wake. You should add Shortsweep function, as flar2 added. It's much more easier to wake up with Shortsweep enabled.
[Nexus 7 (2013) Original Android Development] PainfulLover:
Ditto, I get lock ups and crashes with 6, had to restore to v5.
[Nexus 7 (2013) Original Android Development] Krowbarr:
No problems here on 6r2 CAF with Pacman.

We were born in a time where if something was broken we would fix it and not just throw it away
[Nexus 7 (2013) Original Android Development] pauldgroot:
Sorry if I'm asking something stupid. I'm using paranoid android. What's the difference between CAF and regular? Is it drivers? Does it matter for performance and stability?
[Nexus 7 (2013) Original Android Development] shreddintyres:
if PA is CM based use CAF

if PA is AOSP use regular

It has to do with the libraries and how CM has rebased to CAF over AOSP
[Nexus 7 (2013) Original Android Development] xfrancis14:
Caf is for cymanogenmod
[Nexus 7 (2013) Original Android Development] PainfulLover:
So was I, unfortunately, or fortunately I don't know how to fix it. I am merely stating a fact that I had trouble with the new version.
[Nexus 7 (2013) Original Android Development] silver04v:
So is pacman cm based, or aosp, can't tell. I see above saying caf on pacman is running good. So I assume I should use caf?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Yes. Pacman is cm based.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] DroidIt!:
Thinking about doing a little experiment. Anybody using an aosp ROM with non-caf kernel? Gonna see if 6r2 works on something like Vanir.
[Nexus 7 (2013) Original Android Development] silver04v:
Is the faux app found on xda? I thought it might be installed with the kernel. This is my first time on a faux kernel.
[Nexus 7 (2013) Original Android Development] PiggySmalls:
Play store

Sent from my Nexus 7 using Xparent Skyblue Tapatalk 2
[Nexus 7 (2013) Original Android Development] OttoDeFe:
It seems my N7 doesn't like the color controls - I cleared the data for the app re-flashed r006_2 and it booted - set the recommended setting from the second post (including color) - screen went solid. Redid the same thing only skipped the color settings and all is fine. Puzzling. The screen seems to freeze on a color about the time the app is granted root.

Just running stock.
[Nexus 7 (2013) Original Android Development] cyberprodigy:
Boot your device into Safe Mode by holding the volume down button while it boots. Uninstall the Faux Kernel Enhancement Pro app. Reboot without safe mode, then go to the Play Store and reinstall Faux Kernel Enhancement Pro. Open it and you should be fine now and be able to tweak as you please.
[Nexus 7 (2013) Original Android Development] Sucalakafufu:
Data reset for FauxClock fixed it for me too. Strange. Wish CM didn't become CAF.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Interesting....non-caf 6r2 works great on Vanir :what:
[Nexus 7 (2013) Original Android Development] lndeed:
Have you tried Slimport? That's the most significant problem when flashing the wrong kernel.
[Nexus 7 (2013) Original Android Development] OttoDeFe:
I did this - everything worked fine until I checked "Set on Boot" on the Screen tab - then black screen on the next reboot.
[Nexus 7 (2013) Original Android Development] DroidIt!:
:confused: I believe Faux said to use non-caf fir non-cm roms. Vanir is an aosp Rom, so think we're supposed to use non-caf.

from my Viped out one x
[Nexus 7 (2013) Original Android Development] lndeed:
Ah, I thought Vanir was CAF. Apologies.
[Nexus 7 (2013) Original Android Development] faux123:
it's there. I just haven't enabled the option in FauxClock to adjust it..

I was trying to push out Gamma control so people can play with it.

you can do "echo 1 > /sys/android_touch/shortsweep" to enable for now using terminal/script app/adb shell
[Nexus 7 (2013) Original Android Development] Tysovwik:
Good to hear about it, but i will wait until you add the function to FauxClock app.

By the way, may be you say something about Adaptive Voltage Scaling http://xdaforums.com/showpost.php?p=45796321&postcount=834 ? Just want to know, is it on or off in your kernel? Can it be fixed?
[Nexus 7 (2013) Original Android Development] sk8trix:
After flashing the kernel before r2 now my nexus is dead and wont power on...not sure how to bring it back on cant power it on even get into recovery...any ideas ??
[Nexus 7 (2013) Original Android Development] PainfulLover:
I had that happen on r1 and 2.

Press and hold power + volume down?!
[Nexus 7 (2013) Original Android Development] ktkr:
R2 is running fine with PA rc2, will try out the screen settings later. Thanks for the great job!
[Nexus 7 (2013) Original Android Development] sk8trix:
Yup tried already and nothing is haooening tried pluggin to charger to see if it would force it to start still nothing.its a 100 battery just doesnt wannanpower on...this is the first time i have an issue like this since my attix 4g days. ...

Ok after messing with it for a while i got ibto recovery and flashe 005 and then went in cleared fauxclock app data downloaded r2 and flashed that. Could the issue havr been related to the color settings on fauxclock?
[Nexus 7 (2013) Original Android Development] faux123:
Just remembered your gif... it's from pineapple express... an amazing movie... hilarious!
[Nexus 7 (2013) Original Android Development] AlderCass:
Had the problem with mainline 006 r2 on PA 3.99 RC2 where about 30 seconds after reboot the screen would go completely black (with the backlight still on), what fixed it for me was going back to the non-r2 006 and resetting the colour settings in FauxClock, after that I could reflash r2 and set the screen settings again without the black screen problem, no need to clear data on the FauxClock app or reinstall it. [MENTION=3332811]faux123[/MENTION] if it'd be of any use I could try reproducing (I can do this easily from a backup I have from before r2) and doing a logcat?
[Nexus 7 (2013) Original Android Development] ktkr:
Met my first blue screen on an Android device, no joking. xD

After a reboot the screen stuck at a blue screen and forcing a reboot with long pressing the power button it booted fine again. Let me know if you need any logs.
[Nexus 7 (2013) Original Android Development] stfudude:
I had device freeze with white screen problem if I try to use my N7 as soon as it finish booting. I found out that if I do a quick turn off-On, this problem wouldn't occur. Could be related to gamma, I guess. I'm using the stock colour (255-255-255)
[Nexus 7 (2013) Original Android Development] OrBy:
Messing with gamma was giving me blue screen freezes as well (running stock JSS15R with the non-caf ES R2 kernel). Also it seems to be randomly rebooting if I mess with anything on the CPU tab (speeds, gov, eco, or snake) where is was stable before. Kinda wish the Faux app had a easy way of rolling back to the stock kernel if users encounter issues. Future feature request? ;)
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hmm, well I didn't play with gama control at all. Just was trying to use the tablet as usual and I got the blue screen. My cpu freqs are well within the reccommended guidelines, anything you need for more info Faux just let me know :)
[Nexus 7 (2013) Original Android Development] ep0ch2:
quick question regarding sweep to wake/double tap to wake... does it drain the battery more when the screen is off?
[Nexus 7 (2013) Original Android Development] darkobas:
i have a question regarding iosched. why is the recommended read buffetr set so high? i think lower gives better bench? what are the benefits?
[Nexus 7 (2013) Original Android Development] AlderCass:
I was wondering the same thing, since I love double tap to wake (the power button just feels so awkward to press for me). When I Googled it I got conflicting results, some kernels claim it does drain battery more, others claim it doesn't drain it in any noticeable way :confused:
[Nexus 7 (2013) Original Android Development] tni.andro:
It does. Deep sleep with everything turned off (Wifi, etc.) and no wakeups consumes around 7mW. S2W consumes an additional 55mW.

The big difference is that normally the touch screen controller is suspended during deep sleep; with S2W, it remains powered on and will wake the CPU when there is input.

The 62mW power consumption with S2W correspond to the battery being drained in 10 days.
[Nexus 7 (2013) Original Android Development] ep0ch2:
Ouch. Thanks for the info. I've disabled it now
[Nexus 7 (2013) Original Android Development] BLueBLaze100:
Hi all, I'm running stock odex xxxxxR, I just want louder speakers so I have to install "enhanced stock" and the app from play store. Is this correct?
[Nexus 7 (2013) Original Android Development] ktkr:
The kernel tweaker won't help with sound settings, you'll need fauxsound to tune the volume. Also you can take a look at viper4android.
[Nexus 7 (2013) Original Android Development] timrock:
what does viper do that faux sound doesnt? is there any reason to have both?
[Nexus 7 (2013) Original Android Development] ktkr:
Viper is kind of software hack and fauxsound is hardware/kernel hack, I have both and the difference is obvious.
[Nexus 7 (2013) Original Android Development] Jake-CT:
Wish my battery could last 10 days. Android OS is killing it in a couple of days...
[Nexus 7 (2013) Original Android Development] ÜBER™:
Not the kernels fault. Blame the apps you have installed. One of em is polling data and killing battery.
[Nexus 7 (2013) Original Android Development] Jake-CT:
I know, wasn't blaming the kernel, which is awesome.
[Nexus 7 (2013) Original Android Development] MarcoPolo78:
Anyone know the color settings to get more of an Amoled look ? I've looked everywhere and haven't had much luck .
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Viper is DSP and faux is gain controls.
[Nexus 7 (2013) Original Android Development] DroidIt!:
You know a lot of people make a big deal out of amoled, but what many people don't know is that LCD is still the king of longevity. There's been extensive studies of the organic light emmitting diodes and at the current level of technology did you know the blue hue within an amoled display will start to fade after about a year to a year and a half. Blue is always the first pigment to go. Sorry for the complete tangent :) but glad the N7 isn't amoled.

from my Viped out one x
[Nexus 7 (2013) Original Android Development] MarcoPolo78:
LoL I like LCD also , just like the deep color of amoled
[Nexus 7 (2013) Original Android Development] shreddintyres:
Generally speaking Amoled displays tend to be over saturated. That said there isn't going to be one set of color settings that will universally make your display look like an Amoled especially since my perception of the colors can be completely different from your own, the only way right now is to look at am Amoled display and fiddle with settings until you get somewhere that is satisfactory to your eyes

FLO'd from my fingertips
[Nexus 7 (2013) Original Android Development] RedDevils88:
May I know how did you disable it?
[Nexus 7 (2013) Original Android Development] ÜBER™:
[MENTION=3332811]faux123[/MENTION] I've noticed colors being reset when opening a game. Is that some kind of battery saving feature like the tegra dimmer? Can that be disabled?
[Nexus 7 (2013) Original Android Development] faux123:
Yeah I was recently made aware of this. It seemed videos or games do something to gamma. I need to investigate this further.
[Nexus 7 (2013) Original Android Development] ÜBER™:
You know... Actually FIFA 14 is the only game I've played recently that I've seen do it. Asphalt 8 and Reaper didn't reset the gammas... :confused:
[Nexus 7 (2013) Original Android Development] codf4ther:
Faux123 I really like your kernel on the Nexus 4 but I'm having a hell of a time with it on my Nexus 7. I run CM nightlies (9/22 currently), and 50% of the time I change something in the FauxClock app (I'm a paid user), the tablet will lock up and become unbootable, even to the point where re-flashing my rom doesn't work. I end up having to find the app apk using the FileManager in TWRP and deleting it to get the device to boot again.I know some of these issues have been mentioned before in the thread, but if there is anything I can do to help debug please let me know. FYI I use the CAF/mainline kernel with my CM build with your recommended settings for performance.
[Nexus 7 (2013) Original Android Development] PiggySmalls:
Asphalt did it for me.

Sent from my SPH-L720 using Xparent BlueTapatalk 2
[Nexus 7 (2013) Original Android Development] ep0ch2:
With faux clock
[Nexus 7 (2013) Original Android Development] RedDevils88:
Just reverted back to 005 Coz I have encountered with unresponsive screen. I think it is due to the s2w as I had the exact same problem while using elementalx kernel before
[Nexus 7 (2013) Original Android Development] lndeed:
Faux, I've been playing around with kernels lately and I have a thought regarding this CAF incompatibility problem.

I've tried everything I can think to do and I can find no more than one bug resulting from flashing a non-CAF kernel on a CAF ROM: it breaks Slimport. If I may suggest, I think the most practical approach would be to try to fix this lone bug using the AOSP library. It would eliminate the need to maintain two kernels and frankly, the CAF kernel has been pretty unstable anyways. EDIT: Crashes only occur in specific circumstances and I believe I've identified the problem.

Thoughts? I would love to help in any way I can.
[Nexus 7 (2013) Original Android Development] juried:
I endorse this approach.
[Nexus 7 (2013) Original Android Development] faux123:
it's not that simple. When CM deviated from AOSP and turned to CAF, they've changed more than just Slimport. You can see the amount of patches from Cy's patch bomb. it's HUGE. I also experienced several boot issues when you only cherry pick a few patches here and there. Matter of fact, I've already reduced the patch bomb to its bare essentials (if you compare CM to my kernel).

Remember the delay release of this kernel? (Approximately a week), during that time I had to test all the subsystems changes introduced by the switch to CAF. The kernel itself is stable, I haven't seen a last_kmsg that point kernel being the cause of instability (ie, kernel panics). Currently I would blame the ROM more than the kernel at this moment for all instability unless specific last_kmsg says otherwise.

Edit: statistics of the patch bomb.

It's OVER 12 pages of commits on my github. Check it here:

Start from here https://github.com/faux123/flo_nexus7/commits/cm_jb_mr2?page=12 back to page 1 https://github.com/faux123/flo_nexus7/commits/cm_jb_mr2
[Nexus 7 (2013) Original Android Development] DroidIt!:
Yeah been using your non-caf ultra on Vanir for about 2 weeks now and runs rock solid. Have come across no problems whatsoever. No reboots, no freezes, no blues screens, zip. So yeah, gotta agree, CM itself has become unstable with the changeover. Maybe the issues will be addressed in time, but for myself definitely sticking with aosp for the forseeable future. 6r2 has been running great as all previous versions.

from my Viped out one x
[Nexus 7 (2013) Original Android Development] lndeed:
Hm. I can try to get a last_kmsg if you'd like, since it certainly seems the CAF kernel is at least partially at fault.

Flashing your CAF kernel on any CAF ROM (I tried on CM, AOKP and Carbon) works perfectly for around 20 minutes until eventually it randomly becomes unresponsive and shuts off. Afterwards, any attempt to even boot will fail after about a second in the same way. The device is effectively soft-bricked until you flash a non-CAF kernel, then things start working normally (except Slimport no longer works, of course).

No doubt CM's changes are extensive. However, as you've probably seen, many people are running your non-CAF kernel on CAF ROMs and haven't experienced any problems. If only Slimport worked, the kernels would be basically transparent. Maybe I've misunderstood, but since running an AOSP kernel on a CAF ROM seemingly only produces one bug, why can't we try to figure out what goes wrong with Slimport and see if it can be addressed with the AOSP library instead of making the drastic switch to CAF? Why is it not that simple?
[Nexus 7 (2013) Original Android Development] tni.andro:
The kernel log is by default turned off when the kernel is suspending - so last_kmsg not pointing to the kernel doesn't necessarily mean much. There definitely is GPU driver/kernel bug with the GPU not suspending properly in some cases (and the watchdog timer triggers a reboot). E.g. check:

https://code.google.com/p/chromium/issues/detail?id=286378
[Nexus 7 (2013) Original Android Development] faux123:
My repo is open. You are more than welcome to compile and find the magical fix and share with everyone.

Matter of fact I encourage all advanced users to fork and modify or fix my bugs and report back to me via pull requests.
[Nexus 7 (2013) Original Android Development] lndeed:
Was just trying to help you. Sorry.
[Nexus 7 (2013) Original Android Development] Krowbarr:
I've been running the CAF mainline r2 kernel on Pacman with zero issues,none,as others surely have also. Thank you for your work faux.

Owner/Operator Nexus 7 2013/Pacman Rom/faux CAF mainline r2 kernel

We were born in a time where if something was broken we would fix it and not just throw it away
[Nexus 7 (2013) Original Android Development] lndeed:
If anyone wants it, here's a last_kmsg hopefully detailing the Slimport issue. If not, that's fine too.

EDIT: To be clear, this was with the non-CAF kernel on a CAF ROM.
[Nexus 7 (2013) Original Android Development] faux123:
It's not my kernel.
[Nexus 7 (2013) Original Android Development] MrPhilo:
Bump for the Adaptive Voltage Scaling, i'm abit curious about it too that we aren't undervolting at all
[Nexus 7 (2013) Original Android Development] stab244:
Hey Faux,

I was looking at the other kernels and some seem to have more than 4 GPU frequency steps. I thought that was impossible or is that limitation only present in the N4? Thanks.
[Nexus 7 (2013) Original Android Development] faux123:
4 slots is max supported by the firmware. What other kernels have done, they swap out the highest slot on-the-fly with even higher frequencies, thus overcoming the 4 slot issue. My GPU overclocking is based on static table therefore only 4 steps.

I won't go higher than what I got already. [MENTION=1144067]hamdir[/MENTION] (this guy is very good at gaming and 3D benchmarks, he did it with rigor and under very controlled usage scenarios) did an exhaustive 3D benchmark comparison with varying degree of GPU OC (up to 600 MHz) and found severe diminishing returns beyond 450 MHz (ie, the benefit is so small, but the price of battery and heat so great). Based on his finds, 450/487 will be the highest for me on Adreno 320 chipsets...

The next breakthrough will be the newer Snapdragon 800 and Adreno 330, an actual hardware upgrade...
[Nexus 7 (2013) Original Android Development] stab244:
Ah. I was hoping it would be more actual steps so simple would have more frequencies to jump around.

Can't wait for N5 and use your kernel their too!
[Nexus 7 (2013) Original Android Development] mjwhirly:
Color control seems to have disappeared from faux kernel control app, have you taken it away?

Edit: after reboot the option seems to have reappeared. ....weird
[Nexus 7 (2013) Original Android Development] ÜBER™:
Not weird... Normal ;)
[Nexus 7 (2013) Original Android Development] drms12:
There is a major problem with the latest 006mcaf, probably with all of the latest versions.

Sweep2wake is on by default, turning it off only makes it won't turn screen on, but touch screen isn't turned off as it should.

The problem? Standby battery drain is exactly 1.6% per hour of deep sleep, after few days of test.
[Nexus 7 (2013) Original Android Development] thedan55:
I'm running the latest kernel on pure stock 006m and I'm getting some touchscreen issues. Anyone else?

Edit. Looks like it was the screen protector. My mistake
[Nexus 7 (2013) Original Android Development] auggie246:
With both s2w dt2w off, my screen won't turn on. big problem.
[Nexus 7 (2013) Original Android Development] cyberprodigy:
It's not even possible for me to turn off S2W and DT2W. I turn them off in Fauxclock, close the app, open it back up and they're back on. Changing "Set on boot" does nothing. It's not just the app either, testing the screen after turning them off shows that they're not actually turned off as well.

I'm running CleanROM 1.7 and 006_r2 (non-CAF version).
[Nexus 7 (2013) Original Android Development] faux123:
Sounds like a permission issue
[Nexus 7 (2013) Original Android Development] Krowbarr:
Just noticed that it's the same for me. I'm using the CAF.

Owner/Operator Samsung E4GT running Pacman Rom w/Blasphemy v6 kernel.

We were born in a time where if something was broken we would fix it and not just throw it away
[Nexus 7 (2013) Original Android Development] Crwolv:
I don't think and it certainly does not look like with your message your blaming this awesome kernel for your battery woes so send alogcat to faux and I'm sure he would help you. Not only is he an awesome dev but he is a great guy and always answers with a great attitude. I'm a lot less busy than him so gtalk me and if my tiny bit of knowledge can help I would be happy to also. motownstation@gmail.com is my hangouts id.

---------- Post added at 06:23 PM ---------- Previous post was at 06:13 PM ----------

Yup ,as usual your right. You can use trickster to control permissions also, just a tidbit I thought I'd tell for those who don't know
[Nexus 7 (2013) Original Android Development] sk8trix:
I got a bootloop. Is there a file I can flash while on the boot loader to restore the settings of the faxclock app or maybe someway to flash the stock kernel from the bootloader?
[Nexus 7 (2013) Original Android Development] stab244:
If you can get to recovery, you can just reflash your ROM. Otherwise, if you're on stock, find the stock image for the tablet and only flash the boot.img.
[Nexus 7 (2013) Original Android Development] sk8trix:
I know that I can fix it that way,the thing is tho I'm not aure if that will erase all my stuff auch as my apps and media in the internal memory.I could care less for the apps and settinfs but I dont want to have to download all my muaic movies etc.You think this wipe the whole thing?
[Nexus 7 (2013) Original Android Development] stab244:
It shouldn't as long as you only flash the boot.img I think. Refreshing your ROM won't touch anything.
[Nexus 7 (2013) Original Android Development] sk8trix:
Im on the stock image only was rooted and kernel.I guess ill have to start up from scratch.
[Nexus 7 (2013) Original Android Development] cyberprodigy:
How should I fix this?
[Nexus 7 (2013) Original Android Development] sk8trix:
Does this kernel the non caf version run on CArbo ROM? Has anyone tried it? Thanks in advance
[Nexus 7 (2013) Original Android Development] roustabout:
Thanks so much for this - being able to adjust the color balance is fantastic, it eliminates one of the few things that bugged me about this device.
[Nexus 7 (2013) Original Android Development] lndeed:
CAF would be the correct choice.
[Nexus 7 (2013) Original Android Development] sk8trix:
I'm using the standard non CAF kernel on Carbon ROM, it's an AOSP ROM isnt it supposed to use the regular kernel? I'm having no issues but should I flash the CAF version then? will the device get stuck in a bootloop or something?